How we did it

We had an existing SUS installation running on a 2.6 GHz (1G byte RAM) Windows 2003 server. We opted to test a larger enterprise installation process using SQL server instead of the MSDE database provided with the WUS installation, making our first step in the upgrade process the installation of SQL Server on our system. We then installed WUS.

Because SUS was already running on the server, WUS installed its Web server on Port 8530.

We then followed the documentation to use the WUSUTIL program to migrate content and patch approvals from our existing SUS server to the new WUS server. Once this process was complete, we uninstalled SUS using Add/Remove Programs and configured WUS to listen on Port 80.

Once WUS was installed and running, we created computer groups in our Group Policy Object (GPO) to test the new grouping functionality. We created three groups: Test Servers, Infrastructure Servers and Workstations. We had two Win 2003 servers in the Infrastructure group, a Windows XP and a Windows 2000 system in the Workstation group, and a Windows 2000 server in the Test group. We set the GPO for Automatic Updates differently for each group.

To fully use WUS, client systems need to be running BITS 2.0 and Windows Installer 3.0, available through the WUS installation. We configured synchronization to occur each night at 2 a.m. As soon as all the information was synchronized from the Microsoft servers, we approved the installations for the Infrastructure group, starting the installs on those systems.