Place holder root domain advantage
- From: "Randy Jackson" <jacksors@xxxxxxxxx>
- Date: Tue, 5 Aug 2008 21:36:28 -0400
I've been struggling with a domain design to choose. I've always read that
it is best practice design to create an empty place holder root domain to
hold the enterprise admin group and to hold the forest schema operations
role. Then have another domain to hold all users/groups/computers. The
alternative being one domain, that holds all of the above.
There is obviously additional hardware costs associated with the empty place
holder domain, but there isn't going to be much administrative overhead
since the domain is going to me basically unused.
What are the underlying reasons why the place holder root domain is setup
and should this domain design be favored in a large enterprise organization
vs the single domain model?
Thank you.
.
- Follow-Ups:
- Re: Place holder root domain advantage
- From: Paul Bergson [MVP-DS]
- Re: Place holder root domain advantage
- From: Ace Fekay [MVP Directory Services]
- Re: Place holder root domain advantage
- Prev by Date: Re: Problem running a script
- Next by Date: Re: Problem running a script
- Previous by thread: Script to create multiple groups
- Next by thread: Re: Place holder root domain advantage
- Index(es):