Skip to main content

Purging Expired Updates in CM12

Got a question at the user group meeting yesterday about expired updates in CM12.

When I look at the source folder for my System Center Endpoint Protection, I see lots of files never being deleted:

You can't just delete them as they're being deployed.  So navigate back to All Software Updates and search for expired updates (and filter criteria for defintions):

Highlight all of these and edit membership to remove them from your EP deployment(s).  From this point, you can't delete them on your own, but being expired and not deployed, CM can delete them and will with a maintenance task each week.  You can't see or edit this task.  I can't find the FAQ published regarding this yet, but this is what it's going to say:

In Configuration Manager 2012, superseded updates that the admin has intentionally kept as deployable (by configuring to allow superseded updates going back X months), will never be removed or deleted by site maintenance.  Expired updates and their associated content on distribution points will be removed by a cleanup task running every 7 days.  Only expired updates that are not associated with a deployment are automatically cleaned up, however.  To remove expired updates from all update groups and deployments so that they are auto-cleaned, simply search for expired updates using the search functionality, select all returned results, choose edit membership, and de-select these expired updates from any update group they are members of.

  • Created on .