I am in an enterprise environment using Windows XP. There's a long delay between after I login and when the desktop shows up, usually around 5 minutes of waiting. I suspect a significant part of the delay is the computer trying to connect to the 10 or so network drives, of which I only need 2. I've disconnected the other 8 unnecessary network drives several times, but whenever the computer reboots, it puts those drives back. Perhaps the company has deployed a login script that automatically maps these drives - I'm not sure. Nevertheless, I would like to know if there is a good way to PREVENT the unwanted network drives from being remapped?
migrated from stackoverflow.com Oct 28 '11 at 22:20
closed as not constructive by Ward, Shane Madden, Miles Erickson, Iain♦, MDMarra Nov 13 '11 at 17:38
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
In a proper environment, mapping drives should not take much time at all. In my experience, most logon delays are caused by the system waiting for your user profile to download. The profile includes your settings/preferences as well as anything you have stored on your Desktop, in your "My Pictures", "My Documents", etc. If you have a mapped drive that is supposed to contain user files, store as much as you can there and as little as you can actually in your profile.
Other delays can be caused by network timeouts (possibly from mounts that no longer exist) and a large number of applications starting at logon.
Remove yourself from the user permission on these drives.
Assuming you don't have the credentials to do this yourself, ask someone from IT. Without permission, it will just skip and move on.