Pre-Requisites
Before installing Migration Manager, make sure your environment meets the system requirements listed in the System Requirements and Access Rights document. In particular, check the requirements for the following computers:
- Migration Manager console
- Domain controllers (source and target)
- Source and target Exchange servers (for Migration Manager for Exchange)
- Migration Manager database servers
- Active Directory Application Mode server
- Migration Manager for Exchange database server
- Migration Manager agents’ servers
- Directory Synchronization Agent server
- Statistics Collection Agent server
- Statistics Portal server
Migration Manager Components and Service Accounts
As described in this guide, Migration Manager consists of several components, including:
- Migration Manager console
- Directory Synchronization Agent
- Migration Manager for Exchange agents
- Statistics Collection Agent
- Statistics Portal
To perform their tasks, these components use several accounts, called service accounts or administrative accounts. Access rights and permissions required for these accounts are described in the System Requirements and Access Rights document.
Providing for Resources Availability (Active Directory Migration)
To ensure that resources will still be available to users when they start using their target accounts and when you have cleaned up SIDHistory, permissions granted to source accounts to access the resources must be reassigned to the target accounts.
Service accounts and accounts used to run scheduled tasks must also be changed to the corresponding target accounts to ensure that services and scheduled tasks will run correctly after the source accounts are disabled.
The resources can be divided into two groups:
- Distributed resources, such as end-user workstations, file and print servers, servers running IIS, scheduled tasks, and other services and applications
- BackOffice servers, such as Exchange, SQL, and SMS
To make the migration transparent to users, Migration Manager for Active Directory uses a set of utilities that provide for automated resource processing to reflect the domain reconfiguration.
Administrative Access to Distributed Resources
Administrative rights over the resources are required for successful resource updating. To obtain administrative rights, do either of the following:
- Add the account you are currently logged on to the console to the local Administrators group on each computer to be updated.
|
|
Note: By default, the Domain Admins group of the domain that the computer is a member of is a member of a computer’s local Administrators group. You will get administrative access to the computer if the account you are using to use to log on to the console is a member of the source Domain Admins group. |
Use another account that is a member of a computer’s local Administrators group to connect to the computer. Establish the connection to the machine’s administrative share using a standard net use command, as follows:
net use \\MachineName\Admin$ /u:DomainName\Admin_Account
net use \\MachineName\C$ /u:DomainName\Admin_Account
where the Admin_Account is the account that is a member of a computer’s local Administrators group.
Server Service
Server service is automatically installed when you install the File and Printer Sharing service on the computer.
Server service must be running on a computer to be updated from either Resource Updating Manager or the command-line updating tool VMover.exe. If for some reason (for example, due to your corporate policy), Server service is not allowed to run on the computers, you need to install or enable Server service temporarily, update the computers, and then disable or uninstall the service.
Administrative Access to BackOffice Servers
For information about the permissions required for successful Exchange, SMS, and SQL server update, please refer to Appendix A. How to Set the Required Permissions for Active Directory Migration of the System Requirements and Access Rights document.
To learn how to set the required permissions for Microsoft BackOffice products, refer to their documentation.
Additional Pre-Installation Considerations
This section describes environment peculiarities you may need to consider before deploying Migration Manager and starting your migration project.
Active Directory Connector
If you have already started Exchange migration with the Active Directory Connector (ADC), note that Migration Manager and ADC use different object matching criteria, so ADC should be completely replaced with Migration Manager directory synchronization in the inter-org migration scenario.
Migration Manager and Microsoft Outlook
Microsoft does not recommend installing Outlook on Exchange Server, because its security extension is low for the server side. For more information, please refer to Microsoft does not support installing Exchange Server components and Outlook on the same computer Microsoft Knowledge Base article.
Migration Manager and Backup Utilities
If any backup tools are installed on the servers where Migration Manager agents are to run, the schedule for these tools and the agents should not overlap; that is, the backup utility and the agents should be scheduled to work during different hours. In any case, the use of any backup utility together with Migration Manager should be tested in the lab before deployment in the production environment.
Providing Communication Using IP version 4 for Exchange Migration
TCP/IP version 4 (IPv4) must be installed and configured on all servers on which you are going to install Migration Manager for Exchange agents.