This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
If you're having sync problems or seeing an update dated 3008 with Tuesdays catalog then this one's for you:
The June 10, 2008 release of the WSUS Offline Scan Catalog (wsusscn2.cb) fails to synchronize on a ConfigMgr 2007 or ConfigMgr 2007 SP1 site server using the Inventory Tool for Microsoft Updates (ITMU). This prevents security update deployments to SMS 2003 clients for the June release. This is a result of an issue with updated content published for the Office 2003 Service Pack 1 update.
The issue can be identified in the Wsyncmgr.log on the ConfigMgr 2007 site server with the following entries:
// 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 //
A new catalog is under development at the highest priority and will be made available for automated download as soon as it has been tested.
J.C. Hornbeck | Manageability Knowledge Engineer
We recently posted some new information regarding the inability to deploy updates to SMS 2003 clients.
132 Microsoft Team blogs searched, 105 blogs have new articles in the past 30 days. 641 new articles