Evaluate each patch with an impact
analysis – specifically which components/services are being updated. With
that change, what is likely to be threatened – OS behavior, data access,
etc?
Do you think the update will impact your
general server operation? If yes, what part, generally, or if you can determine
it, specifically? Make a test plan. Most don’t have to be onerous or
extensive.
Is the patch likely to impact applications,
database or network access? If MDAC, do your apps use MDAC? Summarize the
change in a note to your applications or database folks – ask them what
testing they would want/need to do.
If you show them you’re on their
side (don’t want to make a change that threatens their app without giving
them the chance to test/approve) – involve them in the change.
Use some sort of isolated test environment
and test those components that you and the impacted parties feel are likely to
be threatened.
Service packs are, of course, a whole
other level. Your most likely going to have to give yourself and all your
critical applications folks some testing time. Impact analysis is still helpful
here, but there are generally so many bug fixes and changes, a more thorough
test is appropriate.
This gives you the best bang for the buck.
A little analysis, and process, goes a long way to determine what is best to
test.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: April 5, 2004 4:31 AM
To: Patch Management Mailing List
Subject: RE: Still trying to
decide - Implementing a PM system
We are using HFNetchk and it does works OK
for us. Only problem for us is that we don't have a dedicated test facility
hence every patch we apply, we have to keep our fingers crossed. Can
anyone advise how should we approach towards creating a test environment for
the patches..We have SQL, IIS, Oracle and lots of bespoke applications running
in our environment which makes it difficult to plan a test environment.
Can anyone advice how to approach testing
and we can then try to finetune it to our requirements.
-----Original Message-----
From: Charlene Griffith
[mailto:[EMAIL PROTECTED]
Sent: 01 April 2004 17:59
To: Patch Management Mailing List
Subject: RE: Still trying to
decide - Implementing a PM system
We just bought HFNetChk. It has
worked wonderfully for us. I have never encountered any
complications. I strongly recommend this software. Its
definitely great for someone who wants a cost effective, and easy solution for
patch management. I believe that you can download a trial version on their
website that allows you to play around with the software. It only will
allow you to manage ten computers, but it will let you get a feel for the
product.
Also, please do not forget about Michael's
recommendation about testing patches first, that is one of the most important
parts of Patch Management.
I also have no affiliation with Shavlik
Technologies, this is only my opinion.
-----Original Message-----
From: Michael O'Coners
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004
11:33 AM
To: Patch Management Mailing List
Subject: RE: Still trying to
decide - Implementing a PM system
I have installed HFNetChk in about 20+
environments and have never required scripts or anything more complicated than
running from the HFNetChk GUI. The only problem I occasionally run into is
related to patches not working properly with applications on test machines.
>From my experience HFNetChk is by far one of the easiest and most cost
effective solutions for managing patches. The GUI is excellent and the built-in
help can get a new user up and running quickly - its all point and click. Don't
let the simplicity fool you with any product. Always plan your roll-out
strategy and policies before you actually implement them and always remember to
roll-out patches on test machines or isolated machines first. Then perform a
larger scale roll-out.
By the way - I have no affiliation with Shavlik
Technologies so my opinions are only biased on my personal experience :-)
-----Original Message-----
From: Marsh, Richard
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004
11:10 AM
To: Patch Management Mailing List
Subject: Still trying to decide -
Implementing a PM system
Several
months back, I mentioned my greenness and the overwhelming feeling all the
choices (regarding patch management) gave me. I did some research and
read a lot more posts. Currently, we do all patching manually and there
is no budget for a patch management solution, which means my suggestion must be
cheap. Norton's ghost seems cheap enough (we would only need 1 license)
though hfnetcheck pro sounded reasonable as well. I did see that I would
need to write scripts for the Ghost to do updates, that isn't really a task I'm
ready to take on. Is hfnetcheckpro the same, will I inevitably need to
learn how to script? Still confused but learning...Thanks as always.
Sincerely,
Rich Marsh
"It is our attitude at the
beginning of a difficult task which, more than
anything else, will affect its
successful outcome."
William
James
1842-1910
http://plato.stanford.edu/entries/james/
---
To unsubscribe send a blank email to [EMAIL PROTECTED]
---
To unsubscribe send a blank email to [EMAIL PROTECTED]
---
To unsubscribe send a blank email to [EMAIL PROTECTED]
---
To unsubscribe send a blank email to [EMAIL PROTECTED]
---
Welcome to the Virus.Org Mailing List Archive 