Target Exchange 2013 Environment Preparation
Follow the steps that are described in the Preparation Overview topic to prepare your Exchange 2013 organization and its environment for being the target organization in the Exchange migration process conducted by Migration Manager for Exchange. For more information about Migration Manager for Exchange refer to the Migration Manager for Exchange Overview.
On some of steps you may need to coordinate the setup process with the administrator of the source Exchange organization.
Preparation Overview
This section provides a short overview of the main steps that should be performed to set up your target Exchange 2013 organization and its environment for migration using Migration Manager for Exchange. These steps are described in detail in the related subtopics.
Setting up the target Exchange 2013 organization consists of four main steps:
Checking the System Requirements
On this step make sure that your environment meets the minimal system requirements for Migration Manager for Exchange agents. For more details, see Checking System Requirements.
Setting Up Accounts and Required Permissions
On this step you should set up the accounts and required permissions for Exchange migration. There are four main types of accounts used by Migration Manager for Exchange agents:
- Target Active Directory Synchronization Account
This account is used by:
- The Directory Synchronization Agent (DSA) to access the target Active Directory domain
- The Migration Agent for Exchange (MAgE) to perform mailbox switch
- Target Exchange Account
This account is used by Migration Manager for Exchange agents installed on agent host to access the target Exchange server.
- Target Active Directory Account
This account is used by Migration Manager for Exchange agents to access the target domain.
- Target Agent Host Account
This account is used to install and run the Migration Manager for Exchange agents on agent host and to access the license server.
You can simplify the setup by using a single account for all Migration Manager for Exchange processes. This account should have the permissions that are required for Migration Manager for Exchange console and all agents on every server that is involved in the migration.
For more details, see Setting Up Accounts and Required Permissions.
Preparing the Target Exchange Environment for Exchange Migration
On this step you should perform common environment preparations:
- Back up Exchange
- Install Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 version 6.5.8353.0 or later on agent hosts
- Create custom throttling policies
For public folder synchronization, the following additional steps are required:
For more details, see Preparing the Target Exchange Environment for Exchange Migration.
Setting Up Connection with the Source Exchange Organization Using SMTP Connectors
On this step you should set up the connection with the source Exchange organization using SMTP connectors. This task consists of three subtasks given below:
- Setting up the target Exchange 2013 organization for Internet mail flow between target and source Exchange organizations
- Configuring target DNS server for mail forwarding
- Testing the SMTP connectors (optional)
For more details, see Setting Up Connection with the Source Exchange Organization Using SMTP Connectors.
Preparation Checklist
This checklist will help you set up your target Exchange 2013 organization and its environment properly. Make sure you have done all the steps below before completing the preparation.
□ |
Check the system requirements |
□ |
Set up the Target Active Directory Synchronization Account |
□ |
Set up the Target Exchange Account |
□ |
Set up the Target Active Directory Account |
□ |
Set up the Target Agent Host Account |
□ |
Back up Exchange |
□ |
Create the Aelita EMW Recycle Bin public folder (optional) |
□ |
Install Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 version 6.5.8353.0 or later on agent hosts |
□ |
Create custom throttling policies |
□ |
Set up the target Exchange organization for Internet mail flow between target and source Exchange organizations |
□ |
Configure the target DNS server for mail forwarding |
□ |
Test the SMTP connectors (optional) |
Prerequisites
Before starting the preparation of the target Exchange 2013 organization and its environment, make sure that you have the privileges to grant all of the following permissions to accounts.
|
NOTE: The list of permissions given below contains all required permissions for the accounts. However some of the permissions can be replaced with their equivalents. For more information, see the corresponding steps for each account. |
Target Active Directory Synchronization Account
- Membership in the Administrators or Domain Admins group of the target domain.
Target Exchange Account
- Read access to the target domain.
- Membership in the local Administrators group on all target Exchange servers involved in the migration. If a server is a domain controller, the account should be added to the domain local Administrators group of the domain.
- Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located.
- Full Control permission on target Exchange 2013 organization
- Permissions to log on to every mailbox involved in the migration.
- Membership in the Recipient Management group.
- The ApplicationImpersonation role in the target Exchange 2013 organization.
Target Active Directory Account
- Read access to the target domain.
- Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located.
- Read permission for the Microsoft Exchange container in the target Active Directory.
Target Agent Host Account
- Membership in the local Administrators group on the license server (unless alternative credentials are used for the license server). If server is located in another trusted forest, the account should have local Administrator permissions on the license server.
- Local Administrator permissions on the agent host server.