Solved

Migrate Exchange 2013 to Exchange 2016 between trusted domains

Posted on 2016-11-14
2
27 Views
Last Modified: 2016-11-16
I am standing up a new Exchange 2016 environment.  Current AD has 3 domains.  Domain1, Domain2 and Domain3.  We have a sister company that we have established a Domain Trust with and they have 1 domain (Domain4).  Domain4 has a pre-existing Exchange 2013 environment and I wish to migrate their mailboxes into our Exchange 2016 environment.  Or is the best way to accomplish this to upgrade Domain4's Exchange to 2016?  My concern is how account creation would work?  I know that we can share GALs but where do the mail-enabled AD accounts need to live?  I have not worked with connecting an Exchange server to different forests.  Any input to point me in the right direction would be great.
0
Comment
Question by:SDISupport
2 Comments
 
LVL 41

Expert Comment

by:Amit
Comment Utility
What is your end goal? Keep Domain 4 or?
0
 
LVL 14

Accepted Solution

by:
Schnell Solutions earned 500 total points
Comment Utility
Many times there are businesses that they want to isolate their IT environments, specially if they expect the possibility of separating the companies. Other companies prefer to consolidate the resources, and in that way bring simplicity to the network.

If your company and you vote for simplicity, you can consolidate all your Exchange services in one unique Exchange Organization that serves to both forests. However, it means that you will need to complete a process called 'Exchange cross-over migration', which will consist on moving your mailboxes on Domain4, to your Exchange 2016 in your largest forest.

About the accounts: It is very interesting how it works, it uses a concept called 'Linked Accounts', which consist in creating an Exchange Mailbox in your resource forest (the large forest with three domains), this mailbox will be associated to an disabled account in that forest - Yes, because the idea is that the user is not there. And then the real user that is located in domain 4 will be 'linked' to this mailbox and will access it with its own account. It means that at the end of the consolidation, you will not have Exchange 2013 on the small forest, and the same user accounts will access a mailbox at the other forest pointing to a disabled account there).

From the administrative perspective it will be much easier, and you will not need to deal with GAL synchronization, Availability synchronization, and many more things. Moreover, you can focus your administration on your resource forest and make it more high-available and better, for example)
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

Suggested Solutions

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
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…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

772 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now