WSUS cleanup

Forums › IT Pro and developers › WSUS cleanup

1101

1538 posts

Uber Geek
+1 received by user: 349

Topic # 185668 1-Dec-2015 11:24

Hi guys.
More a general question than for 1 specific instance

On SBS2008/2011 servers, where WinUpdate Services has NEVER been maintained ....

Win Update services stops working properly,workstations no longer get updates, WSUS folder gets huge (70G+)
any attempt to use the cleanup tool or remove unwanted updates will throw out the "reset server node" timeout error

Obviously a mess . From the research Ive done, fixing unmaintained WSUS isnt going to be easy. Freeing up all that space used by WSUS is often a priority as often the HD is lacking free space.

So, change policies so Workstations download updates direct from MS, just to get that working , set Update services to not
store updates on the server (to stop WSUS content folder getting any larger)
Any suggestions as to cleaning up WSUS , when its a bit of a mess ?

redherring

67 posts

Master Geek
+1 received by user: 30

Reply # 1438451 1-Dec-2015 11:49

One person supports this post

I've done this a few times, it usually comes down to uninstall WSUS, delete all folders, reinstall WSUS and set it up how you like it. by default SBS will sync updates for a lot of products you probably don't have, so ignore the SBS integration and just use WSUS from its own console.
If you don't want to manage it too much, set up critical and security updates to automatically approve and use Invoke-WsusServerCleanup powershell command to clean up the database and old updates periodically.

CitizenErased

136 posts

Master Geek
+1 received by user: 31

Reply # 1444578 9-Dec-2015 15:28

SBS is a special case. Even though the WSUS console has a tick in the "all products" box, it will only download updates for products detected on your WSUS clients. Modifying WSUS settings from the WSUS console rather than the SBS console will break the integration.

CitizenErased

136 posts

Master Geek
+1 received by user: 31

Reply # 1444581 9-Dec-2015 15:35

Here's a solution to the OP's problem.