Skip to main content

Exchange 2016 Migration Batch Completes Successfully, But Mailbox is Not Moved

 Here's weird problem that happens to Exchange admins while they want to move some users to different DB. I'm testing a mailbox move from Exchange 2016 database to different database that hs different mailbox quota . I can create a new migration batch for the user and it completes in short order, but the mailbox is not moved. The number of Total, Synced, Failed, and Successful mailboxes for the batch is zero. I get a notification email saying the batch completed successfully, but no mailboxes were moved or synced.


When I look at the details of the migration batch in EMS I see that the ValidationWarningCount is 1 and the ValidationWarnings 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."


Whoever wrote that error message deserves a raise. MUCH better than the "Error code 2" I'm used to getting.

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. or maybe sometimes completed with no issues, it is better to delete unwanted batches whatever the status is.

So, I removed the migration user using the Remove-MigrationUser cmdlet. I needed to use the -Force parameter since the move request no longer exists

or you can remove the migration batch jobs on ECP, go to recipients and then migration tab yo can see all the batches you can select them and delete them.

This fixed the problem and I was 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.

Labels:

Comments

Post a Comment

Popular posts from this blog

Exchange OWA Error (Something Went Wrong)

Exchange OWA Error (Something Went Wrong) Exchange 2016 Cu8 on Windows Server 2012 R2 gave error on OWA, ECP will work if administrator doesn’t have a mailbox. else even ecp will throw the same error. An unexpected error occurred and your request couldn't be handled. X-ClientId: 15BED63F62FB4FDB809703ED2534C19D request-id 1ac56275-a1ab-48cf-9f82-880c49767a19 X-OWA-Error Microsoft.Exchange.Diagnostics.ExAssertException X-OWA-Version 15.1.1415.4 X-DAGServer COMM X-DAGerver COMM Date:11/07/2018 3:30:06 PM Description: Unable to find the certificate with thumbprint [Thumb code] in the current computer or the certificate is missing private key. The certificate is needed to sign the outgoing token. or invalid or expired ' Microsoft Exchange Server Auth Certificate' Solution: Create new  Microsoft Exchange Server Auth Certificate  1.      Open Exchange admin Center ECP, then go to servers, certificates, find Microsof...
Post a Comment
Read more

CredSSP Encryption Oracle Remediation RDP issue

  CredSSP Encryption Oracle Remediation RDP issue An update released by Microsoft ( KB 4093492 )on  May 8, 2018 , for Windows 10 Operation System was targeted to change the default settings CredSSP from  Vulnerable  to  Mitigated . However, post patching this caused an issue where the patched clients were blocked from communicating with unpatched servers over RDP protocols. This has been reported to cause an error thrown by Windows RDP as below: Solution: Use the group policy settings changes described below to rollback the changes to ‘Vulnerable’ state to allow RDP access. 1. Open Group Policy Editor, by executing  gpedit.msc 2. Policy path:  Computer Configuration -> Administrative Templates -> System -> Credentials Delegation Run  gpedit.msc  and expand  Administrative Templates Expand  System Expand  Credential Delegation Edit  Encryption Oracle Remediation Select  Enabled  and change Production Leve...
Post a Comment
Read more

How to configure E-Mail notification in WSUS

How to configure E-Mail notification in WSUS The WSUS server can be configured to send e-mail notifications of new updates and reports on the status of the WSUS network. Notifications will be sent whenever the WSUS server synchronizes new updates, and status reports can be sent daily or weekly.  Set up e-mail notifications In the WSUS Administration console, click  Options in the left pane. In the center pane, click  E-Mail Notifications . Click the  General If you want update notifications, select the  Send e-mail notification when new updates are synchronized check box. In the  Recipients box, type the e-mail addresses of the people who should receive update notifications. Separate the names with semi-colons. If you want status reports, select the  Send status reports check box. In the  Frequency box, select either  Daily  or  Weekly . In the  Send repo...
Post a Comment
Read more