E2K3 to E2K3 Interorganization migration. Just making sure I have my ducks in a row

Posted on 2005-04-20
Last Modified: 2010-08-05
Been very busy and unable to get in and answer any questions of late. I have my own migration to do and I want to make sure I have my ducks in a row.

Current environment:
AD2003 directory with about 400 user accounts
Exchange 2K3 SP1 environment

New environment: (currently empty, this is what it will be like)
AD2003 directory with about 100 user accounts
Exchange 2K3 SP1 environment

A portion of my current company is splitting off into a separate forest/domain and separate Exchange server. I need to migrate about 100 users from the current environment to the new environment. I actually did a 2000 to 2003 interorganization migration last year and now I am pulling about about the same people...

I will be using all of the free Microsoft tools. I plan to use ADMT to migrate the groups and computer accounts on one weekend and move the user accounts and mailboxes over the next weekend.

Can someone lay out a rough procedure and any gotchas that you are aware of. I am happy to spawn extra questions and spliting points up that way. I am under a time crunch and have to build the whole new environment and migrate all the users in about a 3-4 week window and want to make sure I don't miss anything.

Thanks all,

Question by:cjpalmer
    LVL 7

    Accepted Solution


    This is all hypothetical rambling from me, 'kay?

    1)  Assuming you build domain2 under forest1, then want to isolate it..  what's required?  Name changes through machines, DNS, perhaps DHCP and whatnot are non-trivial..  Forest wide (FSMO) roles would seem obvious..  I guess you'd just have to "capture", rather than transfer the FSMO roles..?  

    The migration steps seem nutty to me..  because they're not common.  

    Instead of building a second domain within your forest, then ripping it out..  might it not be easier to build an independant domain/forest for the 100 acct's and migrate them ..  

    ..  avoiding all the "migration" issues for the servers you're allocating to 'em 100..?  

    Do it the other way around -- build the directory -- then use ADMT to populate it..?

    I'd appreciate your results -- once you live through it.

    -- Scott.
    LVL 11

    Author Comment

    I am building a completely separate forest. The intent is that the new domain/forest will have no relation to the old one over the long run. The new domain/forest exists and has exchagne installed as a different organization name. I patching the server to all the latest SPs and HFs. Getting IMF and AntiVirus installed and configured. When that is done, I am going to use ADMT to migrate the groups over. Then the computer accounts with ADMT. Make sure I have all my permissions working ok. Start moving Servers over manually to make sure I minimize effect on the environment. I intend to migrate the SID History as well so that I don't have to re-ACL everything, but I use local groups to assign permissions on the file systems, so I wll be adding the global groups to the local groups.

    Primarily I am looking for any gotchas that I might be foregetting because it has been a year since my last migration...

    LVL 7

    Expert Comment


    I learned migration basics when consolidating 4 NT(v4) domains and 3 Exchange Orgs at 12 physical sites into one 2000 A/D domain.  ~850 arses in chairs.  Ugly stuff, for sure.  About 2.5 years ago.

    Honestly, I remember jack-squat's diddly zippo, as far as details go.  

    Yup, a new forest is the best approach, I agree.

    Without a doubt -- you'll find a few problems.

    If you'd be kind enough to write about whatever you find, I'd appreciate it.


    LVL 11

    Author Comment

    Since I never got any other verification than the above, I will accept your answers SCDAVIS. I did the migration and did all of the above and didn't have any issues other than the normal Public Folders permissions being hosed and some of the NTFS permissions on our File Server being dorked. Nothing that we couldn't fix with a little group reassignment.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Email statistics and Mailbox database quotas You might have an interest in attaining information such as mailbox details, mailbox statistics and mailbox database details from Exchange server. At that point, knowing how to retrieve this information …
    "Migrate" an SMTP relay receive connector to a new server using info from an old server.
    To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    761 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    8 Experts available now in Live!

    Get 1:1 Help Now