Reset WSUS in SCCM to start from scratch

Question

Have done these steps: >

I. REMOVE SUP and WSUS

1. Remove SUP role from SCCM console. Check the SUPSetup.log to check when the removal was successfull.
2. Run Administrative PowerShell to remove WSUS role and management tools:

Remove-WindowsFeature -Name UpdateServices,UpdateServices-DB,UpdateServices-RSAT,UpdateServices-API,UpdateServices-UI -IncludeManagementTools

3. Remove the Database WSUS (SUSDB.mdf and SUSDB_log.ldf). Make sure to remove the entire C:\Windows\WID folder a. If WSUS used the Windows Internal Database (WID), specifically delete the SUSDB.mdf and SUSDB_log.ldf in

C:\Windows\WID\Data

or

C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data for Server 2008/2008 R2

Remove the WID feature from powershell: Remove-WindowsFeature -Name UpdateServices-WidDB Make sure to remove the entire C:\Windows\WID folder too

b. If WSUS used SQL, detach the database from the local server instance and physically delete the SUSDB.mdf and SUSDB_log.ldf or re-name it in case you need it as a backup.      

4. Open IIS and manually remove the ‘WSUS Administration’ website and the ‘WsusPool’ Application Pool if they still exist
5. Rename the WSUS Content folder wherever you had it previously installed (eg. C:\WSUS, or D:\WSUS)
6. Reboot server

WSUS should now be completely gone from your server.

https://cybersoda.com/configmgr/f/fix-wsus-role-on-the-sccm-sup but i still have updates in "All Software Updates" in the sccm console?

how do i empty this to start from zero again? Somehow i manage to get old update to windows 7 and server 2008 but only needed windows 10 updates.

![38090-image.png][1] [1]: /api/attachments/38090-image.png?platform=QnA

Answer 1

@Longquo
Thank you for posting in Microsoft Q&A forum.
There is no way to empty these updates directly.
You can configure the WSUS and SUP first and when a full software update point synchronization runs, the updates that missing from WSUS will be expired.
Expired updates still show up in the console , but they are marked as expired. They will remain in the console for 7 days following expiration, where the next process around cleanup starts.
After 7 days, expired updates that are not associated with active deployments , are tomb-stoned. This means they are no longer visible in the UI.
You may read this article for more details:
https://techcommunity.microsoft.com/t5/configuration-manager-archive/software-update-content-cleanup-in-system-center-2012/ba-p/273069

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.