chrismebs
asked on
Multiple Mapped Drives to one Shared Folder
This isn't really a problem per say - as much as a "why would this happen?"
We have a user who keeps getting duplicate mappings of a network drive throughout the day.
Details are:
Window XP Pro client bound to a Windows 2003 Server on a domain. Mapped drives are not assigned with a login script or by the directory, users are free to map or not as they choose.
When the client boots the Network share folder called "Public" is mapped to the "P" drive. By the end of the day it shows up as "V", "X", etc. Sometimes up to 6 mappings to the same folder.
Running the Net Use /delete * command disconnects them all, but they eventually just show up again.
My first question would be why this would happen, and secondly, how to undo it.
When a user clicks on a share and selects "Map Network Drive" and "Reconnect at logon" where does that info reside should you want to undo it?
Any thoughts welcome. Thanks!
We have a user who keeps getting duplicate mappings of a network drive throughout the day.
Details are:
Window XP Pro client bound to a Windows 2003 Server on a domain. Mapped drives are not assigned with a login script or by the directory, users are free to map or not as they choose.
When the client boots the Network share folder called "Public" is mapped to the "P" drive. By the end of the day it shows up as "V", "X", etc. Sometimes up to 6 mappings to the same folder.
Running the Net Use /delete * command disconnects them all, but they eventually just show up again.
My first question would be why this would happen, and secondly, how to undo it.
When a user clicks on a share and selects "Map Network Drive" and "Reconnect at logon" where does that info reside should you want to undo it?
Any thoughts welcome. Thanks!
Check the registry on the machine. I believe the key is Persistent connections. Delete the ones that don't need to be there.
HKCurrentUser\software\mic
Philip
HKCurrentUser\software\mic
Philip
Another thing is to try using a new user profile.
I hope this helps !
I hope this helps !
ASKER
RobWill > no we do not have any group policy scripts that map network drives
MPECSInc:>
HKEY_CURRENT_USER\Software
has a string "SaveConnections" with a value of "yes". I still want the drives to map, so would changing this to "no" change that?
MPECSInc:>
HKEY_CURRENT_USER\Software
has a string "SaveConnections" with a value of "yes". I still want the drives to map, so would changing this to "no" change that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Click on the Persistent Connections folder and export it before deleting the subkeys. This will backup as RobWill mentioned.
In the end, you will have the user map the share once, and you should see a new Persistent Connection key created in that location.
Philip
In the end, you will have the user map the share once, and you should see a new Persistent Connection key created in that location.
Philip
ASKER
Final solution was to use a group policy rather than "reconnect @ logon".
Changing the registry settings did not produce the desired result. That being said, I did not spend much time persuing changing registry key settings as creating the group policy fixed the problem (as one would expect).
I wouldstil like to know "why" this behaviour happened - but it doesn't really matter. If you do things the right way you can avoid this kind of hassle :)
Changing the registry settings did not produce the desired result. That being said, I did not spend much time persuing changing registry key settings as creating the group policy fixed the problem (as one would expect).
I wouldstil like to know "why" this behaviour happened - but it doesn't really matter. If you do things the right way you can avoid this kind of hassle :)
Thanks chrismebs.
Cheers !
--Rob
Cheers !
--Rob
net use /persistent:no
Do you have any group policies in place to run scripts to map drives? If so they will periodically refresh.