While performing a remote mailbox move to off-board a user from Office 365 to Exchange Server 2013 on-premises you may encounter an error due to a mismatched archive GUID.
Error: MigrationPermanentException: Recipient ’office365bootcamp.net/Staff/People/DirSync/Alan.Reid’ has mismatched archive GUID (00000000-0000-0000-0000-000000000000). Expected value: 77d97d5b-8f61-4fd4-b355-1463525a068f.
In this example a Hybrid configuration has been established and the user Alan Reid is being migrated to the on-premises Exchange 2013 server. Alan is archive-enabled in Office 365.
Using PowerShell connected to Exchange Online and looking at the properties of the cloud mailbox the archive GUID is visible:
PS C:\> get-mailbox alan.reid | fl *archiveguid* ArchiveGuid : 77d97d5b-8f61-4fd4-b355-1463525a068f
For the on-premises object the archive GUID does not match.
[PS] C:\>Get-RemoteMailbox alan.reid | fl *archiveguid* ArchiveGuid : 00000000-0000-0000-0000-000000000000
To resolve the issue and allow Alan’s mailboxes to be moved we can set the on-premises archive GUID to the expected value so that they match.
[PS] C:\>Set-RemoteMailbox alan.reid -ArchiveGuid "77d97d5b-8f61-4fd4-b355-1463525a068f"
Resume the migration batch and it should now proceed without the archive GUID error.
Thanks a bunch, it saved me, after a good hour of searching the web!
I have a different issue. I’m in the middle of a migration to Office 365. We had migrated the archive mailboxes first to O365 some months ago. Now we are migrating primary mailboxes. I have a group of users where a tenant mailbox got inadvertently created before the primary mailbox could be moved to O365. Now the empty tenant mailbox is associated with the archive mailbox, but there is also a primary mailbox on prem. I know how to get rid of the unwanted tenant mailbox, but it will kill the archive with it. I was thinking that maybe I could move the unwanted O365 mailbox back to on-prem to mash up with the real primary mailbox. This would eliminate the primary mailbox in O365, leaving the archive which I still value, and setting me up to complete the migration back to O365. It isn’t that simple though. The tenant mailbox GUID doesn’t match the on-prem GUID.
I don’t think it is possible to change the O365 mailbox GUID to match the on-prem GUID. Is it safe to change the on-prem GUID to match the tenant, or will that destroy the on-prem mailbox?
Is there any other way to recover from this situation where there is an inadvertent mailbox in O365 and a mailbox on prem, but the valuable archive is already in O365?
Why does the GUID go missing or become mismatched ?
Pingback: Work Placement – Day 14 – FD Computer Science – CPD Blog
What about the opposite direction? Onboarding from exchange 2013 set up in hybrid with office 365.
Error: MigrationPermanentException: The archive GUIDs on source ’first last’ and target ’first last’ recipients don’t match. Source archive GUID: 00000000-0000-0000-0000-000000000000, target archive GUID: 5xxxxxxx-0xxx-4xxx-bxxx-fxxxxxxxxxxx. (edited for privacy).
The user was attempted to migrate twice, then we disabled his in place archive, exported it to PST, then are now attempting to migrate just his mailbox with no archive.
I have the same question as you. I am trying to migrate a user from on premises exchange 2013 to Exchange online/office 365 but the user keeps failing. I too disconnected the in-place archive for the user since it seems like it was the issue. I too, exported his archive to .PST and then tried to migrate the user again and got the “has mismatched archive GUID” message I did all the steps in this article except change the GUID as I am not sure the “remoteMailBox” command should be used in this case.
I wonder what command I should use?
Client is seeing the same issue when trying to “onboard” a mailbox from on-prem to o365. Did you ever get a solution?
How do you identify the folks w/ mismatched archive folders? You used to be able to find them in the old portal – originally under Users/Active Users/”Users with errors” filter, but that whole filter was turned off a year or so ago. Then, again under the old portal, you could see the error box if you opened the user’s properties. But I’m not seeing anything in the new portal anywhere that identifies this problem.
So we can’t get ahead of it, we just have to wait for the user to call us….
What about a Mailuser showing archive GUID as Ghost archive
Thanks for the nice article, it helped me to offload the mailbox from o365 when I was stuck with an error of mismatch of guid.
does this work with exchange 2010? I’m getting ‘Set-remotemailbox’ is not recognized as the name of a cmdlet
Yes, the Set-RemoteMailbox cmdlet is available for Exchange 2010.
When moving an Office 365 mailbox with Archive Mailbox back to On-Premise Exchange, is there any special switched need to make both mailboxes move back to Exchange?
Below is the PS command I’m using:
new-moverequest -outbound -RemoteTargetDatabase $TargetDB -RemoteHostName $RemoteHostName -RemoteCredential $Cred -TargetDeliveryDomain $TargetDeliveryDomain -Identity $UserIdentity
Do i need to include switches for the Archive Mailbox and DB?
New-Moverequest is documented here:
In particular, look at the ArchiveTargetDatabase parameter.
Great articles, thank you so much !
Work like a charm …..
Awesome this helped me out, thanks.