Migration Manager for Exchange 8.14 - User Guide

Exchange 2010 Considerations

If an Exchange 2010 organization is involved in the mailbox migration process, consider that in Exchange 2010 all mailbox communications flow via Client Access Servers (CAS) instead of Mailbox Servers as in previous versions of Exchange. Therefore Migration Manager for Exchange agents use CAS for mailbox and calendar processing.

In addition, if an Exchange 2010 organization acts as a migration destination, consider the following:

• After a mailbox move operation is performed or a new Exchange 2010 mailbox is created during the migration process, the mailbox does not immediately become available for login. The Mail Target Agent will record login errors until the mailbox is ready (this can take up to 20 minutes). In these situations, login errors can be safely ignored.
• If a mailbox move request completes with an error, delete this request before the agent creates a new one.

Exchange 2013/2016/2019 Considerations

When migrating mailboxes to Exchange Server 2013/2016/2019, consider the following:

• Migration Agent for Exchange cannot process a message that is larger than 40MB. This limit is set in Migration Manager for Exchange configuration project to ensure migration stability. If you have strong reasons to change that value, see the SizeLimitInMbPerBatchUploadToO365 and SizeLimitInMbPerBatchUploadToExchange parameters in Configuring Migration Using PowerShell

• If you want to change an agent instance for a collection that is being processed, you should stop the agent, wait until the current session is finished and then specify the agent instance you need.
• If a mailbox is added to more than one collection via groups or organizational units, the Migration Agent for Exchange processes this mailbox only for the collection that is the first in the synchronization order.
• One instance of Migration Agent for Exchange cannot process collections from on-premise Exchange migration and Microsoft Office 365 migration projects at the same time.
• If a mailbox move request completes with an error, delete this request before the agent creates a new one.

Public Folder Synchronization

Public folder synchronization should be started before mailbox migration and before calendar and free/busy synchronization. This order of migration allows the users to keep using their public folders during the entire migration period, regardless of which mailbox (source or target) is currently used by the user.

Setting Up a New Public Folder Synchronization Job

To create a new public folder synchronization job, right-click the Public Folders Synchronization node of the console management tree and select the Add Public Folders Synchronization Job option from the shortcut menu.

This will start the Add Public Folders Synchronization Job Wizard that will help you to install the public folder synchronization agents and configure the job.

This section guides you through each step of the wizard and explains the available public folder synchronization options. For more details, see the related topics.

Step 1. Select Exchange Servers

The public folder synchronization job is set up between the source and target servers that you select in this step of the wizard. If you want to synchronize public folders with Microsoft Office 365, the choice of server is unavailable. Selecting your Office 365 tenant as the target organization is enough. For details about synchronizing public folders with Office 365, see theMigrating to Microsoft Office 365 document.

For both the source and the target server, you should specify a mailbox that will be used by the public folder synchronization agents.

The account under which the public folder synchronization agents are running must have full access to the administrator mailboxes so that they can get administrative access to the synchronized folders.

Migration Manager will retrieve the public folder hierarchy using the mailboxes you specify. If you are logged on under an account that does not have access to these mailboxes, click Advanced to use an alternate NT account to retrieve the hierarchy.

The wizard will also create the first collection for the job. This first step prompts you for the collection name.

Step 2. Select Public Folders

The next step allows you to configure the public folder synchronization collection. Select the root folders to be synchronized. If you don’t want to change the folder hierarchy, the easiest way is to select All Public Folders on both the source and target servers as the synchronization root. Simply select Public Folders in both the Source server box and the Target server box. The wizard will ask if you want to create a Public Folders folder on the target server and synchronize all the source public folders to this folder. Select Yes or No as appropriate.

Alternatively, you can select an existing Exchange folder as a target root folder. If the target root folder does not exist, you can create it by selecting the Add New Folder option from the shortcut menu as shown below.

To add a pair of folders to the collection, select the folders in both lists, set the synchronization direction, and click Add. The folders and all their subfolders will be marked as included to the collection.

You can also select the synchronization direction. Click the <->button to change the initial source -> target direction of synchronization if necessary.

To exclude a folder from synchronization, right-click the folder in the tree and click Exclude. The public folder synchronization agents will not synchronize the content of the folder, but will create it on the corresponding server and synchronize its subfolders, if any.

Click Exclude PF with subfolders to exclude from synchronization a folder itself and all its subfolders.

Step 3. Specify Agent Installation Path

The wizard will install the public folder synchronization agents on the source and target Exchange servers. If no Migration Manager for Exchange component has been yet installed on these servers, you will be able to specify the installation path for the agents. As soon as the agents are installed, the QMMEx$ServerName$ shared folder will be created in the path you specified. All the agents or components you install later will be installed in the same location. However, if by the time you install the public folder agents, any other agents or components have already been installed, you will not be allowed to specify the installation path for the agents, and they will be installed in the location where the QMMEx$ServerName$ shared folder has been created.

By default the shared folder is created in the Windows %SystemRoot%\System32 folder. On Microsoft Exchange x64 the default shared folder is created in the %SystemRoot%\SysWOW64 folder.

Step 4. Completing the Wizard

After the agents are installed, the wizard will inform you that you can start the public folder synchronization job. It is strongly recommended that you verify all the agents and collection settings before starting the public folder synchronization. The available options are discussed in theChanging the Settings of a Public Folder Collection and Changing the Settings of Public Folder Synchronization Agentstopics in this guide.

Step 5. Commit Changes

After a new job is created, it is marked with an exclamation mark. This means that you need to update the public folder synchronization agents’ databases before starting the job. Right-click the job in the management tree and click Commit Changes on the shortcut menu to update the agents’ task lists on the remote servers.

You can also commit changes for all the public folder synchronization jobs you have created. To do that, right-click the Public Folder Synchronization node in the management tree and select Commit All Public Folder Jobs from the shortcut menu.