Home
.. About WSUS Wiki

RSS

WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List

WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice

SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues

Wiki Community
.. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page

Miscellaneous Stuff
.. Other Resources
.. Do You Know?

Site Meter


Terms of Use
Trademarks
Privacy Statement

 

Testing Updates


Tell us how you test updates.

Things to talk about:

  • What criteria do you use to decide what updates to test and what not to test?
  • How do you pick your Guinnea pigs?
  • Can you share your testing methodology doc or process? Just attach the documents to this page.

Comments:

From TomLamond - 4/26/07 10:19 AM

I use the same technique as supersyl. I made a list of all the unique platforms in my environment, then I picked one person from each group. Every time I approve updates, I send an email with the KB# for each update.

From SuperSyl - 4/19/06 10:56 AM

Hi, We have now 1150 wsus client on 37 computer group...

I create a wsus group and i have 1 person of each important department in this group...

When 1 approve update it's always for my wsus group and i copy the list of update and paste to my mailing list wsuslist that told them what update i do to wsus group and they have 2 or 3 days for testing them...

After 2 - 3 days if i did'n receive mail from wsus group... i apply udpates for all computer...

Presently, I'm looking for a tools that told me  by mail when new updates are avalaible on wsus and when new computer appear on computer group "unassigned computer"

 

 

From inthralled - 4/4/05 10:20 AM

I have a group of 118 desktops and laptops all Windows XP SP2. In addition I am running two Windows 2003 Servers on my segment of a much larger network. I test all up dates on the easiest to replace computers. Usually those with basic programs (Operating System and Office). I then have the rest of the computers broken into two groups Critcal and "kinda" Critcal computers. If the update works ok with the 1st group for a week I then approve the second or kinda Critical computers. After a week running new updates on the "kinda" Critical group I approve the last group or Critical computers. So after 2 weeks all updates are approved for install. All users are local admins and all updates are forced. I am the tester for a much larger portion of our network. jt 



Last Modified 3/28/05 6:03 AM

Hide Tools