Re: Best Practice: Patches that are not critical or security related
- From: "WB" <woundedbackREMOVETHIS@xxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 19:25:33 -0400
"paulc2480" <paulc2480@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C203A8C2-AD27-4439-87DF-B43559513C5B@xxxxxxxxxxxxxxxx
What is the best practice for installing patches that are not listed as
"Critical" or "Security" related? Does Microsoft have an official stand
on
this?
Some would say push them all to be safe and fix any potential issues. On
the other side it has been said that by pushing patches for problems that
don't specifically affect you it creates a greater chance that something
else
might be broken. Any references containing recommendations or best
practices
on this subject? Thanks!
Install optional updates if they address a particular issue or
functionality.
For example, windows updates offers a patch for the FAST wizard, not able to
transfer files and settings from a 32-bit machine to a 64-bit machine.
If you need this functionality, you install the patch.
For hardware it is common practice to get drivers from the manufacturer
site. The reason MS lists such updates is because the drivers meet testing
standards.
--
woundedback
Please drive safely
.
- Next by Date: Security Certificate Warning!
- Next by thread: Re: Best Practice: Patches that are not critical or security related
- Index(es):
Relevant Pages
|