Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question

migrated from Oct 28 '11 at 22:20

This question came from our site for professional and enthusiast programmers.

closed as not constructive by Ward, Shane Madden, Skyhawk, 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 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, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

It sounds to me like you're not part of the sysadmin team. You should contact contact your help desk, raise a ticket and get it solved that way. – Iain Oct 29 '11 at 8:03

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.

share|improve this answer

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.

share|improve this answer
if my permission is removed from these drives, can I still access them by going to their full paths ("\\...")? I still want to be able to access them, just not automatically remapped at login time. – PJx Oct 28 '11 at 20:51
If your permission is removed you will NOT be able to access them by their full paths. – MaskedPlant Oct 29 '11 at 1:56

You can try net use /persistent:no to try and prevent re-mapping remembered maps, but the maps may well be due to a login script.

As others have pointed out, the delay is probably not due to the drive mappings though.

share|improve this answer