Why is Windows 10 Version 2004 preventing logon scripts from mapping NAS drives at first logon attempt?

Anonymous
2020-06-06T22:33:25+00:00

Since we updated Windows 10 to Version 2004 that all the machines in our domain stopped mapping NAS drives at first logon.

When the users start the machines and logon the logon script maps correctly the drives in several servers but not in the NAS.

If they logoff and logon again then the mapping is done correctly.

The problem occurs sistematically and started only after Version 2004 was installed.

It has nothing to do with SMB 1.0 being enabled - it was already enabled before Version 2004 as it was needed because we are talking about an old NAS.

Direct SMB appeared enabled and we disabled it, but it didn't solve the problem.

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

42 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-06-08T11:46:51+00:00

    Try doing that on all machines in your domain.

    No. That's not a solution. It's a band-aid.

    The purpose of using logon scripts is doing things only once.

    I've tried GPO but for some reason - maybe because it's an old domain - it doesn't work with Windows 10, compliments of MSFT.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-08T11:35:59+00:00

    This worked for me: create a scheduled task that launches this command at boot: "net use \your_server_or_NAS" (without quotes) and reboot.

    All the mapped drives should be working again

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments