Complaints are coming in when users log in to their mailboxes Outlook does not connect and in OWA they receive an error : Your mailbox is being moved.
Removing ( if still there ) the move-requests does not help, even not through ADSIedit.
You think propably moving these mailboxes to another mailbox database again would solve the problem. But you cannot trigger a new move-request for these mailboxes since you receive warnings like this :
Warning: Failed to reset the target mailbox after the move.
Error details: MapiExceptionCorruptData: Unable to set properties on object. (hr=0x8004011b, ec=-2147221221)
Error: MapiExceptionCallFailed: Unable to read mailbox signature basic info. (hr=0x80004005, ec=2631)
The solution is to start the move-request as follows :
Get-mailbox -Organization “TenantName” -Identity “MailboxToBeMoved” | New-MoveRequest -TargetDatabase DB1 -BatchName Batch1 -MRSServer “CASServerName” -DoNotPreserveMailboxSignature -Priority High
There will be no switching between CAS servers when peforming the move-request. The move request will completly handeled by the given CAS server.
-DonNotPreserveMailboxSignature : This one is the real solution. Where MailboxSignature is not the lokal Outlook signature you use at the end of an email. This parameter is responsible ( Exchange 2010 ) for the fact , that the user will not notice the mailbox move. Otherwhise the users needs to close Outlook and reconnect. ( This is what will happen when you use the move-request above )
We noticed this behaviour after we have rolled up to 2010 SP3 RU14 .2 Likes