

Gpo mapped drives windows 7#
As per the policy description, drive mapping refresh should work during the background processing by default - but it is not the case.This article provides methods to solve the issue that mapped drives are unavailable in an elevated command prompt.Īpplies to: Windows 7 Service Pack 1, Windows Server 2012 R2 Original KB number: 3035277 Symptoms I STRONGLY recommend to not to follow the description of Drive mapping CSE it is really contradicting with its behavior. I again relied on GPO logs and realized that drive mapping CSE refresh is happening as part of background processing. Problem#2: Background processing of drive mapping is not working.Īfter login, if I delete mapped drives and initiate a “gpupdate /force” command, my drives are not coming back. Things started working and drive mapping is happening every time I re-login.įirst problem is solved.

Hmm, whatever it is doing is right and I have enabled “Process even if the Group Policy objects have not changed” option in “Drive maps preference extension policy processing” policy which is located at and restarted my PC. They are clearly saying that drive mapping CSE processing skipped as there is no change in version number. Well, now I enabled GPO debug logging on my Windows 7 machine and started looking at the logs. This made me to realize that drive mapping CSE didn’t triggered at all. I ran rsop and there drive mapping processing time is not updated. Initially I am not sure why the drive mapping is not happening at every login. Problem#1: Drive mapping not happening at every login After taking a break, I followed the divide and conquer method. The very big mistake I did to resolve above is, trying to resolve both the problems at same attempt and really mixed up the things and made myself confused. Background processing of drive mapping is not working.Drive mapping is not happening at every attempt.Finally after applying multiple tests like this, I came to a conclusion that, I have below two problems… I surprised and made relogin again, this time they mapped. Again, what I did is, I re-logged into the machine and found that they are not in place still. What I did to make my life tough is, I deleted the mapped drives after login and did a “gpupdate /force” no drives were mapped L. If you start playing with it to satisfy different kind of situations, then you are caught. So, I decided to write this post to help my blog visitors by providing as much as information I have gathered/learnt in Drive mapping related things.Īs said before, things are really smooth when you configure drive mapping preference for the first time. It’s easy as you see, but very difficult when you want to troubleshooting. I had spent real huge amount of time in dealing with drive mapping in Group Policy preferences in last week.
