Question Locked

GPO change causes 'mystery' shares

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Experts,

We are migrating to a new file server, from 2000 to 2003 domain. Two days ago I began the task of migrating users' My Documents folders. Began with one OU, changing the folder redirection setting to point to the new server and share. After the change, reboot, and subsequent file transfer, varying numbers of network shares are appearing on each client, some using every letter (E-Z) with shares. Each share is pointing to the old public share on the old server, and says 'Disconnected Network Drive', but each will open when double-clicked. Attempting to disconnect results in 'The network connection could not be found' error.

Troubleshooting steps taken so far:

Removed logon scripts and home folder redirection in every users profile.

Remove all shortcuts to previous share and My Docs folder (if I could find them).

Remove items in startup menu.

Clear Temp folders and remove .tmp files in My Documents folders.

Installed MS User Profile Hive Cleanup Service.

Removed startup scripts (logon.bat) both in user profile and in default domain policy.

NET USE commands don't do much good. I have gpupdate'd and restarted more times than I care to mention.

I have been researching this for the past 16 hours, so I hope someone out there has a fresh idea.

Thanks!!!!

4 replies

by retro77

Is there something recursive in the script?
Also does the script map a certain drive letter or just the next one available?
Also does the script work if you just run it, and not in the GPO?
If you wipe out the local user profile, do the drives come back?

If you can post the script, that would also help us.

by maniacman

Here's the registry key you need to add to fix the disconnected drive madness, as I too spent a week until I found the solution to this:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\
MountPoint2

Add a new key under MountPoint2 and name it the drive letter of the disconnected network drive that you're having

Under that newly created key, create a new string called BaseClass and give it a value of Drive

Exit the registry and reboot your machine(s). You will now be able to delete the disconnected drive permanently. You will need to do this on every machine that has this problem.

This problem has to do with persistent drive mappings and the stupid method by which Windows saves passwords when attempting to remap. The problem here is that it's using old and invalid credentials upon boot, thus showing a disconnected status, but when double clicking it uses the right credentials and grants you access. You can thank Microsoft for this bullsh!t bug.

Please give me a thumbs up if this fixes your problem.

Thanks.

by tmichael

Thanks to both for the replies...

retro77: The script is mapping a specific drive letter (P). Everyone in the building is using the exact same script (about 80 individuals) and it has been in place since WAY before I began working there. I did not try running the script outside of the policy. I have been trying to avoid deleting user profiles, though I did think of it. I did test creating a new user, add to the OU, and login to a fresh PC, and there were no mystery drives and the My Docs folder pointed to the correct place.

Maniac: Thanks for the tip. I will test this at the beginning of the week and post back.

Cheers!

This discussion is closed to new replies.