ConfigMgr 2007: When upgrading from the SMS 2003 client to the ConfigMgr 2007, installation fails due to not being able to remove SMS 2003 remote control drivers

When upgrading from the SMS 2003 client to the ConfigMgr 2007, the ccmsetup installation fails due to not being able to remove SMS 2003 remote control drivers.  Examining the CCMSetup.log we see the following errors:

MSI: Action 8:25:34: RemoveW2KDrivers. Removing Remote Control drivers
ccmsetup is shutting down
Shutdown has been requested
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602.
MSI: Action 15:14:28: SmsRemovePatchManagerService.
Shutdown has been requested
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602.
MSI: Internal Error 2502.
Shutdown has been requested
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602.
Installation was cancelled (1602)

Examining the client.msi.log we see the following errors:

MSI (s) (B4:4C) [08:25:34:814]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI13.tmp, Entrypoint: RemoveW2KDrivers
Action start 8:25:34: RemoveW2KDrivers.
RCSvcs: Entering RemoveW2KDrivers
RCSvcs: RemoveNT5Devices: Starting removal of Win2K device drivers
RCSvcs: FindDevice(*SMS_MOUSE): found SMS Virtual Mouse
RCSvcs: RemoveNT5Device(*SMS_MOUSE) succeeded
RCSvcs: InstallNT5Device(*SMS_KEYBOARD): SetupDiGetClassDevs failed, error 0xd
RCSvcs: RemoveNT5Device(*SMS_KEYBOARD): FindDevice failed, error 0
RCSvcs: RemoveNT5Device(*SMS_KEYBOARD) succeeded
RCSvcs: InstallNT5Device(*SMS_DISPLAY): SetupDiGetClassDevs failed, error 0xd
RCSvcs: RemoveNT5Device(*SMS_DISPLAY): FindDevice failed, error 0
RCSvcs: RemoveNT5Device(*SMS_DISPLAY) succeeded
RCSvcs: RemoveNT5Devices: succeeded
RCSvcs: Leaving RemoveW2KDrivers
MSI (s) (B4:44) [15:14:28:500]: Doing action: SmsRemovePatchManagerService
Action ended 15:14:28: RemoveW2KDrivers. Return value 1.
MSI (s) (B4:44) [15:14:28:516]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 19
MSI (s) (B4:44) [15:14:28:516]: Note: 1: 2502
DEBUG: Error 2502:  Called InstallFinalize when no install in progress.
MSI (s) (B4:44) [15:14:28:547]: Product: Configuration Manager Client -- Internal Error 2502.

MSI (s) (B4:44) [15:14:28:547]: No System Restore sequence number for this installation.
MSI (s) (B4:44) [15:14:28:547]: Unlocking Server
MSI (s) (B4:44) [15:14:28:547]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 19
MSI (s) (B4:44) [15:14:28:547]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 19
MSI (s) (B4:44) [15:14:28:547]: PROPERTY CHANGE: Deleting RESUME property. Its current value is '1'.
MSI (s) (B4:44) [15:14:28:547]: PROPERTY CHANGE: Deleting Resume property. Its current value is '1'.
MSI (s) (B4:44) [15:14:28:547]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Internal Error 2502.
Action ended 15:14:28: INSTALL. Return value 2.

This issue could be caused due to permissions on registry keys for the SMS 2003 remote control drivers (Mouse, Keyboard) not being set correctly. In particular, the SYSTEM account may not have Full Control to the keys and subkeys. Since the SYSTEM account is used to install the ConfigMgr 2007 client when doing client push, if the permissions of these keys are not set correctly for SYSTEM to have Full Control, it will not be able to remove the old SMS 2003 remote control drivers that are no longer used or needed in ConfigMgr 2007 and the installation will fail.

Open Regedit and under the key HKLM\SYSTEM\CurrentControlSet\, do a search for

kbstuff

Kbstuff is the name of the driver and service associated with SMS 2003 remote control. Any key that refers to kbstuff and any subkeys should have permissions set for SYSTEM having Full Control. When setting the permissions, make sure that permissions propagate down. In particular, check the key

HKLM\SYSTEM\CurrentControlSet\Enum\Root\*SMS_MOUSE

and make sure it has proper permissions.

After setting the permissions correctly, rerun the installation and the installation should succeed.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.