Email Migration Scenarios

Reasons Behind Migration

Companies grow at a rapid pace and the functions and scales that are necessary for the company email can change with the growth. In many of these situations, migration of mailbox is necessary to fulfill the new needs. 

For AirWatch Mobile Email Management (MEM) Solutions and other MEM related topics, please refer to the Mobile Email Management (MEM) Guide

 

Migrating Devices

AirWatch can migrate devices across organization groups and MEM deployments. For example, you want to migrate all your devices managed by "MEM Deployment A" to "MEM Deployment B." To do the migration use the following steps:

  • Navigate to Email Dashboard
  • Filter the "MEM Deployment A" managed devices. The List View page displays the filtered results. 
  • Select all devices and click the Migrate Devices option from the Administration drop-down menu.
  • In the Migrate Devices Confirmation screen, enter the given key code to confirm the migration and select the configuration to which you want to deploy the devices. Click Continue

After you perform these steps, AirWatch automatically removes the earlier Exchange ActiveSync (EAS) profile and pushes the EAS profile associated with MEM Deployment B. The new device then connects to its new MEM Deployment B. Finally, AirWatch displays the memconfigID against the device on the Email Dashboard. 

 

Migrating from Exchange earlier version to later version/Office 365 (without SEG)

Note: This is used when your Exchange URL is changing, if not there should not be anything done on the AirWatch side.

If you do not wish to move/migrate in batch (that is, you are moving all users to another Exchange URL at once), then you would need to change the URL in the EAS payload and save and publish again. This will prompt users to enter their password if certificate is not used. 

You will need to have two different profiles with each pointing to each Exchange server URL and assign them to the Smart Groups with users in each Exchange server.

With Smart Group assignment, you can easily move users in bulk without affecting the users that already have the profile assigned to them. 

Note: When you save and publish and Exchange ActiveSync profile after adding a version, devices will get a prompt to enter their email password unless certificate is used. Therefore, unless you are changing the URL or anything in the EAS payload, do not select Add a Version and then publish. Assignment/Smart Group change should not require a new version. Please pay attention to the existing profile. If it is already out of date, it will prompt for a password when getting published since the version will be updated. 

If you would like to have PowerShell or SEG setup after migration, it is recommended to go through the deployment process with the assistance of the AirWatch team, as it will be a first time configuration. Please contact your Account Executive or call into AirWatch Support to discuss he procedure (may require purchase of professional service hours). For additional information regarding Secure Email Gateway and PowerShell, please refer to the Secure Email Gateway (SEG) Administration Guide and the PowerShell Integration Administration Guide

 

Migrating from Exchange earlier version to later version/Office 365 (with SEG)

Migrating with 2 SEG configuration (recommended if device number is large)

 

In this case, another Exchange Active Sync profile will be set up for the second SEG URL and pushed down to the devices that are migrating to the second Exchange server. For more information regarding Multi-MEM and Multi-MEM migration, please refer to the Mobile Email Management (MEM) Deployment and Migration Guide

One SEG is only able to point to one Exchange server, therefore, you would need another SEG server in order to have both Exchange traffic flows going through SEG proxy. For first time setup of a SEG server (even if it is the second one), it is recommended to go through the deployment process with the assistance of the AirWatch team that is dedicated to the implementation. Please contact your Account Executive or call into AirWatch Support to discuss the procedure (may require purchase of services). 

 

Migrating with 1 SEG configuration (recommended if device number is small)

In this case, only the users are on the Exchange server that has SEG pointed to will have their device email traffic going through SEG. You will have to have two profiles of one pointing to the SEG server and one pointing to the Exchange server that is not connected to the SEG server and push down to different Smart Groups.

With Smart Group assignment, you can easily move users in bulk without affecting the users that already have the profile assigned to. 

To redirect traffic from one Exchange server to another URL, locate the web.config file and change the host name URL. 

Note: When you save and publish and EAS profile after adding a version, devices will receive a prompt to enter their email password unless certificate is used. Unless you are changing the URL or anything in the EAS payload, do not select Add a Version and then publish. Assignment/Smart Group change should not require a new version. Please pay attention to the existing profile. If it is already out of date it will prompt for the password when getting published since the version will be updated. 

 

Migrating with 1 SEG configuration and 1 PowerShell configuration

For first time PowerShell Integration, it is recommended to go through the deployment process with the assistance of AirWatch. Please contact your Account Executive or call into AirWatch Support to discuss the procedure (may require purchase of services). 

For this configuration you will have two profiles, one pointing to the SEG server and the other pointing to the Exchange server that is not connected to the SEG server. These profiles will be pushed down to different Smart Groups. 

To redirect traffic from one Exchange server to another URL, locate the web.config file and change the host name URL. 

Note: When you save and publish and EAS profile after adding a version, devices will receive a prompt to enter their email password unless certificate is used. Unless you are changing the URL or anything in the EAS payload, do not select Add a Version and then publish. Assignment/Smart Group change should not require a new version. Please pay attention to the existing profile. If it is already out of date it will prompt for the password when getting published since the version will be updated. 

For more functionality of PowerShell, please refer to the PowerShell Integration Administration Guide

 

Migrating by connecting two Exchange servers

1. Proxying between Exchange environments - In this instance, a new mail environment (2013) will check if the mailbox exists, and if not, proxy back to the old environment to fetch the mailbox. 

2. Redirection of the client to a new environment - This leverages an HTTP 451 redirect to provide the client a new mail endpoint to reach out to. SEG can be leveraged to either cache this information and handle the redirection on behalf of the client, or provide it back to the device. 

 

For more information, see the Microsoft Knowledge Base article on Proxying and Redirection

Have more questions? Submit a request

0 Comments

Article is closed for comments.