Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Sub Domain and Site Replication
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.
Asked:
-
2
- +1
2 Solutions
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.
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.
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 Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
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).