Article ID: 252718 - View products that this article applies to.
This article was previously published under Q252718
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When a Systems Management Server (SMS) client that has been discovered by an SMS 2.0 Service Pack 2 (SP2) site server resides inside the site boundaries of an SMS 2.0 release version (build 1239) site, that site's Client Configuration Manager (CCM) attempts to install the remaining client components and optional client agents. This can potentially place the client in an unstable condition.
A supported fix that corrects this problem is now available from Microsoft. This fix is one of two fixes that are required for SMS 2.0 sites without Service Pack 1 (build 1239) before any site can be upgraded to SMS 2.0 SP2. This fix is included in the Smsqfe folder on the SP2 CD-ROM. Detailed instructions for hotfix installation are also included in the Release Notes that accompany the service pack.
For additional information about the accompanying fix that you must apply to SMS 2.0 sites without Service Pack 1 (build 1239), click the article number below to view the article in the Microsoft Knowledge Base:
251070For additional information about these fixes and similar fixes that you must apply to SMS 2.0 sites with Service Pack 1 (build 1380), click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/251070/EN-US/ )SMS: Copylog.tcf File Does Not Reflect Which Site Last Updated the Logon Point
261931To avoid the condition described in the "Symptoms" section of this article, you must apply the fix described in this article to all SMS 2.0 sites without Service Pack 1 (build 1239) before any site is upgraded to SMS 2.0 SP2. Click the following file name to download the file from the Microsoft Download Center:
(http://support.microsoft.com/kb/261931/EN-US/ )SMS: Required Hotfixes Before Installing SMS 2.0 SP2
WARNING: This hotfix may not install on some secondary sites even though the hotfix installation may appear to run successfully. These hotfixes check for the existence of the Full Version value in the following registry key:
Download Q252718.exe now
Collapse this imageExpand this image
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\SetupIf you have secondary sites that were either installed or upgraded directly from the primary site, this key may not be created or properly updated. Before applying this hotfix, please verify the existence of this key on all secondary sites. The Qxxxxxx.log file that is generated when you install the hotfix will state that the version is 000. To correct this, manually create or update the registry value. To create or update this value on secondary sites, use the following steps.
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.
The English-language version of the fix should have the following file attributes or later:
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
Date Time Version Size File name Platform -------------------------------------------------------------------- 1/28/2000 11:12AM 2.0.1239.64 137 KB Ccm.dll Intel 1/28/2000 11:12AM 2.0.1239.64 386 KB Ccmbtldr.exe Intel 1/28/2000 11:13AM 2.0.1239.64 217 KB Ccm.dll Alpha 1/28/2000 11:13AM 2.0.1239.64 625 KB Ccmbtldr.exe Alpha
Refer to the "More Information" section of this article for installation instructions. For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/EN-US/ )How to Obtain Microsoft Support Files from Online Services
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.
This hotfix is required for interoperability between SMS 2.0 sites without Service Pack 1 (build 1239) and SMS 2.0 SP2 sites.
NOTE: You must install this hotfix on all SMS sites that share a domain with other SMS sites.
To install the hotfix update, use the appropriate method.
Method 1: Using the Update InstallerNOTE: This method is only for Intel-based computers.
Method 2: Manual Installation
How to Manually Update a Remote SMS SQL Monitor ServerNOTE: Before you implement this update on your SMS site database server, you must install the update on the SMS site server(s) in your environment.
To update a remote SMS SQL Monitor server, use the following steps:
Manually Updating a Remote SMS ProviderThis section describes how to implement SMS 2.0 QFE updates to the SMS Provider when it is running on a computer other than the site server.
NOTE: Before you implement this update on your SMS Provider server, you must install it on the SMS site server(s) in your environment.
To update a remote SMS Provider:
How to Manually Update a Remote SMS Administrator ConsoleThis section describes how to implement SMS 2.0 QFE updates to the SMS Administrator console when it is running on a computer other than the site server.
NOTE: Before you implement this update on your SMS Administrator console, you must install it on the SMS site server(s) in your environment.
To update a remote SMS Administrator console, use the following steps: