Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Quick help on AD design

$
0
0

Hi there,

I have experience with LDAP/OD, and windows server, but finally setting up my first AD!  Looking for a little bit of help on design.  Here's the scoop.

-  three offices in three different cities in the US, all on 250mbit fibre, S2S over IPSec

- 50 or so people in each office

- will be using vmware to virtualize server 2k12 in a redundant environment with each controller on another esxi host.

- we use office 365, but don't care too much about tying it together

- we typically use a prefix on our suffix for each office to name client computers and servers in each office, our current DNS is setup like that.  (serverone.chi.domain.com, serverone.sea.domain.com, anotherserver.nyc.domain.com, etc.)

-  we plan on ditching bind dns and using windows dns of course.

- we also collaborate on projects cross office, so we need to make sure authentication will work across offices

I've found conflicting info on parent and child domains and wanted to get a little clarity.  I read that you should be careful about using a parent domain that matches the name of your website as it can cause some issues.  I've also seen someone recommend that you should setup each child domain as it's own dc in each office.  My thoughts are that we should have two dc's in each office for redundancy.  I want the setup to be as simple as possible, I know how bad things can get with broken directory services!

Any help on design would be MUCH appreciated.  thanks!



Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>