Although remote control interoperability is available, it is preferable to upgrade the client to the SMS 2.0 level of client software. The upgrade of client-side SMS 1.2 software is automatically performed when the SMS 2.0 client software is installed to the client workstation.
Although a description of the full migration process is beyond the scope of this chapter, the specific issues are detailed below:
When the SMS 2.0 CCIM (Client Component Installation Manager) starts on an SMS 1.2 client, it detects the SMS 1.2 client software and begins a multi-pass migration process. The details of all actions carried out by the migration program are logged to the Migrat1x.log file in the SMS 2.0 client-side %Windir%\MS\SMS\Logs directory.
While the 1.2 to 2.0 migration process is happening, the registry flag
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Client\Configuration
\SMS 1.2 Client Migration
contains the values:
| (Default) | (value not set) |
| AppControl deinstall | “Pending” |
| Overall 1.x migration status | “Pending” |
| Processed migration commands | “Migrate base files” |
| SMS.ini backup path | C:\Windows\MS\SMS\Core\Data\sms1x.ini |
During the migration, the value of Overall 1.x migration status will be Pending. This prevents the Remote Tools client-side package (Remctrl.exe) resident on the client access point (CAP) from installing until the migration is complete. If the Remote Tools component tries to install to the client, it will detect that the migration is still in-progress and will write an entry to the Remctrl.log file.
After the migration is complete (which could require multiple restarts of the client), the Pending flag will be cleared and the Remote Tools component will install on the client. As is the case with any Remote Tools installation, yet another restart is necessary before the low-level services (RCHELP and KBSTUFF or Vuser9x.vxd and Vuser.exe) are enabled.