Remote 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 remote server migration procedure is a four-step process, with an optional step for testing. If you intend to utilize a computer without a SUS installation to deploy WSUS, use this process.

Remote server migration is helpful if you were using multiple SUS servers to approve content for different types of client computers. This scenario features the ability to map migrated SUS approvals and updates to computer groups on the WSUS server, as depicted in the following illustration.

Consolidating Multiple SUS Servers

Unlike same-server migration, you do not have to concern yourself with installing WSUS in any special way. You must, however, 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 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.

Remote server migration requires that you share the Content folder on each SUS server you want to migrate to the WSUS server (or use the default share to access the content folder).

You do have to make sure that SUS is not synchronizing before you migrate content or approvals. You do not have to migrate both content and approvals from the remote 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.

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. On the SUS computer, locate the SUS content store in the file system. By default, SUS content is stored in C:\SUS\Content\.

  2. Right-click the Content folder, and then click Sharing and Security (or Sharing, on computers running Windows 2000).

  3. In the Properties dialog box for the Content folder, click Share this folder.

  4. Click the Security tab, and ensure that the Everyone group has Read NTFS permissions for the Content folder.

  5. Click OK.

  6. Repeat this step on each SUS server you intend to migrate.

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

  2. Type the following:

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

    For example:

    wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 "all desktops" /log remote_migration.log

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

  2. Type the following:

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

    For example:

    wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 /log remote_migration.log

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

  2. Type the following:

    wsusutil.exe migratesus /content LocationOfRemoteSUSContent /log filename

    For example:

    wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 /log remote_migration.log

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

  2. Type the following:

    wsusutil.exe migratesus /approvals SUSServerName /log filename

    For example:

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

Any computer that is going to connect to WSUS must have the WSUS client. When you installed WSUS, the client self-update feature was set up automatically by the WSUS installer.

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

Point the SUS clients to WSUS. As the SUS clients check in with the WSUS server, they will find the WSUS Web site and self-update to the WSUS client.

Community Additions

ADD
Show: