I must admit, I was really surprised to see a guide like this come up. I've been deploying SCCM for years now, and thought the tradional wisdom was 'Don't touch WSUS console!' unless you really needed to.
I think the article could use some context. For instance, when should people consider doing this. Is this mostly for mega enterprises with years of WSUS history, or is this a concern for new builds today. Why is this even needed? What are the affects of not doing it, is there any indicating condition which should signal us that we need to begin pruning WSUS? Instead, it's heavy on the how, and very light on the why. On Wed, Jan 27, 2016 at 1:45 PM, <[email protected]> wrote: > Really Good write Up by Meghan Stewart from Microsoft – An amalgamation of > the many cases they’ve had the last 2.5 years! > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Art Flores > *Sent:* Wednesday, January 27, 2016 1:36 PM > *To:* [email protected] > *Subject:* [mssms] FYI - The complete guide to Microsoft WSUS and > Configuration Manager SUP maintenance > > > > > http://blogs.technet.com/b/configurationmgr/archive/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance.aspx > > > > > >
