|
Home > Archive > 70-217 > September 2002 > users are not allowed to save any file on local drive
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
users are not allowed to save any file on local drive
|
|
|
| Hello,
I need to setup something, which will not allowed users to save any files on their local drive. How can I do it?
There is one Windows domain in the network.
Server: Windows 2000 server
Wks: Windows 2000 pro & Windows XP
Another question is: when user login to domain, it takes 5 mins to login. Network connection seems fine, any way to make it faster?
Thank you all! | |
| jeff_j_black 2002-09-13, 4:07 pm |
| Check out the post a few ones back called XP logons slow...
It serves as a good reminder to make sure the basics of your network are square, thanks Myo...
Also, things that could slow logons, roaming profiles, desktop and start menu redirections, too many group policies applied, GC not available or taxed.
Make sure in a homogenous environment to turn off NETBIOS over TCP/IP as the clients will register in DNS and WINS will not be neccessary.
Not allowing clients write access the local drive may cause problems with applications that might try to write configuration data under their user context. You could use group policy to redirect 'My Documents' to a central share on the server? | |
| ruscorp 2002-09-13, 5:37 pm |
| quote:
Originally posted by wen
Hello,
I need to setup something, which will not allowed users to save any files on their local drive. How can I do it?
There is one Windows domain in the network.
Server: Windows 2000 server
Wks: Windows 2000 pro & Windows XP
Another question is: when user login to domain, it takes 5 mins to login. Network connection seems fine, any way to make it faster?
Thank you all!
That's a mistake waiting to happen. I agree with jeff_j_black, take his advise. | |
| CyberDude 2002-09-15, 12:34 pm |
| Sorry JB, but I have to disagree with you on the point of disabling netbios over tcp/ip. This is ok if all programs, utilities and drivers are written for winsocks, if not then the will be going by the old conventions and using the netbios interface. This is especially right if you have a SMS server.  | |
| jeff_j_black 2002-09-15, 6:57 pm |
| He's got no downlevel clients, so I thought it might at least be something that could be eliminated during T/S of slow network and client start-up. There's no mention of his DNS or WINS services deployment, so I'm guessing that the slow logon times could be from network services design. | |
| CyberDude 2002-09-16, 4:07 am |
| Jeff what you have to remember is that it is not only network services that use api's, but actual programs aswell. | |
| jeff_j_black 2002-09-16, 10:00 am |
| Yeah, I know, anything the uses network browser or NETBIOS names for functionality, etc. Like restrict use to certain workstations only works with NETBIOS. | |
| CyberDude 2002-09-16, 12:33 pm |
| Jawohl.... |
|
|
|
|