Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - Target Exchange 2010 Environment Preparation (Legacy)

Target Exchange 2010 Environment Preparation
Preparation Overview Checking System Requirements Setting Up Accounts and Required Permissions Preparing the Target Exchange Environment for Exchange Migration Setting Up Connection with the Source Exchange Organization Using SMTP Connectors Appendix A: Exchange 2003 to Exchange 2010 Migration Restrictions

Disable RPC Encryption on Target Exchange 2010 Servers (Optional)

Caution: This step should be performed only in the Exchange 2003 to Exchange 2010 migration scenario in the following cases:

  • Mailbox Source Agent (MSA) is installed directly on the Exchange 2003 server and is configured to check whether the last PST file has been delivered (default setting).
  • Calendar Synchronization Agent (CSA) is installed directly on the Exchange 2003 server.

The EncryptionRequired parameter specifies whether encryption of connections to the Exchange 2010 server is required. The Exchange RPC Client Access service rejects unencrypted connections if this parameter is set to $true.

During the migration, agents that are installed on the source Exchange Server 2003 require connection to Exchange 2010 to perform some operations. Migration Manager for Exchange agents create unencrypted connections, so if the agents are installed on the source Exchange Server 2003, you need to remove the RPC encryption requirement to log on to the target Exchange 2010 server.

NOTE: To avoid disabling RPC encryption perform one of the following steps:

  1. Use agent hosts in the source Exchange 2003 organization.
  2. Install Calendar Synchronization Agent (CSA) in the target Exchange 2010 organization and disable last PST check.

To disable the RPC encryption requirement, use the Exchange Management Shell to run the following command on all target Exchange 2010 servers with mailbox databases and public folder databases that are associated with mailbox databases as well as on all target Exchange 2010 servers with the Client Access Server (CAS) role installed:

Set-RpcClientAccess –Server <Exchange 2010 Server Name> –EncryptionRequired $false

Setting Up Connection with the Source Exchange Organization Using SMTP Connectors

This section describes how to set up a connection with the source Exchange organization using SMTP connectors. On this step you may need to coordinate with the administrator of the source Exchange organization to set up the connection properly.

For more details, see the related topics:

Setting up Target Exchange Organization for Internet Mail Flow between Target and Source Exchange Organizations

You need to establish Internet mail flow between the target and the source Exchange organizations. For that, one of the following methods can be used:

  • Establishing Internet mail flow directly through a Hub Transport server.
  • Establishing Internet mail flow through a subscribed Edge Transport server.

Establishing Internet Mail Flow Directly Through a Hub Transport Server

If you choose this option, you need to create an Internet Send connector and Receive connector on an Exchange 2010 Hub Transport server that can be directly reached through the Internet.

To establish mail flow to and from the Internet through a Hub Transport server, follow these steps:

  1. Create a Send connector (to send email from source Exchange 2010 organization to the Internet) on the Hub Transport server.
  2. Modify the default Receive connector for the source domain to accept anonymous e-mail from the Internet
  3. Add the e-mail domain used for redirection to the list of accepted domains on the Hub Transport server.

Each step is explained in further detail in the related subtopics.

NOTE: For information about configuring Receive connectors in Exchange 2010 organization, refer to the following Microsoft Knowledge Base articles:

  • Allow Anonymous Relay on a Receive Connector
  • Configure the Receive connector as externally secured
Related Documents