Error: The critical property ‘ExchangeGuid’ is missing in the MailUser object

 Assessment

Solution

· Ran the following cmdlet for the affected users: Get-mailuser user@domain.com | FL *guid*

· We can see the exchange guids for all the objects are set to null in the cloud

· Checking the objects on-premise.

· Ran the following cmdlets:

 1. Get-Mailuser user@domain.com | FL *guid*

· We can see the exchange guids on-premise are null as well

· Need to check the object in the Chip Domain where the mailboxes reside and retrieve the exchange guids

· In the Chip domain , we ran: Get-mailbox user@domain |fl *guid*

· We retrieved the exchange guids

· We removed the current mail user objects from the cloud with:

 2. Remove-msoluser -userprincipalname user@domain.com

3. Remove-msoluser -userprincipalname user@domain.com -removeFromRecycleBin

· In the Uconn.edu domain, we ran : Set-mailuser user@domain.com –ExchangeGuid “ExchangeGuid”

· The exchange guids have now been set on the mail-users

· We then ran a delta sync to recreate the mail-user objects in the cloud

· We can now see  the exchange guids populated when running: “Get-Mailuser user@domain.com | FL *guid*”in the cloud

· Resubmitted the migration batch

· Two users failed with the following error: archive mailbox must be enabled before it can be moved

· When checking the on-premise mailbox in the Chip domain for the failed users, we can see there is an archiveGuid present

· When looking at the mailusers in the Uconn.edu domain, the archiveGuid is not present

· We need to set the archive guids on the mailusers in the Uconn.edu domain to match archive guid on mailbox in Chip domain.

· Afterwards, we need to run a sync to synchronize the changes to the cloud.

· Ran the following cmdlets to set the archive guids on-premise : Set-mailuser user@domain.com -ArchiveGuid “ArchiveGuid”

· Ran ADconnect sync

· After sync completed, we can now see the archive guid populated on the mailuser objects in the cloud

· Resubmitted the migration batch

· Mailboxes migration for the user were successfully submitted.