Migration Manager for Exchange 8.15 - Source Exchange 2016 Environment Preparation

Source Exchange 2016 Environment Preparation

Preparation Overview Checking System Requirements Setting Up Accounts and Required Permissions

Setting Up the Source Active Directory Synchronization Account Setting Up the Source Exchange Account

Changing the Default Exchange Account Granting Read Access to Active Directory Domain Granting Read Permission for Microsoft Exchange Container Granting ApplicationImpersonation Management Role Granting Move Mailboxes Management Role Granting Mail Recipients Management Role Granting Membership in Local Administrators Group Granting Mail Enabled Public Folders Management Role Granting Full Control on Mailbox Database Granting Full Control on Public Folder Administrator Mailbox

Setting Up the Source Active Directory Account

Changing the Default Source Active Directory Account Granting Read Access to Active Directory Domain Granting Read Permission for the Microsoft Exchange Container Granting Write proxyAddresses Permission on Descendant PublicFolder Objects

Setting Up the Agent Host Account

Changing the Default Source Agent Host Account Granting SCP Create, Read and Write Permissions Granting db_owner Role on SQL Server

Preparing the Source Exchange Environment for Exchange Migration

Backing Up Exchange Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 Creating Custom Throttling Policies Preparing Agent Host for Public Folder Synchronization Agents Creating Aelita EMW Recycle Bin Public Folder (Optional) Configuring Administrator Mailboxes for Public Folder Synchronization Preparing Public Folder Mailboxes for Public Folder Synchronization Creating Outlook Profiles for Public Folder Synchronization Fine-Tuning Public Folder Synchronization Agents to Use Kerberos Authentication (Optional) Setting Exchange Autodiscover URL (Optional)

Setting Up Connection with the Target Exchange Organization Using SMTP Connectors

Setting up Source Exchange Organization for Internet Mail Flow between Source and Target Exchange Organizations

Creating Send Connector Modifying Default Receive Connector Adding E-mail Domain Used for Redirection to the List of Accepted Domains

Configuring Source DNS Server for Mail Forwarding Testing the SMTP Connectors (Optional)

Preparing Public Folder Mailboxes for Public Folder Synchronization

Ensure that the size of public folder data to be migrated does not exceed the size limit for the primary hierarchy mailbox. If public folder content in the source organization is larger than the limit in the target organization, to migrate it you will need to perform specific steps including creation of additional secondary hierarchy mailboxes in your target Exchange 2016 organization. For detailed instructions, see Appendix B. Migrating Large Public Folders to Exchange 2013 or Higher of Migration Manager for Exchange User Guide.
TIP: For general information on public folders in Exchange 2016, see https://technet.microsoft.com/en-en/library/mt577271(v=exchg.160).aspx.
For each public folder mailbox consider adjusting the Recoverable Items quota according to the needs of your Exchange 2016 organization (by default, the limit is 30 GB per mailbox). If the quota limit is exceeded for a public folder mailbox, deletions of content in the source public folders will not be synced to that target public folder mailbox anymore.
To change the quota value for a public folder mailbox, invoke the following cmdlet:

Set-Mailbox -Identity PFMailbox –PublicFolder -RecoverableItemsQuota 50GB

Creating Outlook Profiles for Public Folder Synchronization

To synchronize public folders with Exchange2016 organization, you need to create special Outlook profiles on the agent host associated with Exchange 2016 where you plan to install PFSA and PFTA.

For that, log on to agent host under the Agent Host Account, open Start | Control Panel | Mail (32-bit) and click Show Profiles. You must create two profiles: one named MMEX_PFSA and the other — MMEX_PFTA. To create each profile, take the following steps:

Click Add and then specify the profile name (either MMEX_PFSA or MMEX_PFTA, respectively). Click OK.
Specify the administrator mailbox you plan to use for public folder synchronization.
Click Next and wait until wizard connects to the mailbox. If prompted for credentials, specify Source Exchange Account credentials and select the Remember my credentials option.
Select the Change account settings option and click Next.
Clear the Use Cached Exchange Mode option.
Click Finish to complete the wizard.

To ensure that logon to created profiles through Outlook can be performed correctly, run Outlook 2013 and select the MMEX_PFSA (MMEX_PFTA) profile. If no error messages, credential prompts or any other message boxes that require user response appear, then profile is created properly and therefore can be used by PFSA and PFTA to perform public folder synchronization.

Note: Make sure that no issues related to certificate validation occur when you run Outlook. For instance, if you use self-signed certificates for Exchange 2016 Servers, you need to log on to each agent host under the Agent Host Account and add certificate from to the Trusted Root Certification Authorities and Trusted Publisher lists.

Fine-Tuning Public Folder Synchronization Agents to Use Kerberos Authentication (Optional)

During public folder synchronization, agents establish PowerShell session with source or target Exchange Server to process mail-enabled public folders. If only Kerberos authentication is available in the environment, then force each deployed PFSA or PFTA to use Kerberos authentication as follows:

Locate CONFIG.INI file of an agent.
Add the following line to the INI file and save the file:
PSForceUseKerberos=1
Restart the agent.

Setting Exchange Autodiscover URL (Optional)

Migration Agent for Exchange uses the Exchange Autodiscover service to query certain properties of mailboxes being migrated. In order to submit queries to the Autodiscover service, MAgE needs to know its URL. In most cases, the agent automatically gets the Autodiscover URLs for both the source and target organizations. However, you may experience situations when automatically discovering the URL fails or returns the incorrect URL.

When the correct URL cannot be obtained, an error will be generated causing the synchronization job to fail. Errors in the log file with the following exceptions indicate problems with obtaining the proper Autodiscover URL:

AutodiscoverLocalException: The Autodiscover service couldn't be located.
ServiceRequestException: The request failed. The remote server returned an error: (401) Unauthorized.
ServiceRemoteException: Invalid user: 'Joe.User@contoso.com'.
AutodiscoverDeploymentIdMismatchException: The User Deployment ID returned from Autodiscover does not match the expected value.

If you encounter any of the above exceptions, you need to manually configure the Autodiscover URL for the source or target organizations (or both) . The Autodiscover URL can be configured using the Set-MMExOrganizationProperties cmdlet from the MMExPowerShell module. Below is an example how to use the cmdlet:

Set-MMExOrganizationProperties -FQDN source.contoso.com -AutodiscoverUrl https://autodiscover.source.contoso.com/autodiscover/autodiscover.svc

TIP: For information how to use the MMExPowerShell.psm1 module, see Configuring Migration Project Settings Using PowerShell.

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Migration Manager for Exchange 8.15 - Source Exchange 2016 Environment Preparation

Preparing Public Folder Mailboxes for Public Folder Synchronization

Creating Outlook Profiles for Public Folder Synchronization

Fine-Tuning Public Folder Synchronization Agents to Use Kerberos Authentication (Optional)

Fine-Tuning Public Folder Synchronization Agents to Use Kerberos Authentication (Optional)

Setting Exchange Autodiscover URL (Optional)