Vista mapped drives disappear

In this video we demonstrate all of the steps to rename a Windows Active Directory Domain using the rendom command. Tags: drive automatically closed drive maps GPO mapped drives mapped drives disappear. Questions or Comments? Cancel reply. I have been having an issue with one user on my network, when they log off and shut down their system they lose one of the 9 mapped drives.

It is always the I: drive. The rest of the drives remain mapped, and simply remapping the I: drive works. The weird thing is that sometimes the drive is there at login, and sometimes not. The reconnect at login is checked, when running the Net Use command it says "new connections will be remembered. I have made sure that there are no devices attached via USB, such as Phones or external drives. I have read through several forum posts about similar issues both here and other sites, but none of those solutions have resolved my issue.

I have made registry changes, changed the drive letter etc. Considering that this is a problem with only one user, I would assume the issue has to reside on his PC. I've had similar issues with Windows 8 and 8. Assuming from your entry that you aren't on a domain? The script I've used is slightly different and so far has worked flawlessly for a workgroup team hence the credentials in the script. I had nothing but headaches with mapping drives via logon scripts or any.

Disable that and see if it makes a difference. We plan to, but for now scripts have to do! GP will reconnect the drives. If you have a Domain Controller, you have Group Policy so I don't see why you wouldn't go ahead with it? I'm with CrimsonKidA on this. I had so many problems with mapped drive once I started migrating to Windows 7, that I gave up in disgust. I use Group Policy Preferences exclusively now and have not had an issue in 4 years.

I stopped using logon scripts when 7 came. I wouldn't think 8 or 10 would be any more forgiving on that ancient legacy approach. Use GPO. Your problem is the very reason I stopped using logon scripts. Then in a different job I warned them not to use log on scripts, but they had tested it and everything worked Well, not in a real environment. About users started having issues. They too used the lame excuse: "We plan to, but for now scripts have to do!

There is no reason why you can not add a foldermapping GPO for now. Even if the logon script does the same. Having both active does not do anything else than ensure the drive is there. The problem is worse on laptops using WiFi. And do not get me started on hibernate at home and wake it up at the office. I remember we had a consultant that refused to use GPO and put a copy of the logon script under the "Startup" folder just to get the drives to show a bit more reliably.

And a shortcut to the logonscript on the desktop for the user to click. You can place the copy or a shortcut to the logonscript there through GPO You can also work a bit parallel by adding the logonscript in the GPO. And the excuse "Logonscripts have to do" is still one of those things that annoys me. It reflects the stubborn old curmudgeon refusing to use the better and simpler tools because he has "always done it this way".