Designing new AD structure


hi there

shortly going creating new business unit, requires seperate ad forest ours, thinking of potential designs ad 2008 structure.

basically, have offices in emea, apac, usa , latam - multiple offices in multiple countries. have 1 exchange org.

of team saying should create:

i) forest root: domain.com
ii) child domains of: emea.domain.com, apac.domain.com, usa.domain.com , latam.domain.com

however, can't see benefit of - why not 1 domain; domain.com, , split continents ou's, , have sub-ou's country etc?

can tell me benefit of having multiple domains? 1 can think of password policy, since set in default domain policy, can't see being issue (unless apac want own password policy emea, say).

with windows server 2008-based fgpp, have way address unique password policy requirements (although that's typically done accommodate exceptions).

in general, approach recommended. start design single domain - unless there compelling reason change (there might non-technical 1 - resulting from unique compliance requirements or internal politics), stick it.

hth
marcin



Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file