Prepare your Source Server for Windows SBS 2011 Standard migration

  • Article

Published: January 28, 2011

Updated: March 24, 2011

Applies To: Windows Small Business Server 2011 Standard

Complete the following preliminary steps to ensure that the settings and data on your Source Server migrate successfully to the Destination Server.

To prepare for migration

  1. Back up your Source Server

  2. Install the most recent service packs

  3. Verify the network configuration

  4. Use Windows SBS 2003 Best Practice Analyzer (BPA) to evaluate the health of the Source Server

  5. Optimize Exchange Server 2003 mailbox sizes

  6. Synchronize the Source Server time with an external time source

  7. Give the built-in Administrators group the right to logon as batch job

  8. Run the Migration Preparation Tool

  9. Plan to migrate line-of-business applications

  10. Run the Exchange Server Pre-Deployment Analyzer

Back up your Source Server

Back up your Source Server before you begin the migration process. Making a backup helps protect your data from accidental loss if an unrecoverable error occurs during migration.

To back up the Source Server

  1. Perform a full backup of the Source Server. For more information about backing up Windows SBS 2003, see Backing Up and Restoring Windows Small Business Server 2003.

  2. Verify that the backup ran successfully. To test the integrity of the backup, select random files from your backup, restore them to an alternate location, and then confirm that the restored files are the same as the original files.

Install the most recent service packs

You must install the latest service packs on the Source Server prior to migration. If updates or service packs are missed, the Source Server will not be eligible for migration, and the Migration Preparation Tool will report the problem and ask you to install the necessary updates before proceeding.

Before installing a service pack, back up your server.

To install Windows SBS 2003 Service Pack 1

Important

To ensure that the correct version of Microsoft .NET Framework is installed, you must install Windows SBS 2003 SP1 before you install Windows Server 2003 Service Pack 2 (SP2).

To install Windows Server 2003 Service Pack 2

Note

  • If you experience network-related issues after installing SP2, see article 948496 in the Microsoft Knowledge Base.

  • To learn more about the best practices and known issues related to SP2 for Windows Server 2003, see article 939421 in the Microsoft Knowledge Base.

    • To install Exchange Server 2003 Service Pack 2

    To install Windows SharePoint Services 2.0 Service Pack 3

    • If you have Windows SharePoint Services 2.0 installed, you must install Service Pack 3 before beginning the migration process.

    Important

    Do not upgrade to Windows SharePoint Services 3.0 until you reach the section Move the internal website for Windows SBS 2011 Standard migration. 

    Download the Windows SharePoint Services 2.0 Service Pack 3 from [Windows SharePoint Services Service Pack 3 (SP3)](https://go.microsoft.com/fwlink/?linkid=211190) and install it.

    To verify that the Companyweb site is updated

    1. Click Start, click Administrative Tools, and then click SharePoint Central Administration.

    2. On the Central Administration page, click Configure virtual server settings in the Virtual Server Configuration section.

    3. On the Virtual Server List page, verify that the version for the Companyweb site is 6.0.2.8165.

    If the version number of the Companyweb site is not correct, use the Stsadm.exe command-line tool to force an upgrade of the content database and the configuration database as follows.

    To force an upgrade of the content and configuration databases

    1. Click Start, click Run, type cmd in the Open box, and then click OK.

    2. At the command prompt, type the following lines, pressing ENTER after each line:

      cd /d \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin

      stsadm -o upgrade -forceupgrade -url https://companyweb

    3. Type exit, and then press ENTER to close the command prompt window.

    To install Microsoft Core XML Services (MSXML) 6.0 Service Pack 1

    To install Microsoft SQL Server Management Studio Express Service Pack 2

    • Download and install the 32-bit version of Microsoft SQL Server Management Studio Express Service Pack 2 onto the Source Server. You can download the service pack from the Microsoft SQL Server Management Studio Express Service Pack 2 website.

    • If your Windows SharePoint Services databases have been migrated to SQL Server 2000, you can also use the native SQL Server 2000 Enterprise Manager in Windows SBS 2003 to install the service pack.

    Verify the network configuration

    To prepare for migration, you must install a router on your network, configure your Source Server to use one network adapter, and disable VPN on the Source Server (if running).

    Reconfiguring your existing network

    Before you can migrate your network to Windows SBS 2011 Standard, you must install and configure a router on your network and configure the Source Server to use one network adapter. When you are done, your network will look like the following figure:

    To configure the Source Server to use one network adapter

    1. Unplug the network adapter from the broadband connection.

    2. Install a router on your network as shown in the previous figure.

    3. To make sure that the Windows SBS 2011 Standard installation wizard can find the router on your network, ensure that the IP address on the network adapter within the router that connects to your LAN is set to 192.168.x.1 or 192.168.x.254, where x is a number from 1 to 254. This IP address is the default gateway address for your network.

    Note

    For information about installing and configuring a router, see the documentation from your router manufacturer.

    1. On the Source Server, run the Configure E-mail and Internet Connection Wizard to configure the Source Server for one network adapter, as follows:

      To configure the Source Server for one network adapter

      1. Click Start, and then click Server Management.

      2. In the console pane, click To Do List.

      3. In the details pane, click Connect to the Internet.

      4. Complete the wizard.

    2. If you are using a virtual private network (VPN) on the Source Server, disable it. To disable the VPN on the Source Server, run the Remote Access Wizard, as follows:

      To disable the VPN on the Source Server

      1. Click Start, and then click Server Management.

      2. In the console pane, click Internet and E-mail.

      3. In the details pane, click Configure Remote Access.

      4. Complete the wizard, making sure that you click Disable remote access on the Remote Access Method page.

    3. If you have computers or devices that are configured with static IP addresses or DHCP reservations, you must manually update each of them with the new default gateway IP address.

    Because the router is the gateway to the Internet, you must use a firewall device to help protect your LAN from unauthorized access. You can use the firewall that is supplied with your router or a separate firewall device.

    If your router supports the UPnP framework, the following happens:

    • The installation wizard automatically configures the Internet connection on Windows SBS 2011 Standard.

    • The installation wizard configures port-forwarding exceptions on the router.

    • After Windows SBS 2011 Standard is installed, the Windows SBS 2011 Standard Console collects and displays information about your router on the Networking tab, in Internet Connection.

    Using Internet Security and Acceleration Server 2004 during migration

    You cannot directly migrate Microsoft Internet Security and Acceleration (ISA) Server 2004 from Windows SBS 2003 Premium Edition to Windows SBS 2011 Premium Add-on. However, you can continue to use Internet Security and Acceleration (ISA) Server 2004 on Windows SBS 2003 during the migration. Verify that ISA Server 2004 with Service Pack 3 (SP3) is installed and configured before you proceed. You can download ISA Server 2004 with SP3 from the Microsoft Internet Security and Acceleration (ISA) Server 2004 Standard Edition Service Pack 3 website.

    After you install and configure ISA Server 2004 with SP3, configure remote procedure call (RPC) filtering.

    To configure remote procedure call (RPC) filtering

    1. Click Start, click All Programs, click Microsoft ISA Server, and then click ISA Server Management.

    2. In the ISA Server Management Console tree, expand Microsoft Internet Security and Acceleration Server 2004, expand ServerName, and then click Firewall Policy.

    3. In the details pane, click the SBS Protected Networks Access Rule.

    4. On the Tasks tab, click Edit Selected Rule.

    5. On the Protocols tab (for an access rule), click Filtering, and then click Configure RPC protocol.

    6. On the Protocols tab, clear the Enforce strict RPC compliance check box, and then click Apply.

    Note

    When you clear the Enforce strict RPC compliance check box, DCOM traffic and other RPC protocols are allowed.

    Note

    When you publish an RPC interface where there is a route:network relationship between networks, port overriding is ignored. The publishing rule uses the original IP address or port.

    Use Windows SBS 2003 Best Practice Analyzer (BPA) to evaluate the health of the Source Server

    If your Source Server is running Windows SBS 2003, you can run the Windows SBS 2003 Best Practices Analyzer to verify that there are no issues on your server, network, or domain before you start the migration process.

    Note

    If your Source Server is running Windows Server 2003 Standard Edition, you cannot use the Windows SBS 2003 BPA. In these cases, make sure that you run the Windows Support Tools to determine if there are any network issues that you need to resolve.

    Run the Windows SBS 2003 Best Practices Analyzer

    Note

    Your Source Server must be running Windows SBS 2003 to run the Windows SBS 2003 BPA.

    The Windows SBS 2003 BPA collects configuration information from the following sources:

    • Active Directory Windows Management Instrumentation (WMI)

    • The registry

    • The Internet Information Services (IIS) metabase

    The Windows SBS 2003 BPA checks the following services and applications:

    • Exchange Server

    • Update Services

    • Network configuration

    • Windows SharePoint Services

    • SQL Server

    To use the Windows SBS 2003 BPA to analyze your Source Server

    1. Download and install the Windows SBS 2003 BPA from the Microsoft Windows Small Business Server 2003 Best Practices Analyzer website.

    2. After the download is complete, click Start, click All Programs, and then click SBS Best Practices Analyzer Tool.

    Note

    Check for updates before you scan the server.

    1. In the navigation pane, click Start a scan.

    2. In the details pane, type the scan label, and then click Start scanning. The scan label is the name of the scan report, for example SBS BPA Scan 8Jun2008.

    3. After the scan finishes, click View a report of this Best Practices scan.

    After the Windows SBS 2003 BPA collects and analyzes the information, it presents a list of issues that are sorted by severity. The Windows SBS 2003 BPA describes each issue that it encountered and suggests solutions. Three report types are available:

    Report Type Description

    List Reports

    Displays reports in a one-dimensional list.

    Tree Reports

    Displays reports in a hierarchical list.

    Other Reports

    Displays reports such as a Run-Time Log.

    To view the description and the solutions for an issue, click the issue in the report. Not all of the issues reported by the Windows SBS 2003 BPA affect migration, but you should solve as many of the issues as possible to ensure that the migration is successful.

    Run the Windows Support Tools

    To determine if there are any other problems with the network, run the Windows Support Tools after you run the Windows SBS 2003 BPA.

    The following table lists the tools that you can use to diagnose issues on your server, network, and domain:

    Tool Description

    Netdiag.exe

    Helps isolate networking and connectivity issues.

    Dcdiag.exe

    Analyzes the state of domain controllers in a forest or enterprise, and reports issues to assist you in troubleshooting.

    Repadmin.exe

    Assists you in diagnosing replication issues between domain controllers.

    You should correct all the issues that these tools report before you proceed with the migration.

    Optimize Exchange Server 2003 mailbox sizes

    Migrating large mailboxes from Exchange Server can take a long time. To save time, reduce the size of the mailboxes before the migration. Send an email message to users with the following instructions about how to empty the Deleted Items folder and archive older mail:

    To empty the Deleted Items folder

    1. In Microsoft Office Outlook®, click Tools in the toolbar, and then click Empty "Deleted Items" Folder.

    2. Click Yes in the warning dialog box.

    To archive older mail in Microsoft Outlook

    1. In Office Outlook 2003 and Office Outlook 2007, click File in the toolbar, and then click Archive. In Outlook 2010, click Cleanup tools under File menu and click Archive…

    2. In the Archive dialog box, click the down arrow next to Archive items older than.

    Note

    You must tell the users what date to select in the calendar that appears.

    1. If you want to make sure that all the older mail is included, select the Include items with "Do not AutoArchive" checked check box.

    2. Click Archive all folders according to the AutoArchive settings at the top of the dialog box.

    3. Click OK.

    In Windows XP, the older mail is moved to the archive.pst file in C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Outlook folder.

    In the Windows Vista® and Windows 7 operating systems, the older mail is moved to the archive.pst file in C:\Users\<user name>\AppData\Local\Microsoft\Outlook folder.

    For additional information about optimizing Exchange Server, see the Exchange Server Best Practices Analyzer at the Microsoft Exchange Analyzer website.

    Synchronize the Source Server time with an external time source

    The time on the Source Server must be within five minutes of the time on the Destination Server, and the date and time zone must be the same on both servers. If the Source Server is running in a virtual machine, the date, time, and time zone on the host server must match that of the Source Server and the Destination Server. To help ensure that Windows SBS 2011 Standard is installed successfully, you must synchronize the Source Server time to the Network Time Protocol (NTP) server on the Internet.

    To synchronize the Source Server time with the NTP server

    1. Log on to the Source Server with a domain administrator account and password.

    2. Click Start, click Run, type cmd in the text box, and then press ENTER.

    3. At the command prompt, type w32tm /config /syncfromflags:domhier /reliable:no /update, and then press ENTER.

    4. At the command prompt, type net stop w32time, and then press ENTER.

    5. At the command prompt, type net start w32time, and then press ENTER.

    Important

    During the Windows SBS 2011 Standard installation, you have an opportunity to verify the time on the Destination Server and change it, if necessary. Ensure that the time is within five minutes of the time on the Source Server. When the installation finishes, the Destination Server synchronizes with the NTP. All domain-joined computers, including the Source Server, synchronize to the Destination Server, which assumes the role of the primary domain controller (PDC) emulator master.

    Give the built-in Administrators group the right to logon as batch job

    Before you migrate an existing Windows SBS 2003 domain to Windows SBS 2011 Standard, verify that the built-in Administrators group still has the right to log on as a batch job to the Source Server. Administrators need this right to run an alert on the Source Server without logging on.

    For instructions, see Give the built-in Administrators group the right to logon as batch job for Windows SBS 2011 Standard migration. Perform the noted procedure on the Source Server.

    Run the Migration Preparation Tool

    The Migration Preparation Tool makes changes to the Source Server that are necessary to migrate to Windows SBS 2011 Standard.

    The Migration Preparation Tool changes the Source Server as follows:

    • Raises the domain and forest functional level of the source domain and forest. When Windows SBS 2003 is installed on a server, the functional level of the AD DS domain and forest is set to Microsoft Windows 2000. To finish the migration successfully, you must raise the level of the domain and forest to Windows Server 2003.

      For more information about raising the functional level of the AD DS domain and forest, see article 322692 in the Microsoft Knowledge Base.

    • Runs Adprep.exe, which extends the AD DS schema and updates permissions as necessary to prepare a forest and domain for a domain controller that is running Windows SBS 2011 Standard. The AD DS schema in Windows SBS 2011 Standard is not the same as the AD DS schema in Windows SBS 2003 or in Windows Server 2003. To successfully complete the migration process, you must update the AD DS schema on the Source Server if it is running Windows SBS 2003 or Windows Server 2003.

    Important

    Back up your Source Server before you run the Migration Preparation Tool. All the changes that the Migration Preparation Tool makes to the schema are irreversible. If you experience issues during the migration, the only way to return the Source Server to the state before you ran the Migration Preparation Tool is to restore the system backup.

    • Installs an update that extends the time limit for finishing the migration. Normally, only one server running Windows SBS 2011 Standard or Windows SBS 2003 is allowed to be a domain controller on your network, but there is a limited exception for a migration. The update extends the time limit for the exception to 21 days.

    Important

    To ensure this task succeeds, install Windows SBS 2003 Service Pack 2 on the Source Server before you run the Migration Preparation Tool.

    Important

    To run the Migration Preparation Tool, you must be a member of the Enterprise Admins group, the Schema Admins group, and the Domain Admins group.

    To verify that you have the appropriate permissions to run the tool on Windows SBS 2003

    1. On the Source Server, click Start, and then click Server Management.

    2. In the navigation pane, click Users.

    3. Right-click the administrator account that you are using for the migration, and then click Properties.

    4. Click the Member Of tab, and then verify that Enterprise Admins, Schema Admins, and Domain Admins are listed in the Member of text box.

    5. If the groups are not listed, click Add, and then add each group that is not listed.

    Note

  • You might receive a permission error if the Netlogon service is not started.

  • You must log off and log back on the server for the changes to take effect.

    • Note

  • To run the migration tools, you need Microsoft .NET Framework 2.0 SP1 on the Source Server. To download and install Microsoft .NET Framework 2.0 SP1, see Microsoft .NET Framework 2.0 Service Pack 1 (x86).

  • To ensure that the server update process works properly, go to Microsoft Update to automatically install the latest version of the Windows Update Agent. For more information, see article 949104 in the Microsoft Knowledge Base.

  • Installation requires that you first install Microsoft PowerShell 2 0. You can download and install the software from the Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) website.

  • Installation requires that you install Microsoft Baseline Configuration Analyzer 2.0. You can download and install the software from the Microsoft Baseline Configuration Analyzer 2.0 website.

    • Run the Migration Preparation Tool

    1. Insert Windows SBS 2011 Standard DVD1 in the DVD drive on the Source Server.

    Note

    If the Migration Preparation Tool is already installed on the server, run the tool from the Start menu.

    1. When the Windows SBS 2011 Standard installation wizard starts, click Install the Migration Preparation Tool. Choose the most recent version of the tool to install.

      A wizard installs the Migration Preparation Tool on the Source Server. When the installation is complete, the Migration Preparation Tool runs automatically and installs the latest updates.

    2. In the Migration Preparation Tool, click I have a backup and am ready to proceed, and then click Next.

    Note

    If you receive an error message that is related to a hotfix installation, see “Method 2: Rename the Catroot2 Folder” in article 822798 in the Microsoft Knowledge Base.

    1. The Migration Preparation Tool prepares the Source Server for migration by raising the domain and forest functional level, extending the Active Directory schema, installing an update to extend the time limit for finishing the migration, and preparing Exchange Server for migration. After the tasks are completed, click Next to continue.

    2. After the source domain is prepared, the Migration Preparation Tool scans the Source Server to identify potential problems. There are two types of issues that can be identified by the Migration Preparation Tool:

      • Errors: Issues found on the Source Server that might block the migration from proceeding or cause the migration to fail. You must fix the issues by following the steps provided by the description, and then click Scan Again to start the scan.

      • Warnings: Issues found on the Source Server that might cause functional problems during migration. We highly recommend that you follow the steps that are provided in the description to fix the issue before proceeding.

      After all the issues are fixed or acknowledged, click Next.

    3. If you have not created a migration answer file, click Create an Answer File and follow the instructions that appear.

    Note

    For more information about creating a migration answer file, see Create a migration answer file for Windows SBS 2011 Standard migration.

    1. Click Finish.

    2. When the Migration Preparation Tool finishes, you must restart the Source Server before beginning the migration process.

    Note

    You must complete a successful run of the Migration Preparation Tool on the Source Server within two weeks of installing Windows SBS 2011 Standard on the Destination Server. Otherwise, installation of Windows SBS 2011 Standard on the Destination Server will be blocked, and you will have to run the migration preparation tool on the Source Server again.

    Plan to migrate line-of-business applications

    A line-of-business (LOB) application is a critical computer application that is vital to running a business. LOB applications include accounting, supply-chain management, and resource-planning applications.

    When you plan to migrate your LOB applications, consult with the LOB application providers to determine the appropriate method for migrating each application. You also must locate the media that is used to reinstall the LOB applications on the Destination Server.

    You can fill in the following table as you collect LOB application information. A good place to start is to run Windows Control Panel, click Add Remove Programs and look in the “Program Files (x86)” and the “Program Files” folders.

    Application or general data folder name Path to data Notes

     

     

     

     

     

     

     

     

     

    Run the Exchange Server Pre-Deployment Analyzer

    We recommend that you run the Exchange Server Pre-Deployment Analyzer on the Source Server. The Analyzer identifies issues that might prevent you from deploying Exchange Server 2010. For example, the Analyzer will notify you if you haven't installed the minimum required Exchange Server service pack on all your existing Exchange servers. To download the Exchange Server Pre-Deployment Analyzer, see Exchange Server Pre-Deployment Analyzer.