Active Directory trust advantage and disadvantage when setting up trust for more than 15 new location ?

Hi people,

I got some question regarding Active Directory trust model and planning for my current company situation.

At the moment I only have one single forest AD domain (let say with the Domain and Forest functionality Windows Server 2003. The main domain controller FSMO role holder is in the Data Center spread across three different VMs running on Windows Server 2008 R2.

Head Office: City A, Location A
Data Center: City A. Location B

Recently, the parent company acquiring some other smaller company in multiple different geographical locations. But this company is running its own Active Directory domain one per city or office like the following:

Office: City A, Location A

Office: City B, Location B

Office: City C, Location C
Office: City X, Location X

So in this case what are the benefits or advantage in creating Active Directory trust for each of the new Company AD above to the main head office ?

If you have any other good suggestion in creating the AD setup than above, please share it here.

Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
MaheshConnect With a Mentor ArchitectCommented:
ADMT works on domain trust In case of inter forest
If you have intra forest migration, trust is already in place

Migration Sequence:

See attached document I have build long back ago for customer as prerequisites for domain migration
Spare your half and hour and go through document
I have mentioned all prerequisites, limitations, migration sequence and so on.

Computers and servers are migrated in same way, only you migrate computer 1st and lastly you migrate servers
Will SzymkowskiConnect With a Mentor Senior Solution ArchitectCommented:
Biggest issue having trusts in place rather than migrating them all to the same domain will be the management side of it. You will need to manage everything independently. For example Group Policies, Maintenance, Monitoring, Backups, etc.

Having them under one domain will make management much easier and it will centralize everything.

You also have to take into consideration for other active directory aware applications like exchange server which will also need to be managed independently.

Senior IT System EngineerIT ProfessionalAuthor Commented:
many Thanks will,

So yes, in this case what's the side effect to the user in the newly acquired company when the Active Directory domain is deleted and the domain is introduced to all of the branch office location ?

because in the current situation, in every branch office, there is one domain controller in each of the building. Consolidating it into the existing domain controller in the Data Center: City A. Location B wouldthat be any side effect ? apart from I need to recreate all of their user account and exchange mailboxes ?
7 new features that'll make your work life better

It’s our mission to create a product that solves the huge challenges you face at work every day. In case you missed it, here are 7 delightful things we've added recently to monday to make it even more awesome.

Will SzymkowskiSenior Solution ArchitectCommented:
You can use the Active Directory Migration Tool to migrate AD objects to your domain. Depending on the latency at the remote offices you could have the users authenticate back to your DC's in the main office.

The only time you really require a DC in a remote location is if you will be using Exchange / slow wan links. Personally if you can afford to have a DC in the location it would be beneficial because if the wan goes down then no one can authenticate.

If you have a DC at each site users will still be able to access local file servers printers etc.

Also depending on how you are going to set up the DC placement you will also need to configure sites and services subnets and links for each site. Even if you have a site with no DC's you will have to associate your IP subnet of the remote site into the AD site you want authentication to take place.

ADMT download

ADMT step by step

Senior IT System EngineerIT ProfessionalAuthor Commented:
wow, I never knew that tool exist to migrate the AD user account from one AD domain to another one.

so Do I still need to create the trust in order to copy / transfer the user account to my domain in a certain OU ?

So in this case the last thing to do for all of the server and workstation is to exit the old AD domain (, reboot and then join the new domain ( after the AD user account is deleted.
How big the acquired companies?

I mean no of users, computers and servers approximately?

Are they using their own email solution?
Senior IT System EngineerIT ProfessionalAuthor Commented:
Mahesh, the company got around 50 users up to 100 in one domain.

Computers around 20 and 5 servers including domain controllers in each of the branch office.

The email is not a problem because I have already deployed terminal server to my domain to access the exchange server.
MaheshConnect With a Mentor ArchitectCommented:
So you mean to say there are 20 computers per company with 100 users and 5 servers including domain controllers?

U can use ADMT, but ADMT cannot not take care of Email solution migration.
U need to grant migrated users new mailbox in your exchange and then restore there original mailbox data in the form of PST

You should setup domain trust with one company at a time, migrate users, computers with ADMT, migrate file servers and after all server migration get finished, decommission domain controller because domain controllers in source domain cannot be migrated, you must decommission it.
Ensure that source and target domain functional level is 2003 minimum

User migration and group migration can be happened over slow WAN link as well and its painless activity, however migration of computers over WAN link will required good network bandwidth.
If you have 2 to 4 Mbps network bandwidth between sites, tool will migrate computers without any issues
However if link speed is not good (1 Mbps or 512 Kbps) probably you should manually migrate computers from source domain to target domain one by one to avoid failures
Because ADMT will push agent on client computers and this agent would migrate computers

Lastly only for 20 computers I would prefer to let authenticate machines over WAN link to my HO location

Probably you can hire AD consultant for migrating one domain to get feel how it works and then you can own other domains
Probably you could setup test lab with TWO forests to play with and do cross forest migration with ADMT to get better understanding and feel
There are lot things involved in ADMT migration right from setting up name resolution, building trust, enabling SID History, maintaining co-existence, migrating groups, users, computers, servers and so on.
Also if exchange server is there in source and target, then it complicate the migration because ADMT cannot migrate Exchange attribute and in that case whole migration process got changed in flavor of MS Exchange
Check below article for more information
Senior IT System EngineerIT ProfessionalAuthor Commented:
Many thanks Mahesh for the detailed explanation.

In this case yes, there is more advantage to do the migration from the smaller company AD domain to the parent company AD domain. So in order to use ADMT the domain must be trusted two ways first so the migration of the User object and also the computer object can be done, is that true ?
NewCompany1\user1 will become ParentCompany\user1 and so on .

What about the server ? Does the domain membership of the server also gets migrated and rebooted automatically as well ?

There is no exchange server in the new company AD domain so no need to worry about the exchange server mailbox migration.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.