We have deployed Windows 2000 Professional, with each client having a home drive on the network. Recently, we've discovered that clients whose home drive is across a slow network link suffer greatly, especially when doing simple things like starting up Explorer, IE, etc. After running network traces, we can see why: the working directory is set to the network drive (M:), so every DLL or file that, say, Explorer tries to load it will first look to that network drive before finding it in C:\WINNT\SYSTEM32. Explorer does this about 50 times, for DLLs, sound files, etc. When we're talking about a 56Kb microwave link, the delay this causes is in the 30-60 second range.
I've been playing with various ways to resolve this "issue", and have found one way that seems reasonable: If I defined HOMEDRIVE in the user's profile to point to C: instead of our network drive M:, the delays go away. Does anyone see any problem with doing this, or do you have any better suggestions? -Michael ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
