Exchange 2013 Migration Batch Completes Successfully, But Mailbox is Not Moved
Here's weird one. While a mailbox is moved from Exchange 2013 to Exchange 2016 or in local for a mailbox with an in-place archive. A new migration batch is created for the user and it completes in short order, but the mailbox and archive are not moved. The number of Total, Synced, Failed, and Successful mailboxes for the batch is zero. You get a notification email saying the batch completed success fully, but no mailboxes were moved or synced. When you look at the details of the migration batch in EMS you see that the Validation Warning Count is 1 and the Validation Warnings show, "Error:The user already exists, but the migration batch that includes it couldn't be found. Before you try migrating the user within a batch again, please remove the existing user by running the Remove-MigrationUser cmdlet." A "MigrationUser" object is created for each user who is in the process of being migrated or the migration has not been completed, so it remains...