Office 365
- Active Directory, Exchange 2007, Exchange 2010, Exchange Management Shell, Exchange Online, Exchange Tools, Microsoft Exchange, Office 365
Error due to mismatch of GUID: Recipient “NameOfRecipient” has mismatched Archive GUID
You receive the error “Recipient “NameOfRecipient” has mismatched Archive GUID” when you try and off board a mailbox from Exchange Online to on premises Exchange. Follow the below steps o resolve the issue and migrate the mailbox back to the on premises Exchange environment: Logon to Exchange Online using Powershell. Run: get-mailbox user | fl *archiveguid* Make a note of the GUID Open Exchange Management Shell on premises Run: Get-RemoteMailbox User | fl *archiveguid* You should see that the GUID on prem is different to the GUID from Exchange Online To resolve, in Exchange Management Shell on prem run: Set-RemoteMailbox User -ArchiveGuid “GUID you got from Exchange Online” The above should work without…
-
Newly migrated mailbox to Office 365 does not receive new e-mail
We had an interesting issue where user’s mailbox was migrated to Office 365 but he could not see any new mail in the mailbox. Even sending himself mail did not show the new e-mail items. We sent a few test mails and tracked the mail from on premises Exchange to Office 365 which showed that the mail delivered to the cloud. We then traced the mail items from within the Office 365 admin portal and confirmed that the mails delivered to the mailbox but we could still not see the items. Thinking that it might be desktop related we asked the user to logon to Outlook Web App and we…
-
Moving an on premise mailbox to Office 365 gives the error “Transient error StoragePermanentException has occurred. The system will retry (6/640).”
One of my colleagues battled to migrate an on premise Exchange 2010 mailbox to Office 365. After trying to repair the mailbox and numerous other things he still received the below error: Transient error StoragePermanentException has occurred. The system will retry (6/640). Eventually he appended the -SkipMoving:FolderRestrictions to the New-MoveRequest cmdlet and managed to migrate the user’s mailbox to Office 365.