Solved

Exchange 2010 to Exchange 2013 Cross Forest Migration

Posted on 2014-03-21
3
1,771 Views
Last Modified: 2014-03-31
We are looking to move the mailboxes from an on-premise Exchange 2010 server hosted at a child company to our Exchange 2013 server using a cross forest migration.

I have setup a two way forest trust and have successfully migrated a couple test mailboxes however I'm encountering a problem.

When I move user1@domain.com to the new exchange server, user1 is not able to email anybody who's mailbox is still waiting to be transferred and visa-versa. In other words, user1@domain.com (now hosted on Exchange 2013) cannot send an email to user2@domain.com (who's mailbox is still waiting to be transferred).

The goal in the near future is to decommission the Exchange 2010 server altogether however for a period, both servers will need to coexist while the mailboxes are being moved.

Is there a way for Exchange 2010 to redirect email that has been sent to a mailbox now hosted on Exchange 2013?
0
Comment
Question by:Adeste
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 9

Expert Comment

by:David Carr
ID: 39945615
Using the EAC from a 2013 Server Add the 2013 CAS or Multi-role server to the Exchange Send Connector(s). Remove the 2010 CAS or Multi-role Server(s) and  Save.
0
 

Author Comment

by:Adeste
ID: 39946079
Thanks for your reply. I've tried to decipher what your suggesting without success.

From what I understand, I need to open the EAC on the 2013 Server and remove the Exchange 2010 server from the send connectors? Is what you mean?

There is only 1 send connector configured currently and that is setup so the Exchange 2013 server will route email directly to the MX record.

I've figured out one issue. I need to use the "prepare-moverequest" script on all mailboxes before User1 is able to email to send messages to users hosted on Exchange 2010.

The only issue left is that users on Exchange 2010 cannot send email to users who have already been moved to Exchange 2013.
0
 
LVL 9

Accepted Solution

by:
David Carr earned 500 total points
ID: 39950782
Sorry if I was not clear. you should only remove the 2010 Server after you have added the 2013 Server. The goal is to have all mail routed using the 2013 Connector. It will get the mail to the older mailboxes.

Do you see the mail from the 2010 users queuing anywhere?
1

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question