If you’ve spent some time using GPP such as Drive Maps and Printers you might have noticed that it simply doesn’t always apply when you added/removed/changed something… I did notice this and it was driving me crazy not to know the reason for it. So I decided to post my findings. Please feel free to comment if you have found any other reasons.
Please note that most of my tests have been performed on Windows 7 clients (SP1 and fully patched at time of writing) and a Windows 2008 R2 server where I edited the GPO:s and 2003 DCs. Your setup might be different and therefore also a different result. Here are some examples of weird behavior I’ve been seeing:
- Adding a Drive Map wasn’t simply mapped.
- Changing a setting on Drive Maps simply wasn’t reflected on the clients no matter if I used Update or Replace on the GPP setting and even though DC:s had been replicated.
- Printers weren’t mapped
- …and I wasn’t alone. Google it and you’ll find plenty.
So, here are some quick checks you might want to try:
- Sometimes the following GPO setting needs to be Enabled: Computer Configuration -> Administrative Templates -> System -> Logon -> Always wait for the network at computer startup and logon
- Try the GPP setting: Run in logged-on user’s security context (user policy option)
- Check the event log of the client. Way to often the error sits there and it’s usually “network path not found” which means that you either misspelled the path, the users doesn’t have permission to the folder or that the client simply can’t find the share (name lookups?)
- Check that Loopback policy procesing is not on and set to Merge. Outexperience is that this can sometimes cause these problems.
So here are some other suggested solutions where to look
A mapped drive that has the non-persistent flag set is displayed as a disconnected drive in Windows 7 or in Windows Server 2008 R2
Mapped Drive Connection to Network Share May Be Lost
All about Drive mapping in Group Policy Preferences