Mapped drives GPO Issue (drive labels not showing properly)

benjilafouine
benjilafouine used Ask the Experts™
on
Hi,

I have a bit of a mystery here. I activated today a GPO with mapped drives to replace existing manual mapping drives in some PCs on a AD domain. For each of these new maps, I gave them a simple "label". Settings used for these drives are "update" and the "reconnect" button is checked.

Basically, I had two kinds of machines: the ones with existing manual drive mappings and the ones that had no manual mappings at all.

To activate the drives on the machines that had existing mappings, I "disconnected" all the drives manually, then did a "gpupdate /force" on each machines and logged back in.

Results

PCs that did not have mappings accepted the new mappings and the "labels" displayed correctly.

For the machines that already had a manual drive letter with the same drive letter as the new one I am trying to introduce will not display the labels correctly. Instead, they will show the complete share name rather than the label I am trying to introduce (I would prefer that the user don't see the real share name since the naming convention is more complicated.

Has anyone come up across this problem and how to fix it? The only solution I found was to destroy the user's profile and recreate it but this is rather a complicated task for a little drive map. There must be something in the registry key for this particular user, but every key I deleted so far has not fixed the issue (I tried erasing any information in the registry pertaining to the old drive mapping).

Thanks for helping.

Benji.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Network Engineer
Commented:
Change the GPO drive mapping option to Replace instead of Update.

Author

Commented:
OK, will do and report. I tried create so far without success. And what about that reconnect check? What does it do exactly? And for the replace, should it be permanent?

All these options are not well explained on Technet I believe.
kevinhsiehNetwork Engineer

Commented:
Reconnect is that same thing as checking reconnect when manually mapping the drive. It causes a persistent mapping so that it will remain mapped even after the GPO is removed and across reboots. The replacement will be permanent, or at least until another setting is applied.
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Krzysztof PytkoSenior Active Directory Engineer
Top Expert 2012

Commented:
So, in this case I would suggest 2 settings in map section

Create Drive letter to be deleted (Action: Delete, Existing: <drive_letter>) then go to "Common" tab and check "Apply once and do not reapply"

Set these action for each drive. Set up then each mapping drive. And check if it resolves your problem. After some time when you sure that all clients don't have this problem, you can delete these settings (only DELETE action) :))

Regards,
Krzysztof

Author

Commented:
The replace option doesn't seem to work. I set one of the maps to replace, then did a gpupdate /force on one user computer and when I looged back in, same problem. I even retried a second time by disconnecting manually the drive first and then execute the gpupdate command.

Now I have to test the delete option but I will wait at the end of the business day not to disrupt users (not sure what could happen when the policy gets to all the PCs.

Benji.
kevinhsiehNetwork Engineer

Commented:
You can create an OU for testing and put a test PC and user into that OU. Apply yhr GPO to that OU and you can test without affecting the rest of your environment.

Author

Commented:
Actually, it seems good now! The "replace" setting seemed to have done the job I think. Without any other intervention, I am looking at all several machines and the label is now OK!! I didn't even have to disconnect the old drive. Not sure if a reboot or logoff did it or if the letter got replaced during a user session but after looking at four machines, they are now OK.

I will report once I have complete confirmation on all the machines.

Thanks.

Benji

Author

Commented:
Completely fixed by itself without any intervention.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial