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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-07-27T22:26:26+00:00

    A partial work-around:

    I added

    NET USE * /DELETE /YES

    to the top of the login script. Issue seems worse if the mapped drive already exists. Impatient people reboot, and it works 2nd time (no mapped drives).

    For people that follow instructions:

    I added a line to copy a simple batch file to their desktop called ReBoot.bat with:

    @ECHO OFF

    ECHO *** Press ENTER when all programs are closed, system will reboot ***

    PAUSE

    NET USE * /DELETE /YES

    SHUTDOWN /R /T 20

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-24T12:01:53+00:00

    Had the same issue after 2004 update, mapped drive on windows server 2012. Found the fix a moment ago, enable smbv2 protocol with the following powershell command :

    Set-SmbServerConfiguration –EnableSMB2Protocol $true

    • shame on microsoft for having us suffer this long!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-07T11:25:16+00:00

    I've posted this issue on various forums, MS Technet included.  I either get NO answer or simply get ragged on for daring to use such an old protocol on a 17 year old OS.  Admittedly that's the answer to those having the issue for regular MS OS's like 2003, it won't fix the issue to those using older SAN hardware that can't be upgraded. 

    I fear we will never get this issue resolved, it will instead fall to us to replace hardware / OS software to make the issue go away. 

    ...such lack of respect for customers...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-07T11:23:22+00:00

    Any chance you are using Guest access on your NAS and you need to change the following key and restart your PC/laptop?

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "AllowInsecureGuestAuth"=dword:1

    https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser

    No chance.

    Each user has its own credentials.

    And as the article points out, that occurs in Windows 10 version 1709 and later, but in our case the problem started only with version 2004.

    But thanks for the suggestion.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-07-07T10:46:05+00:00

    Any chance you are using Guest access on your NAS and you need to change the following key and restart your PC/laptop?

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "AllowInsecureGuestAuth"=dword:1

    https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments