Two Forests and two domains - want to merge into one forest and do

Discussion in 'Server Migration' started by Craig, Mar 24, 2009.

  1. Craig

    Craig Guest

    Currently we have two forests which have a trust setup just so the users in
    Forest B can access the mail server in Forest A, want i want to know is would
    we be able to migrate AD data, objects etc from Forest B into Forest A and
    what would be the best solution to do the migration.

    Forest A - test.local:
    Server1 – Exchange 2007 and DC(2003 64bit)

    Forest B - test_old.local:
    Server1 – file server and dc (2003 32 bit)

    Server2 – database server (2003 64 bit)

    Server3 – old mail server (2000)
     
    Craig, Mar 24, 2009
    #1
    1. Advertisements

  2. Hello Craig,

    Use ADMT for the migration of forest B to A.

    V3:
    http://www.microsoft.com/downloads/...7B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

    http://www.microsoft.com/downloads/...70-3BBB-4B9E-A8BC-01E9F7EF7342&displaylang=en

    V3.1:
    http://www.microsoft.com/downloads/...01-7DCA-413C-A9D2-B42DFB746059&displaylang=en

    http://www.microsoft.com/downloads/...19-1BA5-41CA-B2F3-C11BCB4857AF&displaylang=en

    Try it out on a test sytem before going in the production environment.

    It is not recommended to run Exchange, especially 2007 on a domain controller,
    performance and also security reason. A DC should do it's main task, except
    you have SBS version which is built for that.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Mar 24, 2009
    #2
    1. Advertisements

  3. First, I agree with Meinolf. You do not want Exchange on a DC. Other than
    security, a DC by default disabled write cache on teh controllers to help in
    case of a disaster with the AD database. Exchange needs that to perform
    properly, as well for it;s own databases. And it cannot be enabled on a DC.
    So there's a bit of a conflict there, besides of causing Exchange to slow
    down to a crawl compared to if it is on a non-DC.

    Second, I would install an additional DC. This will give you AD fault
    tolerance. What would happen if one of the DCs were to go down? In many
    cases when I have a customer that cannot afford to purchase an additional
    box for a DC, I would dig up an old desktop or some machine not being used,
    out of the closet, install Windows server on it, and promote it just to have
    an additional DC in case anything were to happen. I then tape a sign to it
    saying DO NOT TOUCH, just in case anyone would want to use it for something
    else. Lucky I did on one of my customers. Their main DC went down. I had
    that desktop setup sitting in an unused desk running as a DC that was now
    the main DC on the network. I cleaned up AD, rebuilt the main machine,
    promoted it, etc, all in 3 hours. Otherwise it would have been a nasty
    recovery to rebuild the only DC that had failed.

    As for the migration, Meinolf provided you with ADMT links, which you want
    to use. In your case, you want to collapse Forest B into an OU on Forest A.
    Use SID History so they can still get to their old resources and mail. For
    mail, after you've migrated the users, I would suggest to use Exmerge to
    merge Forest B's mailboxes to Forest A's Exchange.

    Read over the following links for more info on the Exchange side of it.

    Exchange migration

    Download details: Microsoft Exchange Server Mailbox Merge Wizard ...
    Others who downloaded Microsoft Exchange Server Mailbox Merge Wizard
    (ExMerge) also downloaded: Exchange Server 2003 Service Pack 2; Microsoft
    Exchange Best Practices Analyzer v2.8
    http://www.microsoft.com/downloads/...EC-DCDF-47DC-96DA-1C12D67327D5&displaylang=en

    Microsoft Exchange Mailbox Merge program (Exmerge.exe) information
    The Microsoft Exchange Mailbox Merge Program (Exmerge.exe) enables an
    Exchange Server administrator to extract data from mailboxes on an Exchange
    Server computer and then merge ...
    http://support.microsoft.com/kb/174197

    Upgrading to Exchange 2007, Aug 7, 2007 ... Migration is the scenario in
    which you upgrade to Exchange 2007 by ... When transitioning from Exchange
    Server 2003 to Exchange 2007, ...
    http://technet.microsoft.com/en-us/library/bb124008.aspx

    You Had Me At EHLO... : Exchange 2007 migration overviewExchange 2007
    Move-Mailbox improves on the existing Exchange 2003 logging functionality
    (event .... especially with the use during 2003 to 2007 migration. ...
    http://msexchangeteam.com/archive/2006/10/27/429522.aspx

    You Had Me At EHLO... : Exchange 2007 Cross Org Mailbox MigrationExchange
    Migration Wizard was used to perform this task in Exchange 2003. Exchange
    2007 has incorporated Cross Org migrations into the ...
    http://msexchangeteam.com/archive/2006/11/02/430289.aspx

    Exchange Migration Wizard for Exchange 2007 Migration and Exchange
    ....Migrate from Exchange 5.5 to Exchange 2003 or Exchange 2007. Exchange
    Migration Wizard. Quest Exchange Migration Wizard is an award-winning
    migration and ...
    http://www.quest.com/exchange-migration-wizard/


    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [Microsoft Certified Trainer], Mar 25, 2009
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.