Discussion Locked

Login Script

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Having some problems getting the old style login scripts to work in windows 2K server. Are they suppose to be *.bat or *.cmd, or either but when are they suppose to be bat and when cmd? Where are they suppose to be put, what is the full path, and dopermissions come to play? I gues I need a step by step.

7 replies

by jellimonsta

You can find an overview for logon scripts in the following technet article.

http://support.microsoft.com/default.aspx?scid=kb;en-us;198642

Remove any spaces from the above URL

For a universal domain logon script, i.e. 'logon.bat'
Create alogon script for all users.
In the Properties dialog box for each user account, specify the name of the logon script.
Place the logon script in the following folder:

winnt\sysvol\sysvol\domainname\scripts

For info on OS specific scripts see
http://support.microsoft.com/default.aspx?scid=kb;en-us;190899

Another cool way of using scripts

http://support.microsoft.com/default.aspx?scid=kb;en-us;284193

by sgt_shultz

hmmm. i am stuck on obsolete old nt4 server here so shouldn't even be responding but nobody else is jumping in so, in my browsing thru the mskb for 'win2k login scripts' i find no mention of doing this other that thru Group Policy. can you add that?what are your workstation os's? do you have active directory?
does this help any?

by picturethat

Yes I believe the new way is Group Policy, I like the positive control I had with NT and that is what I was looking for. But thanks.

by curlergirl

The choice between *.bat and *.cmd files is largely dependent on your workstation OS's. If you have Win9x/Me workstations, you have to use *.bat files, since they will not read *.cmd files as batch files. If you have NT/2K/XP workstations, you canuse *.cmd files or *.bat files. I usually use *.cmd files, since there are some commands that I like to use that don't work in a *.bat file (for example, the /persistent:yes/no switch for drive mappings does not work in *.bat files).

For a straight, vanilla login script that will be run by all users, you can mimic the NT behavior by placing the script file in the NETLOGON share. However, the NETLOGON share is now in a different location than in NT - it's %systemroot%\winnt\sysvol\sysvol\[domain]\scripts. Replication between DCs is automatic now, so you don't have to configure anything to ensure that all of your DC's get their copies of the scripts. Then, you set up your users to use the login script the same way you did in NT - by specifying it in the user properties (in AD Users and Computers).

If you want to use Group Policies to deploy different login scripts for different groups of users, then you would use the Group Policy console to set up policies specifying differentlogin scripts. However, then you have to have each group of users in a separate organizational unit in order to assign different group policies to each group. You can set up a Default Domain Policy that covers all users if all users will share the same login scripts and policies. I don't think it is necessary to go to this extent unless there are other group policies that you want to use besides just assigning a login script. I like group policies, but they can get pretty complex, so I advise only to use when there are compelling reasons.

Hope this helps!

This discussion is closed to new replies.