rickjames Posted May 6, 2015 Posted May 6, 2015 Addressing our WSUS server which just rolls out whatever updates it feels like when we do our imaging process. Had no idea the WSUS Server Cleanup wizard was even available until this morning, selected to clean every item and on it's way. However it seems to just hit a halt deleting unused updates. Server hasn't frozen or anything like that. I should add the WSUS folder is 244gb which could be considered quite large but just wanted to check before deciding maybe something is up.
cullingsh Posted May 6, 2015 Posted May 6, 2015 Some of the ones I look after take an age - I leave them overnight!
Norphy Posted May 6, 2015 Posted May 6, 2015 Ages. Especially if you haven't run it before. Leave it overnight like @cullingsh said.
Oaktech Posted May 6, 2015 Posted May 6, 2015 Our cache is about 160gb. First time I ran it it took 6 hours and 2 resets of the server node to complete. Stopped exactly where your's has. Subsequent runs now take about 30 minutes tops.
rickjames Posted May 6, 2015 Author Posted May 6, 2015 Ta. My eyes can barely tell if the progress bar is actually going along at all, hah.
Oaktech Posted May 6, 2015 Posted May 6, 2015 Ta. My eyes can barely tell if the progress bar is actually going along at all, hah. It probably isn't. it's one of those progress bars that only moves when a task is complete rather than showing how the current task is actually going!
sted Posted May 6, 2015 Posted May 6, 2015 and often i find it stops partway through with some message about node reset and you have to run it again
Oaktech Posted May 6, 2015 Posted May 6, 2015 and often i find it stops partway through with some message about node reset and you have to run it again It most certainly does...
southhamster Posted May 6, 2015 Posted May 6, 2015 All day sometimes. It's slower than watching paint dry...
minimoo Posted May 6, 2015 Posted May 6, 2015 I run the equivalent of wsus_cleanup.ps1 from Automate WSUS Cleanup - Spiceworks (or similar at least) with options suitable for us - in our case, that's leave pc's in place (as we deal with removing dead PC's separately when we scrap them) and schedule it to run once a day - as far as I can tell, that's now quite quick. Note: i've never run the sql reindex bits myself, so might have a look at what that part of the script does and see if our sql instance needs any reindexing The reason I choose not to let the wsus server cleanup old pc's is so if a PC sits in a cupboard, I can get a global picture of what updates are 100% and what updates are 99% + 5 unused pc's that need them when next turned on. With wsus only cleaning up updates once the last pc finally has it.
rickjames Posted May 7, 2015 Author Posted May 7, 2015 23 hours later and we're about halfway there. Well, there we go.
rickjames Posted May 7, 2015 Author Posted May 7, 2015 Oh f****ing great, server node reset. This is a problem if it's going to carry on doing this. 1
Mako Posted May 7, 2015 Posted May 7, 2015 This is a problem if it's going to carry on doing this. Carry on my wayward node. There'll be peace when you are done. Lay your weary cores to rest. Don't you crash no more.
Oaktech Posted May 7, 2015 Posted May 7, 2015 Oh f****ing great, server node reset. This is a problem if it's going to carry on doing this. Yeah, they do that. nothing to do but reset and try again. It usually gets to the point it failed at much faster second time round though, if that's any consolation.
rickjames Posted May 7, 2015 Author Posted May 7, 2015 I've just run each one individually, or tried. The unused updates and update revisions one just resets the server node. Cleared about 25gb from the option options so obviously this is where the bulk of it must lie. Desperately want rid of any 32bit/Win 7 based update none of machines need whatsoever.
sted Posted May 7, 2015 Posted May 7, 2015 it still works im pretty sure just deosent report what its done just keep repeating till it works
Tesla Posted May 7, 2015 Posted May 7, 2015 This be the error. comes up in less than 5 minutes of running it. The WSUS administration console was unable to connect to the WSUS Server Database. Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL. System.Data.SqlClient.SqlException -- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. Source .Net SqlClient Data Provider Stack Trace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
rickjames Posted May 7, 2015 Author Posted May 7, 2015 I get this after about a minute The WSUS administration console was unable to connect to the WSUS Server Database. Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL. System.Data.SqlClient.SqlException -- Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x80040e19). Source .Net SqlClient Data Provider Stack Trace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
rickjames Posted May 7, 2015 Author Posted May 7, 2015 Also just tried it in Powershell, same results, pah.
CraigM Posted May 8, 2015 Posted May 8, 2015 I scrub my WSUS store quite often, since I found that the longer I leave it as is, the slower it gets. I must say though, I wish the automatic approval rules were granular enough so that I can reject things like 64 bit Office or Itanium updates. Going to be another mission once I finally get rid of the last of my Win 7 32 bit clients and need to clear those patches out...
minimoo Posted May 14, 2015 Posted May 14, 2015 How many updates do you have on the wsus server / clients? What version of wsus? have you tried running the maintainence script that rebuilds indexes ?
Tom91 Posted May 15, 2015 Posted May 15, 2015 (edited) What I've done with various WSUS servers it's completely scrap them and start again, if the server isn't running anything else, I just start afresh. Takes about 5 hours but also saves hours of troubleshooting when something does go wrong. Especially easy if their Hyper-V. Yes the clients may be without updates for a day or so but in that time it can be back up and running in a good state. Edited May 15, 2015 by Tom91
Gatt Posted May 15, 2015 Posted May 15, 2015 Just started using WSUS at home (I've ditched SCCM due to too much resources) and trying to get into the habit of doing cleanups every couple of days I might look into doing a daily scheduled task for it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now