Forum Discussion
Exchange 2016 Mailbox Migration - Couldn't find a move request that corresponds to the specified id
Hello everyone, In our environment, we have 4 Domain Controllers in DC, 2 Domain Controllers in DR, and exchange server 2016 with stretched DAG (2 MBX in DC and 2 MBX in DR site). When i try ...
rizkafauzanul
Could you please run the command
Get-migrationuser -identity mailbox@domain.ext | Get-MigrationUserStatistics | FL
Before completing the request?
This should give you more details on why the move request was completed with errors.
Could you please run the command
Get-migrationuser -identity mailbox@domain.ext | Get-MigrationUserStatistics | FL
Before completing the request?
This should give you more details on why the move request was completed with errors.
- I have exactly the same issue during expansion and migration of our Exchange 2016 cluster.
Today i logged a ticket with Microsoft support. I'll hope to get a reply soon.
I did use the command below, but it says {} after skipped items.
Get-migrationuser -identity mailbox@domain.ext | Get-MigrationUserStatistics | FLI am a little less concerend now. What i did was:
- Removed the pending “move request” for a user with this error.
- Re-created a new migration for the same user.
- Guess what? The output is exactly the same, that means that there really are no items skipped for real.
