Skip Ribbon Commands
Skip to main content

On-Premises Exchange 2007 to On-Premises Exchange 2010, 2013 or 2016 Migration Guide

Last Update: 3/20/2017 1:27 PM

​​​​On-Premises Exchange 2007 to On-Premises Exchange 2010, 2013 or 2016 Migration Guide

Introduction

  • This is the complete onboarding task flow for migrating mailboxes from On-Premises Exchange 2007 to Exchange 2010, 2013 or 2016.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • If your Source server is running Exchange version 2003, or Small Business Server (SBS), refer to KB004952.
  • If migrating from Exchange 2010+ instead of Exchange server 2007, the steps will be the same. However, when preparing your Source server, you should follow the instructions under Option 1 in KB004945 to disable throttling for the admin account that is being used for migration.
  • The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.
  • We strongly recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario. Note: DeploymentPro requires licenses to be purchased before it can be used. KB004875
  • Important: It is not possible to install Exchange 2016 into the same forest as an Exchange 2007 server. Therefore, it is imperative to complete all the prerequisite steps (as listed below) before beginning your migration project. More details can be found in the TechNet article here.

Prerequisites

  • Set up the new AD forest.
  • Configure forest trust.
  • Run the Active Directory Migration Tool (ADMT) to migrate objects over to the new forest.
  • Install Exchange 2013 or 2016 server into the new forest.
  • Create Exchange users on new Exchange server.
  • Set up router ports for OWA traffic. Set different OWA URLS for each environment, and configure the router ports to accept inbound/outbound mail traffic for those OWA URLs. KB005047

Prepare the Source Environment

  1. Set up an admin account for migration on the Source Exchange mailbox server.  KB004725
  2. OWA must be working on the Source Exchange server. KB004392
  3. Test mailbox access. KB004616
  4. Set up router ports for OWA traffic. Set different OWA URLS for each environment and configure router ports to accept inbound/outbound mail traffic for those OWA URLs. KB005047
  5. If you want to migrate archived email with in-flight stub rehydration, deploy the archive extractor agent in the Source environment. KB005639

    Note: Archived email migration is only supported for Veritas Enterprise Vault 9 or later. Read KB005463 to learn more about archive email migration with in-flight stub rehydration.

Prepare the Destination Environment

  1. Set up user accounts.
  2. Create an admin account for migration that has full access permissions to all mailboxes. KB004725
    • Set up a remote PowerShell session with Exchange 2010+. KB005111

    • To manually grant administrative access for migration, execute the following PowerShell command in the Exchange Powershell Console:
    • Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz
    • Notes:
      • In the PowerScript script above, change the -User account to match the name of the admin account that was set up for migration.
      • Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
  3. Disable throttling against the admin account. Refer to Option 1 in KB004945.
  4. Verify mailbox accessibility using EWS.​ KB004304
  5. If using ISA to protect an Exchange Server, make sure that Exchange is published properly. KB004960
  6. If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

    • Increase maximum accepted content length. KB004609
    • Increase maximum receive message size. KB004532
    • Increase maximum accepted re​​​​quest length. This is only valid if your Destination server is running Exchange 2007. KB004610

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    • For the Source endpoint:

      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+
      • Enter the OWA URL. KB004392

      • Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment section of this guide.

    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+
      • Enter the OWA URL. KB004392

      • Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment section of this guide.

  1. Purchase licenses. From your MSPComplete Dashboard, click on Purchase > Mailbox Migration > select MigrationWiz-Mailbox and enter the number of licenses you wish to purchase. Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle).  KB004647
  2. Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:
    • Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. ​KB005412  video
    • Via email. KB005411

DeploymentPro Steps

  1. Launch DeploymentPro.
    • Go to All Products > DeploymentPro and follow the prompts to launch.
    • Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
    • Configure customer DeploymentPro module:
      • Enter the Domain.
      • Select the Destination endpoint.
      • Checkmark the Auto-populate box. 
      • In the Client Interface Configurations section, upload your company logo and add supporting text. Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
      • Save and continue.
  2. Activate DeploymentPro module for users.
    • Either select all users (by checkmarking the box to the left of the Primary Email column heading), or select the individual users (by checkmarking the boxes to the left of the user email addresses). Note: You will need to purchase DeploymentPro licenses for each user that will be using DeploymentPro. KB004647
    • Click on the Run Module button.
  3. Schedule profile cutover date.
    • Set the date and time for the Outlook profile configuration to occur, and click on the Run Module button.
      • Notes:
        • The DeploymentPro module will install on user devices immediately, and then run silently until this date.
        • The profile cutover date should be set to a date and time that is shortly after MX record cutover.
  4. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

MigrationWiz Steps 

Watch this video to see a walk-through of the steps below.

    1. Create the Mailbox Migration project. KB005070

      • Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
    2. If you want to migrate archived email with in-flight stub rehydration, provide additional Source configuration information, such as the Enterprise Vault SQL server and Active Directory information. KB005489

      Note: Archived email migration is only supported for Veritas Enterprise Vault 9 or later. Read KB005463 to learn more about archived email migration with in-flight stub rehydration.
    3. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
    4. Set the Project Advanced Options. KB004834
      • The following options are the most valuable for this migration scenario:
        • Set Maximum concurrent migrations. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1MBPS of bandwidth. Therefore, for example, if there is a 10MBPS connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has a very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
    5. Run Verify Credentials. KB004511
    6. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
    7. Pre-Stage pass: Select the users > Click on the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click on Start Migration. KB004938
    8. MX Record Cutover. Change over MX records on the DNS providers' portal. Also include the AutoDiscover (CName) setting.
      • Note: If migrating in batches and mail coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must perform this extra step:
    9. Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
    10. Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
    11. Run Retry Errors. KB004658
    12. Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
    13. If problems persist, contact Support. KB004529
    14. If not using DeploymentPro, users must create new Outlook profiles, set up their signatures again, and reattach any PST files that were attached to their previous profile.
    15. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
​​​