That
is simply a new tree in your forest, pretty basic. It doesn't have to be
disjoint (neither netbios toAD name norAD domain name to machine
domain suffix).
If you
want true admin level security boundaries though, you are talking separate
forests.
My
running recommendation for AD is
Let's say I have adomain called DomainA.com
and now my organization is talking with another organization who would like to
have DomainB.com. Management at both organizations would like "pretty seamless"
access to each other's resources while maintaining their own identities...i.e,
DomainB
: [ActiveDir]
Domains in a Forest
Let's say I have adomain called DomainA.com
and now my organization is talking with another organization who would like to
have DomainB.com. Management at both organizations would like "pretty
seamless" access to each other's resources while m
From: [EMAIL PROTECTED] on behalf of Lou Vega
Sent: Fri 10/24/2003 10:25 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Domains in a Forest
Let's say I have a domain called DomainA.com and now my organization is
talking with another organization who would like to have DomainB.com.
Management
: [ActiveDir] Domains in a Forest
DomainB wants to be separate in what sense? You mean they want their login
to
remain the same? they want their email address to remain the same? Websites?
And what resources are we needing seamless access to? Exchange in the
picture? If so, do they want seamless GAL
