Chat now with support
Chat with Support

Preparing Migration 8.15 - System Requirements and Access Rights

Migration Manager Console Migration to Microsoft Office 365 License Server Migration Manager Database Servers Migration Manager Agent Servers Statistics Portal Server Resource Updating Manager Resource Updating Wizards Processed Platforms Additional Environment Security Configuration Ports Used by General Migration Manager Components Ports Used by Migration Manager for Exchange Components Ports Used by Migration Manager for Active Directory Components Ports Used by Resource Updating Manager Accounts Required for Migration Manager Operation Accounts Used by the Directory Synchronization Agent Source Accounts Used by Migration Manager for Exchange Agents Target Accounts Used by Migration Manager for Exchange Agents Agent Host Account Used by Legacy Migration Manager for Exchange Agents Agent Host Account Used by Migration Agent for Exchange (MAgE) Accounts Used for Migrating to Microsoft Office 365 Accounts Used by RUM Agent Service Accounts Used by RUM Controller Service Account Used by Statistics Collection Agent Service Accounts Used by Statistics Portal Accounts Accounts and Rights Required for Active Directory Migration Tasks Accounts and Rights Required for Exchange Migration Tasks Using the Exchange Processing Wizard with Exchange 2010 or later Appendix. How to Set the Required Permissions for Active Directory Migration

Migration Manager Agent Servers

Directory Synchronization Agent Server

Requirement Details
Platform

One of the following:

  • Intel x86
  • AMD 64
  • Intel EM64T
Operating System

One of the following:

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016

Directory Synchronization Agent depends on the Remote Registry service. Please make sure that the Remote Registry service startup type is set to Automatic on the Directory Synchronization Agent server.

Directory Migration Agent Server

Requirement Details
Platform

One of the following:

  • Intel x86
  • AMD 64
  • Intel EM64T
Operating System

One of the following:

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
Additional Software

All of the following:

  • Microsoft .NET Framework 4.5 or later
  • Microsoft PowerShell 3.0

Exchange Migration Agents Server

Migration Manager uses the following Exchange-specific agents:

  • Public Folder Source Agent
  • Public Folder Target Agent
  • Mail Source Agent
  • Mail Target Agent
  • Calendar Synchronization Agent
  • Free/Busy Synchronization Agent
  • Transmission Agent
  • Migration Agent for Exchange

Agents work on agent host servers.

Requirements and limitations for agent host servers:

  • Multiple Exchange servers can be associated with a single agent host server.
  • Agent host cannot be
    1. Microsoft Cluster Server (MSCS)
    2. Microsoft Cluster Server node
    3. Exchange Virtual Server
    4. Exchange 2003/2007 SCC cluster
    5. Exchange 2007 CCR cluster
  • Agent host can be:
    1. An Exchange server itself, which is the default configuration. After you enumerate an Exchange organization all Exchange servers are registered as agent hosts for themselves (excluding Migration Agent for Exchange installations).
    2. Another Exchange server from the same Exchange organization.
    3. A stand-alone server. Agents hosts associated with Exchange Server version 2003, 2007, 2013, 2016 or 2019 can be located in another forest or workgroup. Agents hosts associated with Exchange Server 2010 must be located in the forest where the Exchange Server 2010 resides.

Legacy Migration Agents

For agent hosts associated with Exchange Server 2016, 2019, or Office 365 (public folder synchronization only)

The following requirements apply to agent hosts associated with Exchange Server 2016 or Office 365 which you plan to use for public folder synchronization. Requirements for agent host used for other types of synchronization are described in Migration Agent for Exchange (MAgE).

Requirement Details
Platform

One of the following:

  • AMD 64
  • Intel EM64T
Operating System

One of the following:

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
Additional Software

All of the following:

  • Microsoft .NET Framework 3.5 Service Pack 1

  • Microsoft Exchange Collaboration Data Objects must not be installed on the agent host
  • Microsoft Outlook 2013 32-bit or Microsoft Outlook 2016 32-bit version must be installed on the agent host.
    NOTE: The MMEX_PFSA and MMEX_PFTA profiles must be created as described in the Creating Outlook Profiles for Public Folder Synchronization of the following documents:
    • Exchange 2016: Target Exchange 2016 Preparation document
    • Office 365: Migrating to Microsoft Office 365 document

Important: The Communicate with Exchange Server via Outlook MAPI option must be selected on the General | Connection node in the properties of each agent host associated with Exchange Server 2016, 2019, or Office 365 on which PFSA or PFTA will be installed.

Migration Agent for Exchange (MAgE)

Requirements from the following tables apply to standalone servers acting as agent hosts for Migration Agent for Exchange (MAgE). Note that Migration Agent for Exchange cannot be installed on Exchange servers.

Hardware Requirements

Requirement Details
Platform

One of the following:

  • AMD 64
  • Intel EM64T
Processor

2 GHz or higher (before Turbo Boost if applicable)

Minimum: 1 CPU core per 2 MAgE instances

Recommended: 1 CPU core per each MAgE instance

Memory (RAM)

Minimum: 0.8 GB per MAgE instances

Recommended: 1.6 GB per MAgE instance

LAN Bandwidth

Minimum: 100 Mbps

Recommended: 1 Gbps

TIP: Agent host server with maximum number of 20 MAgE instances running concurrently (10 for mailbox and 10 for calendar processing) must have:

  • 10 CPU cores and 16 GB of RAM (minimum)
  • 20 CPU cores and 32 GB of RAM (recommended)

Software Requirements

Requirement Details
Operating System

One of the following:

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
Additional Software

All of the following:

  • Microsoft .NET Framework 3.5 Service Pack 1
  • Microsoft .NET Framework 4.5.2 or later

For specific cases only:

  • Version 6.5.8353.0 or later of Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1. MAPI CDO now is only required for scenarios where MAPI is used: 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.

    Limitation: neither Microsoft Outlook nor Exchange Server 2003 Management Tools must be installed.

IMPORTANT: Migration Manager for Exchange supports work with SQL Servers where the version 1.2 is the only enabled version of TLS, but the following additional software is required for this case:

  • Microsoft ODBC Driver for SQL Server, version 17, on all computers running Migration Manager console and on Statistics Collection Agent host. Required version of ODBC Driver for SQL Server can be downloaded from Microsoft Download Center.

Additional software in case of migration to Microsoft Office 365:

  • Microsoft PowerShell 3.0
  • Microsoft Online Services Sign-In Assistant for IT Professionals RTW*

* To get Microsoft Online Services Sign-In Assistant, go to https://support.quest.com/migration-manager-for-ad/kb/332933/download-links-for-office-365-sign-in-assistant-for-migration-manager-for-ad-and-exchange-to-o365.

Important: Maximum number of MAgE instances per agent host is limited to 20: 10 for mailbox processing and 10 for calendar processing.

 

 

 

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating