E-Mail:

XP And Windows Server Update Services (Part I)

Implementing a Windows Server Update Services (WSUS) infrastructure requires you to install and configure a WSUS server. Once this is complete, you then need to configure the client computers on your network to point to the WSUS server. This entails deploying the required software on the network and configuring the required settings.

In this series of articles I will outline how to configure a computer running XP Professional to obtain updates from a WSUS server on the local network. The articles assume that you have already installed and configure a WSUS server.
Configuring Clients for Automatic Updates
In order to implement a WSUS infrastructure a compatible version of Automatic Updates must be installed on the client computers. The updated software, referred to as the WSUS client, allows clients to download the updates from a WSUS server instead of using the Windows Update.

The updated version of Automatic Updates can run on any of the following platforms:

  • Microsoft 2k Professional with SP3 or later

  • Microsoft XP Professional
  • Microsoft Windows Server 2003 (All editions)

Installing a Compatible Version of Automatic Updates
The process that is use to install the WSUS client will depend on the operating system and service pack version that is installed on client computers. If all clients are running XP Professional with service pack 2, no installation is required because the WSUS client is already installed.

If client computers are not running service pack 2, or they are running a different version of Windows, the WSUS client can be installed through self-update. When WSUS is installed, IIS is automatically configured to distribute the updated version of Automatic Update when each client computer contacts the WSUS server. The self-update method is supported by the following clients:

  • 2k with SP3 or SP4

  • XP with SP1 or SP2
  • Windows Server 2003

The self-updating client software is not available if client computers are running XP with no service packs. Assuming that there is not Software Update Services (SUS) server on the network already, you must first install the SUS client software on the computers. This will add the self-updating client software. When the client connects to the WSUS server, the SUS client will be updated to the WSUS server.

The SUS client software (WUAU22.msi) can be downloaded from the Microsoft web site. You can deploy the software locally on each client computer or it can be deployed from a central location using Active Directory. The following steps outline how the client can be deployed using a group policy object:

  1. Click Start, point to Administrative Tools, and click Active Directory Users and Computers.

  2. Right click the appropriate organizational unit and click Properties.
  3. From the Group Policy tab, select an existing GPO and click Edit or click New to create a new GPO.
  4. Under Computer Configuration, select Software Settings as shown in the figure.

    There's a picture here of something that we just bet you'd like to see! Patience! Patience!

    Deploying the SUS client through group policy

  5. Right click Software Installation, point to New, and click Package.
  6. Locate the WUAU22.msi file and click Open.
  7. The Deploy Software window appears. Click Assigned and Click OK.

[tags]microsoft,xp,diana huggins,windows server update services,wuau22.msi,wsus[/tags]

What Do You Think?

 

Want to Start a Blog Here for Free?

Are you an expert in one subject or another? If your goal is to help others and dispense hard-earned information back to the community, stake a claim on your very own Lockergnome blog today! You can write about anything - no matter the topic. Sign-up to start blogging!

66 queries / 0.779 seconds.