It is amazing that WSUS is not able to manage and synchronize the ~5400 updates not even now with ~1900 approvals these are only "critical" and the "security updates" not more.
Because having 1000+ approved updates on a WSUS server is not a practical scenario. I doubt it was ever tested. I've certainly never had a thousand approved updates on a WSUS server!
You're testing it now. It doesn't work. I'm not surprised. Why do you find that you need to have 1900 approved updates?
What would happen when more products and classifications would be activated to manage?
Well, I suspect that most of us, as we've been doing for the past seven years, willremove the approvals for updates no longer needed. Over the past seven years, through the addition of several instances of Windows, and almost every Microsoft application, I've yet to see more than 500 approved updates on my WSUS server at any given time (except when I've been lax about removing the old approvals).
But, part of the difference here is that I do it on a monthly basis, so the effort of removing approvals is [a] trivial, and [b] doesn't send the Server Sync process off in a quagmire of work to do within a time constraint. You're trying to cram three years worth of maintenance effort into a single sitting -- it ain't working.
I must fight further with 20 downstream servers:-/
No, you only need to fix the upstream server. Once the upstream server is healthy, the downstream servers will be perfectly happy campers. There is nothing wrong with the downstream servers except they're trying to duplicate the unhealthy state of your upstream server.
Unapproved: 2609
Approved: 1889
Declined: 1057
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.