Okay... so it's been 3 months now... so the honeymoon is over, and one would think the issue would be dead....
So why is it that over the past three months (Patch Tuesday June 2012 thru the end of September 2012)...
The single most significant issue affecting WSUS Administrator is...
Failing to PATCH the WSUS Server???
Yes.. the update has been particularly troublesome... and I'm truly sympathetic for those who tried and had challenges... (actually I'm gaining a newfound respect just for the fact that you recognized the need!)
But it's not an OPTIONAL update -- and arguably it should have been classified as a Security Update and a WSUS Infrastructure (read: Mandatory) update -- and that doesn't explain the posts we're still seeing on a daily basis of systems that haven't even TRIED to install these updates!?
Help me understand, please -- I'm working on a longer blog post for PatchZone.org and I'd really like to present a balanced perspective -- but if WSUS Administrators are challenged recognizing the significance of a patch for the WSUS server, what does that mean about any other patch in the catalog and understanding the significance (or lack thereof) of any one of those patches?
And, btw... beyond KB2720211 -- there are two more patches that will have just as a significant impact on WSUS operations as this one did -- both of them are already available: KB2734608 (KB2720211 + Win8/Win2012 support for WSUS3SP2, but more significantly a new SHA hashing algorithm) -- and KB2661254 (available via the MDC for almost 2 months, but due to come down the MU/WSUS pipeline in 12 days).
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin