MECM Updates Source directory clean up

Michael Pawlak 21 Reputation points
2022-01-19T19:57:40.89+00:00

I have seen this asked in the past and I have seen use of the contentclean script to clean expired updates from Software update groups that are not automatically getting cleaned up.

I have instances where a SUG is created for a year end wrap up (eg Updates 2015 and earlier) and have been distributed to the DPs. Can I simply remove the source folders for the older year(s) SUGs since they should not be updated anymore or do I need to keep them around on the primary?

I am just trying to reclaim disk space...

https://techcommunity.microsoft.com/t5/configuration-manager-archive/software-update-content-cleanup-in-system-center-2012/ba-p/273069

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Jason Sandys 31,151 Reputation points Microsoft Employee
    2022-01-20T20:23:15.947+00:00

    In general, I would never specifically delete anything from the source folders as these should correspond to an update downloaded and most likely deployed in the console thus delete the source file could break the deployment (assuming the package gets updated at some point as well). If they need or want to reclaim disk space, then they need to clean up the deployed updates in the console first although really, adding disk space is advisable here also because as noted, 210GB is not all that miuch.


5 additional answers

Sort by: Most helpful
  1. Michael Pawlak 21 Reputation points
    2022-01-20T19:04:23.95+00:00

    Thanks again, given the concern of the size of these sources overall, can some of them be deleted from the sources folder or is it wise to keep the source folders since the deployments are still active even if the content has been distributed? If best practice to leave them as is then I will advise they plan for capacity going forward.

    0 comments No comments