Export (0) Print
Expand All

Prepare your Source Server for Windows SBS 2011 Essentials migration

Published: March 10, 2011

Updated: May 12, 2011

Applies To: Windows Small Business Server 2011 Essentials

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

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 updates and 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 updates by using Windows Update

  1. Click Start, click All Programs, and then click Windows Update.

  2. Click Check for updates.

  3. If you are asked to configure Windows Update settings, perform the following steps:

    1. Click OK.

    2. Click Change settings, which is located under the Check for updates link, and then configure the Windows Update settings.

    3. Click Check for updates.

  4. Click Install Updates to apply identified updates.

  5. For each Microsoft Software License Term that is displayed, review the text and click Yes to accept.

  6. If prompted, restart the Source Server

  7. To verify that the updates are installed, click Start, click Control Panel, click Programs, and then click View installed updates.

Next, install individual service packs by performing the following procedures that apply to your Source Server.

Install Windows SBS 2003 Service Pack 1

  • Install Windows SBS 2003 Service Pack 1 (SP1), if it is not yet installed. You can download Windows SBS 2003 SP1 at the Microsoft Windows Small Business Server 2003 Service Pack 1 (SP1) website.

    ImportantImportant
    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).

Install Windows Server 2003 Service Pack 2

  • Install Windows Server 2003 SP2, if it is not yet installed. You can download Windows Server 2003 SP2 at the Windows Server 2003 Service Pack 2 website.

    noteNote
    • 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 that are related to SP2 for Windows Server 2003, see article 939421 in the Microsoft Knowledge Base.

noteNote
Although Exchange Server and SharePoint® Services are not migrated during the process documented here, we recommend that you create a well-known configuration for these applications by applying the required service packs.

Install Exchange Server 2003 Service Pack 2

  • Install Exchange Server 2003 Service Pack 2 (SP2), if it is not installed. You can download Exchange Server 2003 SP 2 from the Service Pack 2 for Exchange Server 2003 website.

    noteNote
    Windows SBS 2011 Essentials does not directly support migrating Windows SharePoint Services 3.0 or Windows Server Update Services 3.0 from Windows SBS 2003 to Windows SBS 2011 Essentials. For information about migrating Windows SharePoint Services 3.0, see Upgrading to SharePoint Foundation 2010.

Install Windows SharePoint Services 2.0 Service Pack 3

Install Microsoft Core XML Services (MSXML) 6.0 Service Pack 1

Verify the network configuration

To prepare for migration, you must install a router on your network to use as a gateway to the Internet. You must also configure your Source Server to use one network adapter, and disable your virtual private network (VPN) on the Source Server (if it is running).

Reconfiguring your existing network

Before you can migrate your network to Windows SBS 2011 Essentials, 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:

Local area network with broadband connection

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 Essentials Installation Wizard can find the router on your network, ensure that the IP address on the network adapter within the router 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.

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

  4. 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.

  5. If you are using a 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, and make sure that you click Disable remote access on the Remote Access Method page.

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

Verify the settings for the DHCP Server role

Windows SBS 2003 is configured to run the DHCP Server role. However, Windows SBS 2011 Essentials does not use the DHCP Server role, and you will eventually need to move the DHCP Server role to the router. During migration, you can manage the DHCP Server role from the Source Server or from the router, depending on your current network configuration:

  • If you are running the DHCP Server role on the Source Server, we recommend that you continue to run this role from the Source Server during migration. After you have removed the Source Server from the network, move the DHCP Server role to the router.

  • If your network already runs the DHCP Server role from the router, and it is running without issues, we recommend that you continue to run the DHCP Server role from the router during migration.

noteNote
Ensure that your Source Server is in a healthy state before you proceed by performing the procedures in the following section.

Use Windows SBS 2003 Best Practice Analyzer 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 (BPA) to verify that there are no issues on your server, network, or domain before you start the migration process.

noteNote
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

noteNote
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

  • Microsoft 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.

    noteNote
    Check for updates before you scan the server.

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

  4. In the details pane, type the scan label. The scan label is the name of the scan report, for example SBS BPA Scan 8Jun2011. Click Start scanning.

  5. 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 that are 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. For more information and to download this tool, see Netdiag.

Dcdiag.exe

Analyzes the state of domain controllers in a forest or enterprise, and reports issues to assist you in troubleshooting. For more information and to download this tool, see Dcdiag.

Repadmin.exe

Assists you in diagnosing replication issues between domain controllers. This tool requires command-line parameters to run. For more information and to download this tool, see Repadmin.

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

Synchronize the Source Server time with an external time source

The time on the Source Server must be set to 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 Essentials 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.

ImportantImportant
During the Windows SBS 2011 Essentials 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 that is set 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.

Raise the functional level of the Active Directory domain and forest

When Windows SBS 2003 is installed on a server, the functional level of the Active Directory domain and forest are set to the Microsoft Windows 2000 operating system. 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.

ImportantImportant
If you have domain controllers that are running the Windows NT® 4.0 operating system or earlier, or Windows 2000 Server, you must demote them before you can raise the domain functional level to Windows Server 2003. Also, after you raise the domain functional level to Windows Server 2003, you cannot change it back to Windows 2000 mixed mode or to Windows 2000 native mode.

ImportantImportant
You must be a member of the Domain Admins group in the domain for which you want to raise functionality or the Enterprise Admins group in Active Directory Domain Services (AD DS), or you must be delegated the appropriate authority. As a security best practice, you should use Run as to perform this procedure.

To raise the functional level of the domain

  1. On the Source Server, click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.

  2. In the console pane, right-click the domain for which you want to raise the functional level, and then click Raise Domain Functional Level.

    noteNote
    The current domain functional level is displayed in Current domain functional level, in the Raise Domain Functional Level dialog box.

  3. In Select an available domain functional level, click Windows Server 2003, click Raise, and then click OK in the warning dialog box.

To raise the functional level of the forest

  1. On the Source Server, click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.

  2. In the console pane, right-click Active Directory Domains and Trusts, and then click Raise Forest Functional Level.

    noteNote
    The current forest functional level is displayed in Current forest functional level, in the Raise Forest Functional Level dialog box.

  3. In Select an available forest functional level, click Windows Server 2003, click Raise, and then click OK in the warning dialog box.

If you receive a warning about having a Windows 2000 Server domain controller and you want to continue with the migration, you should demote the server that is running Windows 2000 Server to avoid problems during migration.

Prepare Active Directory for migration

To prepare for migration, you need to:

  1. Extend the AD DS schema

  2. Update permissions on the Source Server

  3. Extend the time limit for finishing the migration

You can use the Active Directory Preparation Tool (Adprep32) to extend the AD DS schema and update permissions as necessary to prepare the forest and domain for a domain controller that is running Windows SBS 2011 Essentials. The AD DS schema in Windows SBS 2011 Essentials 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.

ImportantImportant
Back up your Source Server before you run Adprep32. All changes that the tool makes to the schema are irreversible. If you experience issues during the migration, you can only return the Source Server to the state before you ran the tool by restoring the system backup.

ImportantImportant
Be sure that you have installed Windows SBS 2003 Service Pack 2 on the Source Server before you run Adprep32.

noteNote
To run Adprep32, 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).

ImportantImportant
To run Adprep32, 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 Adprep32 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.

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

To prepare Active Directory

  1. Open a Command Prompt window as an administrator. See To open a Command Prompt window as an Administrator.

  2. At the command prompt, type <DVDDrive>:\support\adprep32 /forestprep, where <DVDDrive> is the drive in which you have Windows SBS 2011 Essentials DVD1, and press ENTER.

  3. At the command prompt, type <DVDDrive>:\support\adprep32 /domainprep /gpprep, where <DVDDrive> is the drive in which you have Windows SBS 2011 Essentials DVD1, and press ENTER.

  4. Install the update Software Update to Support “Join Domain” Migration of Windows Small Business Server 2003 Data and Settings to New Hardware. This update extends the time limit for finishing the migration. Normally, only one server running Windows SBS 2011 Essentials 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.

  5. Restart the Source Server.

Create a 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 install 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 collecting information is to run Windows Control Panel, click Programs and look in the Program Files (x86) and the Program Files folders.

 

Application or general data folder name Path to data Notes

 

 

 

 

 

 

 

 

 

Create a plan to migrate email that is hosted on Windows Small Business Server 2003

In Windows SBS 2003, email is provided through Exchange Server 2003. However, Windows Small Business Server 2011 Essentials does not provide an inbox email service. If you are currently using Windows SBS 2003 to host your company’s email, you will need to migrate to an alternate on-premise or hosted solution.

noteNote
After you update and prepare your Source Server for migration, we recommend that you create a backup of the updated server before you continue the migration process.

Next topic: Create a migration answer file for Windows SBS 2011 Essentials migration

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft