Remote Support Software

Provide instant remote support to customers and employees:

Click here for a free trial

AD migration issue

Hi All,
I'm working on a migration from 2008 AD ( a.com ) to 2008R2 AD ( b.com )
when I try to migrate a member file server ( windows 2003 ) from a.com to b.com, the server can not reboot automatically, and it can't be renamed.
I'm using the ADMT 3.2. 2-way external trust between 2 domain. Here attached the err log. Any advice would be appreciated!
======================
ERR3:7075 Failed to change domain affiliation, hr=800704f1 The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.
I update a hotfix according below dump, and I can migrate it without computer name changed. but another err occurs during ADMT using a include file to rename host name in batch. T_T

http://blogs.technet.com/b/askds/archive/2009/10/19/admt-rodc-s-and-error-800704f1.aspx


ERR3:7075 Failed to change domain affiliation, hr=800706fb The security database on the server does not have a computer account for this workstation trust relationship.
=====================

Need to support users over the internet? click here try our remote control online beta






June 14th, 2012 7:28am
I would have ask here.

http://social.technet.microsoft.com/Forums/en-US/winserverMigration/threads



Thanks

Need to support users over the internet? click here try our remote control online beta






June 16th, 2012 11:22pm
I would have ask here.

http://social.technet.microsoft.com/Forums/en-US/winserverMigration/threads



Thanks

There is an amazing pack of free network admin tools. click here to download it






June 16th, 2012 11:30pm
Hello,
please see the article from Santhosh

http://portal.sivarajan.com/2010/10/admt-err37075-failed-to-change-domain.html
Also see

http://support.microsoft.com/kb/929493
and

http://support.microsoft.com/kb/942564Best
regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog:
http://msmvps.com/blogs/mweber/


Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Need to support users over the internet? click here try our remote control online beta






June 17th, 2012 10:21am
MYousufAli & Meinolf,
thanks for your adv.
I've found the root cause for the err, it's the wrong structure of my CSV to be imported by ADMT.
but I still failed to rename the win7 clients automatically.
anyway, I will post in (
http://social.technet.microsoft.com/Forums/en-US/winserverMigration/threads
) later.

Need to support users over the internet? click here try our remote control online beta






June 17th, 2012 6:30pm
MYousufAli & Meinolf,
thanks for your adv.
I've found the root cause for the err, it's the wrong structure of my CSV to be imported by ADMT.
but I still failed to rename the win7 clients automatically.
anyway, I will post in (
http://social.technet.microsoft.com/Forums/en-US/winserverMigration/threads
) later.

There is an amazing pack of free network admin tools. click here to download it






June 17th, 2012 6:37pm
ADMT performs the rename of the computer by write the new name to the registry:
HKLM\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName
The problem may occur when the domain join operation does not read the registry to obtain the computer name. Instead, the computer name is obtained from cache. This mismatch in computer names generates the 7050 error.
To work-around the issue, either rename the computer BEFORE or AFTER the ADMT migration.
Regards,
MiyaMiya Yao
TechNet Community Support

Need to support users over the internet? click here try our remote control online beta






June 17th, 2012 11:56pm
ADMT performs the rename of the computer by write the new name to the registry:
HKLM\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName
The problem may occur when the domain join operation does not read the registry to obtain the computer name. Instead, the computer name is obtained from cache. This mismatch in computer names generates the 7050 error.
To work-around the issue, either rename the computer BEFORE or AFTER the ADMT migration.
Regards,
MiyaMiya Yao
TechNet Community Support

Need to support users over the internet? click here try our remote control online beta






June 18th, 2012 12:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics