Windows 10: GPO Drive Mapping Change

Hi,


I use GPO's for drive mapping using security groups. We setup a new server and moved the contents of a share from the old server to the new one. So we went from \\server-share\share to \\shared-server\shares\share$.


I set the GPO to the new path \\shared-server\share$ and set it from update to replace.


The GPO runs without error, but the new share will not apply to the computers.


On the new server, I applied the security group to the share and gave it full read/write access.


All the existing network shares work just fine.


I checked the firewall on the new server and the ports are opened (incoming-Domain) for:



NB-Name 137/UDP
NB-Datagram 138/UDP
NB-Session 139/TCP
SMB 445/TCP


I am at a loss as to what would be preventing the script from mapping to the new share.


Any help? Thanks!

:)

 

Mapping Drive with GPO worked - but not anymore

A couple weeks ago I created a few test mapped drives. I used the item level targeting feature to target a security group. I also used the item level targeting to single myself out for future testing - I seemed to be able to map drives with no problem after doing a group policy force update each time to get the new changes to appear.

My steps are New GPO > User Configuration > Preferences > Windows Settings > Drive Maps

The action is set to replace (tried update and create to no avail) the location is \server\sharedfolder (tried w/ and w/o reconnect) and choosing Existing drive letter high up in the alphabet. Then Common has the 'Run in logged-on user's security context' and Item-level targeting chosen.

Now, for some reason, I am not having any success and it is of course puzzling. I removed the test policies I had earlier and just left one legit one I had made for a small security group. I have mimicked the options and now am not having any new drive appear. The only thing I can think of would be windows updates - but why that changes how the GPO works or breaks it doesn't seem right.

Online results discuss unchecking the 'reconnect' to this drive and different permissions - but the tests that worked before had 'reconnect' check and I was applying them to the same user then as I am trying now.

Any thoughts, or settings to check? Hopefully I am just missing one small step, but I don't know what it would be.

 

GPO Mapped network Drives mapping in Win 10 but not Win 7


Traced it through logs it appears to be a script failure from GPO saying it cannot find the specified file. Also appears to be giving Access denied when trying to manually map and doesnt map home drives or the shared drive to the win 2k8 server but it does to the win 2k12 server

 

Unable to disconnect Mapped drive

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned that you have removed the mapped drives through GPO and still the drive keeps appearing, I suggest you to try removing the mapped drive by running the Net use command in Command Prompt and see if that helps. Please follow the
steps mentioned below:

1. Press Windows key + S, and type Command Prompt.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, type net use f: \\financial\public /delete
   (Replace f: \\financial\public with the drive name)
   

For more information on Net use command, you can refer the article
Net use.



If the issue persists, I suggest you to post your query in TechNet
forums, where we have support professionals who are well equipped with the knowledge on the GPO and mapped drivers to assist you with the appropriate details.



Regards,

Nikhar Khare

Microsoft Community - Moderator