We help IT Professionals succeed at work.

Bulk migration not working ADMT 3.2

iamdieter
iamdieter asked
on
Using ADMT 3.2 to migrate objects from 2008 to 2012 domain. The application worked well at the beginning but of late we can only migrate 4 or 5 objects and then get an error. At times it will examine an object but not copy with no error. The object is then not migrated at all.

Any idea what the problem could be?
Screenshot-2020-02-20-at-20.43.18.png
Comment
Watch Question

Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Any related info in Event Viewer?

I'd try to migrate groups and users separately.

Author

Commented:
Nothing in Event Viewer. We do separate user from group migrations.
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
we can only migrate 4 or 5 objects and then get an error.
Which object is failing to migrate? What error do you get?

https://social.technet.microsoft.com/Forums/windowsserver/en-US/51b3886c-5261-45a9-a11c-63fc480b0ec3/admt-group-migration?forum=winserverMigration
It is recommended to perform the migration in the following order:
Domain Global Group
Domain Local Group
User Account
Computer Account

Also, please do not migrate the associated group members when migrating the group.

Group migration:
Copy group members - not checked              
Fix membership of group - checked  
ID history - checked

User migration:
Migrate associated user groups - not checked
Fix users'' group memberships - checked
SID history - checked

Author

Commented:
We are definitely doing the following:
Copy group members - not checked              
Fix membership of group - checked  
ID history - checked

Logfile and screenshot attached.
Log.rtf
Screenshot-2020-02-21-at-20.02.07.png
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:

have you tried with fresh accounts?

from error log it looks like ADMT is failing to contact either source domain controller or target domain controller


Check if ADMT is able to connect to both side DCs without any issues and its not trying to connect to unreachable DC, probably put ADMT server in same segment as domain controller

Author

Commented:
ADMT is installed on my target domain DC. I can get to both DC's from both domains as per the screenshots
Screenshot-2020-02-22-at-07.57.36.png
Screenshot-2020-02-22-at-07.57.10.png
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Sorry, I am out of the office at weekends... So just a few links to check out.

Exchange server related issue (if you have one on source server and not on target server):
https://social.technet.microsoft.com/Forums/en-US/866e1ee4-1115-49a9-89ac-3c621df7dbd0/cross-forest-migration-with-admt-error?forum=winserverDS
https://samigoncu.wordpress.com/2012/02/08/wrn17561-admt-could-not-migrate-some-properties-for-this-object-type-user-due-to-schema-mismatches/

Please check these links related to DNS and ADMT:
Configure a DNS Server to Use Forwarders
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754941(v=ws.11)?redirectedfrom=MSDN
Important information about setting up DNS for ADMT
https://social.technet.microsoft.com/Forums/windows/en-US/179ffa68-95a7-4dfe-8832-a57c92383f35/admt-will-not-migrate-sidhistory?forum=winserverDS

If nothing above helps you, I would start from scratch. I really like this AMDT series... From preparing Acive Directory to migration itself.
https://blog.thesysadmins.co.uk/admt-series-1-preparing-active-directory.html
I set up the ADMT tool on different DC's and that did the trick