Share via

Network drives do not map for some users

Question

Thursday, March 2, 2017 5:00 PM

We have been using Windows 7 Pro exclusively in our company so Win 10 is somewhat new to me.  I do use Win 10 at home so I am familiar with the interface.

We run Windows 2008r2 servers in a single domain.  I use a GPO to map network drives for my users.

My problem is:  I have a new Win 10 Pro workstation that I am setting up for a user.  The system is joined to the domain.  When he logs in using the new workstation his network drives do not map.  When I login myself, the network drives map correctly.  I cannot figure out why his drives are not mapping.  How can I troubleshoot this? 

All replies (15)

Thursday, March 2, 2017 6:01 PM âś…Answered

How are you mapping the drives in Group Policy? What mechanism is being used?

User Configuration > Preferences > Windows Settings > Drive Maps works.

Thursday, March 2, 2017 5:20 PM

Okay, I found something that helped but it did not completely resolve the issue.

I found the information below about modifying the registry.  When I modified the registry the G: drive mapped for the user but the X: drive did NOT map.  I have two different GPO's that map the drives.  One that maps G: and a different gpo that maps X:.  You can manually map X: by running the net use command.  So I still have a problem and need some help.  thanks

You need to modify the registry.

1. Open regedit
2. HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> Policies -> System
3. On the right, you will see ConsentPromptBehaviorAdmin, ConsentPromptBehaviorUser ... etc.
4. click on empty space, ADD DWORD(32bit), then name it "EnableLinkedConnections". Double click it and set the data to 1.
5. Reboot and you will see the mapped drives showing.

Thursday, March 2, 2017 7:16 PM

I am using:   User Config > Policies > Windows Settings > Scripts > Logon Script
There is a batch file that I use to map the drives.

Again, there are two gpo's.  One maps G: drive and another maps X: drive.  The G: drive starting mapping correctly after the registry edit I mentioned above.  The X: drive still does not map for this user.   Again, I can map it manually no problem.

I have been doing it this way for years.  Maybe I should try your way.  Would I select Action > Create, place the url in the location field, check reconnect, then select the drive letter to use?

Thursday, March 2, 2017 7:32 PM

Right click Drive Maps (or Action) then New > Mapped Drive. I normally select Replace, put the location an friendly label then pick the letter to use.

Thursday, March 2, 2017 7:50 PM

I will try that but will still need to find out why the drive is not mapping thru the login script.  This is crazy.  It has to be something very basic and simple that I am not seeing.

Thursday, March 2, 2017 8:01 PM

It is mapping whatever I throw at it when I login as user-1 (a domain admin account) but when I login as user-2 (another domain admin account) it will only map one drive.  This is driving me nuts.  This is only happening in Windows 10.

Thursday, March 2, 2017 8:32 PM

If I login to the Win 10 workstation as user-2 it will only display one of the mapped drives.  (G:)
If I login to a Win 7 workstation as user-2 it will display both mapped drives. (G: and X:)

I actually logged in as a 3rd user as well.  Same results.

It has to be something to do with Win 10 correct?

Thursday, March 2, 2017 10:33 PM

Yes something to do with Window 10. Your situation is interesting due to the inconsistent results but this anomaly   to due to using login scripts in Windows 10. Windows 10 does secure things, run things in sand boxes and secure sessions more, so does not surprise login scripts are different to Windows 7.

The drive maps GPO have been in for a long time so hence why I asked and to me simply time to move to mapping drivers that way.

Friday, March 3, 2017 6:25 AM

Hi, 

Since we can manually map the X drive, I just consider if there is any difference between G and X drive, are they in the same host PC? 

Same GP configuration for these 2 drives are used, right? 

Let's collect the userenv.log for further research on this issue, which we an use debug logging output to troubleshoot problems with user profiles and Group Policy processing: 

Userenv.log file located in the %SystemRoot%\Debug\UserMode folder, to enable it, check this registry key: 

HKLM/Software/Microsoft/Windows NT/CurrentVersion/Winlogon.

Create a REG_DWORD with the value called UserEnvDebugLevel then set the value to 0x10002 in hexadecimal. 

***After that, please run GPupdate /force, then restart the computer to create the log. ***

***Please Upload the userenv.log onto OneDrive and share the Link here for our research. ***

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, March 10, 2017 3:43 PM

I am having trouble creating the value (0x10002) in hex for the entry.  How do I enter this to make it come out to 0x10002?

Friday, March 10, 2017 3:54 PM

Not sure if this is any use, but are you using Labtech on your network? I believe that can cause problems with drives with the letter X as one of their default scripts uses it. Just thought I would mention it.

Friday, March 10, 2017 4:11 PM

No Labtech on our network.

thanks

Friday, March 10, 2017 4:33 PM | 1 vote

I may be chasing a rabbit here.  It may be easier for me to fall in line and use Mr Happy's way he mentions above by going to User Configuration > Preferences > Windows Settings > Drive Maps

That may be better than trying to figure out what this crap is not working consistently.  I would still like to figure it out and make it work both ways.

Tuesday, March 14, 2017 10:25 AM

Hi Poly, 

Have you taken time to check my suggestions above? 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, March 16, 2017 6:32 PM | 1 vote

I am going to use Mr Happys recommendation for mapping the drives.  When I login to a Win 7 system as User-1 and all drives map successfully then login to a Win 10 system as User-1 and none of the drives map correctly then I know it is a Windows 10 issue.  There is nothing wrong with my network.  But I have tested it using Mr Happys method listed below and it works for every user all the time.  I will mark his as answer.

User Configuration > Preferences > Windows Settings > Drive Maps works.

thanks for the help.