Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
no save to local computer c:\ drive
Name: t-bone Date: December 29, 2006 at 18:14:24 Pacific OS: win 2000 pro CPU/Ram: 600/256 Product: asus
Comment:
Hi, I have a win 2000 domain, 1 2000 server and a few client computers. All users have a roaming profile and home dir on the server. I want to prevent users from being able to save to the c:\ drive of the local computer they are working on. I was logged onto the domain from a client computer and when i saved a document i was able to save it to the local computers c:\ drive in the my documents folder, i do not want users to be able to do this, users should only be able to save to there home dir on the server. How can i configure this setup? Can it be done centrally from the server? I don't want to go from client to client computer to configure options. Thanks anyone
Name: wanderer Date: December 29, 2006 at 22:19:45 Pacific
Reply:
You would do this via group policy though I would suggest you consider terminal services instead. Be careful of too restrictive of a GPO or you could lock yourself out of your pcs.
Knowing the correct answer and giving a correct answer, are two different things
0
Response Number 2
Name: t-bone Date: December 30, 2006 at 21:05:45 Pacific
Reply:
when i make the GPO, when i edit it, would i edit it under computer or user configuration?
Summary: The following is a checklist for ME but it works for 98SE as well. 37 steps to fixing peer-to-peer network problems in Windows Millennium by Carey Holzman 1) The first rule is to follow each of these...
Summary: I would like to have my full C: shared but accessable via login/password only. I would also like to be able share specific subfolders that do NOT require specific passwords access. All computers are ...
Summary: I've fixed the problem now. It had "improved" my PC's security by preventing the release of the PC's name, and by preventing NETBios access to the PC. Changing four registry values fixed the problem -...
0 
