Office 365 to On-Premises Exchange (version 2007 and later) Migration Guide

Introduction

This is the complete onboarding task flow for migrating mailboxes from Office 365 to Hosted Exchange or On-Premises Exchange, versions 2007+.

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

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.

DeploymentPro can be used to configure the Outlook profiles.

We are not able to support migrations with two-factor or multifactor authentication. 


Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

 

Prepare the Source Environment

Create an Administrator Account

Create an administrator account in Office 365 to be used for migration or use the global admin account for the tenant. The administrator account must have either full access to the user mailboxes or be granted impersonation rights. We recommend using impersonation as it will help reduce the likelihood of the migration being throttled by Microsoft. 

To manually set impersonation:

  • Use admin credentials at the Destination.
  • Sign in to the MigrationWiz account.​
  • Edit the Project and click on Advanced Options.
  • If migrating from Office 365, under Source, check Use impersonation to authenticate.
  • If migrating to Office 365, under Destination, check Use impersonation to authenticate.
  • Click on Save Options.

MigrationWiz will automatically run a remote PowerShell command to allow the admin account to log in to (impersonate) user mailboxes.

 

Export the user list to a CSV file

This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source and Destination Email columns within your MigrationWiz project dashboard under Add > Bulk Add.

To export the user list:

  • Go to the Office 365 admin portal
  • Click Users
  • Click Active Users
  • Click Export
  • Click Continue

Be sure to save the csv somewhere you can access it for upload later in the migration.

 

Prepare the Destination Environment

Set up the user accounts

You can use the csv acquired in the previous step as an easy reference point for creating these accounts. 

Create Admin Account

Create an admin account for migration that has full access permissions to all mailboxes. 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.

  1. Open the Exchange Management Console.
  2. Expand the Recipient Configuration node.
  3. Right-click on the Mailbox node.
  4. Click on New Mailbox.
  5. Click on Next.
  6. Click on Next.
  7. Enter "MigrationWiz" as the first name.
  8. Enter "MigrationWiz" as the user logon name, and optionally select a user principal name (UPN) domain.
  9. Enter a password and confirm the password.
  10. Click on Next.
  11. Click on Browse to select a Mailbox database.
  12. Click on Next.
  13. Click on New.
  14. Click on Finish.

To grant the account access, perform the following steps while in the Exchange Server machine. The command needs to be applied each time a new mailbox is created, since permissions are set directly on each mailbox. The administrative account will not have access until the permissions are applied.

  1. Open the Exchange Management Shell.
  2. Enter the following command:
    Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz. Change the -User account to match the name of the admin account that was set up for migration. This username is the Administrative Username that needs to be entered under project source or destination settings, within MigrationWiz, when checkmarking the box labeled: Use Administrative Login.

Disable throttling against the admin account

Exchange Server has very low throttling policy limits. We recommend disabling the throttling limits during the migration. This is only relevant if throttling policies are enabled in the Exchange environment. If you are creating or applying a throttling policy on Exchange, you will need to use delegation for this endpoint.

There are two options for this process. Choose which one works for you, and then expand the relevant set of instructions below. 

Option 1

Disable throttling against only the migrating account (if not using impersonation). This way, the admin account can migrate at a faster rate because it is not subjected to any throttling.

Use this option if you are not using impersonation during the migration, but instead using delegation. If migrating using admin credentials, it is only necessary to disable throttling against the admin account, rather than all users. If migrating mailboxes using administrative credentials at the Source, but not using impersonation, we recommend disabling throttling limits on this administrative account in order to improve the speed of migration.

We recommend the creation of a migration administrative account and disabling policy enforcement for this account.

Option 2

Disable throttling against all user accounts (if migrating using an admin account and using impersonation). This way the admin account can migrate at a faster rate because it impersonates user accounts, which are not subjected to throttling.

If migrating mailboxes using administrative credentials at the Source, and using impersonation, disabling throttling limits on all mailboxes will improve the speed of migration, but it is a security risk. The throttling limits are working together to protect an Exchange server from being overwhelmed by accepting and delivering messages.

Read Understanding message rate limits and throttling before you execute the scripts below.

Admin Account: Exchange 2010

To disable all throttling parameters for an admin account called "MigrationWiz":

  1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
  2. Type the following command and press Enter.
    New-ThrottlingPolicy MigrationWizPolicy
  3. Type the following command and press Enter.
    Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
  4. Type the following command and press Enter.
    Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

 

Admin Account: Exchange 2013+

To disable all throttling parameters for an admin account called "MigrationWiz":

  1. Open the Exchange Management Shell.
  2. Type the following command and press Enter.

    New-ThrottlingPolicy MigrationWizPolicy

  3. Type the following command and press Enter.

    Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

  4. Type the following command and press Enter.

    Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

Option 2: Disable throttling against all user accounts (if migrating using an admin account and using impersonation). This way the admin account can migrate at a faster rate because it impersonates user accounts, which are not subjected to throttling.

If migrating mailboxes using administrative credentials at the Source, and using impersonation, disabling throttling limits on all mailboxes will improve the speed of migration, but it is a security risk. The throttling limits are working together to protect an Exchange server from being overwhelmed by accepting and delivering messages.

Read Understanding message rate limits and throttling before you execute the scripts below.

 

All Mailboxes: Exchange 2010

To disable all throttling parameters for all mailboxes:

  1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
  2. Type the following command and press Enter.
    New-ThrottlingPolicy MigrationWizPolicy
  3. Type the following command and press Enter
    Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
  4. Type the following command and press Enter.
    Get-Mailbox | Set-Mailbox -ThrottlingPolicy MigrationWizPolicy

The steps above will remove throttling policies against all user accounts at your Source. You still need to enable impersonation within your MigrationWiz project, so that the admin account can impersonate the user accounts during migrations, and so that the migrations use the bandwidth available to the individual user accounts, rather than just the bandwidth available to the admin account. Follow the directions in the Help Center article How do I migrate to Exchange or Office 365 using impersonation? to enable this.

All Mailboxes: Exchange 2013+

To disable all throttling parameters for all mailboxes:

  1. Open the Exchange Management Shell.
  2. Type the following command and press Enter.

    New-ThrottlingPolicy MigrationWizPolicy

  3. Type the following command and press Enter.

    Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

  4. Enter the following command and press Enter

    Get-Mailbox | Set-Mailbox -ThrottlingPolicy MigrationWizPolicy

The steps above will remove throttling policies against all user accounts at your Source. You still need to enable impersonation within your MigrationWiz project, so that the admin account can impersonate the user accounts during migrations, and so that the migrations use the bandwidth available to the individual user accounts, rather than just the bandwidth available to the admin account. 

 

Verify mailbox accessibility using EWS

  1. Go to https://testconnectivity.microsoft.com
  2. If using Office 365, click the Office 365 tab.
  3. Select Service Account Access (Developers) and click Next.
  4. Specify the target mailbox email address.
  5. Specify the service account user name. If using admin credentials on the connector, enter the exact same user name.
  6. Specify the service account password. If using admin credentials on the connector, enter the exact same password.
  7. Check Specify Exchange Web Services URL and specify the URL (example: https://server/EWS/Exchange.asmx).
  8. If using Exchange Server, do not check Use Exchange Impersonation. If you are using Office 365, and using impersonation, do check the box.
  9. Check Ignore Trust for SSL.
  10. Click Perform Test.
  11. Once results are displayed, check the overall result, and click Expand All.

It may be necessary to first manage permissions.

 

Optional: Large Messages

If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

Increase Message Size Limits

This is a two-step process. The reason for this is that if the message size limits of Exchange are increased, the IIS limits will also have to be increased to allow increased payloads. There are other non-standard settings that can also cause size restrictions for the IIS or EWS connections, but we are unable to troubleshoot or identify specific environment restrictions outside of these settings.

To display current message size limits:

  1. Open the Exchange Management Shell.
  2. Enter the following commands:

Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
Get-SendConnector | Format-List -Property Identity, MaxMessageSize
Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
Get-MailBox | Format-List -Property PrimarySmtpAddress, MaxSendSize, MaxReceiveSize

To increase message size limits on the Exchange Server:

  1. Open the Exchange Management Shell.
  2. Enter the following commands:

Set-TransportConfig -MaxReceiveSize 150MB -MaxSendSize 150MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 150MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 150MB
Get-Mailbox | Set-Mailbox -MaxSendSize 150MB -MaxReceiveSize 150MB

 

Increase IIS Limits to Allow Accepting Payloads

There are three limits that should be increased in IIS:

  • maxRequestLength
  • maxAllowedContentLength
  • maxReceivedMessageSize

Follow these steps to increase the Exchange message size limits on your client access server:

  1. OpenWindows Explorer.
  2. Navigate to %ExchangeInstallPath%FrontEnd\HttpProxy\ews\
  3. Open the file Web.Config in a text editor, such as Notepad.
  4. Find the XML tag starting with for each change.
  5. Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
  6. Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
  7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
    For example:
    <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />
    <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Basic" maxBufferSize="81920" transferMode="Streamed" />
    etc.
  8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
  9. Save the file.
  10. IIS Reset is not needed, web.config changes are picked up by the next connection.

Follow these steps to increase the Exchange message size limits on your mailbox server:

  1. OpenWindows Explorer.
  2. Navigate to %ExchangeInstallPath%ClientAccess\exchweb\ews\
  3. Open the file Web.Config in a text editor, such as Notepad.
  4. Find the XML tag starting with for each change.
  5. Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
  6. Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
  7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
  8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
  9. Save the file.
  10. IIS Reset is not needed, web.config changes are picked up by the next connection.
Increase Maximum Accepted Content Length

You may increase the maximum accepted content length by following these directions:

  1. Open Windows Explorer.
  2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
  3. Open the file Web.Config in a text editor such as Notepad.
  4. Go to the end of the file.
  5. Insert or edit the following XML code before the </configuration> tag:

    <system.webServer>
    <security>
    <requestFiltering>
    <requestLimits maxAllowedContentLength="104857600" />
    </requestFiltering>
    </security>
    </system.webServer>

If XML code is already present in the Web.Config file, edit it to match what is shown above.

Sample Web.Config before changes:

<configuration>
<system.web>
...
...
</system.web>
</configuration>

Sample Web.Config after changes:

<configuration>
<system.web>
...
...
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600" />
</requestFiltering>
</security>
</system.webServer>
</configuration>

 

Increase Maximum Received Message Size

If you are running IIS7 and Windows 2008, you may need to increase WCF settings:

  1. Open Windows Explorer.
  2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
  3. Open the file Web.Config in a text editor like Notepad.
  4. Find all XML tags starting with maxReceivedMessageSize=
  5. Change existing values to maxReceivedMessageSize="104857600"
  6. Save the file.
  7. Open a Command Prompt (cmd.exe).
  8. Type: cd %windir%\system32\inetsrv
  9. Type: appcmd.exe set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600
  10. Run: iisreset

 

 

MSPComplete Steps

Create the customer

Each customer you add will be displayed in your customer list unless you archive it. There are two ways to add customers.

From the All Customer Page

  1. Click the Add button in the top navigation bar
  2. Click the Add Customer button on the All Customers page
  3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
  4. Click Add Customer.
  5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
  6. Click Save.
  7. Repeat steps 1 through 4 for each customer you want to add. 

Add Button

Add customers from the Add button in the top navigation bar

  1. In the left navigation pane, select the appropriate workgroup.
  2. Click Add in the top navigation bar, and then click Add in the drop-down list.
  3. Enter the new customer’s information in the Add Customer form.
  4. Click Save.

    Tip: When you click a customer in the list in the main pane, the name appears under Recent Customers in the left navigation pane.

 

Create Endpoints

Create the Source and Destination endpoints. 

Source

  • Click Endpoints
  • Click Add Endpoint
  • Enter endpoint name
  • For endpoint type, select Office 365.
  • Click the Provide Credentials radio button, and enter the admin account credentials. This should be a global admin account. 

Destination

  • Click Endpoints
  • Click Add Endpoint
  • Enter endpoint name
  • For endpoint type, select Exchange Server 2003+
  • Enter OWA URL

Provide Endpoint Credentials

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

 

Licensing

Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:

To purchase licenses

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose the license type you need.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

Apply Licenses

  1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
  2. On the left navigation pane, click Customers.
  3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
  4. Click the Users tab at the top of the page.
  5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
  6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
  7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm.
    Important: If there are no User Migration Bundle licenses currently available to be assigned and your role in the workgroup is Manager or higher, the form that appears provides all the necessary information and will walk you through the steps of purchasing User Migration Bundle licenses.

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 one of two ways. Select the one you wish to use and follow the steps provided below.

  • Via Group Policy Object (GPO). This is the recommended methodology because no end user interaction is required.
  • Via email.
Deploy via GPO

To deploy the BitTitan Device Management Agent (DMA) using a Group Policy Object (GPO), complete these steps:

  1. Download the DMA setup file from MSPComplete.
  2. Create a network share that is accessible to all of your customer’s computers, and put the DMA setup file in the share folder.
  3. Create a Group Policy Object that forces the domain-joined computers in a security filter to execute the DMA setup file through a scheduled task.

These three steps are explained in greater detail below. 

NOTE: Some environments have settings which can prevent the successful creation of GPO or the running of scheduled tasks. If you are unable to install DMA with a GPO, our recommendation would be to share the install file from step 1 below with your users either via a Shared Drive or via email in order to allow them to run it themselves.  Alternately, you can create a MSI package which can be used to install DMA using your preferred software deployment tool, such as SCCM.

Step 1: Download the DMA setup file from MSPComplete.

  1. In MSPComplete, click on All Customers from the navigation sidebar. 
  2. Click on the customer name for which you wish to deploy DMA.
  3. On the horizontal menu bar, click Users.
  4. Click Add Users, and then click Add Users via Device Management Agent
  5. On the Add Users via Device Management panel, click Device Management setup file to download the DMA setup file to your local drive.  Please note that this file should not be renamed or altered in any way or it could cause issues when DMA is installed.

    Note: These instructions are more detailed than those listed in the Add Users via Device Management Agent panel. 

Step 2: Create a network share that is accessible to all of your customer’s computers, and put the DMA setup file in the share folder.

Note: For more information about Windows Server file and storage services, read File and Storage Services Overview.

  1. Log on to the file server as an administrator.
  2. Click Start and search for Server Manager.
  3. Click Server Manager from the search results.
  4. Click File and Storage Services
  5. Click Shares
  6. Next to Shares, click Tasks
  7. Click New Share
  8. Continue through the New Share Wizard prompts until finished, then click Create
  9. Right-click on the new share in Server Manager, and click Open Share
  10. Put the DMA setup file in the share.
  11. Write down the share's network path. This will be needed when creating the scheduled task.

Step 3: Create a Group Policy Object that forces the domain joined computers in a security filter to execute the DMA setup file through a scheduled task.

  1. Log on to the Active Directory Domain Controller as an administrator.
  2. Click Start and search for Group Policy Management.
  3. Click Group Policy Management
  4. Right-click on the desired Active Directory domain, and then click Create a GPO in this domain, and link it here.
  5. Enter a name for the GPO, and then click Ok.
    Note: By default, the GPO will apply to all users and computers that successfully authenticate to the Active Directory domain.
  6. To narrow the scope of computers that install DMA, select Authenticated Users, and click Remove
  7. To confirm the removal, click Ok.
  8. To add a new security filter, click Add.
  9. Type the name of the security group that the target computers are a member of, and click Check names
  10. Click Ok.
  11. Right-click on the new GPO, and then click Edit
  12. In the console tree, under Computer Configuration , click Preferences > Control Panel > Scheduled Tasks.
  13. Right-click Scheduled Tasks and click on New, and then click on Immediate Task (At least Windows 7).
    Note: For more information about Scheduled Task Items, read the Configure a Scheduled Task Item TechNet article.
  14. Enter a name and a description for the Scheduled Task.
  15. Click Change User or Group
  16. Type "system" in the Object name text box.
  17. Click Check Names
    Note: Make sure that the system object name resolves to NT Authority\System.
  18. Under Security options , click Run whether a user is logged on or not and add a check next to Run with highest privileges.
  19. In the Configure for drop-down menu, select Windows 7, Windows Server 2008 R2
  20. Click the Actions tab
  21. Click on New.
  22. In the Action drop-down menu, select Start a program
  23. In the Programs/script text box, enter the network path for the DMA setup file.



    If you use the Browse button to find the location of the script, then it will add the path as c:\xxxx. This is incorrect since the script needs to include the UNC path and not the local path. Be sure to replace the c:\ format with the \\servername\sharename\ format.
  24. If the customer's computers use a proxy, you must add a command line parameter into the Add arguments field to ensure that DMA is able to transmit data through the proxy. Read the How do I deploy the Device Management Agent on computers that use a proxy? article for more information.
  25. Click Ok.
  26. Click the Conditions tab.
  27. Add a checkmark next to Start only if the following network connection is available, and then select Any connection.
  28. Click Ok
  29. Close Group Policy Management Editor, and then close Group Policy Management.

The DMA setup file will execute on user computers at the next Group Policy refresh, typically every 90 minutes, with a random offset of 0 to 30 minutes.

 

Deploy DMA via Email

To deploy the BitTitan Device Management Agent (DMA) through email, you ask users to manually install the agent.

We recommend installing DMA through a group policy object because it’s automated and non-intrusive.

To deploy DMA through email:

  1. Click Customers on the navigation sidebar.
  2. Click the customer name for which you wish to deploy DMA.
  3. Click Users
  4. Add a checkmark next to the user(s) that should receive the email.
  5. Click the Enable Device Management Through Email  button.
  6. In the Enable Device Management via Email panel, enter your email address in the Reply-To Address  field.
  7. Confirm that all of the users you chose are listed in the Tofield.
  8. To personalize the email message that the customer's users will receive, type your changes into the message body text box. If the customer's computers use a proxy, you must add instructions to run the DMA installer with command line parameters that ensure DMA is able to transmit data through the proxy. Read the How do I deploy the Device Management Agent on computers that use a proxy? article for more information. 
  9. Click Send Agent Email .

The customer’s users will receive the email asking them to manually install the agent. The users and their computer information will start populating in MSPComplete under the customer’s context soon after the agent is installed and running.

 

DeploymentPro Steps

  1. Launch DeploymentPro.
  2. Enter the domain.
  3. Select the Destination endpoint.
  4. Checkmark the Auto-populate
  5. In the Client Interface Configurations section, upload your company logo and add supporting text.
    1. 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.
  6. Save and continue.
  7. Go to All Products > Device Management, then click on DeploymentPro on the far left and follow the prompts to launch.
  8. Select a customer from the list by clicking on the customer name. The status column will show Enabled when a customer account has had DMA deployed to users.
  9. Configure customer DeploymentPro module:
  10. Activate the DeploymentPro module for users.
  11. Either select all users or select individual users.
  12. Click the Schedule Cutover
  13. Schedule profile cutover date.
  14. Set the date and time for the Outlook profile configuration to occur
  15. Click the Schedule Cutover 

 

The profile cutover date should be set to a date and time that is shortly after MX record cutover. The DeploymentPro module will install on user devices immediately and then run silently until this date. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

 

MigrationWiz Steps

Create a Mailbox Migration project

  1. Click the Go to My Projects button.
  2. Click the Create Project button.
  3. Click on the type of project that you wish to create. For this migration:
    • Mailbox: Mailbox projects are used to migrate the contents of the primary user mailbox from the previous environment to the new environment. Most mailbox migrations can migrate email, calendars, and contacts.

For mailbox migrations, use administrative credentials to access mailboxes​. In most migration scenarios, the admin account needs to have full access rights to the Source mailboxes. 

Next:

  1. Click Next Step.
  2. Enter a Project name and select a Customer.
  3. Click Next Step.
  4. Select a Source Endpoint from the Endpoint dropdown menu.
  5. Select a Destination Endpoint from the Endpoint dropdown menu.
  6. Click Save and Go to Summary.

Mailbox Migration Settings: Every setting on the project is applied to all mailboxes associated with that project. For settings that are represented as checkboxes, only selected settings are applied to the project. Not selecting a checkbox does not disable a selected setting inherited from the project.

Add Users

Add the user accounts that will be migrated to the project. This may be done in several ways, depending on the size of the project. Steps for each option are in the accordion below, simply click to show the option you select and follow the guidance there.

Small Migrations:

For small migrations, it is easy to add users one-at-a-time using Quick Add. The steps for this are below. 

Larger Migrations:

For larger migrations, we recommend either using the Autodiscover or Bulk Add option.

Autodiscover will add all users found on the source tenant. This can then be edited in the project to remove users not being migrated. All users will be added with the source and destination email addresses set to match the source email. This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

Quick Add
This option allows you to add items one at a time. You have to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.
Bulk Add

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click on Add .
  4. Click on Bulk Add .
  5. Follow the instructions on the page.
Autodiscover

​The Autodiscover process within MigrationWiz can be used to discover items from the Source environment, so that they can be imported into your projects.

There are few requirements in order for this to work:

  • The Source has to be Exchange 2007 or later, or Office 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
  • The endpoint on the Source needs to use admin credentials.
  • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
  • The admin mailbox must be listed in the public Global Address List (GAL).
  • The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.

One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.

Autodiscover of items will not work while using Modern Authentication

Autodiscovery exposes the following items:

  • For mailbox migration, autodiscovery will list all mailboxes at the Source.

 

Steps to Run Autodiscover

  1. Navigate to the project you want to import users into.

  2. Ensure that you have created an endpoint for the source project.

  3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

  4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

 

Set the Project Advanced Options

Impersonation: Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. 

For large projects only: If this is a large migration project, increase the value for Maximum concurrent migrations​, under the Performance section, e.g.,1000. This can be set to a high number if impersonation is set to be used at the Source, and your Destination Exchange server has plenty of resources available.

 

Run Verify Credentials

You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click on the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration.

Begin Migration

Pre-Stage pass

  1. Select the users you wish to migrate
  2. Click the Start button from the top
  3. Select Pre-Stage Migration
  4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago
  5. Click Start Migration.

MX Record Cutover

Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.

Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to Sample email to send to users before their Outlook profile is reconfigured for some sample text and screen shots that can be included in this email.

Full (Delta) pass

  1. Select the users
  2. Click the Start button from the top
  3. Select Full Migration
  4. Click Start Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

 

Post-Migration

If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

 

Was this article helpful?
0 out of 1 found this helpful