[Today's post has been provided by Fei Xia ]
System Center Updates Publisher (SCUP) helps users to publish their private updates to Windows Server Update Services (WSUS) and synchronize the updates in Configuration Manager 2007. Typically users synchronize these updates with WSUS by clicking " Run Synchronization " in the Configuration Manager console. This manual synchronization process does not synchronize the " Expired " flag from WSUS to Configuration Manager, so when you want to expire an update by using SCUP and then run the manual synchronization, the log (SMSlogs wsyncmgr.log ) would read "No changes made to the SMS database" as follows:
This behavior occurs because the manual synchronization process does not synchronize the expired flag for an existing update, which is only performed by the scheduled synchronization process. Use the following workaround to synchronize expired software updates by using a scheduled synchronization.
WORKAROUND:
-
Open the SCUP console, and then select and expire the software update that you want to expire.
-
Set the "Publish" flag on the software updates, and then click
Publish Update
to re-publish it. The software update record in WSUS database is flagged as "
Expired"
.
Record in WSUS Database:
-
Open the Configuration Manager console, navigate to
Site Management->[Site Code]->Component Configuration->Software Update Point
, open the properties, and make sure the
“Enable synchronization on a schedule”
setting is checked.
Note: Default is 7 days. You could also set a custom schedule for a quick check.
-
After the scheduled synchronization process completes, check the log (SMSLogs
wsyncmgr.log
). It should read "
Removed 1 unreferenced updates
"
-
Refresh your update list in the Configuration Manager console, and the software update should be flagged as "
Expired
".
-- Fei Xia
This posting is provided "AS IS" with no warranties and confers no rights.
Microsoft
