The Add-MMExExchangeRemoteHost has the following syntax:
Add-MMExExchangeRemoteHost -OrganizationName <Exchange organization name> -FQDN <FQDN name> -Version <Exchange server version> [-ADSite <Active Directory site name>]
ADSite - is a name of Active Directory site where Client Access Server or Load Balancer is located. This parameter is optional.
The following cmdlet adds the FQDN of Client Access Server or Load Balancer that reside in the source or target organization to the project database:
Add-MMExExchangeRemoteHost -OrganizationName ExchangeOrg1 -FQDN ExchCAS.source.com -Version Ex2010sp3
IMPORTANT: This section is applicable for migration scenarios supported by legacy Exchange Agents only. For migration scenarios supported by MAgE refer to the Public Folder Synchronization (MAgE) document.
This section contains performance test results of a single Migration Agent for Exchange instance that performs mail data migration from Exchange Server 2010 to Exchange Server 2013.
Performance test results:
Configuration of the Test Environment:
|Server Role||Server Operating System||CPU||RAM, GB|
|Exchange Server 2010, source||Windows Server 2008 R2 Enterprise SP1||4 vCPUs (Intel Xeon E5-2665)||34|
|Exchange Server 2013, target||Windows Server 2012||8 vCPUs (Intel Xeon E5-2670 v2)||30|
|Agent host||Windows Server 2012 R2||8 vCPUs (Intel Xeon E5-2670)||15|
|SQL server 2008 R2, Migration Manager console||Windows Server 2008 R2 Enterprise SP1||2 vCPUs (Intel Xeon E5-2665)||17|
Network speed: 1 Gbit/s.
Unlike Exchange versions 2010 and earlier, in Exchange 2013 or higher
Important: Currently, Migration Manager for Exchange processes public folders of source Exchange 2013 or higher organizations as a single list of public folders ignoring their actual division by public folder mailboxes. Therefore, you need to plan public folder migration from an Exchange 2013 or higher organization according to information in this section in the same way as for Exchange 2010 and earlier organization.
As a first step, you need to analyze the overall size of public folders that are planned to be migrated to Exchange organization. This can be done by reviewing information in Exchange System Manager (applicable to Exchange 2003) or by invoking theGet-PublicFolderStatistics cmdlet (applicable for Exchange 2007 or 2010).