GrayAndYellowGearsLooks like our very own Fei Xia on the ConfigMgr 2007 Sustained Engineering team wrote up a great blog post on how to expire Software Updates in System Center Updates Publisher and synchronize the expired updates in Configuration Manager 2007.  If you've ever struggled with this or wanted to know more about how it works then this one is for you:

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 (SMS\logs\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.  

To continue reading see Fei Xia's post here.

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002