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

Should I do a Child Domain or just a Domain

We have an existing server at one of our branch offices that needs to be joined to the Primary Domain at our main office.  Example:(Main office... - Branch office... we are running VPN between the two.  Should I set the server at the branch office as a child or as a additional domain and please direct me to a good article on how.  This is a Windows Server 2008 environment.  Thanks
3 Solutions
Radhakrishnan RSenior Technical LeadCommented:

I would suggest to add as a child domain. Create a new child domain when you want to create a domain that shares a contiguous namespace with one or more domains. This means that the name of the new domain contains the full name of the parent domain. For example, sales.microsoft.com would be a child domain of microsoft.com. As a best practice, you create new domains as children of the forest root domain.

You can use this procedure http://technet.microsoft.com/en-us/library/cc787706(v=ws.10).aspx.

Hope this helps
Is the branch server a member of a domain already? I don't see why you would want to create a new domain. You should join the Branch server to the existing domain as a member server. How many domain controllers do you have in the main domain? If you have only one, you should have at least two and you should consider making the branch server a domain controller. If you have multiple domain controllers you can consider making the branch server a read only domain controller.

The general Misrosoft recommendation is to have single domain environments.
AmitIT ArchitectCommented:
One Forest and One Domain is the best option here. So answer to your query is add it as additional server. I don't see any use of creating child domain.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

PowerC280Author Commented:
Does anyone have any good step by step on adding a server to a domain as a member?
There is no reason to even consider a 2nd domain for only 2 offices.  This is a very easy configuration.  

1. Build your 2nd server at the 2nd site.
2. Point the DNS for that server at your existing DC across the wire for DNS as a primary, and at itself as the secondary.
3. Install DNS on that server, and the Active Directory role.
4. Make sure your primary DNS at the primary site only points to itself for DNS.
5. Make sure you have the root hints enabled on both DNS servers.
6. Enable the AD role on the server after the reboot.  The enablement will take some time depending on the link speed.  
7. Define 2 separate sites.  
8. Define your 2 subnets, and assign them to the correct sites.  Your DC's should put themselves in the correct sites.

That's really about it.   Do this over the weekend so that your network has time to replicate and 'settle down'.  

Sarang TinguriaSr EngineerCommented:
In your case I would recommend  to add additional domain controller

Refer below link with screenshot for how to add additional domain controller for existing domain

you add the server to the domain the same way you add a workstation.
It is only if you want to share roles that it gets a little more complicated.

you also need to watch out for dhcp and dns between the two sites but really that is another question.
PowerC280Author Commented:
Thanks guys....
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.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

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