Mapped drives slow to appear (Windows 10 20H2)

[gerardsweeney]

Hi, folks.

 

Over the Summer, I started moving PCs from ye olde Windows 10 1709 to 20H2 (yes, I know - 1709 worked solidly so I was in no blummin' rush!).

 

Anyway...

 

We map drive letters for things like Office Staff, departments etc via KIX scripts running at login.

 

All works brill on 1709 (like it did going all the way back to Windows 95)..

But on the 20H2, the mapped drive letters take about 2 minutes to actually appear in My Computer.

Once they're mapped, they're fine to access.

 

If I fire up a CMD prompt, and type net use, I can see the drives (and list the files with DIR R:\ or whatever), but it's a couple of minutes before they appear in Explorer.

 

Likewise, if I fire up a CMD prompt and type net use Q: \\blahserver\blahshare, it's a couple of minutes before Q: becomes visible in My Computer.

 

I'm assuming Microsoft have brought in some new fangled security measure.

Has anyone else come across this issue?

 

Cheers,

Gerard

[Primus]

We haven't seen that issue with 20H2 at all.

 

I know you're now moving on from 1709 but to say it worked so solidly you were in no rush until now does seem to forget you've had no security updates for it since October 2020.

 

We've found it easier with Windows 10 to stay reasonably current rather than sitting for several years on one release - that was the small issues you might get moving from version to version are more easily handled since you've got fewer of them each time rather than skipping releases and then seeing quite a few issues

[Bedders]

What server operating systems are the mapped drives running on? We saw issues when mapping drives to shares hosted on older OS's.

[thimon]

What server OS version is the file server running?

[gerardsweeney]

They're still running 2008 R2.

Before anyone chastises me .. They were scheduled to be replaced a few years back, but the project fell through - apparently happening soon

[gerardsweeney]

We haven't seen that issue with 20H2 at all.

 

I know you're now moving on from 1709 but to say it worked so solidly you were in no rush until now does seem to forget you've had no security updates for it since October 2020.

 

We've found it easier with Windows 10 to stay reasonably current rather than sitting for several years on one release - that was the small issues you might get moving from version to version are more easily handled since you've got fewer of them each time rather than skipping releases and then seeing quite a few issues

 

Security updates were the least of my concerns if I'm being brutally honest!

[3s-gtech]

They're still running 2008 R2.

Before anyone chastises me .. They were scheduled to be replaced a few years back, but the project fell through - apparently happening soon

 

Server OSs don’t need project planning and management to update (at least, not unless you micro-plan).

 

Check backups

Mount ISO

Run setup.exe

Spin on chair for a while

Job done.

[gerardsweeney]

Server OSs don’t need project planning and management to update (at least, not unless you micro-plan).

 

Check backups

Mount ISO

Run setup.exe

Spin on chair for a while

Job done.

 

 

Oh my sides

 

I won't go into specifics about my workplace, but suffice it to say there was and is substantially more involved.

[thimon]

They're still running 2008 R2.

Before anyone chastises me .. They were scheduled to be replaced a few years back, but the project fell through - apparently happening soon

 

I’m putting this out there, SMB might have something to do with it? Or is that for NAS only? Outside of my expertise. Older versions of Win10 where happy connecting to SMB1 file shares for example, however later versions not so much. May be getting my wires crossed, if so sorry. If you’ve got a newer OS server you could make a test file share and create a test GPO that maps that, see how quickly that appears in File Explorer in comparison.

[Oaktech]

Have you tried the mapped drives via GPP as I'm not seeing any issues at all using that and I have shares mapping to different OS and in different domains via a trust and they're still nigh on instant.