Re: Empty Root Domain required?
- From: "Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 11:44:02 -0400
In that case adding an empty root doesn't really do anything for you. There isn't a domain prune/graft capability so you will follow the same migration process to get into the corporate forest with a single domain as you would with an empty root.
In general, you want to stick to a single domain as possible, many MSFT apps are just designed to run that way. It isn't that they won't run in multidomain environments but you will often find half-assed things you have to do or some functionality that just doesn't work right.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Beno wrote:
Hello.
I want to setup a new AD (Win2k3) for my subsidiary company. We are autonomous from the our overseas parent company, and the parent company does not have a "global AD structure" at this point. I was proposing to create an empty root domain in my new local forest, and then have my "production domain" as a child domain off the empty root domain. If, in the future, the parent company created a new global AD that we, as a subsidiary needed to be part of, I thought I could "cross-migrate" my child production domain straight into the parent "global AD forest" off their root domain. Is this a good idea, or is the empty child domain in my local forest simply a waste of resources?
- Prev by Date: Re: Active Directory Fails as LDAP Address Book
- Next by Date: Re: Public DelegatesBL attribute in ADSIedit console
- Previous by thread: Re: Empty Root Domain required?
- Next by thread: Re: Empty Root Domain required?
- Index(es):
Relevant Pages
|