Converse agora com nosso suporte
Chat com o suporte

Preparing Migration 8.15 - Installation Guide

Opening the Required Ports on Servers, Routers, and Firewalls

Since the Migration Manager agents are installed and updated from the console over RPC and the agents transfer data directly between source and target servers over RPC as well, RPC traffic must be allowed over the routers separating the subnets.

Make sure that ports 135, 137, 138, and 139 are open on the following machines:

  • Source and target servers
  • Routers separating the subnets
  • Firewalls

Note: For the comprehensive list of port requirements for most of the Migration Manager components, refer to the Migration Manager–Required Ports document.

Configuring Windows Server 2008/2008 R2/2012 Firewall

Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012 have built-in firewall that is enabled by default. To migrate passwords and SIDHistory, you need to modify the firewall settings on a target domain controller and create a new inbound rule. This is also required for proper operation of the Undo Wizard.

  • To create a new rule on an x86 target domain controller, run the following command (Windows Server 2008 only):
netsh advfirewall firewall add rule name="Migration Manager Agent" dir=in action=allow program="%SystemRoot%\System32\AelAgentMS.exe"
  • To create a new rule on an x64 target domain controller, run the following command:
netsh advfirewall firewall add rule name="Migration Manager Agent" dir=in action=allow program="%SystemRoot%\System32\AelAgentMS64.exe"

Note: Alternatively, you can create a new rule using the New Inbound Rule Wizard. To run the wizard:

  1. Open the Server Manager console on a target domain controller.
  2. Navigate to Configuration | Windows Firewall with Advanced security | Inbound Rules in the console tree.
  3. Click New Rule.

Caution: In case of two-way directory synchronization, you should perform the same actions on the source domain controller.

Number of NSPI Connections to a Windows 2008-based Domain Controller

A Name Service Provider Interface (NSPI) connection from a MAPI client to a Windows Server 2008-based domain controller may fail with the following error code that is returned from the server: «MAPI_E_LOGON_FAILED».

This behavior occurs because Windows Server 2008 only allows for a default maximum of 50 concurrent NSPI connections per user to any domain controller. Additional NSPI connections are rejected with a MAPI_E_LOGON_FAILED error code.

Note Windows Server 2003 and earlier versions of Microsoft Windows operating systems do not exhibit this behavior. The change of behavior in Windows Server 2008 is intended to protect domain controllers against clients that open too many NSPI connections without then closing the connections. Too many connections such as these can result in resource depletion.

For more information about how to modify registry settings to allow for additional NSPI connections, see the following Microsoft KB article:

Installing Migration Manager

To install Migration Manager, either click Migration Manager and its components on the CD menu or start the Suite\AeCDSuiteLauncher.exe setup program, and then follow the wizard’s instructions.

Note: For security reasons, all network protocols may be disabled by default in SQL Server 2005 and SQL Server Express 2005 or later, which causes trouble with connecting to a project. For details on enabling the network protocols, refer to SQL Server documentation.

To avoid connectivity problems, you should enable all network protocols in SQL Server if you plan to install MAgE agents on the agent hosts that are located separately from the SQL Server host.

To install Migration Manager:

  1. When prompted, specify your name and company. Click Licenses to verify your license information in the dialog displayed: browse for a valid license file, and then click Close.
  2. Next, on the Select Features step, select the components you want to install and specify the installation folder.
  3. On the next step, you are prompted to select the product installation scenario. Possible options are Express or Advanced.

Express means that setup will do the following:

  • Install all the components that are permitted by the license file.
  • Install all other required components, such as the AD LDS or ADAM instance, SQL Server or SQL Server Express instance (for Exchange migrations only), and the Directory Synchronization Agent.
  • Configure the project.
  • If IIS is installed on the computer, Statistics Portal will be automatically installed and configured as well.

Advanced is recommended if you plan to manually install AD LDS or ADAM, SQL Server or SQL Server Express (for Exchange migrations only), and the Directory Synchronization Agent, as well as configure the project by running the Open Project Wizard (described in the Opening a Migration Project topic). Only the basic product components (selected in Select Features step) will be installed automatically.

Note: When selecting the setup scenario, consider the following:

By default, SQL Server Express is installed with only Windows (AD-integrated) authentication allowed; however, Statistics Portal required basic SQL authentication. To provide for SQL authentication method, you can do either of the following:

Use the Express setup scenario (proper configuration will be applied automatically).

After running the Advanced setup, install SQL Server Express using the special installation wizard from Migration Manager CD Autorun, and then use the Microsoft SQL Server Management tools (Enterprise Manager), or edit the registry as described in Microsoft Knowledge Base article 319930 at

If you select the Advanced setup scenario, you will be taken to step 7 of this procedure.

  1. On the Set Account for ADAM Access step, specify the auxiliary account that various Migration Manager components will use to access the AD LDS or ADAM database.
  2. This account does not require any particular rights in the domain; ordinary domain user rights are sufficient. However, this account must be a member of the computer local Administrators group on the computer running the Migration Manager console. Note that this account will be granted Full Admin rights in the project database.
  3. On the MSDE setup step, specify the password for the sa account that will be used to install and configure the local SQL Server database.
  4. Next, the setup checks for third-party software required for Migration Manager (for example, Microsoft Message Queuing). If some required components are missing, setup will notify you and attempt to install these components from the installation CD. To install these components automatically, click Next; alternatively, you can install them manually and after that restart the setup program.
  5. After all the required components are installed, the setup wizard is ready to install the features you have selected (and configure the product if the Express setup scenario is running). Click Next and wait for the installation to complete.

Downloading MAPI CDO (Specific Scenarios Only)

MAPI CDO now is only required for scenarios where MAPI is used: processing messages in Exchange 2010 or earlier by Exchange Processing wizard , migration scenarios where legacy Exchange agents are used, and migration by MAgE from Exchange 2007 or earlier. MAPI CDO is optional for Native Move migration by MAgE scenarios. Source mailbox statistics will be only available with MAPI CDO. For all other supported scenarios, MAPI CDO is no longer needed.

For the cases mentioned above the version 6.5.8353.0 or later of Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 should be installed on the following computers:

  • Where Migration Manager agents will run (that is, Exchange 2007 and 2010 Servers and agent hosts only).
  • Where the Migration Manager console is installed
  • Where the setup package for Exchange Processing wizard task is installed

Since the MAPI CDO setup package is not available for distribution, you should download it from the Microsoft Web site. At the moment of the last document update, the download link is

Caution: This package cannot be installed on a system on which any version of Microsoft Outlook or Microsoft Exchange Server 2003 or earlier is installed.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação