Migrate to exchange online - NotFoundPermanentException

[Stefan Kießig]

Hello,

I have to migrate users form exchange 2013 to exchange online.

By 3 users I get thies error message

Fehler: RecipientNotFoundPermanentException: Error: Cannot find a recipient that has mailbox GUID ‎'...' .

What cna I do to migrate this 3 users?

Thanks for your help

Stefan

[#2]

Hello @Stefan Kießig ,

This usually happens when there is a mismatch between mailbox GUID of your on-premises exchange mailbox and office 365 mail user.

1. From on-premises exchange powershell run:

get-mailbox -identity user@domain.com | fl *guid*
Take a note of Exchange GUID here.

2. Connect to exchange online powershell and run:

get-mailuser -identity user@domain.com | fl *guid*

Check if the Exchange GUID matches.

IF not try matching it:

set-mailuser -identity user@domain.com -exchangeguid "paste Guid here from on-premises"

IF you are not able to find the mail user in exchange online using get-mailuser, check if office 365 created mailboxes for these users in absence of mailbox GUID from on-premises, in that case  permanently delete these users from office 365 and sync them again, then check if the mailbox guid stamped on mail user again. Make sure the users are not using any other services before deleting them from office 365 though.

Thanks

[#3]

Hallo@harveer singh 

es muss eine Mailbox geben da die GUID in der Fehlermeldung nicht der Mailbox GUID im Exchange 2013 entspricht.

Diese beiden GUIDs müssen für die Syncronisation übereinstimmen.

Get Mailbox im Exchange online zur Mailbox GUID in der Fehlermeldung. Danach ändere ich die Mailbox GUID zu der vom Exchange 2013 Server.

Grüße

Stefan

[#4]

Hey @Stefan Kießig ,

In hybrid setup the mailbox GUID stamped on the mail user in office 365 should match the mailbox GUID of on-premises exchange mailbox.

When you run get-mailuser for these three users, do you get a output?

 Run:

get-mailbox -identity user1@domain.com

If you get an output that would mean that office 365 created mailboxes for these users, if there is already a mailbox created in office 365 for these users, you will have to delete these users from office 365 completely and then sync them again with proper mailbox guid. Make sure there is no data in these mailboxes in office 365 before deleting.

If you don't get an output when you run get-mailbox user1@domain.com then simply run:

set-mailuser -identity user1@domain.com -exchangeguid "paste Guid here from on-premises"

Thanks

[#5]

Hallo@harveer singh 

ich führte dieses in Powershell aus

get-mailbox -Identity user@contoso.de | fl *guid*

get-mailuser -identity user@contoso.de | fl *guid*
set-mailuser -identity user@contoso.de -exchangeguid "guid"

Ergebniss: WARNUNG: Der Befehl wurde erfolgreich abgeschlossen, es wurden jedoch keine Einstellungen von 'User' geändert.

die Exchangeguid ist die gleiche.

get-mailbox -identity user@contoso.de  gab keine Ergebnisse.

Die GUID aus dem Fehler kann ich nicht finden. Sie stimmt mit der Exchangeguid nicht übernein.

Grüße

Stefan

[#6]

Hey @Stefan Kießig ,

Run this command and check to what entity the exchange GUID shown in the error message is related to:

Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value from error' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*

check if the GUID in error is that of a soft deleted mailbox.

Thanks

[#7]

Hallo@harveer singh 

das ist das Resultat:

RecipientType    PrimarySmtpAddress       WhenSoftDeleted
-------------        ------------------              ---------------
MailUser            user@contoso.de

[#8]

All looks good here, is the guid in error message still different from the guid you get when you run get-mailuser? Based on the outputs you shared it appears that both are same. Remove one of the users from the migration batch and try to migrate using powershell, here is a link:
https://www.alitajran.com/move-mailbox-to-exchange-online-with-powershell/

Thanks

[#9]

Hallo@harveer singh,

die GUID kann ich nicht mit get-mailuser finden.

[#10]

Hallo @harveer singh ,

when I run it with powershell it also faild.

[#11]

Hello @Stefan Kießig,

I think we are facing a disconnect due to responses being translated. You can also post your issue at answers.microsoft.com for more personalized support in your language.

Assuming you are performing exchange hybrid migration via office 365 batches, I will try to summarize our conversation:

When you run from powershell connected to exchange online :

1. Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value from error' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*

The response you get is: 

RecipientType PrimarySmtpAddress WhenSoftDeleted
------------- ------------------ ---------------
MailUser user@contoso.de

This output means that the 'ExchangeGUID value from error' is associated with the mail user: user@contoso.de

2. Next, When you run  get-mailuser -identity user@contoso.de | fl *guid* , with the same mail user returned in step 1. You don't see the same exchange GUID ? or there is no ExchangeGUID at all ?

Check if same user is present in soft deleted mail users as well:

get-mailuser -softdeleted

3. Next, on your on-premises exchange powershell  when you run:

get-mailbox -Identity user@contoso.de | fl *guid*

You get an exchange GUID, for example 1234-5678-54321

Now from exchange online powershell run the following command:

Get-Recipient -IncludeSoftDeletedRecipients '1234-5678-54321' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*

Do you get any response from this command ?

There are a few moving parts here, You may also be facing an issue with duplicate users, were these 3 users created in office 365 directly at some point before installing aadconnect ? Please check active users and deleted users for any duplicates as well.

Thanks

[#12]

Hello @harveer singh 

Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value from error' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*

did not yield any results

[#13 · Accepted solution]

Ich habe es gelöst. Indem ich die User aus dem Sync nahm, sie im Azure AD löschte und erneut gesynct hatte.