what are general steps to test new released updates

Can anyone advise? Thanks

That depends a lot on your situation.
Generally you probably should all Critical Updates as soon as available.
If you have few systems, some wait a few days to see what happens to
everyone else.
I keep my computers clean of viruses, spyware and other malware so I usually
install all Critical Updates on my main computer as soon as they are
available. Other computers usually get the updates later that day or the
next day.
I have never had problems related to Windows Update.

If you are a business or other organization with many computers, it is
normal for those to install the updates on a test computer to see how the
update reacts with the particular hardware and software configuration. If
no issues are noted, install on other computers in a few days.
This obviously works best if the computers are similar in hardware and
software configurations.
As zero day exploits become more of a reality, this process introduces
another danger of unprotected computers and dangerous exploits already out
there.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


"OM" <> wrote in message
news:...
> Can anyone advise? Thanks

Jupiter Jones [MVP] wrote:
> That depends a lot on your situation.
> Generally you probably should all Critical Updates as soon as available.
> If you have few systems, some wait a few days to see what happens to
> everyone else.
> I keep my computers clean of viruses, spyware and other malware so I usually
> install all Critical Updates on my main computer as soon as they are
> available. Other computers usually get the updates later that day or the
> next day.
> I have never had problems related to Windows Update.
>
> If you are a business or other organization with many computers, it is
> normal for those to install the updates on a test computer to see how the
> update reacts with the particular hardware and software configuration. If
> no issues are noted, install on other computers in a few days.
> This obviously works best if the computers are similar in hardware and
> software configurations.
> As zero day exploits become more of a reality, this process introduces
> another danger of unprotected computers and dangerous exploits already out
> there.
>



Our organization has various hardware/software PC platforms. Some of
them are regular desktop PCs and some of them are special lab.
equipments with Windows installed or some with specialized testing/data
acquisition software running. We did run into problem where machine will
not boot up after SP installation.

Anyway, thanks you for the input.

If your organization has a lot of computers, it may be worthwhile
configuring one or two as close as possible to the majority, particularly
installing programs critical to your operation.
Then install the updates on these before the others to see if there are any
ill effects.
Another good option is to install the updates in phases over time, a few
days at most.
That way if something happens, you lose a few computers and not all.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


"OM" <> wrote in message
news:...
> Our organization has various hardware/software PC platforms. Some of them
> are regular desktop PCs and some of them are special lab. equipments with
> Windows installed or some with specialized testing/data acquisition
> software running. We did run into problem where machine will not boot up
> after SP installation.
>
> Anyway, thanks you for the input.

"OM" <> schrieb:

> Our organization has various hardware/software PC platforms. Some of
> them are regular desktop PCs and some of them are special lab.
> equipments with Windows installed or some with specialized testing/data
> acquisition software running.

You may find the following site useful:
http://www.microsoft.com/technet/sec...anagement.mspx

Bye,
Freudi