Anyone know of a way to completely wipe WSUS of updates and start again?
It seems as if I have loads of language packs and assorted rubbish in the list which we do not need. Having now removed all the unwanted Products, Classifications and Languages what I would like to do is completely clean out the WSUS database and start again. It appears that uninstalling the reinstalling the WSUS role does not help they are all still there. Have also tried the Server Cleanup wizard which seems to be mostly a waste of time, it didn't clean up any of the updates I was hoping it would remove.
I haven't yet installed any of these on a machines yet so if only I could work out how I could completely wipe all listed updates and start again but according to my new reduced Products list.
Thanks, Nick
To re-install WSUS with a clean database i.e. no previous configuration:
Run Windows Powershell as Administrator and use the following commands:
Uninstall-WindowsFeature -Name UpdateServices,Windows-Internal-Database -Restart
Post restart, delete EVERYTHING in the
C:\Windows\WID\
(for Win 2012 r2) folder.Then run the following command to re-install WSUS:
This only works on PowerShell 3 or higher.
More info here: Microsoft TechNet: Removing Server Roles and Features
Answer now found, just posting this for the benefit of anyone else who might come across this problem.
It seems that uninstalling
WSUS
andWID Database
option does not actually remove the WID database.The WID database can be removed by uninstalling the
Windows Internal Database
feature.You will also need to manually delete the file
C:\windows\WID\Data\susdb.mdf
before re-installing everything again.Use official instructions
There is now an official blog post out:
This is my unofficial summary of the official blog post:
For WS2012/WS2012R2: Connecting to the Windows Internal Database requires the use of a Named Pipes connection. The connection string you want is:
\.\pipe\MICROSOFT##WID\tsql\query
For WS2003/WS2008/WS2008R2: Connecting to the Windows Internal Database requires the use of a Named Pipes connection. The connection string you want is:
\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query