Microsoft's official enterprise support blog for AD DS and more
UPDATE June 19 2010 - stop reading and go here:
There’s a known issue with installing Active Directory Migration Tool (ADMT) v3.1 onto a Windows Server 2008 R2 computers that I want to bring to everyone’s attention. At this time it has been acknowledged that version 3.1 (which does require Windows Server 2008) returns the following error when attempting to install it onto R2:
"ADMT must be installed on Windows Server 2008"
This issue also occurs with Windows 2008 machines that previously had ADMT installed, and then upgraded to Windows 2008 R2. ADMT will no longer function correctly and returns the same error as detailed above. Microsoft is aware of the issue and diligently working on a resolution. Please stay tuned for further details and updates.
I’d also like to take this opportunity to ask that you send me any future feature suggestions and requests for the tool, as I’ve been asked to present results of the “voice of the customer”. The ADMT development group would like to hear from our customers on how we could make the product better. Please feel free to post comments or email your recommendations and suggestions in what you’d like to see in a later release of ADMT.
PingBack from http://www.windowsaffinity.com/?p=1571
242 Microsoft Team blogs searched, 113 blogs have new articles in the past 7 days. 292 new articles found
Consider the following scenario...
A Univeristy creates their Active Directory way back in the early days of AD and uses a dedicated forest root design (see http://craigchamberlain.com/library/microsoft/dedicated-forest-root.pdf) to create it. In future years it upgrades to Windows 2003 and keeps the same design.
It now has four domain controllers for 2 domains:
rd.contoso.com is the 'root' domain and contains the Enterprise Admins and Schema Admins groups, but no other standard objects such as users or computers.
campus.contoso.com is the main domain that is used for managing all users and computers in the university.
After reviewing the situation the IT team realise that they no longer require the additional security that this design offers and feel that in the current climate they can reduce the number of servers it is required to maintain!
After some research it appears that ADMT may allow them to push all objects from campus.contoso.com to rd.contoso.com, but this would require massive upheaval for the IT community and would require a further step if once the campus.contoso.com was deleted the rd.contoso.com domain was to be renamed.
What the IT team would like to do is use the ADMT to move the 'forest control' from rd.contoso.com to campus.contoso.com and then delete the rd.contoso.com domain, freeing up 2 servers and with minimal impact on the IT community.
There is no other way to do this....is there?
I think the ADMT is ready to be expanded for Enterprise-scale. Many other MSFT tools and products have evolved to scale (Windows itself, SCOM, SCCM, AD ,etc). It seems that ADMT is still a small-scale tool and not really recommended or easy to use for a large scale migration (i.e. multi-domain; multi-forest; multi-continent, etc). I realize that this is a third-party arena for the most part, but I still think there is room for ADMT to 'grow up' a little more.