ADMT 3.2 released

ADMT 3.2 released

  • Comments 22
  • Likes

Come and get it. Especially you commenters that liked to swear at me anonymously :-). Besides now supporting Windows Server 2008 R2 and fixing some bugs, this version now supports Managed Service Accounts.

Active Directory Migration Tool version 3.2 - download here.
ADMT 3.2 Migration Guide (DOC) - download here

System Requirements

  • Supported Operating Systems: Windows Server 2008 R2
  • ADMT can be installed on any computer capable of running the Windows Server 2008 R2 operating system, unless they are Read-Only domain controllers or in a Server Core configuration.
  • Target domain: The target domain must be running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
  • Source domain: The source domain must be running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
  • The ADMT agent, installed by ADMT on computers in the source domains, can operate on computers running Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

The updated 3.2 Migration Guide is coming shortly, I will update this post with that link when I have it. It's out.

- Ned "you wouldn't say that to my face!" Pyle

  • Brilliant, been waiting for this for a while.  Just started migrating 57 domains into 1 will give it a try this weekend.  Has a new version of PES been released with it or are we sticking with 3.1?

    Cheers

    Kevin

  • Hi,

    PES 3.1 is still used for both.

  • I'm having an issue already with the installation. The SQLExpress install was fine, and the Tool installation was fine (I think). It found the database instance intantly, and installed completely. Now however, when I try to open the ADMT MMC, I get an error that says:

    ---------------------------

    Active Directory Migration Tool

    ---------------------------

    Unable to check for failed actions. : DBManager.IManageDB.1 : Unable to retrieve the database file path from the registry. The system cannot find the file specified.

    ---------------------------

    OK  

    ---------------------------

    After clicking on OK, the MMC comes up, but says "MMC could not create the snapin. The snapin may not have been installed correctly."

    Any thoughts as to what I should do next? Uninstall/reboot/reinstall has not worked.

  • It sounds like the tool installations did NOT go fine. :)

    Can you validate this on another machine first - preferrably a cleanly-built one that has no third parties installed (especially not AV) and is not built from an image. I'd recommend a virtual machine that you just installed Win2008 R2 on and nothing else.

    I'd recommend a support case if this still does not work. This will require a bunch of data from you (including plenty of PII and security-related stuff) that this blog cannot handle.

  • Same Problem, the installation finished with no error (also the wizard don't show an installation overview) - The logs in %windir%\ADMT\Logs didn't say anything except "Finished Sucsefully"... I've installed in Win2008 R2 Guest Machine, as a domain controller (Spanish) with SQL Express 2008 x64 .

    Then in another machine (Also a Domain Controller in the same domain, 2008 r2, "syspreped" and started with the same vhd image) i've install SQL 2005 English and ADMT installs just fine (maybe is a ADMT/SQL 2008 issue)

    Regards

    Rodrigo

  • Ah - so you are saying that SQL 2005 and SQL 2008 are giving you different behaviors here, both with ADMT 3.2? Do you have problems with 2008 on English - there are a few variables still in here that need to be removed.

  • Hi John and Rodrigo,

    I was just now able to reproduce this - in order to have it happen, I needed to be running SQL Server Express 2008 SP1 *on a DC*. If I installed the DB on a Win2008 R2 member server there were no issues.

    I had no issues with SQL Express 2005 SP3 on a DC or member.

    I'll digu further into what's up here. In the meantime, those are your two workarounds. If you must useSQL 2008 make sure it is not on a DC. This explains why most folks haven't reported this yet - typically people avoid running SQL on DC's as it's not recommended for performance reasons.

    - Ned

  • I just confirmed Ned's findings and wasted hours trying to figure it out. :)

  • BTW ... SQL Express 2008 R2 isn't supported by ADMT 3.2 for anyone out there planning a migration.

  • Hi,

    Is there something new about scripting ADMT with powershell ?

    Or have we to use a ADMT.migration ComObject ?

    Ludovic.

  • @NonikTech

    Yep. I am working on a blog post (and likely a KB too) that will cover all these shenanigans, what works and what doesn't.

    @LudovicB

    No new scripting options with PowerSehll. The old way is still the only way.

  • Currently testing migration between two 2008 R2 domains.

    Using 2008 member server with ADMT 3.1 worked fine for migration of groups, users, and computers.

    Testing with 2008 R2 and ADMT 3.2, I've run into a couple of issues.

    As already pointed out, SQL 2005 Express SP3 works right out of the gate; SQL 2008 takes more work.

    Migrating groups and users allows selection of an include file, but migrating Computer accounts does not. Select the radio button for the include file, click "Next" and the wizard will not progress to the include file selection. I've tried this from ADMT implemented on one of the DCs and on a member server, both running 2008 R2.

  • Testing migration from a root and five child Windows Server 2003 Forest to a Windows Server 2008 R2 Single Domain Forest.

    I'm also seeing the issue where you can't select the option to use an Include File when running the Computer Migration Wizard.  You select the radio but but when clicking 'Next' the wizard does not move onto the include file selection window.

  • Dang, I missed this first comment, thanks haganerei and scepticdad. I'll investigate this today and get back to you. Thanks for reporting this.

  • Are there any ADMT that can be used for migrating from Windows 2000 Server to Windows Server 2008 R2 AD ?