wilbywilson Posted June 25, 2014 Report post Posted June 25, 2014 I'm running SCCM 2012 R2 CU1, with a standalone Primary. The Primary has WSUS installed, but the actual SUS database lives on a separate SQL server (which also holds the main SCCM database.) It looks like SCCM 2012 has some nice new features which automatically remove expired and superseded patches from the SCCM console. It also appears that if you "edit the membership" of an expired patch, and remove it from any associated software groups, the files are subsequently removed from any distribution points with that package. But I believe that the WSUS "source" files on the main Primary server still remain. I know that people say not to mess with the WSUS console (only configure the SUP settings within the SCCM console), but I know there is a Cleanup Wizard in there, and that would likely get rid of the source files and permanently remove expired/superseded updates, if you ran it. So, what is the recommended best practice here? Are people running the WSUS cleanup wizard periodically? If my SUS database lives on a remote SQL server, would that cleanup routine even work for someone in my scenario? Thanks for any recommendations. I'm not having any performance issues right now, but I'd like to keep things running tightly. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 25, 2014 Report post Posted June 25, 2014 I won't call it a best practice, but it shouldn't be a problem to run the cleanup wizard. The reason why you shouldn't touch the console is more based on not changing any configurations. Quote Share this post Link to post Share on other sites More sharing options...
