MIgrate Active Directory from 2003 to 2008 and Exchange to New forest

Hi Guys

We are running a Windows 2003 Domain with Excahgne 2007.For compliance reasons we need to rename the domain name from xyz.com to abc.com. Now from what I have read is that renaming the domain will not work because we are running Exchange 2007. Can someone please confirm on that?
Secondly what is the best migration approach to a new Windows 2008 forest for Active directory as well as Exchange 2007? We will have to migrate around 400 users and mailboxes and computers. A step by step approach will be really helpful.

Are two way trusts going to solve our authentication problems in the interim for a variety of business applications that we are running. This is because we wont be able to cutover the all the applications on day one to the new 2008 forest.

Thanks in advance for any help.
kararaitAsked:
Who is Participating?
 
ImaCircularSawTechnical LeadCommented:
I've done this once:

(1) Create and configure your new 2008 domain controllers (without DHCP/DNS) and carry out all the configuration you require.
(2) Set up a trust between your two domain and use the user migration tool from MS to migrate all the users across to the new domain.  This is a bit of a tricky step, you need to ensure that both DCs can see each other by host name, use nslookup to check this.  You will probably have to set DNS up on your new domain now and on each domain set the opposite domain's DNS server as an authorised forwarder.
(3) Install Exchange 2007 on your new domain and configure it as it's configured on your old domain.
(4) Using powershell you want to export all the user mailboxes from one server to another:
             http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx

TIP:  Do not run the import/export on one of the exchange server, install outlook and powershell on a desktop in each domain and run it from there.  I had MAJOR issues which were not documented but well known to MS about this one.

(5) Test outbound mail from new server and internally both send/recieve.  When you're happy, change your MX/internal firewall forwarding to your new exchange server and test.
(6) Move continue to configure DNS/DHCP on your new domain.
(7) Move any remaining applications/server.

Make sure you have a backout at each point.  This is not an easy thing to do for the first time so ensuring you have a way out at each step at least gives you some comfort.  Major issues are getting trusts/user migration working, mailbox export/import, dealing with people pretending they're missing email.  I would schedule downtime if you can so people know not to use email over a certain weekend or something.  Remember, any mails that don't get delivered to you will notify the sender and will also tell the sender if their mail system will try resending.

Hope this helps.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.