Trouble running Logon Scripts

[DaveMusante]

We currently have about 450+ machines out of 1400 total that will not for some reason or another run our SMSLS.bat logon script. The logon is set to run for each user in their Active Directory properties. Each machine has an identical installation of Windows 2000 according to our hardware guys and a users rights to the machine does not appear to be the issue because i have full admin rights and the script will not run for me. Any ideas?

 

[pbxman]

Have you checked this out?

http://support.microsoft.com/?kbid=199987

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[DaveMusante]

I have already looked at that article, we have always been an SMS 2.0 site so it does not apply.

Thanks for trying!

 

[pbxman]

Do they have logon scripts already assigned, or is the sms script the only one? Did you select to have SMS update logon scripts for the entire site or no? pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[DaveMusante]

SMSLS.bat is the only windows logon script we run, the rest are done though Novell and they are fine. Where do I check if SMS update scripts are for the entire site?

 

[pbxman]

I forgot to add something..
Im assuming it was setup right, but you're still having probs, so let me just add these so you can check and make sure it's not something simple:

1. The logon script is not replicated to the BDCs.

2. The logon script name is incorrect.

3. The logon script is in an incorrect location.

4. The user does not have permission to read the file.

The logon script must be stored on each domain control in the NetLogon share, which is mapped to %SystemRoot%\System32\Repl\Import\Scripts.

If you are replicating from the PDC, the script should also be stored on the PDC in %SystemRoot%\System32\Repl\Export\Scripts.

The logon script batch file name should be configured in the user profile by double-clicking the Username in User Manager for Domains, pressing the Profile button, and entering the script batch file name, without the .bat extension, in the Logon Script Name box. You may also set it in batch:

where the path is the logon script batch file name, without the .bat extension.


Most often, it's the addition of the .bat extension in AD properties that does it. You need to leave the .bat extension off when you specify the logon script filename.

...just making sure all the bases are covered
Good luck

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.