Upgrading a 32-Bit Client Computer to SMS 2.0

The client upgrade process begins after you discover a client through any of the methods described in this chapter, provided that the client installation methods relevant to the client’s computer architecture have been initiated. The SMS client software upgrade on 32-bit client computers is a “silent” process, although it does require users to restart their computer. Users will not be aware of the upgrade because no user input is required and no messages appear before or after they restart the computer. You do not need to instruct your users to restart to complete the client upgrade, because they are likely to restart their computer occasionally, and no harm will be done if several days elapse before SMS 2.0 can complete the client upgrade.

Depending on how your SMS 1.2 client was configured, the upgrade process might require a computer restart to start the second procedure. You can determine if a restart is required by verifying whether any SMS 1.2 applications are started automatically by the SMS 1.2 tool SMSrun, 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 a second time before the upgrade is completed.

  To disable automatic component starts and Remote Control in SMS 1.2

1. Open the SMS 1.2 Administrator.
2. Select the site.
3. On the File menu, click Properties.
4. In the Site Properties dialog box, click Clients.
5. In the Clients dialog box, click Proposed Properties.
6. Clear all of the Automatically Start this Component check boxes.
7. Clear the Remote Troubleshooting check box.
8. 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 (32-Bit Clients)

These steps describe the process SMS uses to install the SMS 2.0 client software on a 32-bit computer after you initiate discovery and installation methods in the SMS Administrator console.

1. The Ccmbtldr.exe, Boot32xx.exe or SMSman.exe program starts the upgrade client process. Files are copied to the first fixed drive (usually C), to a location dependent on the user’s local rights.
   • If the user has minimal local permissions, files are copied into the \\%Temp% directory.
   • If the user has full local permissions, files are copied into the %Windir%\MS\SMS directory.
   • On Windows 2000 or Windows NT clients, if no user is logged on, files are copied into the \\%Temp% directory.
   • The security context is changed from the local user to the SMS Service account.

   ---

   Note   For Windows NT Remote Client Installation, Ccmbtldr.exe starts the client upgrade process. For Windows Networking Logon Client Installation, Boot32xx.exe starts the process. If you run the Systems Management Wizard, SMSman.exe starts the process.

   ---

2. Ccim32.dll [Client Component Installation Manager (CCIM)] starts and determines whether the SMS client software needs to be upgraded from SMS 1.2 or installed by searching for the markers described in Table 12.3, “Markers Used by SMS 2.0 to Identify SMS 1.2 Clients.”
3. CCIM unbundles the following files:
   • %Windir%\MS\SMS\Core\Bin\Migratnt.exe or Migrat9x.exe
   • %Windir%\MS\SMS\Core\Bin\Copy1x.exe
   • %Windir%\MS\SMS\Core\Data\Migratnt.ini or Migrat9x.ini

   ---

   Note   Throughout this process, files named *nt.* are used on computers running the Windows 2000 or Windows NT operating systems, and files named *9x.* are used on computers running the Windows 95 and Windows 98 operating systems.

   ---

4. CCIM runs Migratnt.exe or Migrat9x.exe (Migratxx.*).
5. Migratxx.exe starts the executable files referenced in the Migratxx.ini file and performs the following tasks.
   • Copy1x.exe copies the client’s C:\MS\SMS\Noidmif and Idmif directories and their contents to the SMS 2.0 client directory structure.
   • Copy1x.exe copies the hidden Sms.ini file in the root directory of the client computer to the %Windir%\MS\SMS\Core\Data\Sms1x.ini file.
6. Smsrun.exe is removed from the following Windows NT registry key: \HKEY_Users\Software\Microsoft\WindowsNT\CurrentVersion\Window.
7. On Windows NT, the Windows NT Inv32cli, KBstuff, and Wuser32 services are removed if they are inactive. If they are active, they are removed in the next process.
8. The SMS 2.0 client components are installed in the %Windir%\MS\SMS directory.
9. Use Table 12.8 to determine the next steps in the client upgrade process.

Table 12.8 Next Step in the Client Upgrade Process

If a computer restart and/or user logon is indicated in Table 12.8, the second process begins after the user logs off, restarts the computer, and logs on again. This activity is not prompted by SMS, but is probably part of the user’s daily routine.

Starting SMS 2.0 Client Components and Removing the SMS 1.2 Client Software on 32-Bit Clients

SMS completes the installation of client software using this process, with or without a computer restart, as indicated in Table 12.8.

1. The SMS 2.0 services installed in “SMS 2.0 Client Installation Process (32-Bit Client)” are started.
2. Each section in the SMSrun32.ini file is read and the corresponding program group is deleted from the registry through the removal of the \HKEY_Current_User\Software\Microsoft\WindowsNT
   \Current\Version\Windows\Load registry key.
   • If the group exists, it is deleted.
   • If the group does not exist, no error message appears and the upgrade continues.
   • The Startup group is not deleted.
3. The Cl_nt.mod or Cl_w95.mod file content actions are reversed in the order listed in the file.
4. All files listed in the Cl_nt.txt or Cl_w95.txt file are deleted.
5. The SMS 1.2 directory structure under [First Fixed Drive]:\MS is removed.
6. If the computer is running Windows NT, the \HKEY_LOCAL_MACHINE
   \SOFTWARE\Microsoft\SMS\ClientServices registry key is removed.
7. The C:\Sms.ini file is deleted.
8. The Client Registration status in the \HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\SMS\Client\Configuration \SMS1.2ClientMigration registry key is changed to DONE, indicating that the upgrade process was successful.
9. If you 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.
10. If you initiated software inventory in the SMS 2.0 Administrator console, the SMS 2.0 Software Inventory Agent creates a *.sic file and transfers it to the site server.