At the company I work for we have defined 1-2 "power users" in each
deptartment that make use of most everyday applications. We push the updates
to their machines, then monitor them for 4 hours. If the user can report no
problems, and that they have used "key business" apps in that time frame we
deploy to the entire site. On Monday's before the updates I also make sure
that I have a good clean ghost image of the corporate standard in place just
in case I have to re-image those machines quickly.
~todd fencl
Murad Talukdar <[EMAIL PROTECTED]> wrote on 01-09-2006 11:06:22 PM:
Hi all,
I wanted to get a few ideas of what people do to test their systems once
they have applied a patch/hotfix.
Currently I pull one of the hotswap drives that has the OS mirrored on it
and then let it run with the patch applied for a few days/week before
letting it rebuild.
In that time I will check things like event logs/performance and do some
general 'listening' for any issues.
Does anyone have a more scientific method? What do you keep an eye on?
Also,
Do you actually ever check whether the vulnerability(for example) that the
patch was designed to thwart has actually been plugged?
In the last two years I've only had one instance of a patch causing an
OS to
fail--and then just removing and then reapplying the patch seemed to
work
just fine. However, I don't want to get complacent.
---------------------------------------------------------------------------
---------------------------------------------------------------------------
