Windows 10: Windows 10 2004 Enterprise - will not run logon script when mapping drives to 2003 server...

First off, I am pushing to get the old 2003 server replaced, that is being held up due to economic reasons. Up to the 2004 update the logon scripts ran fine and mapped drives to various servers - 2003, 2008,2012,2016. When 2004 is installed the logon scripts stall at the mapping command. But only on our corporate sites that are mapping drives to old Windows 2003 servers that uses SMB1. The map portion of the script will take 15 minutes to complete. Each map progresses slowly like molasses.

Testing this I found if I do a manual UNmap before the next reboot net use * /d /y it takes about 10 minutes to complete. On the next reboot the logon script runs fine and all connections are available - but subsequent reboots stall on the script. Drives to the 2003 server are not available during the the time the logon script is running and stalled, nor after it completes the run, the drives show disconnected.

If I remove mapping commands to the 2003 server the script runs fine, add them back and it stalls again.

SMB 1 IS installed on the PCs and the script currently works on 1909 machines and maps to the old 2003 server.

:)

 

Torrent / Copy Of Windows 2003 Server Enterprise Edition

Anyone know where to get 2003 Windows Server Enterprise Edition with a Registration Key? or without, plz and thank u!

 

Group Policy Deployment to Windows 10 Enterprise PC


Hi,


To expand a little on our setup which will hopefully help the explanation, we use Win 7 Enterprise throughout the business, all PC's\Laptops run a logon script which firstly maps 3 network drives using the standard command below:


net use P: \\Server\Share /persistent:yes
net use R: \\Server\Share /persistent:yes
net use H: \\Server\Share\%username% /persistent:yes
net config server /autodisconnect:-1


All these work as they should, however this same command is not running for the Windows 10 Enterprise PC that I'm testing.


This script is located in USER CONFIGURATION\WINDOWS SETTINGS\SCRIPTS (LOGON\LOGOFF)\LOGON


This same script also includes 4 lines which copies company PDF's (from a network location) to users desktops, this part of the script is working on the Windows 10 PC, it's just not mapping the drives. Does this basic script still require me to copy the ADMX and ADML files into the necessary location?


Hope this adds to a further explanation of my problem.


All help is much appreciated.


Ad

 

Mapped network drives do not connect at logon in vista with automatic logon enabled

I have vista x64 . I have some mapped network drives . They get connected when i enter the password at logon screen. Now i enabled automatic logon in vista and they do not connect anymore . I have to double click on them and enter the password manually .

Windows displays the message "Could not connect to all drives" at logon .

They used to connect automatically in xo with automatic logon enabled.

My logon password is the same as the administrator password with which i can connect to these drives .