Then Michael said it all. The only real reason to separate domains or forests are Security boundaries. All other separations can be done by OU's.
Jon On Thu, Dec 3, 2009 at 10:53 AM, Fogarty, Richard R CTR USA USASOC < [email protected]> wrote: > Right. I should've mentioned that. In our case, we're speaking > specifically about Win2003. We have little plans to upgrade to 2008 in the > near future. As such, we really don't have a need to separate the security > boundaries - ie, no need for a different password policy etc. > > -----Original Message----- > From: Jon Harris [mailto:[email protected]] > Sent: Thursday, December 03, 2009 10:26 AM > To: NT System Admin Issues > Subject: [AKO Warning - Message fails DKIM verification] Re: Windows Child > Domain > > Not that I can give you a real answer but that would depend on which Server > OS you are using and the functional levels. There have been a number of > changes between 2003 and 2008 that have changed this answer. > > Jon > > > On Thu, Dec 3, 2009 at 10:19 AM, Fogarty, Richard R CTR USA USASOC > <[email protected]> wrote: > > > Can anyone explain to me when one would / should use a Child domain > as opposed to setting up a new domain/forest? > > > Rick > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
