Home
.. About WSUS Wiki

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

Troy Watson

Information Technology Support Specialist

Washington State Employment Security Department

Current Projects:

SUS admin for IT Field Support

Symantec Anti-virus admin for Eastern Washington

SMS 2003 design and implementation

Active Directory OU design and implemtation workgroup

Short Bio:

I've been working for ESD for about 5 years now and have pretty much taken the role of project workhorse. For the past 2 or 3 years, my daily work has involved testing, documenting, and designing the support services used in IT field support. It's sort of a double edged sword as I often get to start new projects and continue to learn new technologies. However, often, just as soon as I get a service or server up and running, I end up having to turn it over to others in order to free up time for the next thing coming up.

In my "free" time, my wife and I raise 3 kids, a dog, 2 cats, and play a little World of Warcraft.

Current SUS Configuration:

I'm running both my Server and Workstation SUS systems seperately. For Servers I have a test SUS system, with 5 production File and print and/or application servers as test guinea pigs, and a production system which the remaining 62 servers connect to. Workstations are setup the same way with a variety of production workstations in a test "pool" throughout the state and the remaining 800ish workstations utilizing the production system.

My testing cycle is 1 week, shortened from an initial 2 weeks due to the fequency of exploits over the last 18 months. All new updates are approved on both test SUS severs (workstation and server) and test clients are monitored for any adverse effects to the commercial and locally produced software our staff use. If no reported incidents occur, then the 2 production servers are syncronized to the test workstations and the production pool is allowed to download the tested updates.