You are currently offline, waiting for your internet to reconnect

Migrate to Windows Small Business Server 2011 Standard from an earlier version of SBS

If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
Introduction
When you are ready to migrate from Windows Small Business Server (SBS) 2003 or Windows Small Business Server (SBS) 2008 to Windows Small Business Server (SBS) 2011, you want the migration to be successful the first time.

The migration process is very complex. To avoid any setup failures, carefully follow the steps in this migration guide. Success will depend on careful planning and the completion of every step.

This guide is divided into two sections: "Migrate from Windows SBS 2003 to Windows SBS 2011 Standard" and "Migrate from Windows SBS 2008 to Windows SBS 2011 Standard." Each section is further divided into parts. It is important that you complete all the parts of the appropriate section in the order in which they are presented, and that you complete all the steps in each part in the order in which they are presented.

For an overview of the migration process before you begin, you can view the following video: The following terms and definitions are used in this guide:
  • Source server: The existing server from which you are migrating your settings and data
  • Destination server: The new server to which you are migrating your settings and data
If the Windows SBS 2011 Standard network to which you are migrating will contain more than one server, the following terms are used to distinguish the servers:
  • Primary server: The first server on a Windows SBS 2011 Standard network that contains more than one server
  • Second server: The second server on a Windows SBS 2011 Standard network (which runs the Windows SBS 2011 Premium add-on)

Make sure that you read and understand this migration guide before you try to complete the steps.

When you are ready, practice a migration in a test environment so that you know what to expect. This also lets you test the hardware, and verify that you have the required BIOS updates and drivers. Depending on whether you are migrating from Windows SBS 2003 or from Windows SBS 2008, follow the steps in the appropriate section.
Migrate from Windows SBS 2003 to Windows SBS 2011 Standard

Part 1: Prepare your Source Server for Windows SBS 2011 Standard migration


Step 1: 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. To do this, follow these steps:
  1. Perform a full backup of the Source Server. For more information about how to back 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 the backup, restore them to an alternative location, and then verify that the restored files are the same as the original files.
Step 2: Install all service packs on the source server

Install all the latest service packs on the Source Server. If updates or service packs are not installed, the Source Server is ineligible for migration. In that case, the Migration Preparation Tool reports the problem and prompts you to install the required updates before you continue.

Before you install a service pack, back up your server.
  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.
  2. Install Windows Server 2003 Service Pack 2 (SP2), if it is not yet installed. You can download Windows Server 2003 SP2 at the Windows Server 2003 Service Pack 2 website.

    Notes
    • If you experience network-related issues after you install Windows Server 2003 SP2, click the following article number to view the article in the Micosoft Knowledge Base:
      948496 An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
    • To learn more about the best practices and known issues that are related to Windows Server 2003 SP2, click the following article number to view the article in the Micorostf Knowledge Base:
      939421 Best practices and known issues when you install Windows Server 2003 Service Pack 2 on a Windows Small Business Server 2003-based computer
  3. Install Microsoft Exchange Server 2003 Service Pack 2 (SP2), if it is not installed. You can download Exchange Server 2003 SP 2 from the following Microsoft website:
  4. If you have Windows SharePoint Services 2.0 installed, you must install Service Pack 3 before you begin the migration process. You can download the Windows SharePoint Services 2.0 Service Pack 3 (SP3) from the following Microsoft website:Warning Do not upgrade to Windows SharePoint Services 3.0 until you reach the "Move the internal website for Windows SBS 2011 Standard migration" section.
Step 3: Verify that the Companyweb website is updatedVerify that the Companyweb website is updated. To do this, follow these steps:
  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 website is 6.0.2.8165.
If the version number of the Companyweb website is not correct, use the Stsadm.exe command-line tool to force an upgrade of the content database and of the configuration database. To do this, follow these steps:
  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. At the command prompt, type the following lines, and then press Enter after each line:
    cd /d \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin
    stsadm -o upgrade -forceupgrade -url http://companyweb
  3. Type exit, and then press Enter close the Command Prompt window.
Step 4: Install Microsoft Core XML Services (MSXML) 6.0 Service Pack 1

Download and install MSXML 6.0 from the following Microsoft website:Step 5: 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 follwoign microsoft website: If your Windows SharePoint Services databases have been migrated to Microsoft SQL Server 2000, you can also use the native Microsoft SQL Server 2000 Enterprise Manager in Windows SBS 2003 to install the service pack.

Step 6: 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 it is running). When you are done, your network configuration will resemble the following diagram:

To configure the Source Server to use one network adapter, follow these steps:
  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.
If you are using a virtual private network (VPN) on the Source Server, disable it. To disable the VPN on the Source Server, follow these steps:
  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. Make sure that you click Disable remote access on the Remote Access Method page.
If you have computers or devices that are configured by having static IP addresses or DHCP reservations, you must manually update each of them with the new default gateway IP address. This is because the router is now the gateway device to the Internet. For this same reason, you must use a firewall device to help protect your LAN from unauthorized access. You can use the firewall that is supplied together with your router, or you can use a separate firewall device.

If your router supports the UPnP framework, the following actions occur during the installation of Windows SBS 2011:
  • 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 the Internet Connections window.
Step 7: Internet Security and Acceleration Server 2004

You can continue to use Internet Security and Acceleration (ISA) Server 2004 on Windows SBS 2003 during the migration to Windows SBS 2011. However, ISA Server 2004 with Service Pack 3 (SP3) must be installed and configured before you continue. You can download and install ISA Server 2004 with SP3 from the following Microsoft website: After you install and configure ISA Server 2004 with SP3, configure remote procedure call (RPC) filtering. To do this, follow these steps:
  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 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, click to clear the Enforce strict RPC compliance check box, and then click Apply.
Notes
  • When you clear the Enforce strict RPC compliance check box, DCOM traffic and other RPC protocols become allowed.
  • When you publish an RPC interface if there is a route:network relationship between networks, port overriding is ignored. The publishing rule uses the original IP address or port.
Step 8: Use Windows SBS 2003 Best Practice Analyzer (BPA) or Windows Support Tools to evaluate the health of the Source Server

Depending on the Windows SBS version on the source server, do one of the following:
  • If your Source Server is running Windows SBS 2003, you can run the Windows SBS 2003 Best Practices Analyzer (BPA) Tool to verify that there are no issues on your server, on the network, or on the domain before you start the migration process.
  • If your Source Server is running Windows Server 2003 Standard Edition, you cannot use the Windows SBS 2003 BPA. Instead, run the Windows Support Tools to determine whether there are any network issues that you have to resolve.
To use the Windows SBS 2003 BPA to analyze your Source Server, follow these steps:
  1. Download and install the Windows SBS 2003 BPA from the following Microsoft website:
  2. After the download is finished, click Start, click All Programs, and then click SBS Best Practices Analyzer Tool.
  3. Check for updates before you scan the server.
  4. In the navigation pane, click Start a scan.
  5. 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, the scan label is SBS BPA Scan 8Jun2008.
  6. 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. The following report types are available:
  • 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 the issues that are reported by the Windows SBS 2003 BPA affect migration. However, you should try to resolve as many of the issues as possible to help make sure that the migration is successful. To determine whether there are any other problems that affect the network, run the Windows Support Tools after you run the Windows SBS 2003 BPA.

Run the following Windows Support Tools to diagnose issues on your server, on your network, and on your domain.
ToolDescription
Netdiag.exeHelps isolate networking and connectivity issues
Dcdiag.exeAnalyzes the state of domain controllers in a forest or enterprise, and reports issues to assist you in troubleshooting
Repadmin.exeAssists you in diagnosing replication issues between domain controllers.
Important Correct all the issues that these tools report before you continue with the migration.

Step 9: 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 you start the migration. Send an email message to users that has the following instructions about how to empty the Deleted Items folder and archive older mail.

To empty the Deleted Items folder, follow these steps:
  1. In Microsoft Office Outlook 2007 and in Microsoft Outlook 2003, click Tools in the toolbar, and then click Empty "Deleted Items" Folder. In Microsoft Outlook 2010, right-click Deleted Items in the navigation pane, and then click Empty Folder.
  2. Click Yes in the warning dialog box.
To archive older mail in Outlook, follow these steps:
  1. In Outlook 2007 and in Outlook 2003, click File in the toolbar, and then click Archive. In Outlook 2010, click Cleanup tools on the File menu, and then click Archive.
  2. In the Archive dialog box, click the down arrow next to Archive items older than, and then select a date in calendar that us displayed.

    Note You must tell the users which date to select in the calendar.
  3. If you want to make sure that all the older mail is included, click to select the Include items with "Do not AutoArchive" checked check box.
  4. At the top of the dialog box, click Archive all folders according to the AutoArchive settings.
  5. Click OK.
In Windows XP, the older mail is moved to the archive.pst file in the following folder:
C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Outlook
In Windows 7 and in Windows Vista, the older mail is moved to the archive.pst file in the following folder:
C:\Users\<user name>\AppData\Local\Microsoft\Outlook
For more information about how to optimize Microsoft Exchange Server by using the Microsoft Exchange Best Practices Analyzer Tool, visit the following Microsoft website:Step 10: Synchronize the Source Server time with an external time source

To help make sure 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 do this, follow these steps:
  1. Log on to the Source Server by using 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. At the command prompt, type net stop w32time, and then press Enter.
  4. At the command prompt, type net start w32time, and then press Enter.
The time on the Source Server must be within five minutes of the time on the Destination Server, and the date and time zone settings 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 of the Destination Server.

During the Windows SBS 2011 Standard installation, you have an opportunity to verify the time on the Destination Server and change it, if it is necessary. Make sure 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.

Step 11: Give the built-in Administrators group the right to log on as a 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 require this right to run an alert on the Source Server without logging on.

To give the built-in Administrators group the right to log on as a batch job, follow these steps:
  1. On the Destination Server, click Start, click All Programs, and then click Administrative Tools.
  2. On the Administrative Tools menu, select Group Policy Management.
  3. In the Group Policy Management Console tree, click Forest:<ServerName>, and then click Domains.
  4. Click the name of your server, expand Domain Controllers, right-click Default Domain Controllers Policy, and then click Edit.
  5. In the Group Policy Management Editor, click Default Domain Controllers Policy<ServerName>Policy, expand Computer Configuration, and then click Policies.
  6. In the Policies tree, expand Windows Setting, and then click Security Settings.
  7. In the Security Settings tree, expand Local Policies, and then click User Rights Assignment.
  8. In the results pane, scroll to Log on as Batch Job, and then click Log on as a batch job.
  9. In the Log on as a batch job Properties dialog box, click Add User or Group.
  10. In the Add User or Group dialog box, click Browse.
  11. In the Select Users, Computers, or Groups dialog box, type Administrators.
  12. Click Check Names to verify that the built-in Administrators group is displayed, and then click OK three times.
Step 12: Install Microsoft .NET Framework 2.0 SP1 on the Source Server

If it is not installed already, download and install the Microsoft .NET Framework 2.0 Service Pack 1 (SP1). For more information, see Microsoft .NET Framework 2.0 Service Pack 1 (x86).

Step 13: Install the latest version of the Windows Update Agent

To make sure that the server update process works correctly, visit the Microsoft Update website to automatically install the latest version of the Windows Update Agent. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949104 How to obtain the latest version of the Windows Update Agent to help manage updates on a computer
Step 14: Install Microsoft PowerShell 2 0

To install the Migration Preparation Tool, you must first install Microsoft PowerShell 2 0. For more information about how to download and install the Microsoft PowerShell 2.0, click the following article number to view the article in the Microsoft Knowledge Base:
968929 Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)
Step 15: Install Microsoft Baseline Configuration Analyzer 2.0

To install the Migration Preparation Tool, you must install Microsoft Baseline Configuration Analyzer 2.0. You can download and install the software from the following Microsoft website:Step 16: Verify that you have the appropriate permissions to run the Migration Preparation Tool on Windows SBS 2003

To run the Migration Preparation Tool, you must be a member of the Enterprise Admins group, of the Schema Admins group, and of the Domain Admins group. To verify that you have the appropriate permissions to run the tool on Windows SBS 2003, follow these steps:
  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.
  6. Make sure that the Primary group of the account that you will use to install the SBS 2011 server into the domain is set to something other than Domain Admins, Enterprise Admins, or Schema Admins. To do this, look for the Primary group at the bottom of the Member Of tab. Make sure that the Primary group is not one of the following: Domain Admins, Enterprise Admins, or Schema Admins. To change the Primary group setting, select Domain Users, and then click Set Primary Group.
Notes
  • You might receive a permission error if the Netlogon service is not started.
  • You must log off and log back on to the server for the changes to take effect.
Step 17: Make sure that the Administrator account you are using for the migration has a strong password

To qualify as a strong password, a password must meet the following minimum requirements:
  • Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters.
  • Passwords must be at least six characters in length.
  • Passwords must contain characters from three of the following categories:
    • English uppercase characters (A through Z)
    • English lowercase characters (a through z)
    • Base 10 numerals (0 through 9)
    • Non-alphabetic characters (such as !, $, #, or %)
Step 18: Make sure that Windows SBS 2003 is on a Class C subnet

Windows SBS 2003 must be in a Class C subnet that uses a subnet mask of 255.255.255.0. Windows SBS 2011, in a similar manner as Windows SBS 2008, supports only a Class C subnet. If your Windows SBS 2003 server is not in a Class C subnet, communication problems may occur during Windows SBS 2011 Standard migration setup. To determine the subnet mask that is used on Windows SBS 2003, follow these steps:
  1. Click Start, click Control Panel, right-click Network Connections, and then click Open.
  2. In Network Connections, right-click the network connection that you want to configure, and then click Properties.
  3. In the Local Area Connection Properties screen under This Connection uses the following Items, select Internet Protocol (TCP/IP), and then click Properties.
  4. On the General tab, note the Subnet mask that is configured for the network connection.
Step 19: Install the update for the samsrv.dll file on all Windows 2003 domain controllers

The update for the samsrv.dll file that is described in Knowledge Base article 939820 must be installed on all Windows Server 2003-based domain controllers in your environment, including the Windows SBS 2003 Source Server. To obtain the update, click the following article number to view the article in the Microsoft Knowledge Base:
939820 Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: "No authority could be contacted for authentication" when you use Remote Desktop Connection
Step 20: Change the name of the Postmaster account if it exists in the domain

During the installation of Windows SBS 2011, Setup tries to create a Distribution List that has the SAM account name of "Postmaster." If an account that has the name Postmaster already exists in the domain, regardless of whether the account is on the Source Server or on another server that is running Windows Server, you must rename the account before you start the migration.

Step 21: Remove specific Exchange Server 2003 policies if they exist

Remove the following Exchange Server 2003 policies if they exist on the Source Server:
  • Mailbox Management policies
  • Duplicate SMTP addresses in recipient policies
  • Invalid SMTP addresses in recipient policies
If you have Exchange 2003 or Exchange 2000 recipient policies that are only Mailbox Manager policies and that do not define email addresses (that is, they do not have an E-mail Addresses (Policy) tab), delete the policies. To do this, follow these steps:
  1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
  2. To verify that a policy is only a Mailbox Manager policy, right-click the policy, and then select Properties. To be eligible as a Mailbox Manager-only policy, the policy must not have an E-Mail Addresses (Policy) tab on its Properties tab.
  3. To delete the policy if it qualifies, right-click the policy, and then select Delete.
  4. Click OK, and then click Yes.
If you have Exchange 2003 or Exchange 2000 policies that are both E-mail Addresses and Mailbox Manager policies (that is, they have both the Mailbox Manager Settings (Policy) tab and the E-mail Addresses (Policy) tab), remove the mailbox manager part of the policy. To do this, follow these steps:
  1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
  2. Right-click the policy, and then select Change property pages.
  3. Click to clear the Mailbox Manager Settings check box, and then click OK.
Check for duplicate or invalid SMTP addresses in recipient policies. To do this, follow these steps:
  1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
  2. Right-click the policy, and then click the E-Mail Addresses (Policy) tab.
  3. Examine the check boxes in the SMTP Addresses list for any that are cleared. If you find any, click to select each cleared check box, or remove those addresses.
  4. Examine the SMTP Addresses list for any entries that have an IP address, such as @192.168.1.1. If you find any, remove those addresses that contain IP addresses.
  5. Click OK.
Step 22: Disable Windows Server Update Services on the domain

The Windows Server Update Services (WSUS) may cause the migration to Windows SBS 2011 to fail if it occurs during the migration process. Disable WSUS on the Source Server for the duration of the migration. To do this on the Source Server, open IIS Manager, and then stop the WSUS Administration site.

Step 23: Disable all programs or devices that may update software on any computer in the domain

Programs or devices that automatically install or update software may cause the migration to Windows SBS 2011 to fail if the server is restarted to complete the update or the installation. The following items can be automatically installed or updated:
  • Logon scripts
  • Group Policy-related software
  • Remote management tools
  • Hardware devices, such as printers, that require drivers
Step 24: Verify that the SBS organizational units are present

On the Source Server, verify that the MyBusiness organizational unit (OU) is present and that it contains the expected subcontainers. To do this, follow these steps:
  1. Sign in to the Source Server as an Administrator, and then start Active Directory Users and Computers.
  2. Expand your domain, and then locate an OU that is named MyBusiness.
  3. Expand the MyBusiness OU, and then verify that it contains the following OUs:
Step 25: Run the Exchange Server Pre-Deployment Analyzer

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

Step 26: Verify the health of the Active Directory on the Source Server

If there is only one domain controller, make sure the SYSVOL and NETLOGON shares are present. For more information about how to do this, see Check the Status of the SYSVOL and Netlogon Shares.

Also, if there is only one domain controller, use Event Viewer to examine the File Replication Service event log to see whether the controller is in a Journal Wrap condition. Look for the following logged event:

Event Type: Error
Event Source: NtFrs
Event ID: 13568
Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

If there are more than one domain controllers in the source environment, force an Active Directory replication between the controllers in Active Directory Sites and Services, and then verify that the replication is successful. For more information, see Force Replication Between Domain Controllers.

It may also be useful to run the Microsoft IT Environment Health Scanner diagnostic tool to assess the overall health of the network infrastructure. For more information, see Microsoft IT Environment Health Scanner.

Step 27: Run the Migration Preparation Tool

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 its previous state is to restore the system backup copy.
  1. If the Migration Preparation Tool is already installed on the server, run the tool from the Start menu. If the tool is not installed, follow these steps:
    1. Insert the Windows SBS 2011 Standard DVD1 disk in the DVD drive on the Source Server.
    2. When the Windows SBS 2011 Standard installation wizard starts, click Install the Migration Preparation Tool. Select 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.

    Notes If you receive an error message that is related to a hotfix installation, see “Method 2: Rename the Catroot2 Folder” in the following Microsoft Knowledge Base article:
    822798 You cannot install some updates or programs
  3. 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.
  4. After the source domain is prepared, the Migration Preparation Tool scans the Source Server to identify potential problems. The following kinds of issues that can be identified by the Migration Preparation Tool:
    • Errors: These are issues found on the Source Server and that might block the migration from continuing or cause the migration to fail. You must fix these issues by following the steps that are provided in the issue description. Then, click Scan Again to start the scan.
    • Warnings: These are issues that are 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 issue description to fix the issue before you continue.
    After all the issues are fixed or acknowledged, click Next.
  5. If you have not created a migration answer file, click Create an Answer File, and then follow the instructions. For more information about how to create an answer file, see the "Create a migration answer file for Windows SBS 2011 Standard migration" section in this guide.
  6. Click Finish.
  7. When the Migration Preparation Tool finishes, you must restart the Source Server before you begin 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, the 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.

Step 28: Make a system state backup of the Source Server

For information about how to make a system state backup in Windows SBS 2003, see Back up System State data.

Important Do not make any further changes on the network until the Windows SBS 2011 Standard migration setup is completed. Especially, do not take any of the following actions:
  • Change passwords
  • Install software
  • Remove domain controllers
  • Change network hardware
  • Restore servers
  • Reboot domain controllers
  • Rewire the network
Step 29: 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 to migrate 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 way to begin is to open Control Panel, click Add or Remove Programs, and then examine the Program Files (x86) folder and the Program Files folder.
Application or general data folder namePath to dataNotes

Part 2: Create a migration answer file for Windows SBS 2011 Standard migration


This section introduces the migration answer file, and explains how to use the Answer File Tool to create the migration answer file.

You must use an answer file to start the the migration process during the installation of Windows SBS 2011 Standard. The answer file provides information that is automatically entered into the Windows SBS 2011 Standard installation pages. You can configure an answer file for an attended or unattended installation.

To create a migration answer file, complete the following steps in the order in which they are presented.

Step 1: Collect the information for the migration answer file

Collect the information that is listed in the following table for the answer file.

General information
Information to provideDescription
Clock and time zone settingsIf you choose to manually set the clock and time zone, the migration stops and then prompts you to make the settings. You must manually set the clock in the server BIOS. The system clock cannot be set automatically by using the answer file.
Company information (this information is optional)Name and address of the business (this information is used for settings on your server; it is not sent to Microsoft)

You can edit the company information later in the Windows SBS 2011 Standard Console. To do this, click Help, then click Edit Company Information.
Source Server information
Information to provideDescription
Domain administrator account nameThe user account name of a domain administrator in the existing domain

Important This account must be a member of the Domain Admins, Enterprise Admins, and Schema Admins groups. However, the default security group for the account cannot be one of these three groups.

Note For the migration, we recommend that you create a new administrator account on the Source Server instead of using the built-in Administrator account.
PasswordThe password that corresponds to the domain administrator account name

Note We recommend that you use a strong password for the domain account.
Source Server nameThe name of the server from which you are migrating settings and data
Source domain nameThe full DNS name of your organization's internal domain (for example, contoso.local)
Source Server IP addressThe IP address that is assigned to the Source Server
Default gatewayThe IP address that is assigned to the router on your network
The DHCP Server service is running on the Source ServerSelect this box if the DHCP Server service is running on the Source Server. We recommend that you run the DHCP Server service on the Destination Server. If the DHCP Server service is running on the Source Server, the service will be moved automatically. If the DHCP Server service is running on another server or device, you must manually disable the service.

Note The domain administrator user name and password that you supply in the answer file are also set as the Directory Services Restore Mode (DSRM) user name and password. If you have to log on to the server by using DSRM, you must use the same user name and password that you specified during migration. These passwords do not synchronize. Continue to use the old password to log on to the server by using DSRM after you change the administrator account password on Windows SBS 2011 Standard.
Destination Server information
Information to provideDescription
Destination Server nameThe name of the server to which you are migrating

Note You will install Windows SBS 2011 Standard on this server. The Source Server name and the Destination Server name must differ.
Destination Server IP addressThe IP address that you want to assign to the Destination Server
Step 2: Run the Answer File Tool

To run the Answer File Tool to create the migration answer file, follow these steps:
  1. On a client computer or on a server, insert the Windows SBS 2011 Standard DVD1 disk, and then click Create an answer file. The Answer File Tool opens.
  2. Click Migration from existing server (Join existing domain).
  3. Type the information that you collected based on the table in Step 1.
  4. Save the answer file by using the following file name and extension:
    sbsanswerfile.xml
Step 3: Copy the migration answer file to removable media

Copy the migration answer file to the root partition of a USB flash drive or another type of removable media. Then, connect the removable media to the Destination Server before you start the migration to Windows SBS 2011 Standard. For example, if you used a USB flash drive, plug the flash drive into a USB port.

If the Windows SBS 2011 Standard installation wizard detects a migration answer file, the migration starts automatically.

Important The answer file contains logon and password information that can be used to log on to your server. To help protect your server, delete the answer file after you finish migrating to Windows SBS 2011 Standard.

Note If the Destination Server is a virtual machine, you can create a virtual disk and save the migration answer file there. Then use the virtual disk on the Destination Server before you start the migration mode setup.

Part 3: Install Windows SBS 2011 Standard in migration mode


You are now ready to install Windows Small Business Server 2011 Standard in migration mode on the Destination Server. During migration mode, the Destination Server is joined to the existing domain. The Source Server and the Destination Server can be members of the Active Directory Directory Service (AD DS) domain until the migration process is finished.

Important
  • Windows SBS 2011 Standard requires a 64-bit server. Windows SBS 2011 Standard does not support a 32-bit processor architecture.
  • Before you start the migration, enable the DHCP Server service on the Source Server. Do not enable the DHCP Server service on the router.
  • If DHCP has a custom configuration on the Source Server, back up the DHCP configuration so that it can be restored on Windows SBS 2011 Standard after migration. For more information about how to move a DHCP database, click the following article number to view the article in the Microsoft Knowledge Base:
    962355 How to move a DHCP database from a computer that is running Windows Server 2003 to Windows Server 2008
To install Windows SBS 2011 Standard on the Destination Server, follow these steps:
  1. Turn on the Destination Server, and insert the Windows SBS 2011 Standard DVD1 disk in the DVD drive. If you are prompted to boot from a CD or DVD, press any key to do this. The installation wizard loads files into memory.

    Notes
    • If the Destination Server does not boot from the DVD, restart the computer and check the BIOS configuration to make sure that DVD-ROM is listed first in the boot sequence. For more information about how to change the BIOS boot sequence, see your hardware manufacturer's documentation.
    • If the removable media that contains the answer file is a USB device, you must change the boot order in the BIOS to make sure that the server does not try to boot to the USB device.
  2. Verify your language and regional preferences, and then click Next.
  3. Insert the USB device or other removable media that contains the migration answer file into the Destination Server, and then click Install Now.
    Note The migration answer file is automatically detected on the root of any drive. If the migration answer file is configured to run the installation in unattended mode, values from the file are used during migration. You will not be prompted for values unless they are invalid or missing from the answer file.
  4. Read the license terms. If you accept the terms, click to select the I accept the license terms check box, and then click Next.

    Note If you choose not to accept the license terms, the installation does not continue.
  5. On the Which type of installation do you want page, click Custom (advanced).
  6. If you have to install drivers for your server hardware, click Drive options (advanced) on the Where do you want to install Windows? page. Then, click Load Driver. To install the drivers, follow these steps:
    1. Insert the media that contains the drivers, and then click Browse in the Load driver dialog box.
    2. Browse to the location of the drivers, and then click OK.
    3. When you finish installing the drivers, click Next on the Select the driver to be installed page. You are returned to the Where do you want to install Windows? page.
  7. On the Where do you want to install Windows? page, create and then select the partition in which you want to install the server software.

    If the hard disk that you want to use, such as a Serial Advanced Technology Attachment (SATA) drive, is not listed, you must first download the driver for the hard disk. Obtain the driver from the manufacturer, and then save it to removable media, such as a USB flash drive. Insert the removable media in your server, click Drive options (advanced), and then click Load Driver. After the driver is loaded and the hard disk is listed, complete one of the following steps:
    • To create a partition from unpartitioned space, click the hard disk that you want to partition, click Drive options (advanced), click New, and then type the partition size in the text box. For example, if you use the recommended partition size of 120 gigabytes (GB), type 120000, and then click Apply. After the partition is created, click Next to format the partition.
    • To create a partition that uses all the unpartitioned space, click the hard disk that you want to partition, click Drive options (advanced), click New, and then click Apply to accept the default partition size. After the partition is created, click Next to format the partition.
    Important After you finish this step, you cannot change the partition in which you install the server software.

    Note After this step, the server software is installed in the selected partition, and the Destination Server restarts. If the migration answer file is successfully detected, the Verify the clock and time zone settings page is displayed.
  8. On the Verify the clock and time zone settings page, click Open Date and Time to verify the clock and time zone settings to check the settings. When you are finished, click Next.

    Note If the migration answer file is configured for unattended mode, steps 9 through 12 are completed automatically, unless information in the migration answer file is invalid or missing. If the migration answer file is configured for attended mode, the text boxes on the subsequent installation pages are populated by using the information that you provided in the migration answer file. If the information is not correct, you can change it before you continue.
  9. On the Source and Destination Server networking information page, verify that the default gateway IP address and the IP addresses of the Source and Destination servers and are correct. If appropriate, click to select the DHCP is running on the Source Server check box. Then click Next.
  10. On the Source and Destination Server information page, verify that the information about the Source Server, domain administrator account, Destination Server, and certification authority are correct. Then click Next.

    Note You cannot change the Destination Server name or the internal domain name after you finish this step.
  11. On the Get important updates page, do one of the following:
    • If the Destination Server is connected to the Internet, click Go online and get the most recent installation updates (recommended). If you select this option, the "Connecting your server" page is displayed, and the most recent installation updates are downloaded.
    • If the Destination Server is not connected to the Internet, click Do not get the most recent installation updates. After the installation finishes and you configure Internet access, you can connect to the Internet to get the most recent updates.
  12. On the Company information page, verify that the information is correct, and then click Next.

    Notes
    • The Company information is used to configure the server tools.
    • After you complete this step, the Expanding and installing files page displays the progress of the final installation process. When the Windows SBS 2011 Standard installation finishes, the server restarts.
  13. After the server restarts, do one of the following on the Installation finished page:
    • Click Start the Migration Wizard to close the page and to start using the Windows SBS 2011 Standard Console.

      Note The Home page of the Windows SBS 2011 Standard Console displays the Getting Started Tasks list.
    • If issues are reported to have occurred during installation, click View installation issues on the Installation finished page. The Windows SBS 2011 Standard Console displays the Home page together with the Getting Started Tasks list so that you can start using the Destination Server and resolving the issues.
  14. To complete the migration process, go to "Part 4: Move settings and data to the Destination Server for Windows SBS 2011 Standard migration."
Notes
  • You may receive a Program Compatibility warning message for the Windows SBS 2003 logon script. Click Cancel to exit the warning message. To fix the issue, you must disable or delete the logon script. For more information, see Remove legacy Active Directory Group Policy objects and logon settings for Windows SBS 2011 Standard migration.
  • During the Windows SBS 2011 Standard installation, if the desktop is locked before the Destination Server is promoted to a domain controller, you can unlock the desktop by using the built-in administrator account and by leaving the password blank.
  • During the Windows SBS 2011 Standard installation, if the desktop is locked after the Destination Server is promoted to a domain controller, you can unlock the desktop by using the administrator user account and the password that you provided in the migration answer file.
  • After the installation finishes, you are automatically logged on by using the administrator user account and password that you provided in the migration answer file.
  • To avoid issues when users add printers to their client computers, make sure that the latest 32-bit drivers and 64-bit drivers for your shared printers are available on the network.

Part 4: Move settings and data to the Destination Server for Windows SBS 2011 Standard migration


Now that Windows SBS 2011 Standard is installed on the Destination Server, you must migrate the settings and data from the Source Server to the Destination server. For the remaining parts of the migration process, complete the steps in the following Microsoft TechNet articles in the order in which they are presented:
  1. Move settings and data to the Destination Server for Windows SBS 2011 Standard migration

    How the Migration Wizard helps you migrate settings and data from the Source Server to Windows SBS 2011 Standard.
  2. Move Exchange Server mailboxes and settings for Windows SBS 2011 Standard migration

    How to clean up the Exchange Server database, verify its integrity, and use the Migration Wizard to move Exchange Server mailboxes and settings.
  3. Remove legacy Active Directory Group Policy objects and logon settings for Windows SBS 2011 Standard migration

    How the Windows SBS 2003 logon scripts are replaced by a combination of logon scripts and Group Policy objects in Windows SBS 2011 Standard.
  4. Move users' shared data for Windows SBS 2011 Standard migration

    How to use the RoboCopy tool to copy shared data and folders.
  5. Move the internal website for Windows SBS 2011 Standard migration

    How to use the Migration Wizard to move the internal website and content database to the Destination Server.
  6. Move fax data for Windows SBS 2011 Standard migration

    How to install and configure the fax service on the Destination Server and use the Migration Wizard to migrate fax data.
  7. Migrate Windows Server Update Services data and settings

    How to export software updates and metadata from the Source Server, and then import them on the Destination Server.
  8. Move user accounts and groups for Windows SBS 2011 Standard migration

    How to display the migrated users, security groups, and distribution lists in the Windows SBS 2011 Standard Console.
  9. Enable folder redirection on the Destination Server for Windows SBS 2011 Standard migration

    How to enable Windows SBS 2011 Standard folder redirection by using the Windows SBS 2011 Standard Console, and then deleting the old Group Policy object on the Source Server.
  10. Move Terminal Services Licensing Server for Windows SBS 2011 Standard migration

    How to migrate the service before you decommission the Source Server. If the Source Server is running the Terminal Services Licensing service, you must use this procedure.
  11. Finish Windows SBS 2011 Standard migration

    How to demote and remove the Source Server from the network, and perform other tasks. After you complete the tasks in the Migration Wizard, you must use this procedure.
  12. Delete the old folder redirection Group Policy object for Windows SBS 2011 Standard migration

    How to establish folder redirection on the Destination Server. Perform this task only if you had folder redirection enabled on the Source Server.
  13. Give the built-in Administrator group the right to logon as batch job for Windows SBS 2011 Standard migration

    How to verify that the built-in Administrator group has the right to log on as a batch job to the Destination Server.
  14. Delete DNS entries of the Source Server for Windows SBS 2011 Standard migration

    How to delete the DNS entries that point to the Source Server. After you decommission the Source Server, you must use this procedure.
  15. Optional post-migration tasks for Windows SBS 2011 Standard migration

    How to perform optional tasks after you finish migrating all settings and data to Windows SBS 2011 Standard. For example, you may want to map permitted computers to user accounts, enable folder redirection, configure POP3 connectors, or update mailbox quotas on your new server.
  16. Run the Windows Server Solutions Best Practices Analyzer

    How to download and run the Windows Server Solutions Best Practices Analyzer after you finish migrating settings and data to Windows SBS 2011 Standard.
Migrate from Windows SBS 2008 to Windows SBS 2011 Standard

Part 1: Prepare your Source Server for Windows SBS 2011 Standard migration


Step 1: 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 do this, follow these steps:
  1. Perform a full backup of the Source Server. For more information about how to back up Windows SBS 2008, see Backing Up and Restoring Windows Small Business Server 2008.
  2. Verify that the backup ran successfully. To test the integrity of the backup, select random files from your backup, restore them to an alternative location, and then verify that the restored files are the same as the original files.
Step 2: Install all service packs and updates on the source server
Install all the latest service packs on the Source Server. If updates or service packs are not installed, the Source Server is ineligible for migration. In that case, the Migration Preparation Tool reports the problem and prompts you to install the required updates before you continue.

Important Before you install a service pack, back up your server.

Install Microsoft Exchange Server 2007 Service Pack 3. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
982423 How to install Exchange Server 2007 SP3 on a computer that is running Windows SBS 2008
Note To install Microsoft Exchange Server 2007 Service Pack 3 on Windows SBS 2008, you need to close the Windows SBS 2008 Console and stop the “Windows SBS 2008 Manager” Service. Click Start, click Administrative Tools, and then click Services. Click each service to stop, and then click Stop the service.

Install Windows Small Business Server 2008 Update Rollup 4 if it is not installed already. To determine whether Windows Small Business Server 2008 Update Rollup 4 is installed, follow these steps:
  1. Click Start, click Control Panel, and then double-click Programs and Features.
  2. Verify that Update Rollup 4 for Windows Small Business Server 2008 (KB979454) is listed in the Installed Programs list.
  3. If Update Rollup 4 is not listed, you can download it from the Microsoft Update Catalog.

Step 3: Verify the network configuration

To prepare for migration, you must install a router on your network as the gateway to the Internet. The router should have DHCP disabled and must provide a firewall service, or you must add a firewall device to help protect your LAN from unauthorized access. When you are done, your network will look like the following figure:

If your router supports the UPnP framework, the following actions occur during the installation of SBS 2011:
  • 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.
Step 4: Download and install critical and security updates
Installing critical and security updates on the Source Server helps make sure that your migration will be successful and helps protect your network during the migration process. To synchronize the server with the latest updates, follow these steps:
  1. Click Start, click All Programs, then click Windows Update.
  2. At the bottom-right side of the dialog box, under "You receive updates: Managed by your administrator,” click Check online for updates from Microsoft Update.
  3. If updates are found, click Install updates.
Step 5: Check the System Health reports for critical errors

To generate a system health report from the Windows SBS 2008 Console, follow these steps:
  1. Open the Windows SBS Console.
  2. On the navigation bar, click the Reports tab.
  3. In the Tasks pane, click Generate report.
Step 6: Use Windows SBS 2008 Best Practice Analyzer (BPA) to evaluate the health of the Source Server

You can run the Windows SBS 2008 BPA to verify that there are no issues on your server, network, or domain before you start the migration process. The 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 2008 BPA checks the following components:
  • Exchange Server
  • Update Services
  • Network configuration
  • Windows SharePoint services
  • SQL Server
To use the Windows SBS 2008 BPA to analyze your Source Server, follow these steps:
  1. Download and install the Windows SBS 2008 BPA from the Windows Small Business Server 2008 Best Practices Analyzer website.
  2. After the download is complete, click Start, click All Programs, and then click SBS Best Practices Analyzer Tool.
  3. Check for updates before you scan the server.
  4. In the navigation pane, click Start a scan.
  5. In the details pane, type the scan label, and then click Start scanning.

    Note The scan label is the name of the scan report. For example, the scan label is SBS BPA Scan 8Jun2008.
  6. After the scan finishes, click View a report of this Best Practices scan.
After the Windows SBS 2008 BPA collects and analyzes the information, it presents a list of issues that are sorted by severity. The Windows SBS 2008 BPA describes each issue that it encountered and suggests solutions. The following kinds of reports are available:
  • 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 the issues that are reported by the Windows SBS 2008 BPA affect migration. However, you should resolve as many of the issues as possible to help make sure that the migration is successful.

Step 7: Optimize Exchange Server 2007 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 that includes the following instructions about how to empty the Deleted Items folder and archive older mail.

To empty the Deleted Items folder, follow these steps:
  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, follow these steps:
  1. In Office Outlook 2003 and Office Outlook 2007, click File in the toolbar, and then click Archive. In Outlook 2010, click Cleanup tools on the File menu, and then click Archive.
  2. In the Archive dialog box, click the down arrow next to Archive items older than, and then select a date in calendar that is displayed.

    Note You must tell the users which date to select in the calendar that is displayed.
  3. If you want to make sure that all the older mail is included, click to select the Include items with "Do not AutoArchive" checked check box.
  4. At the top of the dialog box, click Archive all folders according to the AutoArchive settings.
  5. 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 Windows 7 and in Windows Vista, the older mail is moved to the archive.pst file in the C:\Users\<user name>\AppData\Local\Microsoft\Outlook folder.

For more information about how to optimize Exchange Server, see the Exchange Server Best Practices Analyzer tool at the following Microsoft website:

Step 8: Synchronize the Source Server time with an external time source

To help make sure 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 do this, follow these steps:
  1. Log on to the Source Server by uisng 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.
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.

During the Windows SBS 2011 Standard installation, you have an opportunity to verify the time on the Destination Server and change it, if it is necessary. Make sure that the time setting 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.

Step 9: Verify that you have the appropriate permissions to run the Migration Preparation Tool on Windows SBS 2008

To run the Migration Preparation Tool, you must be a member of the Enterprise Admins group, of the Schema Admins group, and of the Domain Admins group. To verify that you have the appropriate permissions to run the tool on Windows SBS 2003, follow these steps:
  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.
  6. Additionally, make sure that the Primary group of the account that you will use to install the SBS 2011 server into the domain is set to something other than Domain Admins, Enterprise Admins, or Schema Admins. On the Member Of tab, look for the Primary group at the bottom. Make sure that the Primary group is not one of the following: Domain Admins, Enterprise Admins or Schema Admins. To change the Primary group setting, click to select Domain Users, and then click Set Primary Group.
Notes
  • You might receive a permission error if the Netlogon service is not started.
  • You must log off and log back on to the server for the changes to take effect.
Step 10: Install Microsoft PowerShell 2 0
To install the Migration Preparation Tool, you must first install Microsoft PowerShell 2 0. For more information about how to download and install the Microsoft PowerShell 2.0, click the following article number to view the article in the Microsoft Knowledge Base: 968929: Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0).

Step 11: Install Microsoft Baseline Configuration Analyzer 2.0
To install the Migration Preparation Tool, you must install Microsoft Baseline Configuration Analyzer 2.0. You can download and install the software from the Microsoft Baseline Configuration Analyzer 2.0 website.


Step 12: Install the latest version of the Windows Update Agent

To make sure 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, click the following article number to view the article in the Microsoft Knowledge Base:
949104 How to obtain the latest version of the Windows Update Agent to help manage updates on a computer
Step 13: Make sure that the Administrator account you are using for the migration has a strong password

To qualify as a strong password, a password must meet the following minimum requirements:
  • Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters.
  • Passwords must be at least six characters in length.
  • Passwords must contain characters from three of the following categories:
    • English uppercase characters (A through Z)
    • English lowercase characters (a through z)
    • Base 10 numerals (0 through 9)
    • Non-alphabetic characters (such as !, $, #, or %)
Step 14: Windows SBS 2003 must be on a Class C subnet

Windows SBS 2003 must be in a Class C subnet that uses a subnet mask of 255.255.255.0. Windows SBS 2011, in a similar manner as Windows SBS 2008, supports only a Class C subnet. If your Windows SBS 2003 server is not in a Class C subnet, communication problems may occur during Windows SBS 2011 Standard migration setup. To determine the subnet mask that is used on Windows SBS 2003, follow these steps:
  1. Click Start, click Control Panel, right-click Network Connections, and then click Open.
  2. In Network Connections, right-click the network connection that you want to configure, and then click Properties.
  3. In the Local Area Connection Properties screen under This Connection uses the following Items, select Internet Protocol (TCP/IP), and then click Properties.
  4. On the General tab, note the Subnet mask that is configured for the network connection.
Step 15: Install the update for the samsrv.dll file on all Windows 2003 domain controllers

The update for the samsrv.dll file that is described in Knowledge Base article 939820 must be installed on all Windows Server 2003-based domain controllers in your environment, including the Windows SBS 2003 Source Server. To obtain the update, click the following article number to view the article in the Microsoft Knowledge Base:
939820 Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: "No authority could be contacted for authentication" when you use Remote Desktop Connection
Step 16: Change the name of the Postmaster account if it exists in the domain

During the installation of Windows SBS 2011, the setup program tries to create a Distribution List that has the SAM account name of Postmaster. If an account that has the name Postmaster already exists in the domain, regardless of whether the account is on the Source Server or on another Windows Server, you must rename the account before the migration begins.

Step 17: Disable Windows Server Update Services on the domain

The Windows Server Update Services (WSUS) could cause the migration to Windows SBS 2011 to fail if an update occurs during the migration process. Disable WSUS on the Source Server for the duration of the migration. To do this on the source server, open IIS Manager, and stop the WSUS Administration site.

Step 18: Disable all programs or devices that may update software on any computer in the domain

Programs or devices that automatically install or update software may cause the migration to Windows SBS 2011 to fail if the server is restarted to complete the update or the installation. The following items can be automatically installed or updated:
  • Logon Scripts
  • Group Policy
  • Remote Management Tools
  • Devices, such as printers, that require drivers
Step 19: Verify that the SBS organizational units are present

On the Source server, verify that the MyBusiness organizational units (OU) is present and that it contains the expected sub-containers. To do this, follow these steps:
  1. Sign in to the Source Server as an Administrator, and then start Active Directory Users and Computers.
  2. Expand your domain, and then locate an OU that is named MyBusiness.
  3. Expand the MyBusiness OU, and then verify that it contains the following OUs:
Step 20: Run the Exchange Server Pre-Deployment Analyzer

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.

Step 21: Verify the health of the Active Directory on the Source Server

If there is only one domain controller, make sure the SYSVOL and NETLOGON shares are present. For more information about how to do this, see Check the Status of the SYSVOL and Netlogon Shares.

Also, if there is only one domain controller, use Event Viewer to examine the File Replication Service event log to see whether it is in Journal Wrap condition. Look for the following logged event:

Event Type: Error
Event Source: NtFrs
Event ID: 13568
Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

If there are more than one domain controllers in the source environment, force an Active Directory replication between them in Active Directory Sites and Services, and then verify that it is successful. For more information, see Force Replication Between Domain Controllers.

It may also be useful to run the Microsoft IT Environment Health Scanner diagnostic tool to assess the overall health of the network infrastructure. For more information, see Microsoft IT Environment Health Scanner.

Step 22: Run the Migration Preparation Tool

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.
  1. If the Migration Preparation Tool is already installed on the server, run the tool from the Start menu. If the tool is not installed, follow these steps:
    1. Insert Windows SBS 2011 Standard DVD1 in the DVD drive on the Source Server.
    2. 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.

    Notes If you receive an error message that is related to a hotfix installation, see “Method 2: Rename the Catroot2 Folder” in the following Microsoft Knowledge Base article: 822798: You cannot install some updates or programs.
  3. The Migration Preparation Tool prepares the Source Server for migration by extending the Active Directory schema. After the task is completed, click Next to continue.
  4. 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 continuing 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 you continue.
    After all the issues are fixed or acknowledged, click Next.
  5. If you have not created a migration answer file, click Create an Answer File and follow the instructions that appear. For more information about how to create an answer file, see the "Create a migration answer file for Windows SBS 2011 Standard migration" section of this guide.
  6. Click Finish.
  7. 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.

Step 23: Make a System State backup of the source server

For information about how to make a System State backup in Windows SBS 2003, see Back up System State data.

Important Do not make any changes on the network until the Windows SBS 2011 Standard migration setup is completed. Especially, do not take any of the the following actions:
  • Change passwords
  • Install software
  • Remove domain controllers
  • Change network hardware
  • Restore servers
  • Reboot domain controllers
  • Rewire the network
Step 24: 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 way to begin is to open Control Panel, click Add or Remove Programs, and then examine the Program Files (x86) folder and the Program Files folder.
Application or general data folder namePath to dataNotes

Part 2: Create a migration answer file for Windows SBS 2011 Standard migration



This section introduces the migration answer file, and explains how to use the Answer File Tool to create the migration answer file.

You must use an answer file to start the the migration process during the installation of Windows SBS 2011 Standard. The answer file provides information that is automatically entered into the Windows SBS 2011 Standard installation pages. You can configure an answer file for an attended or unattended installation.

To create a migration answer file, complete the following steps in the order in which they are presented.

Step 1: Collect the information for the migration answer file

Collect the information that is listed in the following table for the answer file.

General information
Information to provideDescription
Clock and time zone settingsIf you choose to manually set the clock and time zone, the migration stops and then prompts you to make the settings. You must manually set the clock in the server BIOS. The system clock cannot be set automatically by using the answer file.
Company information (this information is optional)Name and address of the business (this information is used for settings on your server; it is not sent to Microsoft)

You can edit the company information later in the Windows SBS 2011 Standard Console. To do this, click Help, then click Edit Company Information.
Source Server information
Information to provideDescription
Domain administrator account nameThe user account name of a domain administrator in the existing domain

Important This account must be a member of the Domain Admins, Enterprise Admins, and Schema Admins groups. However, the default security group for the account cannot be one of these three groups.

Note For the migration, we recommend that you create a new administrator account on the Source Server instead of using the built-in Administrator account.
PasswordThe password that corresponds to the domain administrator account name

Note We recommend that you use a strong password for the domain account.
Source Server nameThe name of the server from which you are migrating settings and data
Source domain nameThe full DNS name of your organization's internal domain (for example, contoso.local)
Source Server IP addressThe IP address that is assigned to the Source Server
Default gatewayThe IP address that is assigned to the router on your network
The DHCP Server service is running on the Source ServerSelect this box if the DHCP Server service is running on the Source Server. We recommend that you run the DHCP Server service on the Destination Server. If the DHCP Server service is running on the Source Server, the service will be moved automatically. If the DHCP Server service is running on another server or device, you must manually disable the service.

Note The domain administrator user name and password that you supply in the answer file are also set as the Directory Services Restore Mode (DSRM) user name and password. If you have to log on to the server by using DSRM, you must use the same user name and password that you specified during migration. These passwords do not synchronize. Continue to use the old password to log on to the server by using DSRM after you change the administrator account password on Windows SBS 2011 Standard.
Destination Server information
Information to provideDescription
Destination Server nameThe name of the server to which you are migrating

Note You will install Windows SBS 2011 Standard on this server. The Source Server name and the Destination Server name must differ.
Destination Server IP addressThe IP address that you want to assign to the Destination Server
Step 2: Run the Answer File Tool

To run the Answer File Tool to create the migration answer file, follow these steps:
  1. On a client computer or a server, insert Windows SBS 2011 Standard DVD1, and then click Create an answer file. The Answer File Tool opens.
  2. Click Migration from existing server (Join existing domain).
  3. Type the information that you collected based on the table in Step one: Collect the information for the migration answer file.
  4. Save the answer file by using the file name and extension sbsanswerfile.xml.
Step 3: Copy the migration answer file to removable media

Copy the migration answer file to the root partition of a USB flash drive or another type of removable media. Then, connect the removable media to the Destination Server before you start migrating to Windows SBS 2011 Standard. For example, if you used a USB flash drive, plug it into a USB port.

If the Windows SBS 2011 Standard installation wizard detects a migration answer file, the migration starts automatically.
Important The answer file contains logon and password information that can be used to log on to your server. To help protect your server, when you finish migrating to Windows SBS 2011 Standard, delete the answer file.


Note If the Destination Server is a virtual machine, you can create a virtual disk and save the migration answer file there. Then use the virtual disk on the Destination Server before you start migration mode setup.

Part 3: Install Windows SBS 2011 Standard in migration mode


You are now ready to install Windows Small Business Server 2011 Standard in migration mode on the Destination Server. During migration mode, the Destination Server is joined to the existing domain. The Source Server and the Destination Server can be members of the Active Directory Directory Service (AD DS) domain until the migration process is finished.

Important
  • Windows SBS 2011 Standard requires a 64-bit server. Windows SBS 2011 Standard does not support a 32-bit processor architecture.
  • Before you start the migration, enable the DHCP Server service on the Source Server. Do not enable the DHCP Server service on the router.
  • If you have DHCP with custom configuration on the Source Server, backup the DHCP configuration so it can be restored on Windows SBS 2011 Standard after migration.

To install Windows SBS 2011 Standard on the Destination Server, follow these steps:
  1. Turn on the Destination Server, and then insert the Windows SBS 2011 Standard DVD1 disk in the DVD drive. If you are prompted to boot from a CD or DVD, press any key to do this. The installation wizard loads files into memory.

    Note If the Destination Server supports booting from USB flash drives, you can use the Windows 7 USB/DVD Download Tool to create a bootable USB Flash drive from the Windows SBS 2011 Standard ISO file. This significantly speeds up the installation process because the Flash drives read much faster than the DVD-Rom drives. After the bootable USB flash drive is created, you can add the answer file to this drive. To download the Windows 7 USB/DVD Download Tool, go to the Windows 7 USB/DVD Download Tool section on the Microsoft Store Help webpage.

    Note If the Destination Server does not boot from the DVD, restart the computer and check the BIOS setup to make sure that DVD-ROM is listed first in the boot sequence. For more information about how to change the BIOS boot sequence, see your hardware manufacturer's documentation.

    Note If the removable media that contains the answer file is a USB device, you must change the boot order in the BIOS setup to make sure that the server does not try to boot to the USB device.
  2. Verify your language and regional preferences, and then click Next.
  3. Insert the USB device or other removable media that contains the migration answer file in the Destination Server, and then click Install Now.

    Note The migration answer file is automatically detected on the root of any drive. If the migration answer file is configured to run the installation in unattended mode, values from the file are used during migration. You will not be prompted for values unless they are invalid or are missing from the answer file.
  4. Read the license terms. If you accept the terms, click to select the I accept the license terms check box, and then click Next.

    Note If you choose not to accept the license terms, the installation does not continue.
  5. On the Which type of installation do you want page, click Custom (advanced).
  6. If you need to install drivers for your server hardware, on the Where do you want to install Windows? page, click Drive options (advanced), and then click Load Driver. To install the drivers, follow these steps:
    1. Insert the media that contains the drivers, and then click Browse in the Load driver dialog box.
    2. Browse to the location of the drivers, and then click OK.
    3. When you finish installing the drivers, click Next on the Select the driver to be installed page. This returns you to the Where do you want to install Windows? page.
  7. On the Where do you want to install Windows? page, create and then select the partition in which you want to install the server software.

    If the hard disk that you want to use, such as a Serial Advanced Technology Attachment (SATA) drive, is not listed, you must first download the driver for the hard disk. Obtain the driver from the manufacturer, and then save it to removable media, such as a USB flash drive. Insert the removable media in your server, click Drive options (advanced), and then click Load Driver. After the driver is loaded and the hard disk is listed, complete one of the following steps:
    • To create a partition from unpartitioned space, click the hard disk that you want to partition, click Drive options (advanced), click New, and then type the partition size in the text box. For example, if you use the recommended partition size of 120 gigabytes (GB), type 120000, and then click Apply. After the partition is created, click Next to format the partition.
    • To create a partition that uses all of the unpartitioned space, click the hard disk that you want to partition, click Drive options (advanced), click New, and then click Apply to accept the default partition size. After the partition is created, click Next to format the partition.
    Important After you finish this step, you cannot change the partition in which you install the server software.

    Notes
    • After the server software is installed in the selected partition, the Destination Server restarts.
    • If the migration answer file is successfully detected, the Verify the clock and time zone settings page opens.
  8. Click Open Date and Time to verify the clock and time zone settings to check the settings. When you are finished, click Next.

    Note If the migration answer file is configured for unattended mode, steps 9 through 12 are completed automatically, unless information in the migration answer file is invalid or missing. If the migration answer file is configured for attended mode, the text boxes on the following installation pages are populated with the information that you provided in the migration answer file. If the information is not correct, you can change it before you continue.
  9. On the Source and Destination Server networking information page, verify that the IP addresses of the Source and Destination Servers and the default gateway IP address are correct. If appropriate, click to select the DHCP is running on the Source Server check box. Then click Next.
  10. On the Source and Destination Server information page, verify that the information about the Source Server, domain administrator account, Destination Server, and certification authority are correct. Then click Next.

    Note You cannot change the Destination Server name or the internal domain name after you finish this step.
  11. On the Get important updates page, do one of the following:
    • If the Destination Server is connected to the Internet, click Go online and get the most recent installation updates (recommended). If you select this option, the Connecting your server page is displayed, and the most recent installation updates are downloaded.
    • If the Destination Server is not connected to the Internet, click Do not get the most recent installation updates. After the installation finishes and you configure Internet access, you can connect to the Internet to get the most recent updates.
  12. On the Company information page, verify that the information is correct, and then click Next.

    Notes
    • The Company information is used to configure the server tools.
    • After you complete this step, the Expanding and installing files page displays the progress of the final installation process. When the Windows SBS 2011 Standard installation finishes, the server restarts.
  13. After the server restarts, do one of the following on the Installation finished page:
    • Click Start the Migration Wizard to close the page and to start using the Windows SBS 2011 Standard Console. The Home page of the Windows SBS 2011 Standard Console displays Getting Started Tasks.
    • If issues are reported to have occurred during installation, click View installation issues on the Installation finished page. The Windows SBS 2011 Standard Console displays the Home page and includes the Getting Started Tasks list so that you can start using the Destination Server and resolving the issues.
  14. To complete the migration process, go to "Part 4: Move settings and data to the Destination Server for Windows SBS 2011 Standard migration" section.
Notes
  • During the Windows SBS 2011 Standard installation, if the desktop is locked before the Destination Server is promoted to a domain controller, you can unlock the desktop by using the built-in administrator account and by leaving the password blank.
  • During the Windows SBS 2011 Standard installation, if the desktop is locked after the Destination Server is promoted to a domain controller, you can unlock the desktop by using the administrator user account and the password that you provided in the migration answer file.
  • After the installation finishes, you are automatically logged on by using the administrator user account and password that you provided in the migration answer file.
  • To avoid issues when users add printers to their client computers, make sure that both the latest 32-bit drivers and 64-bit drivers for your shared printers are available on the network.

Part 4: Move settings and data to the Destination Server for Windows SBS 2011 Standard migration



Now that Windows SBS 2011 Standard is installed on the Destination Server, you must migrate the settings and data from the Source Server to the Destination server. For the remaining parts of the migration process, complete the steps in the following Microsoft TechNet articles in the order in which they are presented:
  1. Move settings and data to the Destination Server for Windows SBS 2011 Standard migration

    How the Migration Wizard helps you migrate settings and data from the Source Server to Windows SBS 2011 Standard.
  2. Migrate the internal website for Windows SBS 2011 Standard migration

    How to move the internal website and content database to the Destination Server.
  3. Move fax data for Windows SBS 2011 Standard migration\

    How to install and configure the fax service on the Destination Server, and then use the Migration Wizard to migrate fax data.
  4. Migrate Windows Server Update Services data and settings for Windows SBS 2011 Standard migration

    How to export software updates and metadata from the Source Server, and then import them on the Destination Server.
  5. Re-apply user roles for migrated accounts

    How to make sure that all migrated user accounts are assigned the correct group membership settings.
  6. Move Terminal Services Licensing for Windows SBS 2011 Standard migration

    How to migrate the service before you decommission the Source Server. If the Source Server is running the Terminal Services Licensing service, you must use this procedure.
  7. Finish Windows SBS 2011 Standard migration

    How to complete the tasks in the Migration Wizard before you continue the migration process.
  8. Demote and remove the Source Server from the network

    How to demote and remove the Source Server from the network, and perform other tasks. After you complete the tasks in the Migration Wizard, you must use this procedure.
  9. Optional post-migration tasks

    How to perform optional tasks after you finish migrating all settings and data to Windows SBS 2011 Standard. For example, you may want to map permitted computers to user accounts, enable folder redirection, configure POP3 connectors, or update mailbox quotas on your new server.
  10. Run the Windows Server Solutions Best Practices Analyzer

    How to download and run the Windows Server Solutions Best Practices Analyzer after you finish migrating settings and data to Windows SBS 2011 Standard.
MORE INFORMATION
For more information about this migration process, visit the Small Business Server forum. You can use the Small Business Server forum to locate answers to your questions, seek advice about your migration plan, or learn what issues other people have encountered during the migration process that you might not have considered.
SBS upgrade how to SMB Portal
Properties

Article ID: 2677001 - Last Review: 04/30/2012 20:03:00 - Revision: 3.0

Windows Small Business Server 2011 Standard

  • kbsurveynew KB2677001
Feedback