[Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

Company Acquisition Active Directory and Exchange Design

Our company of 500 employees, acquired another company of 500 employees overseas.

Our company as a single forest, single domain, single Exchange 2010 org.

The acquired company, is spread across different countries, each location having its own forest, domain, and Exchange org.

We are planning on the most practical design on how to integrate into our company.

What we do know, is that our company US location, forest, domain, and Exchange org will remain unchanged.

The acquired company will have a new infrastructure built out in one country, and the other locations will be integrated into the new infrastructure.

We are trying to determine if it's best to integrate the overseas company and locations into our single Forest/Single Domain, effectively keeping ourcompany.net internal domain.

Another option is to create a new subdomain, call it UK.ourcompany.net, and have it under ourcompany.net forest.

I'm looking for some pros/cons for each method.  We would ideally want to integrate into single forest/single domain, but if there are items of concern, please mention.

As for Exchange, is it better to maintain a single Exchange organization, or create a 2nd Exchange organization.  We would keep US mailboxes in the US, and overseas mailboxes, overseas.

Overseas network link is redundant 500Mbit over VPN.

Appreciate any links to articles, past experiences and pros/cons and things to look out for for each option.
1 Solution
Mohammed KhawajaCommented:
The important point to remember is Exchange Organizations.  Unless you are willing to get rid of all other Exchange Orgs, you will not be able to put them under a single forest.  The other thing to remember is administration, who administers all these acquired companies as they are overseas.  If the existing IT team for acquired companies stay then they either need to be their forest (not recommended) or their own domain.  At the end of the day, the IT admin could determine as to what it would be.  My feeling is that you will end up with single forest, multiple domains.  In this scenario, you could maintain a single organization for Exchange and still have full decentralized admin.  If IT teams will be merged to one entity then single forest, single domain would be the ideal scenario.

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now