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

This page shows how to setup WUS Beta 2, including screen shots.

Instal Pre-Requsites

1. Install base OS

You first need to install an OS for WUS B2 to run on top of. Windows Server 2003 and IIS 6 is the prefered platform, although you can use Windows 2000 and IIS 5. You should install the OS, and install all necessary patches.

2 Install IIS

With Windows Server 2003, IIS is an optional install. If you run Windows 2000, IIS5 may or may not have already been installed. Chould check to ensure IIS installed, and install it if not. For both OS's accept the default installation, as WUS B2 Setup hardens the web site during intallation.

You also need to determine whether WUS B2 can use the default web site (the site on port 80), or whether you want a separate port to hold the site.

WUS needs ASP.NET v1.1, but WUS Setup installs this if it is not already installed.

Q: How much, specifically is IIS needs to be installed?
Q: Does the default installation really work as noted above?
Q: How does it differ IIS 5 vs IIS 6

3 Install BITS V2.0

For Beta 2, BITS V2 is a seperate download that you need to obtain from the WUS beta site. See the WUS Installation Prereqs Page for details on how to get BITS v2.0. The file downloaded from the WUS beta site is BITS 2.0 English.zip. As you might imagine, this is a ZIP file, and it contains two Microsoft hot fixes (one for Windows 2000, the other for Windows Server 2003). Both files appear to be version sensitive to avoid mistakes. You then need to run the relevent .EXE to install BITS.

For Windows Server 2003, Bits 2.0 is delivered as a hotfix - KB article 842773. Running the KB installation package, you see:

Click Next to bring up the License Agreement Page:

From the License Agreement page, select I Agree, then click Next. The Setup Wixard then updates your sysem. You may see

If so, click Continue to complete the BITS V2.0 installation. When completed displays a final page:

After rebooting our system, BITS 2.0 is instaled.

Q: How can you tell BITS 2.0 is installed?

4 Install .NET Framework 1.1 SP1

Windows Server 2003 comes with .NET Framework 1.1 installed, but WUS requires SP1. See the WUS Installation Prerequsites Page for details on where to get .NET Framework 1.1 SP1.

5 Install WUS

To install WUS, run WUSSETUP.EXE, which you downloaded earlier. This will begin by extracting the WUS installation files to a temporary file on the volume on your system with the most free space:

The setup files extracts 58 in 9 folders taking up a total of 91.5mb. The folder structure will look like this:

If you had and earlier version of WUS on your system, running the WUS Beta 2 Setup Wizard produces this dialog box.

After the installation files are decompressed, you see the start of the WUS Setup Wizard:

Click next to bring up the License Agreement page:

Click on the relevant radio button to agree to the License agreement (which obligates you to be Bill Gate's towel boy every summer for life), then click Next to select the update source:

You can store the updates locally, or have clients download them from Microsoft. Select the option for udate storage, click Next to bring up the Database Options Page.

Specify whether WUS should use a local SQL Server database, or whether MSDE should be installed and used for WUS data storage. Then click Next to bring up the Web Site Selection page:

You can use the default web site, runnng on port 80, or the WUS setup can create a new site, running on a default port number of 8530. You can change this using the IIS Manager after installation if needed.

One possible approach is to have selfupdate on port 80 and the the server on port 8530. Or you can run it all via port 80. If you setup you WUS server to run on a different port, you can reset WUS to setup the WUS web site to run on port 80 and to allow selfupdate from Automatic Update Client on port 80. A script is provided to do this at: %ProgramFiles%\Microsoft Windows Update Services\ "SetupInstallSelfupdateOnPort80.vbs.

Q: Is this port number random? How is it determined.

After selecting the web site details, click Next to bring up the installation option confirmation page:

Click Next to start the installation:

If ASP.NET is not already loaded, the WUS Installation Wizard installs it automatically.

If you are not using SQL Server, WUS Setup installs the MSDEE engine (which does take some time).

WUS Setup also downloads the client self update files:

When setup has completed, it displays the completion page:

From here you can launch the WUS web administration tool, or simply finish the installation (and configure the service some other time).

To check your installation of WUS, you should open the WUS Admin site: