Exchange 2016 Mailbox migration issue. Error 'MAPI provider is not supported for mailbox with version \ Version 15.1 (Build 2308) on server '#servername'

Question

I wan't to move a Exchange 2016 on premise mailbox from a source domain with a Exchange 2016 server to a target domain with a Exchange 2016 server through a powershell script.

The Exchange 2016 server in the source domain is upgrade to the same version and build as the target Exchange 2016 server 'Version 15.1 (Build 2308.0).

First i migrated the account from the mailbox through ADMT.
Then i started the preparation script. The target mailbox is prepared as it should be.

When i start to move the mailbox through powershell script the following error appears : "MAPI provider is not supported for mailbox with version \ Version 15.1 (Build 2308) on server '#servername'"

Does somebody know how to solve this issue or had the same issue . Normally i migrate Exchange 2010 mailboxes to a Exchange 2010 server through the powershell script and everything went well.

Thanks in advance

Answer 1

Have a look at this doc - Move mailboxes between on-premises and Exchange Online organizations in hybrid deployments

I hope this will solve your problem.

Answer 2

@vincent van de kraats

Did you enable the MRS Proxy endpoint on your Exchange server?

For cross-forest moves that are initiated from the target forest (known as a pull move type), you need to enable the MRS Proxy endpoint on Mailbox servers in the source forest. For cross-forest moves that are initiated from the source forest (known as a push move type), you need to enable the MRS Proxy endpoint on Mailbox servers in the target forest.

Then, I would suggest you try to create this migration request from Exchange admin center, it could prevent this exist some error in the command that you used:

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi @vincent van de kraats

Were you able to resolve this problem?
I am also facing the same problem. MRS Proxy endpoint is already enabled. And we are having '.com' domain. However, still no luck.

Can anyone please guide?

Thanks
Tony