The traditional wisdom was exactly that. And that served well for many years … 
until about 1.5 years ago when it didn’t. The WSUS catalog has just become so 
bloated and ConfigMgr clients don’t the filter the WSUS catalog in exactly the 
same way as pure WSUS client do so the problem just got worse and worse. Also, 
the WSUS team lives in a silo and doesn’t consider anything outside of their 
little core scenarios (sorry that’s my opinion but the problems that are 
addressed by this article are a result of that … once again IMO).

So who should do this? Honestly, everyone. Why? Because the problems aren’t the 
result of scale, they are the result of the catalog size (mainly) and thus 
independent of the site size or number of managed clients. In the customers 
I’ve performed this cleanup (and more) at, I’ve seen dramatic improvements in 
many different things including console responsiveness, scan times, OSD 
deployment of updates reliability and times, and more.

Do note though that this article doesn’t contain much new – they actually 
published a KB almost 6 months ago with this info in it. Here’s a post I wrote 
at the time: http://blog.configmgrftw.com/wsus-cleanup-for-configmgr/

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Stephen Owen
Sent: Wednesday, January 27, 2016 2:09 PM
To: [email protected]
Subject: Re: [mssms] RE: FYI - The complete guide to Microsoft WSUS and 
Configuration Manager SUP maintenance

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]<mailto:[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]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Art Flores
Sent: Wednesday, January 27, 2016 1:36 PM
To: [email protected]<mailto:[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






Reply via email to