There is a practice to run the WSUS clean-up task from WSUS console. Is that the best practices from SCCM perspective when that WSUS is used as part SUP? But, the cleaning up WSUS is a very important activity for SCCM admins to have healthy SUP and SCCM environment. There are two options to setup WSUS cleanup maintenance scheduled task from SCCM console. In this post, we will see How to Setup WSUS Cleanup Task from SCCM console.
First Option to setup WSUS Cleanup Maintenance Activity from SCCM console?
In SCCM CB, there is an option to schedule the WSUS cleanup while setting up the SUP site system role. This option is part of SUP setup wizard in Supersedence Rules page.
This is good initiative as running the WSUS clean up wizard from WSUS console was against the best SCCM practices. The SCCM best practice is NOT to open WSUS console and perform any changes from WSUS console when you are using SUP.
Second Option to setup WSUS Cleanup Maintenance Activity from SCCM console?
The second option to schedule the WSUS cleanup for your SCCM environment is under settings – Configure Site Components – Software Update Point (SUP) Component properties – Supersedence Rules TAB. This option is useful when you forget to enable the WSUS Cleanup task during the installation of SUP on your SCCM CB server.
When you select to run the WSUS clean-up task from SCCM console, it will run at the next software updates synchronization.The expired software updates are set to a status of declined on the WSUS server., and the Windows Update Agent on computers will no longer scan these software updates. More details are available here.
Will WSUS Cleanup Task from SCCM console Applicable for Multiple SUPs and Secondary site SUPs?
I have not tested this for secondary site SUPs and multiple SUPs on the same site with Windows Internal Database. But, I think, it’s the same when you have multiple secondary site SUPs and multiple SUPS on the same site.
If in case the WSUS cleanup task configured in SCCM CB console is not working as expected then, it’s better to raise a support case with Microsoft or run the WSUS clean-up wizard from WSUS console.
