Chatee ahora con Soporte
Chat con el soporte

Migration Manager for Exchange 8.15 - Target Exchange 2019 Environment preparation

Target Exchange 2019 Environment Preparation
Preparation Overview Checking System Requirements Setting Up Accounts and Required Permissions Preparing the Target Exchange Environment for Exchange Migration Setting Up Connection with the Source Exchange Organization Using SMTP Connectors

Creating Custom Throttling Policies

To prevent possible issues in an Exchange 2019 organization, you should create custom throttling policies, apply them to the Exchange Accounts and then restart the Microsoft Exchange Throttling Service. To do this, run the following cmdlets in Exchange Management Shell for each Exchange Account:

New-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited –PowerShellMaxConcurrency Unlimited

Set-ThrottlingPolicyAssociation -Identity <QMM_Exchange_Account_Name> -ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

Restart-Service -Name MSExchangeThrottling

Configuring Transport Layer Security (TLS) Protocols

All servers involved into migration process must have at least one matching TLS protocol version enabled in order to communicate.

Microsoft Exchange 2019 by default uses TLS 1.2 only.

To ensure NativeMove requests can be handled successfully you should select one of the following options:

  • Configure your source Exchange Server to use TLS 1.2

-OR-

  • Configure your target Exchange Server to support TLS 1.0 or 1.1

Preparing Agent Host for Public Folder Synchronization Agents

To perform public folder synchronization you will need one (or more) standalone agent host server associated with each target Exchange 2019 server.

Such agent host must meet the following specific requirements:

  • Outlook 2013 32-bit or Outlook 2019 32-bit version must be installed on the agent host.
  • The agent host must be used only for PFSA and PFTA to work with target Exchange 2019. No other agents can be installed on it.

Note: For complete set of requirements, see Exchange Migration Agents Server in the System Requirements and Access Rights document.

Later when configuring migration in Migration Manager for Exchange console, after you register that agent host(s), open its Properties, go to the General | Connection node and select the Communicate with Exchange Server via Outlook MAPI option. Then select the agent host as Default Agent Host in the Properties of an Exchange 2019 server.

Creating Aelita EMW Recycle Bin Public Folder (Optional)

 

NOTE: If you skip this step, the Aelita EMW Recycle Bin folder will be created automatically by PFTA during public folder synchronization.

If you plan to perform public folder synchronization using Migration Manager Public Folder agents, you should create a special public folder called Aelita EMW Recycle Bin.

This folder will help prevent data loss in case of accidental public folder deletion. When a public folder is deleted in one of the environments, the public folder synchronization agents move the corresponding folder in the other environment to the Aelita EMW Recycle Bin folder, if it exists, instead of permanently deleting the folder. You can use this folder to check whether important information has been deleted, and restore any data deleted by mistake.

Caution: Only deleted public folders will be put into the Aelita EMW Recycle Bin. If you delete a message from a public folder, it will be destroyed permanently in both the Source and Target Exchange organizations.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación