?
Solved

WSUS: always ignore superseded ?

Posted on 2014-12-19
3
Medium Priority
?
197 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 2000 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

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

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

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
Suggested Courses

801 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