Same-server Migration

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server Update Services

The same-server migration procedure is a four-step process, with an optional step for testing. If you intend to utilize the SUS server to deploy WSUS, use this process. If you have multiple SUS servers in your organization, you can use this process in combination with remote server migration to consolidate multiple SUS servers on the server running WSUS.

When installing WSUS on a computer that has SUS installed, you must install WSUS by using a custom port. You must synchronize the WSUS server prior to migrating. Consider using the synchronization option for deferred downloads, which is enabled by default. Also, configure WSUS to download updates for the same number of languages that SUS was configured to download updates. By default, WSUS is configured to download all languages. These configurations ensure that you do not unnecessarily download updates already on your network or in languages that you do not require.

You do not have to migrate both content and approvals from the SUS server. You can opt to initially migrate content and then migrate approvals at another time, or any number of combinations that suit your purpose.

You do have to make sure that SUS is not synchronizing before you migrate content or approvals. Use WSUSutil.exe to migrate content and approvals from SUS to WSUS. For more information about WSUSutil.exe, see Migration Command-line Tool earlier in this guide.

If you intend to map SUS approvals to a WSUS computer group, first create the group on WSUS. For step-by-step instruction, see Create Computer Groups for Computers earlier in this guide.

  1. At the command prompt, navigate to the directory that contains WSUSutil.exe.

  2. Type the following:

    wsusutil.exe migratesus /content PathToLocalSUSContent /approvals SUSServerName "WSUSTargetGroupName" /log filename

    For example:

    wsusutil.exe migratesus /content c:\sus\content\cabs /approvals sus1 "all desktops" /log local_migration.log

    That is, WSUSutil.exe followed by the migratesus command, a space, the /content command-line option, a space, the location of the SUS .cab files, a space, the /approvals command-line option, a space, the NetBIOS or fully qualified domain name (FQDN) of the SUS server, a space, a quotation mark, the name of the target group on WSUS, another quotation mark, a space, the /log command-line option, a space, and the name of the log file.

  1. At the command prompt, navigate to the directory that contains WSUSutil.exe.

  2. Type the following:

    wsusutil.exe migratesus /content PathToLocalSUSContent /approvals SUSServerName /log filename

    For example:

    wsusutil.exe migratesus /content c:\sus\content\cabs /approvals sus1 /log local_migration.log

  1. At the command prompt, navigate to the directory that contains WSUSutil.exe.

  2. Type the following:

    wsusutil.exe migratesus /content PathToLocalSUSContent /log filename

    For example:

    wsusutil.exe migratesus /content c:\sus\content\cabs /log local_migration.log

  1. At the command prompt, navigate to the directory that contains WSUSutil.exe.

  2. Type the following:

    wsusutil.exe migratesus /approvals SUSServerName /log filename

    For example:

    wsusutil.exe migratesus /approvals sus1 /log local_migration.log

noteNote
If there are additional SUS servers in your environment and you want to consolidate them on this WSUS server, finish this procedure and testing, and then see the "Step 2 Remote Server Migration: Migrate Content and Approvals" section in Remote Server Migration for instruction on migrating approvals from a remote computer.

Any computer that is going to connect to WSUS must have the WSUS client installed.

  • Deploy the WSUS clients in your environment to test WSUS (optional). See Update Automatic Updates earlier in this guide for instruction.

Decommission the SUS server, and change the WSUS Web site from the custom port to port 80. As the SUS clients check in with the WSUS server, they will find the WSUS Web site and self-update to the Automatic Updates client compatible with WSUS. Note that you do not need to make any changes to Group Policy to get the SUS clients to self-update.

If you prefer to leave your updating solution on a port other than port 80, you can leave WSUS on the custom 8530 port and change the client policy to point to this port on your WSUS server. You still need to leave the virtual selfupdate directory on port 80 to allow client computers that are not WSUS-compatible to get updated to the WSUS-compatible client.

  1. Click Start, and then click Run.

  2. In the Open box, type inetmgr, and then click OK.

  3. In IIS, right-click the SUS Web site, and then click Stop.

  1. Click Start, and then click Run.

  2. In the Open box, type inetmgr, and then click OK.

  3. In IIS, right-click the WSUS Web site, and then click Properties.

  4. In the WSUS Administration Properties dialog box, change the value in TCP port from 8530 to 80.

noteNote
If you change the port number after installing WSUS, you have to create a new shortcut on your Start menu with the new URL to access the WSUS console from the Start menu. See Help and Support for instruction on creating shortcuts.

Community Additions

ADD
Show: