- Windows Server 2016
- Exchange
- Windows Server 2019
- Installation
- Active Directory
- Windows 10
- Windows
- Azure
urgent cross forest migration
Hi Experts,
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.
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:
MigrationPermanentException: Error: MapiExceptionCorruptData: Unable to write mailbox info. ‎(hr=0x8004011b, ec=-2147221221)‎ Diagnostic context: Lid: 1607 StoreEc: 0x8004011B Lid: 1494 ---- Remote Context Beg ---- Lid: 36024 StoreEc: 0x8004011B Lid: 59009 StoreEc: 0x8004011B Lid: 53912 StoreEc: 0x8004011B Lid: 1750 ---- Remote Context End ---- Lid: 9954 StoreEc: 0x8004011B
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.
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
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
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
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
Yes , I have checked the permissions, we used the domain admin.
And the user is also member of OrganizationManagement.
Yes I migrate to another forest.
And the user is also member of OrganizationManagement.
Yes I migrate to another forest.
Exchange 2016 CU2 and earlier Exchange 2013 SP1 and later are compatible with windows 2008R2 and 2016
please go through
https://docs.microsoft.com/en-us/exchange/architecture/mailbox-servers/prep-mailboxes-for-cross-forest-moves-in-powershell?view=exchserver-2019
step by step
all the best
please go through
https://docs.microsoft.com/en-us/exchange/architecture/mailbox-servers/prep-mailboxes-for-cross-forest-moves-in-powershell?view=exchserver-2019
step by step
all the best
Hello Sajid,
Thanks for your link and I did this many times.
But I still get the same error. What can be the problem ?
Thanks for your link and I did this many times.
But I still get the same error. What can be the problem ?
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
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
Yes, you do need public certificates at both ends for efficient connectivity and migration even through 3rd party tools
Please, what is the correct manual ?
MRSProxies enabled.
Endpoint created.
Prepare-Moverequest.ps1 started and succeeded.
But Migration batch always fail :-(
MRSProxies enabled.
Endpoint created.
Prepare-Moverequest.ps1 started and succeeded.
But Migration batch always fail :-(
Explore More ContentExplore courses, solutions, and other research materials related to this topic.
-
![]()
received a Solution
raise forest level to 2019 -
![]()
wrote an Article
![]()
This user's on-premises mailbox hasn't been migrated to Exchange Online. The Exchange Online mailbox will be available after migration is completed.
-
![]()
created a Video
![]()
Exchange 2019 - Join Exchange Server created in Azure to your new test lab domain
-
Explore Cloud Class® ![]()
Certification: MCSE Microsoft Certified Systems Engineer - Identity with Windows Server 2016
Premium Content
You need an Expert Office subscription to comment.Start Free Trial