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-07T12:25:32+00:00

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

    Yeah, I work for a Fortune 1000 company and we spend hundreds of thousands yearly on Azure and other MS licenses for like 10,000 O365 users.  So, I am stuck with the dumb 32 bit Win 2003 server that' is a VM that the company does not want invest on replacing the Host so we can migrate it an it's 3TB disk array to a new OS. 

    The SILENCE is what is chapping my you know what.  this has a solution, as it worked fine all the way to 1909.  No one is addressing it because it's such an old OS and crappy protocol.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2020-07-01T15:56:42+00:00

    Same issues.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-23T12:30:58+00:00

    We have the same problem.

    I hope MS resolve it asap.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-06-23T10:50:37+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.

    Was this answer helpful?

    0 comments