"Pascal" <pascal_t[ at ]nospam.hotmail.com> wrote in message
news:mn.73217d76cba1c96a.70874[ at ]nospam.hotmail.com...
[Quoted Text] > Hello,
>
> please could you tell me what kind of test on Microsoft updates are you
> doing before deploying them on every computers ?
Install them on one or more computers configured similar to or identical to
computers in your production environment, and then use the computers. If
nothing breaks, that's it. If something doesn't work, isolate the cause to a
specific update (by uninstalling and reinstalling one at a time and
rebooting/testing between each installation). Once you isolate the cause,
don't install that update on the production computers.
> I see :
>
> Reboot computer
> Check event viewer
> Test network access
The big one (not listed) is to test all non-Microsoft application software
installed on the system, with critical evaluation to line of business
applications.
In some cases, you might also want to test Microsoft applications. A few
updates have been known to do freaky things to Microsoft Office applications
(like Outlook).
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|