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 Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page
Miscellaneous Stuff
.. Other Resources
.. Do You Know?
Terms of Use
Trademarks
Privacy Statement
WSUS Before You Deploy |
Before Deploying WSUS
WSUS is an add-on service that you have to install and configure in order to deploy software updates to clients. As with any service, before installing WSUS you should understand your deployment scenairo and have all the needed necessary elements of your deployment planned.
Deployment issues to consider include:
- Placement of your WSUS servers - You should determine how many servers do you need and where you need them.
- Identify Network Bottlenecks - This will help you determine how to segment your WAN in terms of WSUS coverage and how many WSUS servers will be needed.
- Where clients obtain updates - you can either download and serve updates from the WSUS server or have clients download directly from Microsoft Update.
- Client Group Targeting - you can target different updates to differerent groups of clients either based on client or WSUS Server settings.
- Update Approval Process - you need to determine who tests and approves your WSUS updates.
- Compliance checking - you need to determine if compliance reporting is required, and how you can achieve it.
- Troubleshooting - you should determine who is responsible for troubleshooting WSUS and ensure they have the needed tools.
- Identify Your Target Client Types - Desktops, Laptops and Servers may benefit from separate configurations and update schedules. Consider work schedules for each site and how they should be scheduled to receive and install updates.
- Decide Which Types of Updates to Deploy - WSUS allows for more products to be updated, and provides far more granularity of update types (e.g. drivers, roll-ups, tools, service packs, etc.).
While WSUS handles many updates, it does not do all updates. You need to plan how to update those packages and applications that are not supported by WSUS.
Comments:
From JeanDit - 6/7/07 3:26 PM
Last Modified 3/25/05 11:16 AM
This is what I used as action plan. Might not fit with your project/business, but can be a good start :)
1. Design / Architecture
Determining WSUS needs, groups and groups membership
Define WSUS client settings for each groups
How WSUS client settings are applied to servers (GPO, Regedit, SMS, script, etc)
How update are going to be triggered (Wait until time, wuauclt /detectnow, script, etc)
How many WSUS we want (DMZ, LAN, etc)
Get a baseline group of patches (also get it to the actual prod level)
What languages and products we want to support
Determining hardware requirements
2. Test Planning:
How updates are going to be triggered
Select some “testing servers" in production; which group we need to create
3. Proof of concept (On the WSUS test server):
Assign updates and servers to groups
Use WSUS to updates these servers on next patch cycle*
Monitor closely the update process; address any issues*
*(Repeat these exercises if needed)
4. Implementation
Find a server that meets the minimum requirements
Install the OS
Installing required components
Setting up your server (OS fine tuning)
Get the correct open ports into firewall
Get an image of the server (backup)
Install & Setup WSUS
Configuring WSUS
Getting WSUS synch
Creation of groups and assign membership
Deploy WSUS client settings into production
Assign updates to groups
Monitor closely the update process; address any issues
5. Post – Implementation
Monitor closely the update process; address any issues