System Center Configuration Manager 2007 blocked from deploying security updates

Article ID: 954474 - View products that this article applies to.

Technical update: June 17, 2008

Microsoft 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:
http://www.microsoft.com/technet/security/advisory/954474.mspx
(http://www.microsoft.com/technet/security/advisory/954474.mspx)
Expand all | Collapse all

On This Page

SYMPTOMS

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:
Performing legacy sync STATMSG: ID=6709 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" …
Started with command line: C:\Program Files\Microsoft Configuration Manager\bin\i386\updatewuscatalog.exe …
Processing security catalog C:\Program Files\Microsoft Updates Inventory Tool\PkgSource\wsusscn2.cab ...
Initializing catalog C:\Program Files\Microsoft Updates Inventory Tool\PkgSource\wsusscn2.cab for synchronization.
Pre-processing updates...
Error 0x80004005, Unexpected DeploymentAction for update 1293995. Returned from CreateUpdateNode
Updates summary: 0 processed, 0 matched, 0 outdated, 0 updated
Back to the top | Give Feedback

CAUSE

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.
Back to the top | Give Feedback

RESOLUTION

Service Pack Information

To 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
(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:
971348
(http://support.microsoft.com/kb/971348/ )
List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image
Download
Download the Update for System Center Configuration Manager 2007 package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=26BBF6D0-C430-430D-9D83-CCF1AF0704A9&displaylang=en)


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:
119591
(http://support.microsoft.com/kb/119591/ )
How to obtain Microsoft support files from online services
Microsoft 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.

System Center Configuration Manager 2007

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Updatewuscatalog.exe4.0.5931.142132,53601-Jan-200809:25x86

System Center Configuration Manager 2007 Service Pack 1

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Updatewuscatalog.exe4.0.6221.1102132,02416-Jun-200819:49x86SP1
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.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

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:
WARNING: Unexpected DeploymentAction of Evaluate for update 1293995
Back to the top | Give Feedback

Properties

Article ID: 954474 - Last Review: June 19, 2008 - Revision: 3.1
APPLIES TO
  • Microsoft System Center Configuration Manager 2007
Keywords: 
atdownload kbexpertiseinter kbinfo kbsecadvisory kbsecurity kbsecvulnerability KB954474
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top