Article ID: 305209 - Last Review: October 25, 2006 - Revision: 2.3 Cannot Upgrade to SMS 2.0 If Any Component Uses the LANDesk Registry KeyThis article was previously published under Q305209 On This PageSYMPTOMS You cannot upgrade a Systems Management Server (SMS) 1.2
client to SMS 2.0 if any software on the client uses the HKEY_LOCAL_MACHINE\Software\INTEL\LANDesk registry key. This may prevent migration for SMS 1.2 clients that
are not running Intel LANDesk software, but instead are running other software
that uses the HKEY_LOCAL_MACHINE\Software\INTEL\LANDesk key, such as Norton
AntiVirus 6.0. CAUSE A previous hotfix for SMS 2.0 implements functionality to
prevent remote control files from being upgraded during a client migration if
Intel LANdesk is detected. This prevents the Intel LANDesk software from not
working after SMS 2.0 is installed. Intel LANDesk is detected if the
HKEY_LOCAL_MACHINE\Software\INTEL\LANDesk registry key exists, even if a
different program installed the key and Intel LANDesk is not installed.
RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:288239
(http://support.microsoft.com/kb/288239/EN-US/
)
How to Obtain the Latest Systems Management Server 2.0 Service Pack Hotfix InformationA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
NOTE: In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The typical support costs
will apply to additional support questions and issues that do not qualify for
the specific update in question.The English post-Service Pack 3 (SP3) version of this fix should have the following file attributes or later: Date Time Version Size File name Platform ----------------------------------------------------------------------- 22-Aug-2001 17:24 2.0.3.0 253,957 Q305209.exe 10-Apr-2001 17:55 2.0.92.1 1,925,391 Ccmcore.exe Alpha 10-Apr-2001 17:55 2.0.1493.3175 4,800,854 Clicore.exe Alpha 01-Mar-2001 17:45 2.0.1493.3170 203,024 Cliex32.dll Alpha 01-Mar-2001 12:55 2.0.1493.3112 125,712 Clisvcl.exe Alpha 01-Mar-2001 17:55 2.0.1493.3175 13,584 Cliver.exe Alpha 01-Mar-2001 17:55 67 Compverbase.ini 01-Mar-2001 17:40 2.0.1493.3169 66,832 Cqmgr32.dll Alpha 01-Mar-2001 17:55 2.0.1493.3175 578,832 Migrat1x.exe Alpha 01-Mar-2001 13:00 2.0.1493.3125 578,832 Mslmclin.dll Alpha 01-Mar-2001 13:00 2.0.1493.3125 259,936 Bindclin.dll X86 10-Apr-2001 17:55 2.0.92.1 1,324,282 Ccmcore.exe X86 10-Apr-2001 17:55 2.0.1493.3175 3,658,842 Clicore.exe X86 01-Mar-2001 17:45 2.0.1493.3170 128,864 Cliex32.dll X86 01-Mar-2001 12:55 2.0.1493.3112 88,432 Clisvcl.exe X86 01-Mar-2001 17:55 2.0.1493.3175 8,512 Cliver.exe X86 01-Mar-2001 17:55 67 Compverbase.ini 01-Mar-2001 17:40 2.0.1493.3169 39,264 Cqmgr32.dll X86 01-Mar-2001 17:55 2.0.1493.3175 383,296 Migrat1x.exe X86 01-Mar-2001 13:00 2.0.1493.3125 338,272 Mslmclin.dll X86 01-Mar-2001 13:00 2.0.1493.3125 269,664 Ndsclin.dll X86 05-Feb-2001 20:51 2.0.1250.7 762,688 Preinst.exe X86 STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft Systems
Management Server 2.0 Service Pack 5. MORE INFORMATIONHotfix Installation InstructionsApply the hotfix that is mentioned in this article to all sites in the SMS hierarchy. To install the fix, use one of the following methods.How to Use the Hotfix InstallerNOTE: You can use this method only on Intel-based computers.
How to Manually Install the Hotfix
| Article Translations
|
Back to the top
