Re:SCCM/WSUS Patch Cleanup Best Practices (klopez)

Thu, 02 Aug 2012 16:50:50 GMT

I personally cleanup expired and superseded updates from the Update Lists and Deployments on a monthly basis (typically the day after Microsoft releases patch on the second Tuesday of the month). Doing this will not reclaim disk space, it only prevents the deployment specialists from deploying patches that have been superseded. Every 6 months I will then clean up the Deployment Packages, I will remove the expired and superseded updates through the ConfigMgr Admin console. There is no need to touch the WSUS Console at all. When you removed updates for the deployment packages it will trigger ConfigMgr to update the packages on the DPs they have been assigned to. This is why I only do it twice a year, I have over 180 DPs and some on very slow links and I want to prevent WAN impact. Sometimes ConfigMgr may resend the entire package down when it should only be removing what is no longer needed because the package may have corrupted on that DP for some unknown reason. So keep that in mind if you have alot of DPs on slow links.

Here are some articles of reference: ?

I personally used this page when first learning ConfigMgr 2007:

Hope this helps!

SCCM/WSUS Patch Cleanup Best Practices (jdenzik)

Wed, 01 Aug 2012 08:04:43 GMT

I inherited a SCCM 2007 system and the patches are filling up the drive...I am trying to find the best way to clean up the patches on my server to free up the drive space. I currently have MS update packages setup by year....2009,2010,2011,2012. I see one place where the patches exist. D:\Microsoft Updates\MS_Security_2009...etc, and the folders correlate to the name of the packages on my server. Do they exist in another place? If I use the WSUS cleanup tool to remove updates will it remove it from the console? The console only shows superseded updates, no expired ones. All my images are up to date. Can I get rid of all the superseded updates?

-Thanks

Newbie.