RE: [ActiveDir] Moving forest root domains to child domains in another forest

Mon, 05 Sep 2005 14:57:43 -0700

Title: Re: [ActiveDir] Moving forest root domains to child domains in another forest
I (mostly) agree with Roger.  You have a high degree of flexibility with replication control.  And with Windows 2003 forest functional level you get LVR, which obviously helps to reduce the replication overhead.  On the other hand there are some global companies that I know of that do use the replication boundary of domains to reduce bandwidth utilization on slow links.  Fast and cheap WAN connections are not yet widely available in all parts of the world.
 
Tony 
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Seielstad
Sent: Tuesday, 6 September 2005 8:30 a.m.
To: [email protected]
Subject: RE: [ActiveDir] Moving forest root domains to child domains in another forest

Link speed really has nothing to do with the decision to split into separate domains. You've got a LOT of control over replication and really can build a topology that works for just about any WAN design you care to put out there.
 
Keeping in mind that forests are the true security boundary, are you getting any real benefit from moving from 3 forsts to 4 domains?
 

--------
Roger Seielstad
E-mail Geek

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaves, Jan Amcil L.
Sent: Monday, September 05, 2005 5:37 AM
To: [email protected]
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest


Right. Mostly for administrative and exchange consolidation. And to implement a logically consistent naming convention.

The domains are related enough to put into a single forest, but not quite that “intimate” to all fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention slow links connect global sites thus necessitating the split in the domains.

Our objective, just recently revised, is to come up with an empty forest root and three (possibly more) child domains under it. And then build exchange around the forest.


Jan


-----Original Message-----
From: [EMAIL PROTECTED]
To: [email protected]
Sent: Mon Sep 05 16:07:23 2005
Subject: RE: [ActiveDir] Moving forest root domains to child domains in another forest

can you mention some of your reasons WHY you want to merge your three forests in the way you describe?

I certainly understand that you might want to consolidate, but why in the world would you want to go from three single-domain forests to one forest with a root + 2 child domains, leaving you with managing three domains? 

I'd actually vote that this is worse than what you have right now.  If you do consolidate, then I'd suggest you migrate the objects from those two forests directly to the existing root of your third forest, leaving you with a single domain to manage.

/Guido

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Chaves, Jan Amcil L.
Sent: Sonntag, 4. September 2005 03:15
To: [email protected]
Subject: [ActiveDir] Moving forest root domains to child domains in another forest




Hi!  I have a huge task to do.  I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot).  I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.

Is there any way (by hook or by crook) to do this?  Pointers to third-party apps are very much appreciated.


Thanks,

Jan


This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal at Gen-i Limited

Reply via email to