Solved

WSUS: always ignore superseded ?

Posted on 2014-12-19
3
193 Views
Last Modified: 2016-02-19
Does this sound ok as a way of making administration of WSUS less onerous:

1.      Unless it’s for software we don’t use (e.g. office 2013 since we are office 2007 users): We shall always approve superseding updates.

2.      We shall always disapprove superseded updates.

3.      Two weeks after Microsoft publishes updates, we will approve all updates (unless for products we don’t use).

4.      Even if ALL pc’s on our network are up-to-date for superseding updates, we will keep that update around until it gets superseded in case we spin up a new pc which has not received the updates yet.

We do realize that we disapprove the superseded updates and have not yet approved the superseding update,  there could be two weeks where the PC’s might be vulnerable.  However, in practice, if a user complies and applies updates and reboots as we release updates, chances are, this should not be a big problem.

Any glaring problems with this strategy?

If there’s a better approach to make WSUS less terrible to administer, I’d love to hear any suggestions.  

Sorry for sounded like such a woose but I hate applying these updates!

Thanks,
Mike
0
Comment
Question by:mike2401
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 35

Accepted Solution

by:
Seth Simmons earned 500 total points
ID: 40509921
Unless it’s for software we don’t use...

then uncheck that category so it won't look for office 2003

We shall always disapprove superseded updates.

agree. decline updates that have been replaced with something else

Two weeks after Microsoft publishes updates, we will approve all updates

that's more of a business decision but if that works for you, then ok

we will keep that update around until it gets superseded

not sure i understand this one correctly
if you bring up a new system, install the superseded update and not the old one first
0
 

Author Comment

by:mike2401
ID: 40524941
I am so sorry for loosing track of this question.

Your answers make sense,
Thank you!

Mike
0
 

Author Closing Comment

by:mike2401
ID: 40524942
Thank you!

(My EE email notice went into my gmail promo folder which I don't check often :-)
0

Featured Post

The Ultimate Checklist to Optimize Your Website

Websites are getting bigger and complicated by the day. Video, images, custom fonts are all great for showcasing your product/service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, can lead to some difficult decisions about what to cut.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question