This blog post is a part of a 5 post series consisting of:
Exchange Hybrid Migrations: More Than Just a Pretty Face (Part 1)
Digging Into Hybrid Migration Move Report Data (Part 2)
Troublesho...
Updated Aug 13, 2021
Version 8.0
Blog Post
Hello,
I'm currently moving a lot of mailboxes to Exchange online , big project to move 65 TB for around 14000 users and shared mailboxes
During a migration of 1300 users , migration done with 9 migration batches .... 8 TB to move
All migration was done after 3 days . then on the 4th day, we swa a lot of errors in the migrationuser status
ErrorSummary : An error caused a change in the current set of domain controllers. --> An error caused a change in the current set of domain controllers.
All associated move request were fine ... status synced
We start again the start again the migration user with the following command
Get-MigrationUser -BatchId O365Mig4-March1-1 -Status failed -ResultSize unlimited | Start-MigrationUser
Then after a few minutes, all migration user were ok at synced level to be finalized on Saturday
Why is the issue of different status between migrationuser and moverequest status ?
IS a issue on our side or on MIcrosoft side ?
I raised anyway a call with Mcirosoft premier support as I want to have a clear expalnation on this topics
Thanks