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

 

Patch Management In Networks With 10 Computers

Show Menu

Here is a comprehensive document from Microsoft regarding patch management and Software Update Services: http://www.microsoft.com/technet/itsolutions/cits/mo/swdist/pmsus/pmsus251.mspx.

But more importantly tell everyone what worked for you. Just add your raw information here. Someone esle will organize it and will make it pretty.

Thinngs to talk about?

  • Do you use WSUS or Windows Update? How about Automatic Update?
  • How often you deploy updates?
  • How do you train your users to update their machine?
  • How do you deploy Service Packs?

Comments:

From sdiamond - 10/10/05 4:30 AM

I have installed WSUS and, at first, was organizing the groups by department.  I soon realized that this was pointless and remembered the KISS (keep it simple stupid) principal.  I run a small network, but with multiple locations.  I mainly need to ensure that computers are updated and keep the management of it simple but effective.

I now maintain just three groups.

  1. Servers:  I want to control what is installed on these machines. 
  2. Testing: In a small network this includes some PCs that are in main production and I.T. PCs.
  3. Production: All other PCs are lumped into the Production group. 

If I have the luxury of a testing PC it has a place in the testing group.  If I lack a good test bed, usually the case in a small network, I can solve this problem by including IT and a sampling of production PCs (i.e. one sales pc) into the testing group.  I can see what the real-world effects of the patches are before rolling them out company wide.  Worst case scenario is that I have one sales pc down, not all of them.


Last Modified 3/30/05 11:01 AM