Opening a Migration Project
In most cases you will need just one Migration Manager project for your whole migration, no matter how many domains you have. Normally, you would use a separate project only for lab testing before you start migration in the production environment.
|
|
Caution: If you plan to migrate objects from Active Directory to Microsoft Office 365 using Migration Manager, you need to create a separate migration project in Migration Manager for Active Directory (Microsoft Office 365) console. You will be prompted for a name for the project and AD LDS instance to store its data. For more information on migration to Microsoft Office 365 scenario, refer to the Migrating To Microsoft Office 365 document included in the Migration Manager documentation set. |
The Open Project Wizard will help you with configuring the migration project and all its components: the AD LDS or ADAM database, the SQL Server database (for Exchange migrations only), and Statistics Portal.
|
|
Note: These configuration steps are required if you installed Migration Manager using Advanced mode. |
If you used Express setup mode, AD LDS or ADAM was installed and configured automatically.
The wizard can be used to start a new project, connect to an existing project, or change any settings of the current project.
When you run Migration Manager for the very first time, the Open Project Wizard is started automatically. To start the Open Project Wizard for subsequent uses, in Migration Manager console, select File | Open Project.
The following steps are presented in the Open Project Wizard to help you configure your migration project.
Configuring AD LDS or ADAM Database
|
|
Note: If you installed Migration Manager using Advanced mode, you need to install and configure Active Directory Lightweight Directory Service (AD LDS) or Active Directory Application Mode (ADAM) manually. AD LDS and ADAM can be found on the Migration Manager CD and on Microsoft’s Web site If Express setup mode was used, AD LDS or ADAM was installed and configured automatically. |
Migration Manager uses Microsoft Active Directory Lightweight Directory Service (AD LDS) or Active Directory Application Mode (ADAM) to store its project data.
On the Select Project | Configure ADAM/ADLDS Project page of the wizard, configure the following settings:
- ADAM or ADLDS server—Specify the name of the server on which AD LDS or ADAM is installed. Migration Manager will try to connect to the server by LDAP and locate the AD LDS or ADAM instance.
- Port—The port number of the AD LDS or ADAM instance. By default, AD LDS or ADAM uses port 389. The port number might be different if AD LDS or ADAM is installed on a domain controller or this is not the first AD LDS or ADAM instance on the server.
- Select a project—For each new project, Migration Manager automatically creates a partition in the AD LDS or ADAM instance you specify. You can either connect to the existing project or create a new one:
- To create a new project, select the Create a new project option and type a name for the project. Migration Manager will create an AD LDS or ADAM partition for the new project and, if required, extend the AD LDS or ADAM schema.
- To connect to an existing project, select the Use existing project option. If the AD LDS or ADAM database already has Migration Manager projects in it, select the necessary project from the Use existing project dropdown list. Alternatively, click the Retrieve Projects button. Migration Manager will connect to AD LDS or ADAM and retrieve the list of its projects already in the database.
Setting Auxiliary Account
The AD LDS or ADAM database is the central configuration storage for the migration project. On this step of the wizard, you can specify the auxiliary account that various Migration Manager components will use to access the AD LDS or ADAM database.
Username—Specify the username for AD LDS or ADAM access. This can be any account that can be successfully resolved on the console, AD LDS or ADAM server, computers from which the resource updating will be performed, and other computers on which Migration Manager components will run.
Password—Type the password for the account.
|
|
Note: This account must be a member of the computer local Administrators group on the computer running the Migration Manager console. No particular rights in the domain are required; ordinary domain user rights are sufficient. Consider that the account will be granted Full Admin rights in the project database. |
Configuring SQL/MSDE Database
|
|
Note: This step applies to Migration Manager for Exchange only. |
An SQL Server database is required to store information related to Exchange migration.
SQL server—Specify the name of the SQL server and instance to be used to store the Exchange migration information, for example: SQLSERVER\QMMINSTANCE.
Authentication—Specify the authentication type and credentials to access the server:
- Use Windows authentication—If this option is selected, Migration Manager will use the logged-in user credentials to connect to the database.
- Use SQL Server authentication—If this option is selected, Migration Manager will use a SQL Server account to connect to the database. Specify the SQL Server account and password to be used to access the database.
Select database—You can either connect to an existing database or create a new one:
- If the SQL Server or SQL Server Express installation already has a database containing the Exchange migration project data, you can select the Use existing database option. Select the database from the list, or click the Retrieve Database List button to have Migration Manager connect to the server and retrieve the list of databases.
|
|
Caution: You should not share the Migration Manager database with other applications or between different projects. |
- Alternatively, select the Create a new database option and type the database name. Migration Manager will connect to the SQL Server you specified and create the database.