Domain Controller placement after moving servers from main site to data center hosting facility

We are in the process of planning a move of all of our servers from our in house server room to a Co-Lo data center hosting facility.

Right now, in our main site, we have two 2003 Domain Controllers and they are moving to the hosting facility.

Our main site will be connected to the Hosting Facility by very fast and redundant dark fiber and is supposed to act like a very long Ethernet cable. Our network IP addresses will not change.

There was talk about adding two new DCs in the main site to keep all of the authentication traffic local, but I don't think we'll be able to control that because the network IPs won't change, so I really don't have another Site to put DCs in.

Is there a point to having two domain controllers at the hosting facility and another two domain controllers at the main site?

Thanks for your input and thoughts.
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.

Or at least one DC on your main site.

There is a reason for this, if your connection between the Co-Located Site and your main site is servered, your clients will not be able to authenticate to the domain.  Not to mention access they will loose to other services, DNS, DHCP, WINs (if installed), Files, Printers, Shares, Time Services, etc. etc.


Experts Exchange Solution brought to you by

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
TG TranIT guyCommented:
Of course you have DC local to take care of logins and you can do this by tweaking DNS SRV records to point local DC for authentication.  However, you then have to deal with DC replication traffics...

So, if you do have fast fiber connection to the data center, I would suggest leaving DC there and not adding DC locally just yet..  If things become clogged up, you can always add local DC later...
I forgot to mention, your clients can still login to their machines using cached domain credentials.

joshsfinnAuthor Commented:
Thanks for your information.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.