Upgrading a 16-Bit Client Computer to SMS 2.0
The client upgrade process begins after you discover the client through any of the methods described in this chapter, provided that the client installation methods relevant to this client computer architecture have been initiated.
Because 16-bit computers do not support multitasking, different steps are used for this SMS client software upgrade. You can determine if a second restart is required by verifying whether any SMS 1.2 applications are started automatically by SMS 1.2 or whether Remote Control is initiated on the client. If either of these conditions exists, the client computer might be slow to appear in site server listings because the computer must be restarted and the user must log on twice before the upgrade is completed. Regardless of how your SMS 1.2 client was configured, the process will require a computer restart to complete the client upgrade.
To disable automatic component starts and remote control in SMS 1.2
- Open the SMS 1.2 console.
- Select the site.
- On the File menu, click Properties.
- In the Site Properties dialog box, click Clients.
- In the Clients dialog box, click Proposed Properties.
- Clear all of the Automatically Start this Component check boxes.
- Clear the Remote Troubleshooting check box.
- Click OK, and then click Yes to update this site.
After you disable Remote Control by using this procedure, it can only be initiated by an administrator at the SMS 2.0 site server, and then only after the SMS 2.0 client software installation is completed.
SMS 2.0 Client Installation Process (16-Bit Clients)
These steps describe the process SMS uses to install the SMS 2.0 client software on a 16-bit computer after you initiate discovery and installation methods in the SMS Administrator console.
- Boot16xx.exe (Windows networking installation) or SMSman16.exe (Systems Management Wizard) starts the client upgrade process.
- Ccim16.exe (CCIM) is started and determines if the SMS client software needs to be upgraded from SMS 1.2 or installed by looking for the markers described in Table 12.5.
- CCIM unbundles the following files:
- %Windir%\MS\SMS\Core\Bin\Migrat16.exe
- %Windir%\MS\SMS\Core\Bin\Copy1x16.exe
- %Windir%\MS\SMS\Core\Bin\Runonce.exe
- %Windir%\MS\SMS\Core\Data\Migrat16.ini
- CCIM executes Migrat16.exe which adds a new line, or modifies it if the line exists, in the hidden SMS.ini file under the heading [local]. The line is SetupPhase=deinstall. This file is stored in the root directory of the c: drive.
- Migrat16.exe launches the executable(s) referenced in the Migrat16.ini file:
- Copy1x16.exe copies the client’s c:\MS\SMS\Idmif directory and its contents to %Windir%\MS\SMS\Idmifs.
- Copy1x16.exe copies the client’s c:\MS\SMS\Noidmif directory and its contents to %Windir%\MS\SMS\Noidmifs.
- The hidden SMS.ini file in c:\ is copied to %Windir%\MS\SMS \Core\Data\SMS1x.ini.
- The SMS 2.0 client components are installed in the %Windir%\MS\SMS directory.
The client upgrade process continues with the second procedure after the computer is restarted and the user logs on. The process will be complete when all the SMS 1.2 components are removed and the SMS 2.0 services are started.
Starting SMS 2.0 Client Components and Removing the SMS 1.2 Client Software on 16-Bit Clients
SMS completes the installation of client software using this process.
- The SMS 2.0 client services installed in “SMS 2.0 Client Installation Process” are started.
- The SMS 1.2 directory structure under <FIRSTFIXEDDRIVE>:\MS is removed.
- If you have initiated hardware inventory in the SMS 2.0 Administrator console, the SMS 2.0 Hardware Inventory Agent creates a *.raw file and transfers it to the site server.
- SMS file entries are created or changed.
- The Sms.ini file [local] section has a line added, or, if it already exists, modified, to read: Setup=Deinstall.
- The Smscfg.ini file entry is modified to read: SMS Client Services Deinstall Client=‘Yes’.
- SMS 1.2 additions and changes are removed from the Win.ini, System.ini, and Autoexec.bat files:
- The Win.ini file is changed to remove SMSrun16.exe from the ‘Load=’ line, if needed.
- In System.ini, the following files are removed from the [386Enh] section: Vsmsnet.vxd, Smsroutr.vxd, and Vuser.vxd.
- In Autoexec.bat, the call to the Client.bat file is removed. This line will read ‘call client.bat’ or ‘command /c client.bat’.
- Each section in the Smsrun16.ini file is read and an attempt to delete a corresponding program group from Program Manager is made:
- If the group exists, it is deleted.
- If the group doesn’t exist, no error message appears, and the upgrade continues.
- The Startup group is not deleted.
- Cl_Win.mod file content actions are reversed in the order listed in the file.
- All files listed in the Cl_Win.txt file are deleted.
- All files and directories listed in and under the C:\SMS directory are deleted.
- The C:\SMS.ini file is deleted. The client upgrade is complete.