You can run SMS Client Setup manually from the appropriate *.BIN subdirectory of the LOGON.SRV directory (SMS_SHR share) on an SMS logon server. You can run SMS Client Setup with one or more command line options. For example, you can initiate the removal of clients by modifying the SMSLS batch file to run SMS Client Setup with the /r option. Users can initiate removal of their client by connecting to the SMS_SHR on their SMS logon server and running SMS Client Setup manually with the /r option, or they can run DEINSTAL.BAT. The syntax for SMS Client Setup is as follows:
{cli_dos | cli_nt | cli_os2} [/r | /u | /f | /p:path | /d:drive | /v | /k]
/r
Removes the SMS client components. With this option, SMS Client Setup must run twice because SMS applications must be stopped before files are removed. This overrides Client settings in the Site Properties dialog box.
/u
Upgrades SMS client components. With this option, SMS Client Setup must run twice because SMS applications must be stopped before files are updated.
/f
Verifies that each SMS client component file is correctly installed and that the client's system files are correctly configured for SMS. With this option, SMS Client Setup must run twice.
/p:path
Specifies the path for the SMS\LOGON.SRV directory. For example, at a client running MS-DOS, from the command prompt, type:
cli_dos /p:R:
Where R: is the connection to the SMS_SHR on the SMS logon server.
You can also use a UNC path. For example:
cli_dos /p:\\SMS_server\SMS_SHR
/d:drive
Specifies the installation drive on the client. By default, SMS is installed on the drive with the largest amount of free space.
/v
Sets verbose mode. SMS Client Setup displays status messages on the client desktop as it completes its tasks.
/k
Specifies that SMS components are not running, and they can be overwritten if necessary.
If conflicting options are used (for example, /r and /u), SMS Client Setup selects the first option.
For information about how SMS Client Setup installs and upgrades SMS components on and removes SMS components from a client, see Chapter 3, "System Flow."