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 successfully, 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 in a syncing state. I ran the Get-MigrationUser cmdlet which revealed that the mailbox was indeed "stuck" in a migration with no other issues.
So, you should remove the migration user using the Remove-MigrationUser cmdlet. You need to use the -Force parameter since the move request no longer exists.
This fix the problem and you will be able to move the mailbox and archive successfully. This condition would prevent a mailbox from moving to any other database or Office 365. It's strange that Exchange doesn't detect this when the batch request is created.





Comments

Post a Comment

Popular posts from this blog

Exchange Move Request

-
In practical, there are several ways to monitor the mailbox moves: Using the Exchange Management Shell (EMC) Using the Exchange Management Console (EMS) Using the performance monitor We’ll go through all of the above procedures and define whichever method you prefer as effectively as possible. ➤Exchange Management Shell: There are number of options available.when using the EMS, actually have several cmdlet options to monitor the move requests: Get-MoveRequest Get-MoveRequestStatistics Get-MailboxStatistics ➤Get-MoveRequest: Get-MoveRequest ; by itself, this PowerShell cmdlet will only give you a brief overview of the move requests which are currently active or queued. Without using the | fl command in the pipeline, it will only display: displayname status targetdatabase Which may , in some cases, be enough, particularly if you only want an overview of the move-requests currently active or queued, and you’re not interested in more detailed information...
Read more

Organizational unit blank in Exchange admin center

-
Image
Sometimes we face error " Organizational unit blank" while creating new mail account in ecp .The reason why organizational unit is blank is that ECP web application has a limit of not displaying more than 500 organizational units. Error:       Please follow the below steps to solve the issue: Step 1: PLease check the no of  organizational unit whether it has exceeded the default value 500.                       Command:  ( Get - OrganizationalUnit - ResultSize unlimited ) . count Step 2: If  more than 500 than please delete some OU which is not necessary or redundant.Otherwise,please modify each servers web.config file (Path: \\<server>\c$\Program Files\Microsoft\Exchange Server\V\ClientAccess\ecp\web.config) by adding the following code.   < ! -- allows the OU picker when placing a new mailbox in its des...
Read more

WINDOWS SERVER 2012 “THE USER PROFILE SERVICE SERVICE FAILED THE LOGON. USER PROFILE CANNOT BE LOADED.” WHEN SIGINING INTO A SERVER THROUGH RDP”.

-
Image
Scenario: When trying to log into a 2012, 2012 R2 server, you receive the following error: Error: This info is displayed in the application log (Event 1509). “Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm to location \\?\C:\Users\<username>\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm. This error may be caused by network problems or insufficient security rights.” Solution:  There are two Solution which will be fixer for the above problem. 1. Go to the permissions of the source file and make sure you select the permissions to be inherited from advanced security settings: File Path: C:\Users\<username>\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm. 2. Delete the file.
Read more