RELATED IDEAS
Remove Expired ConfigMgr Updates From UpdateServicesPackages and WSUSContent
With the introduction of ConfigMgr updates our UpdateServicesPackages and WSUSContent folders on our SCCM distribution point are not purging updates that have expired from Configuration Manager. Manually purging these takes a significant amount of time as we need to coorilate GUIDS to ensure the update is actually expired. Please add functionality to RMS/Patching to delete expired updates from our content folder locations. Automating or even providing a manual option in RMS would save us a significant amount of time.
Thanks for the idea. Our preference is to let the existing Configuration Manager and WSUS maintenance tasks handle the cleanup of expired updates rather than introducing a separate cleanup mechanism within RCT Patching at this time. We do see value in helping administrators manage update state directly from the ConfigMgr console however. For that reason, we have a related idea to add on-demand decline and undecline actions for software updates (https://ideas.recastsoftware.com/ideas/RCT-I-46), which would provide a simpler way to manage updates without resorting to scripting. If you think that would be helpful please upvote or comment on it!
Thanks for the feedback and for helping us identify areas where we can improve the update management experience.
We have created instructions on how to change the default settings so that updates are expired and cleaned up sooner: https://docs.recastsoftware.com/help/patching-remove-expired-software-updates. We are also looking for an option to decline any WSUS update with RCT core actions (regardless if the update was added by RCT Patching or not).