Chat now with support
Chat with Support

Binary Tree Migrator Pro for Exchange 20.10.1 - Installation and Configuration Guide

2.5 Uninstalling Migrator Pro for Exchange

This section provides information for:

  • Upgrading Migrator Pro for Exchange from an Earlier Version

  • Necessary Pre-Installation Preparations

  • Migrator Pro for Exchange Default Installation

  • Migrator Pro for Exchange Advanced Installation or Upgrade

  • Uninstalling Migrator Pro for Exchange

2.1 Upgrading Migrator Pro for Exchange from an Earlier Version

Migrator Pro for Exchange can be easily upgraded to a newer version by running the installation wizard for the new release. The wizard will detect any previous version and offer you the option to upgrade. The previously existing SQL database and configuration settings are preserved when upgrading.


Migrator Pro for Exchange provides a direct upgrade path only from its most recent prior GA version (and any subsequent minor releases).  If you want to upgrade from an earlier version, we recommend incremental upgrades, one version at a time.

If the Migrator Pro for Exchange Installer detects a previous version of Migrator Pro for Exchange, it will skip the screen that offers the Default Installation option (as described in section 2.3 below), and will perform an upgrade using the Advanced Installation (as described in section 2.4 below).


Even if a prior Migrator Pro for Exchange version has been uninstalled, the Installer will still perform the installation as an upgrade (by an Advanced Installation) if it finds this entry remaining in the Windows registry:

HK_Local_Machine\Software\Binary Tree\E2E

If you have uninstalled a prior Migrator Pro for Exchange version and now want to run the Default Installation option for the new version, you must first remove that entry from the registry.

2.2 Necessary Pre-Installation Preparations

The Migrator Pro for Exchange server should be installed in one of the following locations:

  • For Intra-org (same forest) or Office 365 installations the Migrator Pro for Exchange server should be installed in the Source forest.

  • For Inter-org (cross forest) migrations, the Migrator Pro for Exchange server should be installed in the Target forest.

  • For migrations to an Exchange resource forest, the Migrator Pro for Exchange server should be installed in the resource forest.

Prior to installing Migrator Pro for Exchange, you need to identify the primary Exchange 2010 and/or Exchange 2013 servers utilized as the PowerShell hosts.

Note also that Outlook must be installed on the Migrator Pro for Exchange server to facilitate MAPI transport for migrations. See the Migrator Pro for Exchange Requirements document for supported versions and other relevant notes.


Migrator Pro for Exchange supports either non-SSL or SSL mode for the PowerShell provider. If you want to utilize non-SSL, then no further action is required; however, if you want to utilize SSL mode for the PowerShell provider, you must make sure that the Migrator Pro for Exchange system trusts the certificate on your Exchange server.

Migrator Pro for Exchange requires a non-self-signed certificate on the Exchange 2010 and/or 2013 servers that will host PowerShell. This can be a public certificate (i.e., VeriSign) or a private certificate (i.e. Windows Certificate Services). The PowerShell host servers need not also be a Client Access Server (CAS) host.

The image below displays the Exchange Certificates in Exchange 2010. The interface in other versions of Exchange is different.

It is recommended that the PowerShell host servers be under-utilized servers, so that any additional load on the production Exchange server can be avoided.

Note also that your remote PowerShell connection will require port 5985 be open for http, and port 5986 for https.

Once the PowerShell machine is identified, perform the following prerequisite PowerShell commands. This applies to both SSL and non-SSL modes.

To execute these commands, launch the Exchange Management Shell:

  1. Click Start, and then point to All Programs. Expand Microsoft Exchange Server 2010 (shown in the image below), Microsoft Exchange Server 2013, or Microsoft Exchange Server 2016 and then click Exchange Management Shell.

  2. In the Exchange Management Shell window, execute the following command:

    Enable-PSRemoting

    This command configures the machine on which it is run, to receive Windows PowerShell remote commands.


  3. Press <Y> to continue.

  4. Press <Y> again to confirm.


  5. The next command lets you authenticate against the server being used as the remote PowerShell host server:

    Set-PowerShellVirtualDirectory “<Exchange Server name>\PowerShell (Default Web Site)” –BasicAuthentication $true

    If using non-SSL mode, Windows Authentication should also be enabled using this command that includes the additional Windows Authentication command:

    Set-PowerShellVirtualDirectory “<Exchange Server name>\PowerShell (Default Web Site)” –BasicAuthentication $true-WindowsAuthentication $true



When the command is executed, even though it configures the system for basic authentication, all the data, including passwords, are encrypted using SSL.

 

Default Installation vs. Advanced Installation

Migrator Pro for Exchange is installed by an Installation wizard. The Installation wizard offers you a choice of two installation types:

  • Default Installation: The wizard will scan your environment to determine the information necessary for installation, and then will install according to those specifications. This option will automatically install SQL Express if no SQL server is detected on the local machine.

  • Advanced Installation: The wizard will lead you through a series of screens for you to specify where you want to install Migrator Pro for Exchange, and the names, locations, and access credentials for certain network and program components, and will then perform the installation to those specifications.

The Default Installation option will suit most organizations. The Advanced Installation will be appropriate if you want to specify particular components other than those the wizard would find and use by default. The two options are described separately in the next two sections below.

2.3 Migrator Pro for Exchange Default Installation

To run the Default Installation option in the Installation wizard:

  1. Once the PowerShell commands are successfully executed, navigate to the folder where you saved the Migrator Pro for Exchange Installation files, then right-click on the Migrator Pro for Exchange Install file and select to Run as Administrator.


  2. Click Run on the security warning, and then click Next on the Welcome screen:

     


  3. The wizard then prompts you to review and accept the Migrator Pro for Exchange license and maintenance agreement. To accept the agreement, select the I accept… radio button and click Next.

     

  4. If you accept the license terms the wizard then prompts you to choose between Default Installation and Advanced Installation. Click on the Default Installation option.

     


If the Migrator Pro for Exchange Installer detects a previous version of Migrator Pro for Exchange, it will skip this screen that offers the Default Installation option, and will perform an upgrade using the Advanced Installation process.  Even if a prior Migrator Pro for Exchange version has been uninstalled, the Installer will still perform the installation as an upgrade (by an Advanced Installation) if it finds this entry remaining in the Windows registry:

HK_Local_Machine\Software\Binary Tree\E2E

If you have uninstalled a prior Migrator Pro for Exchange version and now want to run the Default Installation option for the new version, you must first remove that entry from the registry.

 


The wizard then scans your environment to gather the information it needs, and to determine whether you need to install any of several required accessory applications.  A progress meter shows the wizard’s progress:

These accessory components are required for the Migrator Pro for Exchange installation:

  • Windows features IIS and .NET Framework 4.5.2 full

  • SQL 2012 Express with Tools SQ2 x64 (includes SQL Studio Manager)

    • [local]\SQLEXPRESS installs as a named instance using the format servername\SQLExpress

    • Installs in Mixed mode with install account as SA, and local SA password is Password1

  • Silverlight 5

  • Microsoft Online Sign-on assistant

  • Azure AD PowerShell module

    If you already have these accessory apps installed, you can just skip ahead to the next step below. Otherwise, the Migrator Pro for Exchange installer will prompt you to authorize the installation of the ones you need.  In that case, click the Install button to accept. If you have to install Microsoft .NET 4.5.2 Framework, you may also be prompted to accept Microsoft’s license agreement.  If so, mark the checkbox for I have read and accept…, and click Install.

    The installation of accessory applications may take several minutes.  Some of the newly installed components may then require a system reboot, in which case the wizard will also prompt you to authorize the reboot.  Click Yes to authorize the reboot.  If you do have to reboot, the wizard will automatically resume at the next screen in this process (next step below).


  1. The wizard then prompts you for the login credentials Migrator Pro for Exchange should use for its MCP Service and the Migrator Pro for Exchange AppPool.  Enter the credentials and click Next.

 


The installation resumes when you click Next, and a progress meter shows the progress, and notifies you when the installation is complete:

  1. Click the Finish button to close this portion of the wizard. Another progress meter shows the process progress through this last phase of the installation, and the wizard then notifies you when the process is complete:

  2. Click this Finish button to close the Migrator Pro for Exchange Installer.

Now that the physical installation is complete, see section 3 below to configure Migrator Pro for Exchange for your environment and purposes. The first time you run the Migrator Pro for Exchange Admin Portal after this installation, Migrator Pro for Exchange will prompt you to define your target forest.

2.4 Migrator Pro for Exchange Advanced Installation or Upgrade

To run the Advanced Installation option in the Installation wizard (for either a fresh installation or an upgrade):

  1. Once the PowerShell commands are successfully executed, navigate to the folder where you saved the Migrator Pro for Exchange Installation files, then right-click on the Migrator Pro for Exchange Install file and select to Run as Administrator.

  1. Click Run on the security warning, and then click Next on the Welcome screen:


  2. The wizard then prompts you to review and accept the Migrator Pro for Exchange license and maintenance agreement. To accept the agreement, select the I accept… radio button and click Next.

     

  3. If you accept the license terms the next prompt asks you to choose between Default Installation and Advanced Installation. Click on the Advanced Installation option.


If the Migrator Pro for Exchange Installer detects a previous version of Migrator Pro for Exchange, it will skip this screen that offers the Default Installation option, and will perform an upgrade using the Advanced Installation process.

The wizard then scans your environment to gather the information it needs for installation, and to determine whether you also need to install any required accessory applications.  A progress meter shows the progress:

These accessory components are required for the Migrator Pro for Exchange installation:

  • Windows features IIS and .NET Framework 4.5.2 full

  • Silverlight 5

  • Microsoft Online Sign-on assistant

  • Azure AD PowerShell module

    If you already have these accessory apps installed, you can just skip ahead to the next step below. Otherwise, the Migrator Pro for Exchange installer will prompt you to authorize the installation of the ones you need.  In that case, click the Install button to accept. If you have to install Microsoft .NET 4.5.2 Framework, you may also be prompted to accept Microsoft’s license agreement.  If so, mark the checkbox for I have read and accept…, and click Install.

    The installation of accessory applications may take several minutes.  Some of the newly installed components may then require a system reboot, in which case the wizard will also prompt you to authorize the reboot.  Click Yes to authorize the reboot.  If you do have to reboot, the wizard will automatically resume at the next screen in this process (next step below).


  1. On the installation wizard Welcome screen, click Next.


  2. On the Destination Location screen, select the destination folder for the installation and then click Next.

 


  1. On the Database Server Login screen, select or browse to the Migrator Pro for Exchange database server you are installing to, select the connection authentication method, and enter the Name of database (or Browse to it and select it). Then click Next.


  2. The Database Server Login screen appears again, this time for the Migrator Pro for Exchange Logging Database. Select or browse to the logging database server you are installing to, select the connection authentication method, and enter the Name of database (or Browse to it and select it). Then click Next.

  3. On the Login screen, enter the User Name and Password to use for the Binary Tree Migrator Pro for Exchange MCP Service and Migrator Pro for Exchange AppPool and then click Next.



  1. On the Migrator Pro for Exchange Administrative Group screen, enter an Active Directory Security Group to limit access to the Migrator Pro for Exchange Admin Portal, and then click Next. Note that E2E_Admins is the default group but a different group name can be entered.


  1. On the Ready to Install the Program screen, click Install.

    The installation process may take a few minutes, and the window shows a progress meter while you wait.

    Click Cancel if you want to cancel. The installer will first check to determine if the server has adequate disk space, and will alert you if there is not enough space available for installation.


  2. When installation is complete, the wizard Complete screen appears. Click Finish to close the installer program and return to the Migrator Pro for Exchange Installer.

 

  1. And click Finish again to close the Installer.


When the installation completes, the wizard creates a shortcut icon on the Desktop to launch Migrator Pro for Exchange. This entry is also added to the Windows Start menu along with entries for the Migrator Pro for Exchange Worker.

Now that the physical installation is complete, see section 3 below to configure Migrator Pro for Exchange for your environment and purposes. The first time you run the Migrator Pro for Exchange Admin Portal after this installation, Migrator Pro for Exchange will prompt you to define your target forest.

To uninstall Migrator Pro for Exchange, go to Programs and Features from the Windows Control Panel:

  1. Click Start, and then click Control Panel.

  2. Click Programs and Features, and then select Migrator Pro for Exchange from the list.

  3. Click Uninstall. Uninstalling Migrator Pro for Exchange also uninstalls Migrator Pro for Exchange Worker that is installed on the Migrator Pro for Exchange console.

 

 

If other Migrator Pro for Exchange Workers have been setup on other machines, they may need to also be uninstalled.

 

  1. Click Yes.

  2. Click Finish.

3. Configuring Migrator Pro for Exchange

The first time you run the Migrator Pro for Exchange Admin Portal after installing the software (in section 2 above), Migrator Pro for Exchange will prompt you to define your target forest.  Your target forest can reside in a local Exchange environment, or may be a tenant forest in Office 365.

Use the New Forest wizard to define your target forest.


Double-click the Migrator Pro for Exchange shortcut on the Desktop, or Migrator Pro for Exchange in the Windows Start menu.

The Admin Portal opens, and Migrator Pro for Exchange starts its New Forest wizard with the Migrator Pro for Exchange License screen:

Click Browse to locate your license file (*.lic) or copy and paste the license key and click Add License. Then click Next. Migrator Pro for Exchange then validates the license file and displays the license details. Click Next.

Migrator Pro for Exchange then begins a series of screens for you to define your target forest.

 

 


This screen asks whether your target forest is a local Exchange forest, or a tenant forest in Office 365.

If you are migrating to an Office 365 target forest: Click the Yes option, then click Next, and continue this procedure in section 3.1.1 below.

If you are migrating to an on-premises Exchange forest: Click the No option, then click Next, and continue this procedure in section 3.1.2 below.


If you are migrating to Office 365 but you don’t configure the O365 forest now, you can configure an on-premises Exchange forest first, and then the O365 forest later, and Migrator Pro for Exchange will automatically switch the two. That is, Migrator Pro for Exchange will correctly configure the on-premises forest as the source and the O365 forest as the target.

 

3.1 Defining an Office 365 (Tenant) Target Forest

If your target forest is in a local Exchange environment (not in Office 365), skip ahead to section 3.1.2 below.

Continuing this procedure from the Office 365 Migration screen, where you clicked Yes to begin defining an Office 365 Tenant forest:

Enter the name of the tenant target forest, and click Next.

 

These Exchange Online settings are required for Migrator Pro for Exchange program access to Office 365.

Enter the User Name and Password for the account Migrator Pro for Exchange should use to access Office 365.

Specify a Public Folders Migration Mode from the drop-down list. PowerShell and MAPI are the two available methods. If the Migration Mode is not specified here, Migrator Pro for Exchange will use the MAPI migration method by default.

For Msol Host Name, enter the Office 365 endpoint URL. The default Msol Host Name value is ps.outlook.com.

When you have entered the requested information, click Next.

 

 

 

 

 


These Exchange (MAPI) settings are required only when migrating public folders in cross-forest migrations where no trusts exist.

Enter the User Name, Password and Email Address for the account Migrator Pro for Exchange should use for program calls to Exchange (MAPI), and specify the Outlook Profile the program should use.

When you have entered the requested information, click Next.


If Migrator Pro for Exchange is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You must use an Outlook Profile to connect to a secondary forest.

If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be reached without an Outlook Profile.

 

The Summary screen shows the settings and choices you have entered to configure your tenant target forest.  Review the settings to make sure they are correct for the designated tenant forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

 

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

3.2 Defining a Local Exchange Target Forest

This section 3.2 applies only if your target forest is in a local Exchange environment (not in Office 365). A local Exchange target forest is defined when migrating Intra-org (no other forests would be needed), or when migrating Inter-org (a source forest would be defined).

Continuing this procedure from the Office 365 Migration screen, where you clicked No (as shown here) to begin defining a target forest in your local Exchange environment.

 

 

 

The first screen in this sequence to define a local target forest is this Target Forest screen. Enter the name of the Target Forest (top-level domain).

If the target forest you specify is configured as an Exchange Resource Forest environment, select the Resource Forest check box to create a “Linked User” relationship between the source and target account. This option applies only for an inter-org migration where the target Exchange environment is located in a resource forest. For more information about resource forests, see Microsoft's article http://technet.microsoft.com/en-us/library/aa998031.aspx and other Microsoft resources.

Click Next.

 

In this Active Directory screen: Enter the User Name (in Domain\Username format) and Password of the account to use for Active Directory calls.

You can either automatically select a global catalog by selecting the Auto-Detect a Global Catalog for this Forest checkbox, or manually specify one in the Global Catalog field.

Click Next.

 

 

In this PowerShell screen: Enter the User Name and Password of the account to use for PowerShell calls. By default, the program sets these values to the User Name and Password specified on the previous Active Directory screen, but you can change them here.

You can either automatically select the PowerShell hosts by keeping the Auto-detect the PowerShell Hosts checkbox selected, or deselect it to manually specify the Exchange 2010 Host, Exchange 2013 Host, and Exchange 2016 Host. If specifying the hosts manually, click the Verify PowerShell Host(s) button to validate connectivity to the PowerShell host servers.

Click Next.


When specifying a PowerShell Host manually, you must use a Fully Qualified Domain Name (FQDN). If you use an IP address, it will generate an SSL certificate error.

 

In this Exchange (MAPI) screen: Enter the User Name, Password and Email Address, and specify the Outlook Profile of the account to use for Exchange (MAPI) calls.

Click Next.


If Outlook is installed on the Migrator Pro for Exchange Server, an Outlook Profile should be used.

 

 

In this SMTP screen: Enter the User Principal Name, Password, Reply Email Address (e.g., user@domain.com), SMTP Server, and SMTP Port of the account to use for SMTP calls.

Click Next.

 


Specifying SMTP information is not required at the time of configuration.

You must specify the User Principal Name (user@domain.com) and Password for the account that will be used to send email communications to end users.

By default, the Exchange 2010/2013 Simple Mail Transfer Protocol (SMTP) receives connector rejects mail from any “well known accounts” such as Administrator. We recommend you designate a different account for this purpose.

Make sure the service account being used has access to the Exchange 2003/2007 and 2010/2013/2016 servers.

 

On this Staged Migrations screen: Specify the Exchange 2010 or Exchange 2013 staging server/database that Migrator Pro for Exchange should use when migrating from Exchange 2003 to Exchange 2013, or from Exchange 2007 to Exchange 2016.

Click Next.

 

 

On this Mailboxes screen: Select the sites, servers, and databases to search for mailboxes. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

 

In this Public Folders screen: Select the sites, servers, and databases to search for Public Folders. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

The Summary screen shows the settings and choices you have entered to configure your local target forest.  Review the settings to make sure they are correct for the designated forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

In a non-English locale, the date-time format of the operating system must be set to mmddyyyy (rather than ddmmyyyy)  for Migrator Pro for Exchange to rationalize Office 365 mailboxes.

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

3.1 Defining an Office 365 (Tenant) Target Forest

The first time you run the Migrator Pro for Exchange Admin Portal after installing the software (in section 2 above), Migrator Pro for Exchange will prompt you to define your target forest.  Your target forest can reside in a local Exchange environment, or may be a tenant forest in Office 365.

Use the New Forest wizard to define your target forest.


Double-click the Migrator Pro for Exchange shortcut on the Desktop, or Migrator Pro for Exchange in the Windows Start menu.

The Admin Portal opens, and Migrator Pro for Exchange starts its New Forest wizard with the Migrator Pro for Exchange License screen:

Click Browse to locate your license file (*.lic) or copy and paste the license key and click Add License. Then click Next. Migrator Pro for Exchange then validates the license file and displays the license details. Click Next.

Migrator Pro for Exchange then begins a series of screens for you to define your target forest.

 

 


This screen asks whether your target forest is a local Exchange forest, or a tenant forest in Office 365.

If you are migrating to an Office 365 target forest: Click the Yes option, then click Next, and continue this procedure in section 3.1.1 below.

If you are migrating to an on-premises Exchange forest: Click the No option, then click Next, and continue this procedure in section 3.1.2 below.


If you are migrating to Office 365 but you don’t configure the O365 forest now, you can configure an on-premises Exchange forest first, and then the O365 forest later, and Migrator Pro for Exchange will automatically switch the two. That is, Migrator Pro for Exchange will correctly configure the on-premises forest as the source and the O365 forest as the target.

 

If your target forest is in a local Exchange environment (not in Office 365), skip ahead to section 3.1.2 below.

Continuing this procedure from the Office 365 Migration screen, where you clicked Yes to begin defining an Office 365 Tenant forest:

Enter the name of the tenant target forest, and click Next.

 

These Exchange Online settings are required for Migrator Pro for Exchange program access to Office 365.

Enter the User Name and Password for the account Migrator Pro for Exchange should use to access Office 365.

Specify a Public Folders Migration Mode from the drop-down list. PowerShell and MAPI are the two available methods. If the Migration Mode is not specified here, Migrator Pro for Exchange will use the MAPI migration method by default.

For Msol Host Name, enter the Office 365 endpoint URL. The default Msol Host Name value is ps.outlook.com.

When you have entered the requested information, click Next.

 

 

 

 

 


These Exchange (MAPI) settings are required only when migrating public folders in cross-forest migrations where no trusts exist.

Enter the User Name, Password and Email Address for the account Migrator Pro for Exchange should use for program calls to Exchange (MAPI), and specify the Outlook Profile the program should use.

When you have entered the requested information, click Next.


If Migrator Pro for Exchange is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You must use an Outlook Profile to connect to a secondary forest.

If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be reached without an Outlook Profile.

 

The Summary screen shows the settings and choices you have entered to configure your tenant target forest.  Review the settings to make sure they are correct for the designated tenant forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

 

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

3.2 Defining a Local Exchange Target Forest

This section 3.2 applies only if your target forest is in a local Exchange environment (not in Office 365). A local Exchange target forest is defined when migrating Intra-org (no other forests would be needed), or when migrating Inter-org (a source forest would be defined).

Continuing this procedure from the Office 365 Migration screen, where you clicked No (as shown here) to begin defining a target forest in your local Exchange environment.

 

 

 

The first screen in this sequence to define a local target forest is this Target Forest screen. Enter the name of the Target Forest (top-level domain).

If the target forest you specify is configured as an Exchange Resource Forest environment, select the Resource Forest check box to create a “Linked User” relationship between the source and target account. This option applies only for an inter-org migration where the target Exchange environment is located in a resource forest. For more information about resource forests, see Microsoft's article http://technet.microsoft.com/en-us/library/aa998031.aspx and other Microsoft resources.

Click Next.

 

In this Active Directory screen: Enter the User Name (in Domain\Username format) and Password of the account to use for Active Directory calls.

You can either automatically select a global catalog by selecting the Auto-Detect a Global Catalog for this Forest checkbox, or manually specify one in the Global Catalog field.

Click Next.

 

 

In this PowerShell screen: Enter the User Name and Password of the account to use for PowerShell calls. By default, the program sets these values to the User Name and Password specified on the previous Active Directory screen, but you can change them here.

You can either automatically select the PowerShell hosts by keeping the Auto-detect the PowerShell Hosts checkbox selected, or deselect it to manually specify the Exchange 2010 Host, Exchange 2013 Host, and Exchange 2016 Host. If specifying the hosts manually, click the Verify PowerShell Host(s) button to validate connectivity to the PowerShell host servers.

Click Next.


When specifying a PowerShell Host manually, you must use a Fully Qualified Domain Name (FQDN). If you use an IP address, it will generate an SSL certificate error.

 

In this Exchange (MAPI) screen: Enter the User Name, Password and Email Address, and specify the Outlook Profile of the account to use for Exchange (MAPI) calls.

Click Next.


If Outlook is installed on the Migrator Pro for Exchange Server, an Outlook Profile should be used.

 

 

In this SMTP screen: Enter the User Principal Name, Password, Reply Email Address (e.g., user@domain.com), SMTP Server, and SMTP Port of the account to use for SMTP calls.

Click Next.

 


Specifying SMTP information is not required at the time of configuration.

You must specify the User Principal Name (user@domain.com) and Password for the account that will be used to send email communications to end users.

By default, the Exchange 2010/2013 Simple Mail Transfer Protocol (SMTP) receives connector rejects mail from any “well known accounts” such as Administrator. We recommend you designate a different account for this purpose.

Make sure the service account being used has access to the Exchange 2003/2007 and 2010/2013/2016 servers.

 

On this Staged Migrations screen: Specify the Exchange 2010 or Exchange 2013 staging server/database that Migrator Pro for Exchange should use when migrating from Exchange 2003 to Exchange 2013, or from Exchange 2007 to Exchange 2016.

Click Next.

 

 

On this Mailboxes screen: Select the sites, servers, and databases to search for mailboxes. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

 

In this Public Folders screen: Select the sites, servers, and databases to search for Public Folders. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

The Summary screen shows the settings and choices you have entered to configure your local target forest.  Review the settings to make sure they are correct for the designated forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

In a non-English locale, the date-time format of the operating system must be set to mmddyyyy (rather than ddmmyyyy)  for Migrator Pro for Exchange to rationalize Office 365 mailboxes.

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

3.2 Defining a Local Exchange Target Forest

The first time you run the Migrator Pro for Exchange Admin Portal after installing the software (in section 2 above), Migrator Pro for Exchange will prompt you to define your target forest.  Your target forest can reside in a local Exchange environment, or may be a tenant forest in Office 365.

Use the New Forest wizard to define your target forest.


Double-click the Migrator Pro for Exchange shortcut on the Desktop, or Migrator Pro for Exchange in the Windows Start menu.

The Admin Portal opens, and Migrator Pro for Exchange starts its New Forest wizard with the Migrator Pro for Exchange License screen:

Click Browse to locate your license file (*.lic) or copy and paste the license key and click Add License. Then click Next. Migrator Pro for Exchange then validates the license file and displays the license details. Click Next.

Migrator Pro for Exchange then begins a series of screens for you to define your target forest.

 

 


This screen asks whether your target forest is a local Exchange forest, or a tenant forest in Office 365.

If you are migrating to an Office 365 target forest: Click the Yes option, then click Next, and continue this procedure in section 3.1.1 below.

If you are migrating to an on-premises Exchange forest: Click the No option, then click Next, and continue this procedure in section 3.1.2 below.


If you are migrating to Office 365 but you don’t configure the O365 forest now, you can configure an on-premises Exchange forest first, and then the O365 forest later, and Migrator Pro for Exchange will automatically switch the two. That is, Migrator Pro for Exchange will correctly configure the on-premises forest as the source and the O365 forest as the target.

 

3.1 Defining an Office 365 (Tenant) Target Forest

If your target forest is in a local Exchange environment (not in Office 365), skip ahead to section 3.1.2 below.

Continuing this procedure from the Office 365 Migration screen, where you clicked Yes to begin defining an Office 365 Tenant forest:

Enter the name of the tenant target forest, and click Next.

 

These Exchange Online settings are required for Migrator Pro for Exchange program access to Office 365.

Enter the User Name and Password for the account Migrator Pro for Exchange should use to access Office 365.

Specify a Public Folders Migration Mode from the drop-down list. PowerShell and MAPI are the two available methods. If the Migration Mode is not specified here, Migrator Pro for Exchange will use the MAPI migration method by default.

For Msol Host Name, enter the Office 365 endpoint URL. The default Msol Host Name value is ps.outlook.com.

When you have entered the requested information, click Next.

 

 

 

 

 


These Exchange (MAPI) settings are required only when migrating public folders in cross-forest migrations where no trusts exist.

Enter the User Name, Password and Email Address for the account Migrator Pro for Exchange should use for program calls to Exchange (MAPI), and specify the Outlook Profile the program should use.

When you have entered the requested information, click Next.


If Migrator Pro for Exchange is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You must use an Outlook Profile to connect to a secondary forest.

If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be reached without an Outlook Profile.

 

The Summary screen shows the settings and choices you have entered to configure your tenant target forest.  Review the settings to make sure they are correct for the designated tenant forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

 

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

This section 3.2 applies only if your target forest is in a local Exchange environment (not in Office 365). A local Exchange target forest is defined when migrating Intra-org (no other forests would be needed), or when migrating Inter-org (a source forest would be defined).

Continuing this procedure from the Office 365 Migration screen, where you clicked No (as shown here) to begin defining a target forest in your local Exchange environment.

 

 

 

The first screen in this sequence to define a local target forest is this Target Forest screen. Enter the name of the Target Forest (top-level domain).

If the target forest you specify is configured as an Exchange Resource Forest environment, select the Resource Forest check box to create a “Linked User” relationship between the source and target account. This option applies only for an inter-org migration where the target Exchange environment is located in a resource forest. For more information about resource forests, see Microsoft's article http://technet.microsoft.com/en-us/library/aa998031.aspx and other Microsoft resources.

Click Next.

 

In this Active Directory screen: Enter the User Name (in Domain\Username format) and Password of the account to use for Active Directory calls.

You can either automatically select a global catalog by selecting the Auto-Detect a Global Catalog for this Forest checkbox, or manually specify one in the Global Catalog field.

Click Next.

 

 

In this PowerShell screen: Enter the User Name and Password of the account to use for PowerShell calls. By default, the program sets these values to the User Name and Password specified on the previous Active Directory screen, but you can change them here.

You can either automatically select the PowerShell hosts by keeping the Auto-detect the PowerShell Hosts checkbox selected, or deselect it to manually specify the Exchange 2010 Host, Exchange 2013 Host, and Exchange 2016 Host. If specifying the hosts manually, click the Verify PowerShell Host(s) button to validate connectivity to the PowerShell host servers.

Click Next.


When specifying a PowerShell Host manually, you must use a Fully Qualified Domain Name (FQDN). If you use an IP address, it will generate an SSL certificate error.

 

In this Exchange (MAPI) screen: Enter the User Name, Password and Email Address, and specify the Outlook Profile of the account to use for Exchange (MAPI) calls.

Click Next.


If Outlook is installed on the Migrator Pro for Exchange Server, an Outlook Profile should be used.

 

 

In this SMTP screen: Enter the User Principal Name, Password, Reply Email Address (e.g., user@domain.com), SMTP Server, and SMTP Port of the account to use for SMTP calls.

Click Next.

 


Specifying SMTP information is not required at the time of configuration.

You must specify the User Principal Name (user@domain.com) and Password for the account that will be used to send email communications to end users.

By default, the Exchange 2010/2013 Simple Mail Transfer Protocol (SMTP) receives connector rejects mail from any “well known accounts” such as Administrator. We recommend you designate a different account for this purpose.

Make sure the service account being used has access to the Exchange 2003/2007 and 2010/2013/2016 servers.

 

On this Staged Migrations screen: Specify the Exchange 2010 or Exchange 2013 staging server/database that Migrator Pro for Exchange should use when migrating from Exchange 2003 to Exchange 2013, or from Exchange 2007 to Exchange 2016.

Click Next.

 

 

On this Mailboxes screen: Select the sites, servers, and databases to search for mailboxes. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

 

In this Public Folders screen: Select the sites, servers, and databases to search for Public Folders. All content is selected by default. Right-click in the list area to select options to expand/collapse the list or select/deselect all items.

Click Next.

 

The Summary screen shows the settings and choices you have entered to configure your local target forest.  Review the settings to make sure they are correct for the designated forest.  (If you want to change anything you can click Previous to return to an earlier screen.)

When these Summary screen values appear as they should, click Finish to save the forest configuration information.

In a non-English locale, the date-time format of the operating system must be set to mmddyyyy (rather than ddmmyyyy)  for Migrator Pro for Exchange to rationalize Office 365 mailboxes.

When the forest configuration is saved, it appears on the Configuration Settings screen of the Migrator Pro for Exchange Admin Portal.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating