The Sysadmins

Tips and tricks from the Sysadmins

ADMT Series – 11. Computer Migration Wizard

This post will cover the process of migrating computers from the source domain to the target domain. After you migrate a batch of local user profiles, migrate the corresponding batch of user workstations.

ADMT Supported Operating Systems for Computer Migration

ADMT 3.2 – supports the migration of computers that run Windows XP, Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.

ADMT 3.1 – supports the migration of computers that run Windows 2000 Professional, Windows XP, Windows Vista, Windows 2000 Server, Windows Server 2003, and Windows Server 2008

ADMT 3.0 – supports the migration of computers that run Windows 2000 Professional, Windows XP, Windows NT 4, Windows 2000 Server, and Windows Server 2003.

Computer Migration

From the ADMT machine, run ADMT and select Computer Migration Wizard.

Select the source and target domain, you can also select which specific domain controller to use.

Select computers from the domain or use an include file. This may be quite useful if you’re doing an OU at a time as you can export objects of an OU via ADUC (right click -> export list).

Select the target OU.

Choose the objects you wish to translate.

Here you can choose to replace, add or remove the permissions. Add is the safest option and is what I would recommend in most cases.

After the wizard has completed, wait x minutes before restarting the computer. This can typically be set to 0 minutes.

You can exclude particular attributes of the computer here, if needed.

Select Do not migration source object if a conflict is detected in the target domain.

At this stage the computer object will be pre-staged in the target domain, you will be able to refresh the target OU and view the object.

As usual, run the pre-check, then run pre-check and agent operation. Once the Agent operation is complete, the wizard will wait to carry out the post-check. The post check uses a A record in the target domain to contact the machine and remove the ADMT tools. You should see an A record being created on machine reboot.

If you don’t, the post-check will fail- this isn’t a major issue. As long as you’re aware of why it failed. If the A record has not been created you will need to investigate why.

You’ll probably get a message in the logs stating:

Admt unable to retrieve the dns hostname adsi property cannot be found in the property cache hr=0x8000500d

Confirmed joined.

ADMT Series – 1. Preparing Active Directory
ADMT Series – 2. Preparing the ADMT Machine
ADMT Series – 3. SID History
ADMT Series – 4. Password Export Server
ADMT Series – 5. Machine Preparation
ADMT Series – 6. Service Account Migration Wizard
ADMT Series – 7. Group Account Migration Wizard
ADMT Series – 8. User Account Migration Wizard
ADMT Series – 9. Merging Users with a Different sAMAccountName
ADMT Series – 10. Security Translation Wizard – Local Profiles
ADMT Series – 11. Computer Migration Wizard


  1. Thanks you soooooo much!
    I have same issue in my company – i need to migrate from 2003 domain to 2008R2 and i use yours articles about migration like handbook.

  2. Great guide mate. Love your work!

  3. It is very simple for understanding…..

  4. Thank You very much…. now I dont need to follow 265 pages in ADMT 3.2 guide. 🙂

  5. Fantastic guide Tom, really got me out of a bind. Very easy to understand and follow and then everything worked just as you said. I’ve already bookmarked your site and shared this with the rest of my colleagues. Much thanks! 😀

  6. Excellent Job …..!!!!!!!!!!!11

  7. Great job! Helped me to migrate domain to 2008 R2 500 users!

  8. It seems on the computer migration part I have to change the primary DNS to point to the target DC’s IP address to get it to complete. Do you know any way around doing this?

  9. Really good informative guides how to carry out the migration tasks. Makes it easier than trawling through the ADMT guide and different websites to piece together the information.

  10. Nice work.
    Thank you a lot.

  11. I think the re-released ADMT 3.2 supports the migration of down-level systems now. There’s no need to dig up 3.1 to migrate legacy systems.

  12. Great job!
    Thank you very much!

  13. Awesome….Thank you so much for this Series…

  14. Thank you so much for sharing this! 🙂

  15. Great post. This exactly the information I have been looking for.

  16. This is great step by step guidance, Thank you

  17. Cool stuff! Thanks for publishing, help me to save much time!

  18. This post is fantastic! I must leave a “thank you” comment for all of this!
    Thank you so much 🙂

  19. Wow, this was an excellent guide. This will save me a ton of time with our Forest migration. Your instructions were much more straightforward than the Microsoft ADMT guide.

    Thank you very much for taking the time to create and post this.

  20. Great !!
    Thanks a lot !!

  21. Thanks

  22. Thank you!!

  23. Anyone used this with Windows 8.1,10, Server 2012, or Server 2016? Reading a lot about how it’s not been updated to work with those OS’s which is 90% of my workstation and server setups. I find it hard to believe…

  24. Andrew Melillo

    March 13, 2020 at 4:19 pm

    Still out here in 2020 using this guide and works like an absolute charm – Tom you are the man! We just migrated a very complicated customer environment that hadn’t had a single windows update since 2005. Hats off for the excellent and thorough guide. 8 years later and you are still saving people! THANK YOU!

  25. Thanks a ton. This was an amazing article and is still saving us a lot of time looking around for 100 different settings. Your efforts in putting this together are greatly appreciated!!!!!

  26. Thanks for the great guide, really helped to migrate 5 separate forests and domains to a single forest and domain. The steps were much simpler to follow than the ADMT guide. Kudos to you sir.

Leave a Reply

Your email address will not be published.


This site uses Akismet to reduce spam. Learn how your comment data is processed.