Morning,

Today, I am use ADR to deploy security and critical updates to a few servers and its working great so far!  I have the deployment set up to "Add to an existing Software Upgrade Group" as well.

The problem I am running into is the source files are piling up with updates from months ago.  What is the best way to manage those so the drive doesn't fill up?

Shawn

Are you on SP1? Microsoft introduced automatic source file clean up with it.

I am on SCCM 2012 SP1 CU1.  Guess the question would be how do I verify it is working or do I need to enable it somewhere? :)

I see what you mean now.  Looks like it deleted expired updates.  So my problem is that the package source folders have updates that are not expired but are already installed on the servers.  These updates are NOT in the Update Groups as its only using updates from the last two months.  These updates are from months prior.

Have you tried the Server Cleanup Wizard in the WSUS console? I found out about this six months after I started pushing updates and it cleaned over 10Gb of data. 

http://technet.microsoft.com/en-us/library/dd939856(v=ws.10).aspx

 

I gave this a try and it did not remove any files from the Package Source on any of my ADR's.  Said zero files deleted.  Make me wonder if I am doing something wrong in the way I am managing my update deployments.

Shawn

These updates are NOT in the Update Groups as its only using updates from the last two months.  These updates are from months prior.

Update group membership does not matter. Just find those updates in the update *packages* (column: deployed=no) and delete them manually (from within the package).

Thank you Torsten!  Would this be possible using PowerShell to remove the non-deployed updates?

http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx

Everything this link provides has been included in SP1.  Its not the expired updates I am worried about, its the "No Longer Needed" ones I want to have removed from the Deployment Packages.

Shawn

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.