i have an urgent issue with mailbox migrations from another forest to our forest.
Please can you help me out ?
All mailboxes now in Forest-A on a EXCH Server 2016.
The company was bought.
Now we have to migrate all mailboxes to Forest-B to EXCH2013 Server.
I have tried this with a cross forest migration with the script .\PrepareMoveRequest.ps1
But it is not working, see the error here:
More Infos:
The Two-Way Trust is established.
The MRSProxies are enabled on both EXCH-Servers.
The Endpoint is created on the Target-EXCH-Server.
The Script ( PrepareMoveRequest ) works but the Migration with ECP GUI not.
Please help me out this is really urgent.
ExchangeActive DirectoryWindows 10AzureWindows Server 2016
Last Comment
Mahesh
8/22/2022 - Mon
Mahesh
From error it seems that there is network / access related issues
You need to ensure that Any-Any network communication is allowed between below
source 2016 MBX server - Target Exchange 2013 CAS and MBX servers
Source 2016 MBX server - Target DC servers
Target exchange CAS and MBX servers - Source DC servers
You should have organization management group membership account credentials in source and target + local admin rights on respective exchange server
Shabarinath TR
Hello,
Not sure if thats a supported option since you are trying for a cross forest migration from Exchange 2016 to Exchange 2013.
In Exchange 2016, you can move an Exchange 2010, Exchange 2013, or Exchange 2016 mailbox from a source Exchange forest to a target Exchange 2016 forest. If there's at least one Exchange 2016 Mailbox server in the target forest, the forest is considered an Exchange 2016 forest.
In Exchange 2019, you can move an Exchange 2013, Exchange 2016, or Exchange 2019 mailbox from a source Exchange forest to a target Exchange 2019 forest. If there's at least one Exchange 2019 Mailbox server in the target forest, the forest is considered an Exchange 2019 forest.
I dont have experience on Cross forest mailbox migration, but from what I could read out - You have to introduce at least one exchange 2016 on the target exchange organization.
Good luck.
Shaba
Mahesh
Its supported, he is not migrating in same forest, he's migrating from one forest to another
Thanks for your link and I did this many times.
But I still get the same error. What can be the problem ?
Mahesh
I realize that Shabarinath is correct.
If you look at MS documentation, even with cross forest you can migrate from lower to upper version but not in reverse direction
You need to look at 3rd party tools I believe, they will make it possible
You need to ensure that Any-Any network communication is allowed between below
source 2016 MBX server - Target Exchange 2013 CAS and MBX servers
Source 2016 MBX server - Target DC servers
Target exchange CAS and MBX servers - Source DC servers
You should have organization management group membership account credentials in source and target + local admin rights on respective exchange server