Logs of an SMS Administrator at myITforum.com

Losing Hair Daily in the Name of Technology

Syndication

Blog to Blog

Some of My Favorite Web Sites

SMS 2003 - Security Compliance - Manually Updating WSUSSCN2.CAB

The Microsoft Update Sync Tool is installed on a client computer you define. On a schedule you can also define, the Sync Tool will have the client connect to Microsoft and download the latest WSUSSCN2.CAB file. It then compares this file to the same file on the Site Server housing the ITMU. If the files are different, it copies the file from the Sync client to the Site Server, updates the distribution points and updates the site catalog. There will eventually come a time when you are forced to manually update the WSUSSCN2.CAB file within SMS. Here are a couple of ways to manually update this file.

  1. Go to a command prompt
  2. Switch to the directory where the Microsoft Update Tool is installed. By default it should be in C:\windows\system32\VPCache\[Package ID] where PackageID is the SMS-defined numeric ID for your Update Tool package.
  3. Type the following command at the command prompt and press ENTER: Syncxml.exe /s /unattend /site SiteServer /code SiteCode /package PackageID /target PackageSourceFolder where SiteServer is the name of the Site Server, SiteCode is the Site Code of the Site Server which owns the Windows Update Tool package, PackageID is the SMS-defined numeric ID for your Update Tool package and PackageSourceFolder is the path to the Update Tool source files. (By default this path is C:\Program Files\Microsoft Updates Inventory Tool\PkgSource and it is shared as PackageSrc so the path would be \\[SiteServerName]\PackageSrc)

You can watch the progress of the update process by checking out WUSSyncXML.log file on the Sync Client computer.

This log was taken from an automated sync, but the manual sync will look similar: (Check the comparison line in bold.)

Initialized log file - SyncXML started at 5/22/2007 11:18:30 AM Software Updates Scan Helper 1/1/1601 12:00:00 AM 613 (0x0265)
Sync task started with command-line = /s /site [SiteServer] /code [SiteCode] /package [PackageID] /target \\[SiteServer]\PackageSrc Software Updates Scan Helper 1/1/1601 12:00:00 AM 613 (0x0265)
User Account: [UserAccount] Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
User Profile: C:\Documents and Settings\[UserAccount] Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Command line specified folder to update as \\[SiteServer]\PackageSrc. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Command line specified package to update on DPs as [PackageID] Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Command line specified site code: [SiteCode]. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Command line specified site server: [SiteServer]. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Download completed - http://go.microsoft.com/fwlink/?LinkID=74689 Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Download completed successfully. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Trying to calculate hash on C:\DOCUME~1\SMSSER~2\LOCALS~1\Temp\wsusscn2.cab. Software Updates Scan Helper 5/22/2007 11:18:49 AM 788 (0x0314)
Trying to calculate hash on \\[SiteServer]\PACKAGESRC\wsusscn2.cab. Software Updates Scan Helper 5/22/2007 11:18:49 AM 788 (0x0314)
C:\DOCUME~1\[UserAccount]\LOCALS~1\Temp\wsusscn2.cab and \\[SiteServer]\PACKAGESRC\wsusscn2.cab were found to be different. Software Updates Scan Helper 5/22/2007 11:19:02 AM 788 (0x0314)
Copied C:\DOCUME~1\SMSSER~2\LOCALS~1\Temp\wsusscn2.cab to \\[SiteServer]\PACKAGESRC\wsusscn2.cab. Software Updates Scan Helper 5/22/2007 11:20:32 AM 788 (0x0314)
Updating Distribution Points for Package: [PackageID], Site: [SiteServer], SiteCode: [SiteCode], Source dir: \\[SiteServer]\PackageSrc Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Distribution Points updated successfully. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Checking if patch preapprovals are supported by site [SiteServer] Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Patch preapprovals are supported by site [SiteServer], proceeding with catalog updates Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Updating site catalog: CATALOG="\\[SiteServer]\PACKAGESRC\wsusscn2.cab" TYPE="Microsoft Update" SERVER=[SiteServer] SITE=[SiteCode] PACKAGE=[PackageID] LCID=1033 MAXAGE=0 ADDLOC= LOGFILE="C:\WINDOWS\system32\CCM\Logs\WUSSyncXML.log" VERBOSE=2 Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:35): Processing security catalog \\[SiteServer]\PACKAGESRC\wsusscn2.cab ... Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:35): Connected to \\[SiteServer]\root\sms Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:36): Connected to \\[SiteServer]\root\sms\site_[SiteCode] Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:36): SMS_ApplcableUpdatesSummaryEx class does not support ScanPackageID property, link records will be inserted separately Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:37): Loading updates cache from database Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:41): Loaded cache with 2742 updates from database Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:20:41): Initializing catalog \\[SiteServer]\PACKAGESRC\wsusscn2.cab for synchronization. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:21:17): Synchronizing updates from the catalog to the database. Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:24:51): Parser summary: 14685 processed, 1767 matched, 0 outdated, 0 updated Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:24:51): Database summary: 0 writes requested, 0 inserted, 0 updated Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
UpdateWUSCatalog(11:24:51): Processing time: 0d 00h 04m 16s Software Updates Scan Helper 1/1/1601 12:00:00 AM 5429368 (0x52D878)
Loaded "C:\WINDOWS\system32\CCM\smscstat.dll"; the module handle is 0x188A0000. Software Updates Scan Helper 5/22/2007 11:24:52 AM 788 (0x0314)
CreateSMSStatusMessage() succeeded; the status message object handle is 0x01A2F7E8. Software Updates Scan Helper 5/22/2007 11:24:52 AM 788 (0x0314)
ReportSMSStatusMessage() succeeded. Software Updates Scan Helper 5/22/2007 11:24:53 AM 788 (0x0314)

Should the scan files be the same on the Sync client and the Site Server, the following two lines will be located directly after the file comparisons:

C:\DOCUME~1\[UserAccount]\LOCALS~1\Temp\wsusscn2.cab and \\[SiteServer]\PACKAGESRC\wsusscn2.cab were found to be same. Software Updates Scan Helper 5/21/2007 10:00:22 PM 1608 (0x0648)
Distribution points will not be updated. Software Updates Scan Helper 1/1/1601 12:00:00 AM 1608 (0x0648)


Another method to accomplish this manually is: (you will not be able to watch the process and will have to manually compare the files on the Sync Client and the Site Server.)

  1. Download the WSUSSCN2.CAB file from http://go.microsoft.com/fwlink/?LinkID=74689
  2. Copy this file into the PackageSrc folder on the Site Server owning the Microsoft Update Tool package.
  3. Within the SMS Console, update the distribution points for the Microsoft Update Tool package

I hope this helps some people.

Published Tuesday, May 22, 2007 4:28 PM by mlucero
Filed under:

Comments

No Comments