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
- Microsoft Cluster Server (MSCS)
- Microsoft Cluster Server node
- Exchange Virtual Server
- Exchange 2003/2007 SCC cluster
- Exchange 2007 CCR cluster
- Agent host can be:
- 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).
- Another Exchange server from the same Exchange organization.
- 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
Exchange server as an agent host
Requirements from the following table apply to Exchange servers acting as agent hosts.
Requirement | Details |
---|---|
Platform |
One of the following:
|
Operating System |
One of the following:
|
Additional Software |
All of the following:
|
|
IMPORTANT: For Exchange versions prior to 2010: the private information store with the System Attendant should be mounted for each Exchange server where the mail, calendar, or free/busy synchronization agents are running. |
Standalone server as an agent host
Requirements from the following tables apply to standalone servers acting as agent hosts.
For agent hosts associated with Exchange Server 2003, or 2007
Requirement | Details |
---|---|
Platform |
One of the following:
|
Operating System |
One of the following:
|
Additional Software |
All of the following:
|
|
Note: Exchange 2010 Management Tools are required only for agent hosts where Calendar Synchronization Agent, Mail Source Agent (Remote User Collections only), or Mail Target Agent instances processing Exchange 2010 servers are installed. Note that installation of Exchange 2010 Management Tools requires Active Directory schema extension. If that is not appropriate, install those agents on the agent host associated with the target Exchange Server 2010. |
For agent hosts associated with Exchange Server 2010
Requirement | Details |
---|---|
Platform |
One of the following:
|
Operating System |
One of the following:
|
Additional Software |
All of the following:
|
For agent hosts associated with Exchange Server 2013
Requirement | Details |
---|---|
Platform |
One of the following:
|
Operating System |
One of the following:
|
Additional Software |
All of the following:
|
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:
|
Operating System |
One of the following:
|
Additional Software |
All of the following:
NOTE: Restart the computer after applying Microsoft Easy Fix.
|
|
|
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:
|
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:
|
Software Requirements
Requirement | Details |
---|---|
Operating System |
One of the following:
|
Additional Software |
All of the following:
For specific cases only:
NOTE: Restart the computer after applying Microsoft Easy Fix. 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:
Additional software in case of migration to Microsoft Office 365:
|
* 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. |