<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Ray Garza wrote: <blockquote cite="mid200703071255.39905.ray@mission.lib.tx.us" type="cite"> <pre wrap="">On Wednesday 07 March 2007 12:29, Terrell Prudé Jr. wrote: </pre> <blockquote type="cite"> <pre wrap="">You can use share permissions or NTFS permissions; either will do the trick. They'll still be able to see that the shares exist, but they won't be able to actually access them. It's much like when you set 700 permission on the /root directory in GNU/Linux or *BSD. Regular users can see that /root exists, but they can't do anything with it. </pre> </blockquote> <pre wrap="">You mean change the Share permissions on each Staff PC? I could do that but I was hoping to to do it at a single point (server) rather than go around to each Staff PC and make the changes. I'll give your suggestion more thought. Thanks for the input. Ray </pre> </blockquote> I'm afraid so. Windows share security is done per share. Remember that each box has its own database of share security that needs tweaking. Another way to manage permissions, which might make this sort of thing easier, it is to have all the staff members' files on a central file server. At work, we use a "H" drive ("H" is for "home"). Then, you can manage file permissions centrally w/o having to touch the client boxes. Works out rather well for us. You could use a Samba server for this very easily. --TP </body> </html>