GPO for Mapped Drives in 2004.

Question

Here we've been successful in getting only two required drives mapped in every OS version of 10, up until 2004. I'm neither a NW person nor AD person. I create virtual images used in MDT for deployment.
We've had to change back to 1909 because our two drives do not get mapped in 2004.
Just experimenting, I found a link to add SMB2 in the registry and it seems that they map, but only on the LAN, not on WIFI.

How has anyone set up login mapped drives through GPO in 2004? What has changed or needs to change on our end to make that work? Until then, we are at 1909.
Thanks

Answer 1

Hello，

Thank you so much for posting here.

According to our description, the GPO for mapped drives is sucessfully applied on OS version 1909 Windows 10, but failed to get applied in 2004. So sorry that we do not have the environment to do the test now.

Could the shared folder be accessed?

Since it failed to get applied in 2004, have we checked the gpresult report on the problematic machines? Is there any error message? To check the report, please follow the below:

For user configuration:
Logon one client with domain user account who is within the OU linked by the GPO.
Create a new folder in C drive named Folder.
Open CMD, type gpresult /h C:\Folder\report.html and click Enter.
Open report file to check the policies under User Details.

Besides, the article below is for an older version of Windows 10 but the workaround should still work. We could kindly have a check whether it helps.
https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-network-drive-fail-reconnect

Best regards,
Hannah Xiong

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I read that 20h2 fixes the SMB1 issue that many face in this situation.

I upgraded one of my VMs and imported it into MDT. When I deployed the image, I had access to one drive but not the other.

I realize that when we went from 1697, 1703, 1803, 1909.....AD had to grab new templates to apply the GPO's to those OS's. Is there an updated GPO template for 20h2 that is different that the one for 2004?

If that is the case, then we can experiment with that template and apply the same GPO to that OS.

Answer 3

Hello,

Thank you so much for your feedback.

There is Administrative Templates (.admx) for Windows 10 October 2020 Update (20H2). Below is the link:

https://www.microsoft.com/en-us/download/102157

Administrative Templates are registry-based policy settings that appear in the Group Policy Editor under the Administrative Templates node of both the Computer and User Configuration nodes. This hierarchy is created when the Group Policy Editor reads XML-based Administrative Template files (.admx).

Best regards,
Hannah Xiong

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

It seems that in 20h2 the drives are not mapped either. However, I do have to wait for the 20h2 template to get applied to the base GPO and I can test from there. I have no idea why 1909 will not auto-map our drives in GPO as they do in every prior OS.