Migrating Users from Windows 2003 to Windows 2008 using ADMT 3.1

Published on
16,339 Points
3 Endorsements
Last Modified:
Community Pick
Hi guys,
I’m going to talk today about the ADMT 3.1 and the complete process of migrating users accounts and passwords supported with snapshots. Active Directory Migration tool “ADMT 3.1” is the latest version that can be run on Windows 2008.

This task will demonstrate with snap shots the process of setting up the ADMT, configuring user’s migrations, setting password export server on the source domain, migrating users’ passwords and SID history.

First step: installing ADMT 3.1 on Windows 2008 Domain Controller

Installing ADMT

ADMT installation file can be downloaded from
    Active Directory Migration Tool version 3.1

During installation, the installation Wizard will ask about the database to be used by ADMT, the wizard can use existing SQL 2005 instance or it can install a new instance of SQL 2005 Express, in our case we choose to install a new SQL 2005 instance.
2-sql setupThen, the wizard will prompt us if we need to import data from any previous ADMT database, since this is a new installation we choose not to import any data
3-import previous settingsImporting previous ADMT data.
Then the installation Wizard completes successfully
4-finish installationSecond Step: Installing Password Export Server

In order to be able to export the users' passwords, we need to install the password export server.
The password export server will need a password encryption file to secure password migration, to create this password encryption file we use the ADMT utility in the command line to generate the file as follows:

1-We navigate to the location of the installation of the ADMT, in our case it is C:\Windows\ADMT

2-We issue the following command
admt key /opt:create /sd:”Source_Domain” /kf:c:\Domain.pes /PWD *

Open in new window

3-The utility will then ask you to provide the password and validate it.
5- admt key generation_0.previewAfter creating the encryption file we move it the source domain controller where we are going to install and use the password export server as in the following steps
1-Start the installation wizard
6-installing PES2- Accept the license agreement
7-accept the license3- Choose the password encryption key file that we created in the previous steps
4- Insert the password that we used to encrypt the password encryption file
9-password prompt5- Start installing the Password Export Server
10-start installationChoose the service account that the PES server will run under , this account should be administrator on the destination domain, we chose the administrator in the source domain and made it a member of the administrators group in the Windows 2008 domain.
11-pes installationUp to this stage, the installation is finished, the wizard will require the source server to be restarted.

After restarting the server, the PES server has to be started manually.

Running the ADMT Migration wizard

To start the migration wizard, we go to the ADMT console on the destination domain controller, “Windows 2008 DC” and
start the user’s migration Wizard
12-start admt wizardStart ADMT Users Migration
Choose next to the welcome screen
13-start admt wizardStart Migration
Choose the source Domain and domain controller, and the destination domain and domain controller. In our case the source domain is radmins.com and the source domain controller is RDC01radmins.com, the destination domain is nwtraders.com and the destination domain controller is dc01.nwtraders.com
14-Source-Destination DCsThen we choose to select the users from the domain directly and not from a file
15-select users from doamin16-select users from doaminSelecting Users to Be migrated
After selecting the user accounts to be migrated, we choose to migrate the passwords of the users as well and choose the password export server on that we installed on the source domain controller.
17-password migration

Password Migration

Then we choose the target OU to which we will migrate the users to.
18-destination ouThen we choose the state of the migrated users, we can select that the users will be enabled, disabled, or the same state of the source domain, also we can select to migrate the source SID of the users, this will allow users to access the resources that they used to access in the source domain.

Migrated users state and SID migration

When choosing to migrate the users SIDs, the wizard will prompt to enable auditing and creating a group necessary for migration of users SIDs, by selecting “yes” the wizard will enable these settings on the source domain controller automatically ad we can proceed.

Enabling Auditing

The wizard then will prompt for a user account with proper privilege to add SID history
21Administrative Account
The wizard then will prompt for options like migrating users roaming profiles, update user’s rights, migrating associated groups, and fix users group memberships.
22Migration Options
Then the wizard gives us an option to exclude some users from migrations.
23Users Exclusion
Then we can choose how to handle conflicts when they occur.
24Dealing with users conflict
And finally the migration wizard will start migrating users.

Expert Comment

Apt Article, well documented appropriately with the required Screenshots.
Refreshed my learning of using ADMT v2 and v3..


Expert Comment

Precise documentation! Thanks!

Expert Comment

by:Paul Wagner
The ADMT manual says that you have to migrate service accounts and global groups first. Does this article infer that those steps were already done?

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Join & Write a Comment

This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month