Over the years we have created half a dozen articles dedicated to cleaning up or fixing WSUS in some way. Recently we had a client that enabled driver updates in WSUS and now regrets it, so he disabled the DRIVERS category in WSUS, but the drivers that already exist will stay until he declines them. The problem now is that keeps getting:
Error: Connection error an error occurred trying to connect to the WSUS server
Reset Server Node
so he can’t into the updates to decline them. We have the fix and it’s not near as complex as it looks here. Just keep reading and you’ll be fine..
The key is to clean up the WSUS database and create (or update) the SQL indexes. That is easier said than done because WSUS uses the Windows Internal database which is a stripped down version of SQL Express which is self a stripped down version of SQL, so you have to do the cleanup through command line. Fortunately the command line is really easy.
Once this clean up is completed:
It wouldn’t be a bad idea to reindex everything again (see step 1) and restart the Windows Internal database service but neither of those are required.
At this point your WSUS should be in great shape. Also it’s important to note that I’ve had some conflicting reports that while the updates may not show all the dates category that they may take up to 8 days to actually be deleted from the database. I can’t speak to that directly but just be aware of it
This website uses cookies.
View Comments
Correct command (missed one "\")
sqlcmd -I -S \\.\pipe\MICROSOFT##WID\tsql\query -i C:\TEMP\WsusDBMaintenance.sql
Good Catch Oleg... FIXED!