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

Haha good point, Phil :)


Thanks,

Jan


-----Original Message-----
From: [EMAIL PROTECTED]
To: [email protected]
Sent: Sun Sep 04 23:49:58 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest

You could build clusters in your city and ship them out to the remote location, or use something like HP's remote insight board to build the machines remotely.

Or if you're looking for the Airline reward miles you could make a trip around the world ;)

Phil


On 9/4/05, Chaves, Jan Amcil L. <[EMAIL PROTECTED]> wrote:


        Commissioning new servers shouldn't be a problem. My worry is consolidating the Exchange enviromnents during the domain migration.
       
        The largest of the three domains spans 3 cities, each with a clustered Exchange 2003 server, with each server cluster in a different Exchange administative group.
       
        I guess no 3rd party app can move an Exchange cluster accross forests and organizations at the same time :)
       
        So I really have to literally take a trip around the globe, rebuilding servers and clusters as I go. This is going to be a long trip..
       
        Jan
       
       
        -----Original Message-----
        From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
        To: [email protected]
        Sent: Sun Sep 04 15:41:29 2005
        Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
       
        Well, I wouldn't say ample hardware is required, but you will need to have some servers available to setup the new environment. A pretty typical approach is to use a few servers to setup an initial environment then as you free old servers up through the migration you rebuild them into the new environment to support additional resources. How many servers you need to start off with would depend on the size of your environment.
       
        Setting up a whole new environment would be nice though :)
       
        Phil
       
       
        On 9/4/05, Brian Desmond < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:
       
                You'd be well off to bite the bullet and buy the Quest stuff. It will be able to take care of most of this in a moderately painless (much opposed to not very paineless writing scripts and such by hand). You'll need ample hardware to duplicate everything you have in the new setup.
       
               
       
                Thanks,
                Brian Desmond
       
                [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
       
               
       
                c - 312.731.3132
       
               
       
               
       
                ________________________________
       
                        From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]>  [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] On Behalf Of Phil Renouf
                Sent: Saturday, September 03, 2005 9:47 PM
                To: [email protected] <mailto:[email protected]>  <mailto:[email protected]>
                Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
       
               
       
                Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
       
                               
       
                That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
       
               
       
                That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
       
               
       
                http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx <http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx>  < http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx <http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx> >
       
               
       
                Phil
              
               
       
                On 9/3/05, Chaves, Jan Amcil L. < [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > wrote:
       
               
       
                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
       
               
       
              
       


Reply via email to