S
Steve
Okay, racking my brain over this one on pro's and con's
for both ways.
Question:
Need to create a new domain (production) that will be
housed at a data center. This system is a simple eight
server system (IIS, SQL, DC's - no clients) for web
application.
Would it be better to create this "domain" as a seperate
forest or as a tree in our existing forest?
Currently have a single forest (root domain of
abc.company.com) and it has two child domains
(staging.abc.company.com and development.abc.company.com).
Reason for incorporating into current forest:
Administration
Reason for creating as new forest:
Security (Domain and Entriprise admin group new)
Reliability - what would happen if root domain DC's of
abc.company.com (say our office flooded) failed. If in
own forest no longer issue
Autonomy from rest of company
Thanks in advance
BTW - I'm leaning toward own forest but everything I keep
reading on best practices says there are very few
instances you want to do something like this.
for both ways.
Question:
Need to create a new domain (production) that will be
housed at a data center. This system is a simple eight
server system (IIS, SQL, DC's - no clients) for web
application.
Would it be better to create this "domain" as a seperate
forest or as a tree in our existing forest?
Currently have a single forest (root domain of
abc.company.com) and it has two child domains
(staging.abc.company.com and development.abc.company.com).
Reason for incorporating into current forest:
Administration
Reason for creating as new forest:
Security (Domain and Entriprise admin group new)
Reliability - what would happen if root domain DC's of
abc.company.com (say our office flooded) failed. If in
own forest no longer issue
Autonomy from rest of company
Thanks in advance
BTW - I'm leaning toward own forest but everything I keep
reading on best practices says there are very few
instances you want to do something like this.