[1803, au] Windows 10 Pro 1803 Drive Mapping Issue

[geohanson]

Hi,

We are having an issue with drive mappings in Windows 10. Very occasionally a member of staff will login and get no mapped drives. Logging out and back in again, or running GPUPDATE fixes the issue. It happens with different users on different PCs and there seems to be no pattern to which members of staff or which computers are affected.

 

The same user policy is applied to all staff and is only causing an issue on Windows 10. Windows 7 computers aren't affected.

All the drives in the policy are set to 'Update'.

 

Thanks!

[BOOT]

Try with the [reconnect] box unchecked?

[geohanson]

Try with the [reconnect] box unchecked?

Thanks but the reconnect box is already unchecked for each drive.

Edited November 5, 2018 by geohanson

[Hybrid]

What does the event viewer come up with on an affected machine?

[rosslaing]

Hi,

We are having an issue with drive mappings in Windows 10. Very occasionally a member of staff will login and get no mapped drives. Logging out and back in again, or running GPUPDATE fixes the issue. It happens with different users on different PCs and there seems to be no pattern to which members of staff or which computers are affected.

 

The same user policy is applied to all staff and is only causing an issue on Windows 10. Windows 7 computers aren't affected.

All the drives in the policy are set to 'Update'.

 

Thanks!

 

Been seeing this more and more with 1803, alongside printers not mapping, so I think they are both related. Been a lot worse since the October updates.

[free780]

You can turn on Verbose logging for GPP Drive maps. I found if you don't use FQDN it can fail intermittently.

[gomalley]

I've found that a GP with Scope filtered by security group seems to fail, but one with item level targeting on the actual Drive maps and "Authenticated Users" at the top level seems more reliable.