ADMT Service Account

In this article, I did not create ADMT Service Account, because I used my TestLAB and for ADMT service account, I used target domain administrator account (Wiki\Administrator). Please, for ADMT Service Account in Real Scenario, use Santhosh Sivarajan - MVP article:

ADMT Service Account - Permission and Configuration

Creating Trust Relationship

Click Strat, then Administrative Tool, open Active Directory Domains and Trusts.



Right click on the domain (Contoso.com), then click Properties.



Click Trusts tab, then select New Trust.



On the Welcome to the New trust Wizard page, click Next.



On the Trust Name page, write target DNS domain name (Wiki.com), then click Next.



On the Trust Type page, select Forest trust, then click Next.



On the Direction of Trust page, select Two-way, then click Next.



On the Sides of Trust page, select Both this domain and the specified domain, then click Next.



On the User Name and Password page, write domain administrator credentials for the target domain (Wiki.com).



On the Outgoing Trust Authentication Level-Local Forest page, select Forest-wide authentication, then click Next.



On the Outgoing Trust Authentication Level-Specified Forest page, select Forest-wide authentication, then click Next.



On the Trust Selections Complete page, review your settings, then click Next.



On the Trust Creation Complete page, review your settings, then click Next.



On the Confirm Outgoing Trust page, select Yes, confirm the outgoing trust, then click Next.



On the Confirm Incoming Trust page, select Yes, confirm the incoming trust, then click Next.



On the Completing the New Trust Wizard, click Finish.



Click OK to close Properties page.



Now, we need to validate Trust Relationship on Windows Server 2008 R2 Domain Controller (Wiki.com).
Click Strat, then Administrative Tool, open Active Directory Domains and Trusts.



Right click on the domain (Wiki.com), then click Properties.



Click Trusts tab, select target domain (Contoso.com) in Domains trusted by this domain (outgoing trusts) box, then click Properties.



On General tab, click Validate.



Select Yes, validate the incoming trust. Write domain administrator credentials for the source domain (Contoso.com), then click OK.



Now, you can see The trust has been validated. It is in place and active. Click OK.



Now, you see information about update the name suffix routing, click Yes.



Click OK and close Properties page.



Click Trusts tab, select target domain (Contoso.com) in Domains trusted by this domain (incoming trusts) box, then click Properties.



On General tab, click Validate.



Select Yes, validate the incoming trust. Write domain administrator credentials for the source domain (Contoso.com), then click OK.



Now, you can see The trust has been validated. It is in place and active. Click OK.



Now, you see information about update the name suffix routing, click Yes.



Click OK and close Properties page.



Click OK and close Wiki.com Properties page.

Installing SQL Express

ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. You should use SQL Server Express. When you use one of the following versions of SQL Server Express, ADMT installation enforces the following service pack requirements:

• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.

Double click on SQLEXPR_x64_ENU.exe and run application.









On right panel, click Installation, then on left side click New SQL Server stand-alone installation or add features to an existing installation.






On the Setup Support Rules page, click OK.



On the Product Key page, click Next.



On the License Terms page, seclect I accept the license terms box, then click Next.



On the Setup Support Files page, click Install.



On the Setup Support Rules page, click Next.



On the Feature Selection page, select Database Engine Service, then click Next.



On the Instance Configuration page, accept default names and setting, click Next.



On the Disk Space Requirements page, click Next.



On the Server Configuration page for SQL Server Service, use your ADMT Service Account (because is my TestLAB, I used Wiki\administrator account), then click Next.



On Database Engine Configuration page, select Windows authentication Mode, then in Specify SQL Server administrators add Wiki\Administrator account. Click Next.



On Error and Usage Reporting page, click Next.



On Installation Rules page, click Next.



On Ready to Install page, click Install.



On Installation Progress page, click Next.



On Complete page, click Close.

Installing ADMT 3.2

Now, we install ADMT 3.2 on target domain (Wiki.com). Keep in mind, You can install ADMT 3.2 only on Windows 2008 R2 servers.
On Welcome to the Active Directory Migration Tool Installation page, click Next.



On License Agreemnt page, select I Agree, then click Next.



On Customer Experience Improvement Program page, click Next.



On Dabase Selection page, in Databse write your SQL Databse Instance, my instance is .\SQLEXPRESS, then click Next.






On Databse Import page, select No, do not import data from an existing dabase (Default), then click Next.






Review informations, then click Finish.

ADMT error: Unable to check for failed actions. :DBManager.IManageDB.1

When installing Active Directory Migration Tool (ADMT) 3.2 on a Windows Server 2008 R2 domain controller and using SQL Express 2008 with SP1 and SQL 2008 Cumulative Update 4, the installation completes without errors. However, the dialog "Active Directory Migration Tool Installation Wizard" is blank when the install is finished.

When then attempting to run the ADMT console, you receive error:

The MMC console then displays:

There is a code defect in how ADMT interoperates with SQL Express 2008 SP1 on domain controllers resulting in the "SQLServerMSSQLUser$ComputerName$InstanceName" group not being created. This group is required by ADMT to configure specific permissions during the ADMT install and allows the ADMT database to be created in the SQL instance. ADMT expects the group to be present, which leads to the blank dialog and an incomplete installation.

Resolution:

ADMT 3.2 installation incomplete, MMC console error "cannot open database 'ADMT' requested by the login"
 

ADMT 3.2: Common Installation Issues

You can find Common Installation Issues about ADMT 3.2 in this link:

ADMT 3.2: Common Installation Issues - NedPyle [MSFT]

Creating Encryption Key

ADMT key /option:create /SourceDomain:Contoso.com /keyfile:C:\FMP\FiuleMigPass.pes /keypassword:Password01

ADMT Migration Account

Installing ADMT Password Migration DLL

Starting Password Export Server Service