Friday, September 13, 2013

Error moving mailbox from Office 365

In a Hybrid Exchange environment (On-Premises and Office 365) one might stumble upon problems moving mailboxes from Office 365 to On-Premises, known as offboarding with the following error message.
Cannot find a recipient that has mailbox GUID <many numbers>
The reason for this error is that the mailbox has been created in Office 365 and lacks the proper attributes in the On-Premises environment. So, connect to Office 365 using PowerShell and run the following command.
Get-Mailbox john.doe@domain | fl ExchangeGuid
Next, verify that the remote mailbox On-Premises is lacking the proper attribute.
Get-RemoteMailbox john.doe@domain | fl ExchangeGuid
You'll notice that the On-Premises attribute are nothing but zeroes. Copy and paste the attribute from Office 365 on to you On-Premisies environment using the following command.
Get-RemoteMailbox john.doe@domain | Set-RemoteMailbox -ExchangeGuid <copied from Office 365>
That's is. Moving the mailbox from Office 365 to you On-Premiese environment should now work just fine. Or will it? If your On-Premises environment is published by Forefront Threat Management Gateway (TMG) 2010 you might also stumble upon the following error in your move request logs.
Relinquishing job because the mailbox is locked
Or the following status of the request.
StalledDueToMailboxLock 
This might by caused by server affinity of the published web farm or it could be as simple as flooding. If you're certain that affinity is working properly you'll have to do some work on your TMG server to fix the flooding issue. Check out the below link for detailed instructions of what to do.
http://support.microsoft.com/kb/2654376/en-us

1 comment:

  1. Hi, Very nice description about Office 365 Migration.
    I like your web blog.Because whenever i come into your web blog
    then i always get the new interesting and important information in your web blog.

    Thank You

    Office 365 Migration

    ReplyDelete