One such benefit is that it gives administrators an opportunity to download updates to a specific server on the network and use them within a test environment before approving them for installation in the production environment. If you have ever installed updates, you are probably aware that installing them does not always produce positive results. So this gives administrators a chance to install the update before they are installed on production servers and workstations.

There are two different components to a software update infrastructure that uses WSUS. You have at least one server on the network running SUS and you have your automatic update clients as outlined below.

Windows Server Update Services server - This component is installed on a computer running Windows 2000 or Windows Server 2003. Whenever updates are available on the Windows Update Site, the WSUS server can automatically download them (or they can be downloaded manually by an administrator). The updates can then be tested, published for users, and installed on workstations configured to use WSUS.

Automatic Update Clients - This component is installed on all servers and workstations running Windows Server 2003, Windows 2000, and Windows XP so they can connect to the server on the internal network running WSUS.

In the second installment of this series, I’ll outline the pre-installation tasks that you need to complete before installing WSUS.

Read Part I of her series at:
http://www.lockergnome.com/nexus/it/2007/05/18/installing-and-configuring-windows-server-update-services-part-i/