Patch management factors

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

In our organization, enterprise operating system patch management is
considered to be a process, not a product. This process consists of
many factors, determined by policy, software behavior, and enterprise
needs, that all contribute to the success of the implementation.

Quoted text here. Click to load it
were essential to the successful implementation of an enterprise patch
management process within the Freeman School.   Our requirements
included the following mix of administrative and software factors:
Administrative support for the school-wide process from the highest
level down
User notification about process well before the actual start of the
Retraining the user community to keep their computers on all the
time and restart daily
Central control of "pushing" updates and patches to computers
Testing patches before general distribution
Segregation or grouping of computers (lab, classroom, faculty,
staff, researcher)
Define different update behavior (patches, time of day, restart)
for defined groups
The ability to control post-update restarts (specifically to
prevent restart after update for faculty and researcher computers)
Include Microsoft Office and key back-end products in the process
Good pre- and post-update reporting

While we determined that these factors were essential to our specific
patch management implementation, we believe that a set of factors
exists that is essential to the successful implementation of any patch
management implementation in any organization.

If you have implemented enterprise patch management, what factors or
requirements do you believe were most important in the successful
implementation of your patch management process?

If you are considering implementing enterprise patch management, what
factors or requirements do you believe will be most important to a
successful implementation in your specific environment?
Thanks in advance.


Site Timeline