Connecting to a source Exchange server
Once the installation of CodeTwo Exchange Migration is finished, you have to choose a source environment from which the data will be pulled and migrated to selected mailboxes on target Exchange Server. This article describes how to connect to a source Exchange server.
There are two recommended connection methods for Microsoft Exchange Server: EWS and MAPI (IMAP can also be used, but it is best suited for other servers - learn why). By default, the program will ask you to configure a source server connection when you create your first migration job. Click on the links below to learn how to configure each connection method.
- Create an EWS source connection (recommended when connecting to on-premises Exchange 2010 SP1, 2013, 2016 and 2019)
- Create an EWS source connection to a hosted Exchange server (e.g. Intermedia, Rackspace and GoDaddy)
- Create a MAPI source connection (use only when connecting to Exchange 2010 without SP1)
Configure an EWS source connection
You can create a new source connection when you configure a migration job: click Create a new migration on the How to start card (see Fig. 1.) and select Exchange Server. In the first step of the wizard, type the name of your job and proceed to the Source mailboxes step. Select Add new source connection from the Source server drop-down list to open the Exchange source server connection wizard.
Fig. 1. Creating a new source server connection.
You can also start the wizard directly from the Dashboard tab by clicking the Settings () button on the Defined source server connections card and choosing New > Exchange Server connection.
The Exchange source server connection wizard opens with the Protocol step displayed, where you can choose how to connect to your source Exchange Server. Select EWS protocol, as shown in Fig. 2. To proceed, click Next.
Important
You should use EWS if you connect to Exchange 2010 (with SP1) or 2013. You need to use EWS if you connect to Exchange 2016 and 2019.
Fig. 2. Selecting a connection protocol.
In the Server connection step, decide how the program will connect to your source Exchange server. This scenario assumes that you have access to the source Exchange server domain and have installed the program on any machine within that domain (if not, go to this section of the article). Use the Autodiscover Exchange Server option (Fig. 3.) if you want the wizard to find the right server on the basis of the account credentials provided in the next step. Otherwise, choose the second option to configure the connection to the source server manually.
Fig. 3. Selecting how you want to connect to a source Exchange server (EWS connection).
If you chose the Connect to a specific server option, provide the server's Fully Qualified Domain Name (i.e. the server's name followed by the domain name, e.g. myservername.domain.com) or IP address. The EWS URL will be filled in automatically.
Important
You need to provide an FQDN that will allow the software to create both an EWS and a PowerShell connection to your Exchange server. In most cases, these requirements will be fulfilled by the internal FQDN of your server. If you use an external endpoint, make sure that it accepts EWS and PowerShell connections.
In the Admin account step, you need to provide a valid UPN and password of an account that will access the mailboxes on the source Exchange server (Fig. 4.). Make sure that this account is assigned the necessary management roles, as shown in the wizard, or let the program do it for you in the next step. Learn more about the source EWS connection requirements.
Fig. 4. Providing admin account credentials to connect via EWS.
By default, the program will automatically fill in the UPN field with credentials of the admin who is currently logged in to your machine. Use the Browse button if you want to choose another account from your source domain (remember that this account must be mailbox-enabled). Provide the password and click Next.
In the last step, Configuration, the wizard will set up the connection to your source Exchange server. Click Configure and verify the results. In case the account provided in the previous step lacks some of the necessary roles, the program will attempt to assign them automatically (Fig. 5.). Click Yes to accept.
Fig. 5. Assigning the missing management roles.
You might be prompted to provide the credentials of another account that belongs to the Organization Management role group (Fig. 6.). This account will not be used to connect to the source server, but only to assign the missing roles. Learn more about the management roles.
Fig. 6. Providing credentials of an account that has appropriate roles assigned.
Once the setup is complete (Fig. 7.), click Finish to close the window (if you encounter any problems, see Troubleshooting). You can now move on to configure a target on-premises Exchange server of your choice.
Fig. 7. Successful configuration of an EWS connection with a source Exchange server.
When you complete the wizard, the new connection will be displayed on the Defined source server connections card (Fig. 8.).
Fig. 8. Defined source server connections.
Create an EWS source connection to a hosted Exchange server
You can create a new source connection when you configure a migration job: click Create a new migration on the How to start card (see Fig. 9.) and select Exchange Server. In the first step of the wizard, type the name of your job, select The program is installed outside the source Exchange server domain and proceed to the Mailboxes step. Select Add new source connection from the Source server drop-down list to open the Exchange source server connection wizard.
Fig. 9. Creating a new source server connection.
You can also start the wizard directly from the Dashboard tab by clicking the Settings () button on the Defined source server connections card and choosing New > Exchange Server connection. If you do so, the wizard will show the Protocol step, where you need to select EWS protocol first.
This scenario assumes that you want to connect to a hosted Exchange server, which means you don’t have access to the source Exchange server domain and have installed the program outside the source domain (e.g. on a client machine inside your organization). In the Server connection step, select Connect to a specific server > The program is installed outside the source Exchange server domain (if it’s not selected by default). Next, provide the server's Fully Qualified Domain Name (i.e. the server's name followed by the domain name, e.g. myservername.domain.com) or IP address. The EWS URL field will be filled in automatically (Fig. 10.). Click Next to proceed.
Fig. 10. Configuring a connection to a hosted Exchange server.
In the Admin account step, provide the primary SMTP address, e.g. [email protected], and password (as shown in Fig. 11.) for the admin account that will be used by the program to access source mailboxes. The ApplicationImpersonation role must be assigned to this account prior to the migration.
Important
The ApplicationImpersonation role needs to be assigned only for these mailboxes you’re going to migrate – you don’t need organization-wide impersonation permissions. Learn how to set the impersonation rights manually for all or selected mailboxes
Fig. 11. Providing admin account credentials to connect via EWS to a hosted Exchange server.
In the last step of the wizard (Configuration), the program will test and finally set up the connection to the source hosted Exchange server – to do it, click the Configure button. Once the connection test has finished with success, you will see the screen with green checkmarks (Fig. 12.).
Fig. 12. Summary of a successful connection to a source hosted Exchange server.
To verify whether the used admin account is authorized to impersonate a chosen user account which you want to migrate, click Check the impersonation settings.
In the pop-up window that opens, enter the primary SMTP address of a chosen user on your server and click the Check button (Fig. 13.). If your admin account is assigned the ApplicationImpersonation role for that user, you will see an appropriate confirmation message.
Fig. 13. Checking if the admin account can impersonate a given user account and access its mailboxes.
If you are done, click Finish to close the server connection wizard. You can now select this connection when configuring a migration job. The new connection will be displayed on the Defined source server connections card on the Dashboard as well.
Configure a MAPI source connection
You can create a new source connection when you configure a migration job: click Create a new migration job on the How to start card (see Fig. 14.) and select Exchange Server. Type the name of your job, and proceed to the Source mailboxes step. Select Add new source connection from the Source server drop-down list to open the Exchange source server connection wizard. You can also start the wizard by clicking the Settings () button on the Defined source server connections card and choosing New > Exchange Server connection.
Fig. 14. Creating a new source server connection.
The Exchange source server connection wizard opens with the Protocol step displayed, where you can choose how to connect to your source Exchange Server. Select MAPI protocol, as shown in Fig. 15. To proceed, click Next.
Important
You need to choose the MAPI protocol if you connect to Exchange 2010 without SP1.
Fig. 15. Selecting a connection protocol.
In the next step, Server connection, you decide how the program will connect to your source Exchange server. You can choose the Autodiscover Exchange Server option if you want the wizard to find the right server on the basis of the account credentials provided in the next step, or connect to the server manually (Fig. 16.).
Fig. 16. Selecting a source Exchange server (MAPI connection).
If you chose the second option, Connect to a specific server, in order to configure the connection manually, provide the server's Fully Qualified Domain Name (i.e. the server's name followed by the domain name, for example myservername.domain.com) and pick its Exchange version, or use the Browse button to select a previously defined Exchange server (if applicable). Click Next to continue.
The program will create a Windows service that uses a MAPI profile to access source mailboxes selected for the migration. In the third step of the wizard (Fig. 17.), Service account, you need to provide credentials of an account that will be used by this service. The information about all the account requirements is shown in the wizard (learn more).
Fig. 17. Configuring the service account for a MAPI profile.
By default, the application will automatically fill in the account name with credentials of the admin who is currently logged in to your machine. Use the Browse button if you want to choose another account from your domain (remember that this account must be mailbox-enabled). Provide the password and click Next.
Important
After you finish the configuration of your MAPI source connection, the program will automatically create a MAPI profile for the admin's mailbox you selected.
CodeTwo Exchange Migration needs the MAPI profile of a source server administrator in order to work. If the profile is not configured, the service will not be able to access source mailboxes. What is more, the administrator whose account is used in the MAPI profile configuration must belong to an appropriate group (depending on the source server used within your environment). Otherwise, the program will not run correctly and errors are likely to appear.
In the last step of the wizard (Configuration) you can finally create the source server connection. Click Configure and verify the results. Once the setup is complete (Fig. 18.), click Finish to close the window (if you encounter any problems, see Troubleshooting). You can now move on to configure a target on-premises Exchange server of your choice.
Fig. 18. Configuration of a MAPI connection with a source Exchange server.
When you complete the wizard, the new connection will be displayed on the Defined source server connections card (Fig. 19.).
Fig. 19. Defined source server connections.
The program allows you to create multiple connections via EWS, but only one connection if you access the source environment via MAPI (MAPI can only be used within the same domain).