• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 34
  • Last Modified:

How far to go back year-wise, when approving updates

Looking for more of a suggestion here, than a solution. Wondering if there is a "rule of thumb" when it comes to approving updates for installation via WSUS, based on year. If a certain update is relevant to a particular system, how far back should I go in time when approving.

For instance, If I have updates that are from 2006, should I approve them anyway, despite that in all likelihood, they've probably been installed already either manually or automatically, 8 years ago (this being 2014). Or, should I approve everything where appropriate hardware and OS-wise, and ignore the year of issue.
2 Solutions
Donald StewartNetwork AdministratorCommented:
Personally I would sort the updates by "Needed" and only approve them. This will keep your storage space used to a minimum.
Liam SomervilleCommented:
Agreed. While an update from 2006 may or may not be required, dstewardjr's suggestion will identify that.
nurturer69Author Commented:
Thanks guys.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now