Article ID: 954474 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Technical update: June 17, 2008Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, visit the following Microsoft Web site:
You use Microsoft System Center Configuration Manager 2007 or Configuration Manager 2007 with Service Pack 1 (SP1) to deploy updates to Microsoft Systems Management Server (SMS) 2003 clients. In this scenario, the Microsoft Windows Server Update Services (WSUS) Offline Scan Catalog cab file (Wsusscn2.cab) may not correctly synchronize with the site server database when you use the Inventory Tool for Microsoft Updates (ITMU). This problem may prevent the June 10, 2008 security updates from being deployed to SMS 2003 clients.
Note This problem affects only SMS 2003 clients that are managed in a Configuration Manager 2007 environment. Native Configuration Manager 2007 clients, native Configuration Manager 2007 update deployments, and native SMS 2003 environments are not affected.
When this problem occurs, text that resembles the following may be recorded in the Wsyncmgr.log file on the Configuration Manager 2007 site server:
This problem occurs because of changes that were made for the June 10, 2008 release. Additional metadata that is associated with Microsoft Office 2003 SP1 was added to the Wsusscn2.cab file. The catalog synchronization process (UpdateWUSCatalog.exe) was not designed to handle the specific changes that were made. To resolve this problem, a change has been made to the version of the UpdateWUSCatalog.exe file that is included in this update to accommodate the new metadata. This updated file is installed on a Configuration Manager 2007 site server.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140
For a list of issues resolved in this service pack, click on the following article number in the Microsoft Knowledgebase:
971348The following file is available for download from the Microsoft Download Center:
(https://support.microsoft.com/kb/971348/ )List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
Download the Update for System Center Configuration Manager 2007 package now.
Collapse this imageExpand this image
Release Date: Tuesday, June 17, 2008
For more 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 prevent any unauthorized changes to the file.
(https://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
System Center Configuration Manager 2007
Collapse this tableExpand this table
System Center Configuration Manager 2007 Service Pack 1
Note The date stamp on the SP1 version of UpdateWUSCatalog.exe is set several months ahead of the original hotfix release date. This date stamp was set ahead to prevent conflicts with international versions of ConfigMgr SP1. Microsoft was releasing ConfigMgr SP1 at the time of this writing.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This update can be applied to all site servers. To resolve this problem, the update is only required on the Configuration Manager 2007 sites that synchronize the catalog for ITMU.
After the update has been applied, a warning message that resembles the following may be logged in the Wsyncmgr.log file if an error condition existed: