Windows 10 issue with mapped drive
Posted on 2016-08-08
Been running some test PCs with Windows 10 installed and noticed this issue.
We currently have logon scripts which map a user to their needed network drives.
In this case, the mapped drive references an old server name which is actually a CNAME to the current server.
In Windows 7, this is working fine and the drives are mapped.
In Windows 10, when a user logs in, there is no drive mapped or error displayed.
It is when I try mapping it manually that I get the error "The target account name is incorrect."
Doing a ping test, the server name resolves fine and I can ping the server.
If I map it using the current server name, it works.
Is there a setting in Windows 10 I need to change?