SCCM WSUS Cleanup

Managing WSUS database in a health state is always a challenging task. In previous versions of ConfigMgr we use to run various scripts to keep the SUP clean. However nre releases changed the way we need to maintain the SUP database.

Since release of ConfigMgr 1906, majority of these tasks automated by introducing;
- Decline expired updates in WSUS according to supersedence rules
- Add non-clustered indexes to the WSUS database
- Remove obsolete updates from the WSUS database

Once you select all three boxes as above, then wait for next Software Update Point sync or Manually run Synchronize Software Updates

Monitor the wsyncmgr.log soon after starting the synchronization;
The long will show;
Index nclLocalizedPropertyID is created succesfully on LocalizedPropertyID in tbLocalizedPropertyForRevision.Server: sccb, DataBase: SUSDB 

Index nclSupercededUpdateID is created succesfully on SupersededUpdateID in tbRevisionSupersedesUpdate.Server: sccb, DataBase: SUSDB 

Done Indexing SUSDB. Custom indexes were created if they didn't exist previously. SCCB 

sync: SMS performing cleanup
Cleanup processed 517 total updates and declined 270 
Done Declining updates in WSUS Server SCCB 

Starting Deletion of ObseleteUpdates 
Obselete Update with Update ID: 699B3503-0221-4C4A-A7B2-DCD74173D11E was deleted. 
Obselete Update with Update ID: C991073F-CA3E-467D-B5A0-C8574B289B96 was deleted. 
Obselete Update with Update ID: 7C087CB2-E64E-4219-BD54-5B6A328B8CC1 was deleted. 
Obselete Update with Update ID: FF654FD2-3739-4D11-BC51-2B44EB40D616 was deleted.  

Once all the criteria are met, the log will update number of updates are deleted

Thats pretty much it.
WSUS cleanup made easy with new releases of ConfigMgr.