SMS 2.0/SP2 does not modify logon script

[lalberti]

After scheduling SMS NT Logon Server Manager on a SMS 2.0/SP2 server the system notify me (see status messages listed below) that SMS successfully modified logon scripts for 18 users.
But if I check in the logon script nothing is changed; the only difference is that SMS installed some files (smsls.bat, SlwNt32a.exe, ....) in the \NETLOGON share.
How can it be?...Is there anything more to set in order to get an automatic logon script modification?...
or...is there a way to do it manually?

Thanks in advance,

Luca ALBERTI
luca.alberti@ramcube.it

->
Severity Type Site code Date / Time System Component Message ID Description
Information Milestone RAM 9/26/01 6:10:14 PM SOLE SMS_NT_LOGON_SERVER_MANAGER 1402 SMS NT Logon Server Manager completed a processing cycle for all of the domains configured for the Windows Networking Logon Discovery or Client Installation methods.
Information Milestone RAM 9/26/01 6:10:05 PM SOLE SMS_NT_LOGON_SERVER_MANAGER 1400 SMS NT Logon Server Manager successfully modified logon scripts for 18 users and failed to modify logon scripts for 1 users. SMS NT Logon Server Manager examined a total of 29 users in the Windows NT domain RAMCUBE, and modified 18 files.
Information Milestone RAM 9/26/01 6:09:40 PM SOLE SMS_NT_LOGON_SERVER_MANAGER 1401 SMS NT Logon Server Manager is beginning a processing cycle for all of the domains configured for the Windows Networking Logon Discovery or Client Installation methods.
Information Milestone RAM 9/26/01 6:09:03 PM SOLE SMS_NT_USER_DISCOVERY_AGENT 1105 SMS Executive is next scheduled to start this component on "9/26/01 6:11:00 PM".

->

 

[Jpoandl]

In my environment, I didn't want to have SMS modify any logon scritps so I did it manually. I had Kixtart scripts running already and had multiple logon scritps. I didn't want to take the chance of ruining these.

Anyway, you can add a call to SMSLS.bat or simply run SMSLS.bat directly.

What you could do, it highlight all of your users in USERMANAGER for DOMAINS and the choose file properties. Add the SMSLS.bat file under Logon scripts and hit OK. thats it.

(I think the automatic script modification has actually worked for you. Your just looking in the wrong spot. The 18 users that is modified probably didn't have anything listed for a logon script. The other users probably were already running a logon script. You see, SMS will go into *.bat logon script files, and add a call for SMSLS.bat. I would read the help in SMS to find more information)

Here read this from the SMS Administrators guide:

Modifying Logon Scripts
If you do not use the Systems Management Installation Wizard to discover or install clients, you instead use modified logon scripts to invoke the logon discovery and client installation processes. When users log on to the network, the logon scripts run on the clients and initialize the discovery or client installation process.

Tip To minimize unnecessary client activity and network use, you must configure client agents for your site before you enable Modify logon scripts.

When you configure logon discovery and installation methods, you can choose to have SMS automatically modify logon scripts. If you already have logon scripts in place, SMS can modify all of them automatically to include the SMS logon script. If you do not have logon scripts in a Windows Networking environment, SMS will modify user profiles so they use SMSls.bat as the logon script.

In Windows Networking, SMS will modify the script file only if the logon script file name ends with a .bat or .cmd extension, according to the following rules:

If you have a logon script ending in a .bat or .cmd extension, SMS will modify the script file.
If you have a logon script that does not end in a .bat or .cmd extension, SMS will not modify the script file. You can use this feature to make SMS skip specific user profiles by omitting the extension in the user profile and allowing the operating system to default to the .bat or .cmd extension.
You can also select whether SMS inserts changes at the beginning or end of the logon script.

If SMS automatically modifies logon scripts, SMS will configure the logon scripts for all users in the logon points. You can selectively modify logon scripts for individual Windows Networking users by choosing to modify the logon scripts manually. You might want to do this when you roll out SMS slowly to a few users at a time. Whenever you install more clients, you can manually modify the logon scripts for the users whose computers you want to install the SMS client software on.

Tip If it is necessary to do additional processing during discovery or client installation, you can also modify SMSls.bat itself.

Joseph L. Poandl
MCSE 2000

 

[Jpoandl]

(By the way, I would upgrade your site to SMS service pack two ASAP. Especially if your are in the rollout stages. There are many problems with SP1 and SP2 that SP3 resolves...like client hangs and such.) Joseph L. Poandl
MCSE 2000