Hi,
I was going to post the question below but think I have found my answer in this post below:
When I remove the membership of superseded updates from all SUGs I understand that they are deleted from SCCM after 7 days. Does this also include being removed from the Deployment Packages these superseded updates were in? Also, what happens in the source location where they were previously downloaded to and stored? Do they get deleted from there automatically also - if not, how can I track them down to manually delete them? I've seen the below post from three years back about expired updates and that you have to use a script to delete them but wondering if its different with superseeded updates or if anything has changed since then - I'd rather not use scripts which I'm not 100% sure on how they work.
Script: http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
----------------------------------------------------------------------------------------
Possible answer:
https://social.technet.microsoft.com/Forums/en-US/009466ed-bb21-4601-b3d7-a8d01e3a0ce9/software-updates-superseded-and-expired?forum=configmanagersecurity
- Step 1: Edit the membership of the superseded updates and remove them from all SUGs
- Step 2: Show membership of a Deployment Package and 'delete' all superseded updates (just out of interest...if you delete the whole Deployment Package I assume that all updates, whether superseded or not are deleted?)
- Step 3: Once steps 1 and 2 have been completed no trace of the downloaded updates will be left in your source folder (lots more free space if you are clearing 1058 updates!)
- Step 4: After seven days they will be removed from the software updates library and no longer visible in SCCM
Is this all correct?
Thanks again all.