The Connection page displays the name of the server or database availability group (DAG) for which the connection settings are configured. The settings for a DAG, an Exchange server in a DAG and an individual server differ slightly. This is because different synchronization jobs are available in different configurations, as follows:
|Individual Exchange Server||DAG||Exchange Server In DAG|
You can specify the Exchange account used by all of this server's agents to connect to the server and perform all the actions required for synchronizing the server objects. Please note that this account must:
This page also allows you to specify the Mailbox Migration Administrator Mailbox and the Public Folder Migration Administrator Mailbox, which are described below.
Mailbox and Calendar Synchronization agents access the migrated mailboxes via the specified Administrator Mailbox. By default, the Microsoft System Attendant mailbox is used as the Administrator Mailbox. It is not recommended to change this setting until either of the following occurs:
If the Specified mailbox option is selected, the mailbox you specify should be hosted on the same server and must be fully accessible by the Mailbox and Calendar Synchronization agents.
The Public Folder Migration Administrator Mailbox is used to get administrative access to the server’s public folders. It is the same mailbox that you select when setting up a public folder synchronization job. This mailbox does not need any rights on the public folders for the synchronization. The account that is used by the agent should have full access to the mailbox that is specified here.
Caution: Be careful when selecting the administrative mailboxes. Once you start the public folder synchronization process, you should not change the administrative mailboxes; doing so will lead to full resynchronization of public folder contents and might cause other issues.
Because Exchange uses Active Directory to store the directory information, Migration Manager for Exchange uses domain controllers (DCs) to enumerate Exchange objects.
Migration Manager associates one DC with each Exchange server when you first register the source and target organization in the database. In some cases, you may need to change a DC associated with the server. For example, you may need to do this if a DC is temporarily unavailable.
The Associated Domain Controller page allows you to change the server association as well as the account used to work with Active Directory. The account must have the following rights:
Caution: If you are working in a multi-domain environment, it is recommended that the associated DC have a copy of Active Directory Global Catalog. This is needed to apply the mailbox and public folder client permissions granted to users migrated to other Active Directory domains.
This page lets you specify an agent host—a computer that will host the Migration Manager agents performing the migration workload. It is recommended that you use a computer that is not a participating Exchange server. For more information about the automatic choice of default agent host, see the Finding Installed Agents topic. For general details about agent hosts, see the Using Agent Hosts for Migration Agents topic.
This section refers to properties of servers shown in the right pane when any of the following nodes is selected in the treeview:
To collect agent statistics from a server, select the Collect agent statistics from this server check box on the Connection page.
For each server, you can specify the amount of disk space (either in megabytes or in a percentage of the total available drive space) that should not be used by the agents working on the server.
You can also specify the memory limit that should not be exceeded by each agent working on a server. We do not recommend changing this parameter unless your environment requires it.
Increasing the memory limit might be required if the agents’ performance is slow and you see the following trace message in the log: “The agent’s system memory limit 64000 Kb has been exceeded. Agent will be terminated.” This affects the agents’ performance, so you might want to increase the memory limit if you have enough resources.
Decrease the memory limit if the server is unstable and low on memory. Be very careful with this option. Setting it to a lower value will affect the performance of all the agents. If the memory limit is reduced, we recommend that the PST size limit be set to a lower value, since this will reduce the impact on the performance of the mail and public folder agents.
Be aware that the agents might not even be able to start if the limit is too low. The lowest acceptable value depends on the server. An administrator should carefully test this in the environment to find a value that:
The Mail Source Agent can send a notification message to each user whose mailbox has been switched. The Switch notification page in the properties of the Mail Source Agent allows you to edit this message and select whether the notification should be sent to the source mailbox, the target mailbox, or both.
The settings that are applied to the entire Exchange migration project are all gathered in the Options dialog box. To open this dialog box, click Options on the Tools menu.
Because Migration Manager for Exchange uses a distributed architecture, the agents obtain all license information from a single license server that you can specify in this page. By default, a server on which Migration Manager is installed is used as the license server.
If the agents are running under an account that does not have access to the license server, you can force the agents to establish a Net use connection to the license server by selecting the Net use connection check box and specifying the appropriate credentials.
Please refer to the Licensing section of the Migration Manager Installation Guide for further details.
This dialog allows you to fine-tune agents behavior.
Mail-enable / mail-disable and control GAL visibility of the target public folders based on the source settings. If two-way public folder synch is enabled, those settings are also synced from the target to the source public folders. For the corresponding INI value, see SyncMailEnabled in Fine-Tuning the Agents section.
Do not synchronize source and target public folder settings. Public folders created by the migration agent are mail-disabled by default.
Synchronize all settings between the source and target public folders.
If the source public folder is mail-enabled and not hidden from GAL, synchronize the target public folder settings with the source. Otherwise, leave the target public folder unchanged.
Write Migration Manager agent’s logs in Unicode format. This greatly improves the readability of logs containing localized content (such as folder names), but increases the amount of disk space consumed by log files.
Migration Manager for Exchange allows you to manage synchronization agents using the Migration Manager console. To view the list of agents that perform a job, select the job in the management tree and click the Agent Manager button on the Migration Manager toolbar. To view the recent log entries for an agent, right-click the agent in the right pane and select Recent Log Entries from the shortcut menu.
The Agent Manager Options page allows you to fine-tune the refresh options for the information displayed. You can select the time intervals at which Migration Manager will refresh the agent’s list, the agent’s state, and the recent log entries.
To set the default properties for the synchronization agents, synchronization jobs, and servers involved in synchronization, you can use the Default Properties dialog box. Instead of opening the properties of each server, job, or agent and modifying them separately, you can set the default properties all on one page. The default settings can be overridden by modifying the properties of a server, job, or an agent directly.
The Default Properties dialog box provides three sets of pages so you can select the default properties for synchronization agents, synchronization jobs, and servers involved in synchronization.
To change the default settings for agents, jobs, or servers, take the following steps:
To cancel all changes you have made to the default settings for agents, jobs, or servers, take the following steps: