We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Solved
Sub Domain and Site Replication
Posted on 2013-11-13
I have a corporate AD domain running on 2008 servers, for this question it is called X.com.
I also have an engineering group at a separate site, we are creating a separate network for them and want to add them as eng.x.com, they are running 2012
So, adding the subdomain to my AD should be easy, but since they are at another lcation, I am going to need to do Site replication and a bridgehead server, correct?
I have read up on doing the site replication and bridgehead server and how it works. But, I have a few questions.
1-I will need to setup an permanent VPN tunnel up between the 2 sites correct?
2-I am assuming that I have the right idea here.
3-When I setup the new controller on the new network, I don't have to be connected to the Corporate network?
Any other suggestions/information you can provide would be extremely helplful.
I also have an engineering group at a separate site, we are creating a separate network for them and want to add them as eng.x.com, they are running 2012
So, adding the subdomain to my AD should be easy, but since they are at another lcation, I am going to need to do Site replication and a bridgehead server, correct?
I have read up on doing the site replication and bridgehead server and how it works. But, I have a few questions.
1-I will need to setup an permanent VPN tunnel up between the 2 sites correct?
2-I am assuming that I have the right idea here.
3-When I setup the new controller on the new network, I don't have to be connected to the Corporate network?
Any other suggestions/information you can provide would be extremely helplful.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
- +1
5 Comments
1) It is recommended to use a VPN rather than adjusting firewalls on both ends to allow all necessary network traffic, though the true requirement is simply network connectivity.
2) To know whether you have the right idea or not, you'll need to identify why you're creating this subdomain. Why do you feel you need a subdomain? How much of the infrastructure will be different than what you have? For example, you seem to have a 2008 domain and forest, do you have a requirement for engineering to have a higher functional level and a reason not to raise the level of the forest/primary domain? Unless you have some compelling reason for creating this child domain, I'd personally go for just creating another site and breaking them and their devices off onto a separate OU for group policy management.
3) You have to have connectivity to the root domain, yes. In order to create a child domain in a domain, the DC in the child domain has to be able to verify and communicate with the parent domain. You will need to create a AD site that resembles this new site for replication reasons (it's not a LAN link, so replication intervals will likely be spread out more).
2) To know whether you have the right idea or not, you'll need to identify why you're creating this subdomain. Why do you feel you need a subdomain? How much of the infrastructure will be different than what you have? For example, you seem to have a 2008 domain and forest, do you have a requirement for engineering to have a higher functional level and a reason not to raise the level of the forest/primary domain? Unless you have some compelling reason for creating this child domain, I'd personally go for just creating another site and breaking them and their devices off onto a separate OU for group policy management.
3) You have to have connectivity to the root domain, yes. In order to create a child domain in a domain, the DC in the child domain has to be able to verify and communicate with the parent domain. You will need to create a AD site that resembles this new site for replication reasons (it's not a LAN link, so replication intervals will likely be spread out more).
One best practice is to try and limit the number of domains, is there a reason you are going with a child domain in this situation.Avoid having a multi-domain forest In pre-Windows Server 2008-based AD, creating multiple domains would typically be necessary to accomodate different password policies - but, with the introduction of Fine Grained Password Policy in Windows 2008 DFL, this is no longer the case.
Instead of creating child domain you can promote the server in remote site as additional DC(ADC).You can create seperate OU for remote users and computer and apply the policies as per requirement.You can also delegate admin related permission to remote site admin user as per requirement.
Determining the Number of Domains Required
http://technet.microsoft.com/en-us/library/cc732201(WS.10).aspx
Domain controllers # Determining the number of domain controllers you need
http://technet.microsoft.com/en-us/library/cc759623(v=WS.10).aspx
In general it is recommended that at least two DCs in a domain for high availablity and fault tolerance, but how many DCs at each site will depend on your requirement. Normally one DC at each site can serve thousands of users with regard to authentication.
Yes,there should be connectivity between the sites continuosly and VPN is the way to go.In either case child domain or ADC you need to have site connectivity to main office.
Instead of creating child domain you can promote the server in remote site as additional DC(ADC).You can create seperate OU for remote users and computer and apply the policies as per requirement.You can also delegate admin related permission to remote site admin user as per requirement.
Determining the Number of Domains Required
http://technet.microsoft.com/en-us/library/cc732201(WS.10).aspx
Domain controllers # Determining the number of domain controllers you need
http://technet.microsoft.com/en-us/library/cc759623(v=WS.10).aspx
In general it is recommended that at least two DCs in a domain for high availablity and fault tolerance, but how many DCs at each site will depend on your requirement. Normally one DC at each site can serve thousands of users with regard to authentication.
Yes,there should be connectivity between the sites continuosly and VPN is the way to go.In either case child domain or ADC you need to have site connectivity to main office.
Active today
Sandeshdubey, brings up a very good point. You really should limit the number of domains you create unless it is absolutely necessary. You should only create a new domain if there is a requirement for the sub-domain to govern themselves. Although for true separate to control in high security environments is to create a separate forest since it is possible of a sub-domain admin to elevate there rights to be an enterprise admin.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP, Windows Server…
- Ransomware
- Experts Exchange
- Windows XP
- Windows OS
- Windows Server 2008
- Windows Server 2003, Security
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility.
Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
Suggested Courses
Course of the Month6 days, left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.