Preparing Migration 8.14 - System Requirements and Access Rights

See the Source Accounts Used by Migration Manager for Exchange Agents topic.

• User Management Administrator account
• ApplicationImpersonation role
• Mail Recipients role
• Microsoft Exchange Online license
• Default UPN
• The account should be associated with the primary hierarchy public folder mailbox
• The account should be granted by Owner permissions on all public folders

You can use either the Local System account (default) or a specified account.

If you specify an account explicitly, make sure that it has sufficient privileges to create and remove computer accounts as part of the move operation. One way to do this is to give the account administrative rights in both the source and target domains (membership in the Domain Admins group of the source domain and in the domain local Administrators group of the target domain, or vice versa).

However, if you prefer privileges to be more granular, you can give the account the following specific permissions:

• Create All Child Objects on the target domain object
• Delete All Child Objects on the source domain object

Important: If computer running Migration Manager RUM Controller Service (in fact, computer running Migration Manager console) and computers running Migration Manager RUM Agent Service (workstations and servers to be processed) are located in different domains of different forests without trusts established between them then you should specify account for Migration Manager RUM Agent service account explicitly. The Local System account (default) cannot be used.

• Must be a member of the local Administrators group on the computer running the Resource Updating Manager.
• Must have Full Admin access rights on ADAM/AD LDS database.

• Member of the local Administrators group on the server where the agent is installed
• Log on as a service right enabled on the server on which the agent is installed.

To verify that this right is granted, do the following:

1. Start the Local Security Settings snap-in.
2. In the left pane, select User Rights Assignment under the Local Policies node.
3. Double-click the Log on as a service right in the right pane. Verify that the Statistics Collection Agent service account is in the list of accounts that are granted the right. If it is not, add it.