Missing Mapped Drives

[talksr]

Has anyone else had this odd problem...

 

Windows Server 2012 R2

Windows 10 20H2 Stations

 

I have had staff come to me reporting that some or all shared drives are missing.

Of the shares, all but one are hosted on the FRDC server. The other is a NAS share.

No permissions have been changed in years and this has worked reliably for years.

 

I have had some difficulty in replicating this but have just seen it happen myself. It makes no sense to me at all.

 

We are running server 2012 R2 - (waiting for the ok to do an Inplace Upgrade on it). Stations are currently on 20H2 Windows 10. Mapped drives are mapped through a batch script which has worked with no issues for years.

Stations can ping server, and is obviously able to talk to it as it can log in and sometimes gets some of the mapped drives, sometimes none, sometimes all as it should.

 

I have never ever had an issue like this, and not really sure what it could be. We can't upgrade from 20H2 yet as we have WSUS issues (does anyone not have WSUS issues), currently rebuilding wsus server.

 

If anyone else has had experience of this, do let me know. I am stumped.

[jthompson]

You can never really discount DNS as a cause.

 

I'd maybe try a test of using pure Group Policy options in place of mapping them in a logon script, to see if that makes any difference (User Configuration > Preferences > Windows Settings > Drive Maps.

 

Also, did I mention that you can never really discount DNS as a cause?

[thimon]

It’s always dns [emoji846]