Company Acquisition Active Directory and Exchange Design

Posted on 2014-07-16
Last Modified: 2014-09-05
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 internal domain.

Another option is to create a new subdomain, call it, and have it under 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.
Question by:fireguy1125
    1 Comment
    LVL 24

    Accepted Solution

    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

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Set OWA language and time zone in Exchange for individuals, all users or per database.
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    729 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

    21 Experts available now in Live!

    Get 1:1 Help Now