Domain migration with/without Exchange

5 pts.
Domain Forest
Exchange 2010
Microsoft Exchange 2003
Microsoft Exchange 2007
Microsoft Exchange migration
Going to be migrating two separate Windows 2003 AD Forests into a new 2008 AD Forest. One Forest is on Exchange 2003 and one is on Exchange 2007. Would like to move he new domain with Exchange 2010 - but one major application we run will not be supported by Exchange 2010 out of the gate (after discussing with the Vendor). It may be many months after the release of Exchange 2010 before it is offically supported. Which means it could be many months into next year before we could move to Exchange 2010.

Meanwhile the bulk of our users are on Exchange 2003 and we could benefit immediately with an upgrade 2007. One thought is to move forward and migrate to the new domain - but leave the Exchange infrastructures as they are - until we can move to Exchange 2010. The other school of thought is to move forward with the new domain migration and migrate everyone to Exchange 2007. What would be the major caveats of migrating to a new domain but leaving   This is the method I'm proposing.  To me the major caveat of leaving the Exchange environments as is is it greatly complicates the infrastructure - the old domains would need to be intact as well as the maintennance of the new domain. Every migration to a new AD domain I've heard of involves Exchange migrations at the same time. Trying to best justify the move to Exchange 2007 now (and upgrade to 2010 later) and showing the reasons why leaving old Exchange infrastructure intact is not the best idea.

Any thoughts, recommendations, links to similar case studies, etc. that may assist in bolstering our proposal?


Answer Wiki

Thanks. We'll let you know when a new response is added.

My thought on this is it is better to move all to Exchange 2007 rather than leave 2003 in the mix. Exchange 2007 and 2003 communicate differently regarding meetings, free/busy, public folders and account creations etc. It is better to have all on the same version while you await the green light to move to 2010. From my own experience migrating from Exchange 2003 to 2007 the time period where it was mixed was painful for a lot of users and caused a lot of scheduling and calendar headaches until we were all on 2007. OWA is much different as well.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • R vishaal
    hello mate Migrating Domain users & exchange mailboxes are very crucial however you can move your 2003 exch to 2007 exch , dont move to 2010 as its only a beta release there will be bugs and others problems as well... As concern to migrate from 2003 AD to 2008 AD thats very simple , you can try an upgrade of your 2003 server or just created a new domain in 2008 and move the users outta there. thx good day
    355 pointsBadges:
  • Subhendu Sen
    Before migration, mind the following.... Prepare server 2003 forest and domain to 2003 native mode and install dc 2008 in forest. Transfer FSMO roles to new dc 2008, and leave for to replicate with sysvol and migrate server to server 2008 dc by running netsh export data in server 2003 and import data in server 2008.
    141,290 pointsBadges:
  • Genderhayes
    Use the ADMT to migrate users, computers, and groups from one domain to another. This sort of migration is associated with a migration from a Windows NT 4.0 domain to an Active Directory ability to migrate user passwords as well as accounts Run Setup for the Active Directory Mi-gration Tool (available on the Windows Server 2003 CD at \i386\ADMT
    10,730 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: