GPO drive mappings Windows 10 show up disconnected but its really connected

Hey guys,

we are having issues with our mapped drives GPO. We have a drive called the M and N drive that are constantly giving us issues in windows 10 and 8. When the user signs in the M drive will automatically say its disconnected  but the N drive will work correctly. Both are set using the "Create" option in Group policy. When we switch the option from Create to Update , all craziness happens and even more issues will happen from the N and M drive such as it disappears and/or doesnt connect and gives us errors. So...  I ran this GPResults from the command line on a test computer and noticed that both drives show up TWICE in the gpresults . I am thinking maybe it has something to do with the drives acting weird?

I also cannot figure out why its showing twice because the GPO drive mappings are only linked to "one" OU.

Any help would be greatly appreciated... ( by the way ive had this problem for about 6 months now and have run out of ideas).

RSOP data for "hidden"\testuser2 on L439 : Logging Mode

OS Configuration:           Member Workstation
OS Version:                 10.0.10586
Site Name:                 N/A
Roaming Profile:           N/A
Local Profile:             C:\Users\testuser2
Connected over a slow link?: No

    Last time Group Policy was applied: 9/12/16 at 10:09:14 AM
    Group Policy was applied from:     "Hidden"
    Group Policy slow link threshold: 500 kbps
    Domain Name:                       "Hidden"
    Domain Type:                       Windows 2008 or later
    Applied Group Policy Objects
        AP Admin Printers
        Edmonton P Drive APLink
        Kwik Tag Logon Server
        Edmonton O Drive OLENotes
        Edmonton M Drive
        Nuna Company N Drive
        Default Domain Policy
        Edmonton M Drive

        Nuna Company N Drive
Devon EdwardsAsked:
Who is Participating?
Devon EdwardsConnect With a Mentor Author Commented:
infact i created a new thread which actually defines whats really going on..
Weird indeed.
I would unlink the drive mapping GPOs and start with a new one, after making sure that no drive is connected in between.
Hi, can the issue be reproducted everytime ? What kind of network drives are behind ? Some Filer like Netapp or similiar ? In this case maybe try some native share on a "real" windows server ? what about the gpo's. do you use loopback mode ?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Devon EdwardsAuthor Commented:
Hi loopback processing isnt enabled where the GPO drives are at. Yes the issue can be reproduced everytime.
You know that following my suggestion would have led to the solution. Seems funny to just close this.
Devon EdwardsAuthor Commented:
new topic created
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.