SMS called from a bach file

http://www.experts-exchange.com/Operating_Systems/WinNT/Q_11401298.html

One way to control the installation of the SMS client is to use only logon scripts to start the installation. If your logon script is called for example myscript.bat, make sure this is refered to as just myscript (without the .bat) in all users properties. This prevents SMS from modifying the script. Create a copy of the script (e.g. myscriptsms.bat) and add the following line at the end...

call %0\..\smsls.bat

Now you can migrate users in a controlled manner by changing their logon script to myscriptsms.

This of course assumes that users are associated with specific machines and not roaming. If your users are roaming you may have to use other criteria to determine whether or not to run smsls.bat (again from the logon script). You could for example create a file containing a list of machines which require the client to be installed called machines.txt

In your logon script you could include the following code:

find /I "%computername%" machines.txt
if "%errorlevel%" == 1 goto nosms
call %0\..\smsls.bat
:nosms