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.
BufflAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
piattndCommented:
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).
0
 
SandeshdubeySenior Server EngineerCommented:
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.
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
compdigit44Commented:
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.
0
 
BufflAuthor Commented:
I have been convinced that we will do a site and not a sub domain.   Thanks

Now I just have to get the step by steps for setting it up on the 2008 server and 2012 server.
0
 
BufflAuthor Commented:
I was reading up on this on another forum..that it would not be a good idea to have my RRAS server and my DC on the same server?

I have that currently on my 2008 AD server, but from what I read having the RRAS server on the DC in a replication setup could be a problem?
0
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.