Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Child Domain Migration to Parent Domain

Hello Respected Members,

Our Company is planning to move on single Forest and Single Domain Migration

Now we have Single Forest and Multiple Domain on Multiple Sites


ROOT-DC.techtunes.lan               1st Forest ROOT Domain

Sites :

Cambridge Site


Oxford Sites


Karachi Sites


Now we are planning to move our all child domains on root-dc.techtunes.lan then we will create separate OU for each site and also placed Global Catalog Server on each site for backup purpose

I have Read Some thing that Active Directory Migration Tool v3.2 is an important tool to migrate our Users

but how should i start to complete this plan ?
what happened with users those are duplicate Example one user abc is in cambridge site and also in karachi site what happened when we move both child on Single Domain any Conflict ?

What about other Service Like DHCP,DNS because we want to run dhcp locally on on our site ?

if any one knows good plan step by step pls comment it

  • 4
  • 3
1 Solution
Krzysztof PytkoActive Directory EngineerCommented:
First of all, you need to ensure that domains are within the same forest. If so, then you don't have to worry (trust between domains is set up by default). If not, you need to configure forest trust to be able to start migration.

User objects must be unique in a forest, so you cannot have two the same accounts. When conflict is detected by ADMT, you are informed about that and you can allow to add some suffux to user or break migration and rename account in source domain.

DHCP and DNS are not problematic. When you migrate DHCP servers then they will be authenticated in parent AD and still will be isuuing IP leases.

The only one action, you need to do, is to create Subnets for those locations in parent domain in Active Directory Sites and Services and assign them appropriately. Create new Site links to replicate AD data (DNS will be included if zones are AD Integrated).

Everything would be fine. I would recommend to read ADMT guide, first before you start migration process. It's available at

infoplateformAuthor Commented:

We already have subnet objects defined for each site

and we do not want to migrate  atleast DHCP Server on ROOT DC

Yes DNS Zone is Active Directory Integrated

Krzysztof PytkoActive Directory EngineerCommented:
OK, so that's good. Just leave DHCP servers in their location and define scope(s) there or use DHCP Relay Agent to redirect DHCP broadcast from their location to DHCP server in parent domain. Relay Agent required RRaS in those locations to be able to catch DHCP broadcast and send it to appropriate DHCP server

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

infoplateformAuthor Commented:
Can Some one help me regarding ADMT V3.2 ?
Krzysztof PytkoActive Directory EngineerCommented:
What do you want to know? WHat kind of help you need?

infoplateformAuthor Commented:
Easy and Simple working steps of ADMT ?
infoplateformAuthor Commented:
No one answers
I am attaching a file describing the step to setup admt migration. You can skip the part about the dns forwarders and building trust relationships as the guide targets inter forest migrations but is also helpful for intra forest migration.

See if this helps.

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

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