First, decide what you need the script to do. 2nd, write the script (using the .bat extension). 3rd, insert a copy of the script into the winnt/system32/repl/import/scripts folder. This is the "netlogon" share seen in network neighborhood under each domain controller. 4th, specify the script in each users profile.<br>
<br>
If you're just mapping network drives, a sample script would look something like this -<br>
<br>
NET TIME \\<SERVER NAME> /SET /YES<br>
NET USE <DRIVE LETTER ON CLIENT>: \\SERVERNAME\SHARENAME<br>
<br>
Repeat the "net use" command for each share you want mapped on the client.
FYI more uses for login scripts:<br>
<br>
I use a simple xcopy in login scripts to update anti-virus software definitions from a server source:<br>
<br>
xcopy \\<server name>\<source sharename> c:\<av definitions location> /d<br>
<br>
I only need to keep the server source up to date; the /d switch only copies the files if the server source is more recent.
network-If this server is in an NT domain, be sure to put the script in the NETLOGON (\winnt\system32\repl\import\scripts) of ALL domain controllers. Common mistake is to put it only on the PDC. It's gotta be in the BDC's as well.
No one mentionted this so I will. A wonderful tool for writing NT logon scripts for workstation and 95/98 clients is KixTart. This is not technically supported by Microsoft even though it is included in the NT Resource Kit. To get the latest version of KixTart, go to
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.