During SMS 1.2 Client Upgrade Remote Control May Not Complete if the Sms.ini File Is Deleted (262949)

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

SMS 2.0 uses three markers to determine if a client is an SMS 1.2 client:

1. The Sms.ini file.
2. In the SMS registry entry, it checks the load key under HKCU\Software\Microsoft \WindowsNT\CurrentVersion\Windows to see if it contains Smsrun32.
3. It checks the load line in the Win.ini file to see if it contains Smsrun16.exe.

The upgrade from the SMS 1.2 Remote Control components to the SMS 2.0 Remctrl.exe (the SMS 2.0 remote control bundle) consists of two parts: One that depends on migration (Migrat1x.exe) to complete, and another test that it performs separately from the migration.

Migrat1x.exe can only remove the SMS 1.2 components that it knows about. It uses the Sms.ini file as the key to the SMS 1.2 components that are present, and where a component can be found to remove it. If the Sms.ini file is not present, a number of SMS 1.2 components will remain on that client (including Remote Control), because the key to the entire cleanup, or migration process has been removed.

As a result, other client components may not be upgraded either.


The Remctrl.log file generates the following message every time the computer starts: The Install.log for the Remote Control component generates the following message: There is an SMS Client Installation State registry key in the registry that is located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control\Installation Properties. Until migration is completed, and until this key is set to Done (which Migrat1x.exe was unable to set upon completion), SMS 2.0 Remctrl.exe does not try to install Remote Control components. If it were to do so, Migrat1x.exe might unknowingly clean up incoming SMS 2.0 Remote Control components.

If you experience this condition, the migration can be continued by replacing the contents of this registry key with Done, and then restarting the computer, at which point the migration continues.

After the migration is complete, the Remctrl bundle scans all local hard drives for copies of Wuser.exe, and Wuser32.exe. If it finds either of these files, it assumes a third-party Remote Control agent is resident, chooses not to replace it, logs an error in the Remctrl.log file, stops gracefully, and then waits for someone to read the log and make the necessary adjustments so that it can install SMS 2.0 Remote Control at some point in the future.