Skip to main content
Preparing to Migrate WSUS

Published: February 11, 2010

Updated: July 19, 2011

Applies To: Windows Server 2003 with SP2, Windows Server 2008 R2, Windows Server 2008 R2 with SP1, Windows Server Update Services, Windows Small Business Server 2011 Essentials

Before you start the migration process

This migration procedure assumes a working knowledge of Windows Server Update Services (WSUS) 3.0 SP2 deployment basics. For more information about WSUS deployment, see the WSUS 3.0 SP2 Deployment Guide on TechNet. We recommend that you make the following decisions and preparations before you start the migration process.

  • Design a WSUS Storage Strategy. Changing the content storage configuration as part of the migration process is not supported. For example, you can store updates on the local WSUS server, or you can store updates on Microsoft Update. If you want the destination server to store updates in a different location than the source server (on a local WSUS server or on Microsoft Update), the new location must be configured on the source server before migration. See TechNet for more information.

  • Decide which Web site WSUS will use. For more information, see the Configure Internet Information Services (IIS) section of the WSUS 3.0 SP2 Deployment Guide.

  • Confirm that the destination server meets the minimum WSUS hardware requirements and database requirements. See the Determine Capacity Requirements section of the WSUS 3.0 SP2 Deployment GuideDetermine for more information.

  • Install all required software on the destination server. For the most current list of software requirements, see the WSUS 3.0 SP2 System Requirements section of the WSUS 3.0 SP2 Deployment Guide.

Prepare the destination server
  1. Before migrating WSUS, set up a new Windows Server 2008 R2 server in your organization as the WSUS destination server and install WSUS on the destination server.

    For WSUS installation instructions, see the Install the WSUS 3.0 SP2 Server section of the WSUS 3.0 SP2 Deployment Guide.

    WarningWarning
    After you have successfully installed the WSUS role, the Configuration Wizard starts automatically. Close the Configuration Wizard. Do not try to sync the updates at this point, as you will be copying the update binary files later in the migration process.

    The WSUS installation procedure assumes that updates for the new server come from Windows Update. If this is not the case, please see the Select the upstream server using the WSUS Server Configuration Wizard sectionin the WSUS 3.0 SP2 Deployment Guide for more information

  2. If you have decided to use the full installation of SQL Server as the WSUS database, install one of the following versions of SQL Server:

  3. Download a graphical tool for managing your database on the destination server at Microsoft SQL Server Management Studio Express or Microsoft SQL Server 2008 Management Studio Express.

  4. (Optional step) Install Windows Server Migration Tools to migrate WSUS update binaries, WSUS server local security groups, or both, from a source server to a destination server that is running Windows Server 2008 R2. Complete installation, configuration, and removal instructions for Windows Server Migration Tools are available on the World Wide Web, in the Windows Server Migration Tools Installation, Access, and Removal Guide on the Windows Server 2008 R2 TechCenter. Windows Server Migration Tools must be installed on both the destination server and the source server, in that order.

    Windows Server Migration Tools is a set of Windows PowerShell cmdlets. For more information about Windows PowerShell and working with cmdlets, see the section “Working with Windows PowerShell cmdlets” in Windows Server Migration Common Tasks and Information.

    ImportantImportant
    Before you run the Import-SmigServerSetting, Export-SmigServerSetting, or Get-SmigServerFeature cmdlets, verify that during migration, both source and destination servers can contact the domain controller that is associated with domain users or groups who are members of local groups on the source server.

    Before you run the Send-SmigServerData or Receive-SmigServerData cmdlets, verify that during migration, both source and destination servers can contact the domain controller that is associated with those domain users who have rights to files or shares that are being migrated.

  5. Steps 5 and 6 are only necessary if you use Windows Server Migration Tools to perform the data transfer. If you use a different tool to transfer the data, skip steps 5 and 6. Make sure that UDP port 7000 is not being used by other applications. This port is used by Send-SmigServerData and Receive-SmigServerData cmdlets to establish a data transfer connection.

    noteNote
    If you have changed the default behavior of Windows Firewall (or another firewall program) to block outgoing traffic on computers that are running Windows Server 2008 R2, you must explicitly allow outgoing traffic on UDP port 7000.

  6. Open TCP port 7000 and make sure that it is not being used by other applications. This port is used by Send-SmigServerData and Receive-SmigServerData to perform the data transfer.

    For more information about how to open and close ports in Windows Firewall, see Windows Server Migration Common Tasks and Information.

    For more information about how to determine whether a port is being used, see Microsoft Support Article ID: 323352 titled How To Determine Which Program Uses or Blocks Specific Transmission Control Protocol Ports in Windows Server 2003.

  7. If the destination server is not joined to the source server’s domain, visually verify that the time, date, and time zone on the destination server are synchronized with the source server. Use Windows Control Panel to update date and time if it is necessary.

Prepare the source server
  1. Refer to Appendix A: Migration Data Collection Worksheet to collect data about the source server.

  2. (Optional step) Install Windows Server Migration Tools to migrate WSUS update binaries, WSUS server local security groups, or both. Complete installation, configuration, and removal instructions for Windows Server Migration Tools are available on the World Wide Web, in the Windows Server Migration Tools Installation, Access, and Removal Guide on the Windows Server 2008 R2 TechCenter. Windows Server Migration Tools must be installed on both the destination server and the source server, in that order.

    Windows Server Migration Tools is a set of Windows PowerShell cmdlets. For more information about Windows PowerShell and working with cmdlets, see the section “Working with Windows PowerShell cmdlets” in Windows Server Migration Common Tasks and Information.

  3. Download a graphical tool for managing your database on the source server at Microsoft SQL Server Management Studio Express.

  4. Steps 4 and 5 are only necessary if you use Windows Server Migration Tools to perform the data transfer. If you use a different tool to transfer the data, skip steps 4 and 5.

    Make sure that UDP port 7000 is not being used by other applications. This port is used by Send-SmigServerData and Receive-SmigServerData cmdlets to establish a data transfer connection.

    noteNote
    If you have changed the default behavior of Windows Firewall (or another firewall program) to block outgoing traffic on computers that are running Windows Server 2008 R2, you must explicitly enable outgoing traffic on UDP port 7000.

  5. Open TCP port 7000 and make sure that it is not being used by other applications. This port is used by Send-SmigServerData and Receive-SmigServerData to perform the data transfer.

    For more information about how to open and close ports in Windows Firewall, see Windows Server Migration Common Tasks and Information.

    For more information about how to determine whether a port is being used, see Microsoft Support Article ID: 323352 titled How To Determine Which Program Uses or Blocks Specific Transmission Control Protocol Ports in Windows Server 2003.

See Also