i have an exchange server 2003 and windows server 2003 domain controller on a single forest.

i want to implement windows server 2012 and exchange server 2013. and then migrate the mail boxes from windows server 2003 to 2013.

Most recommendation are

1. Double Hop migration - Time consuming

2. PST - Multiple Errors

What i am thinking is to create a separate forest and do a cross forest trust

Question 1. how to i migrate the 2003 domain controller to the new windows server 2012 domain controller?

Question 2. migrating the mailboxes isn't much of a task to 2013 as i will be using a 3rd party software

Worries. Having a second forest and domain worries me, because the client still want to maintain the current forest and domain.

How do i overcome this.

Hi There,

Setting a new forest and manage it will be much harder down the track.

also, Cross forest migration is not simple at all when it comes to permissions and routing messages between forests.

I think your best option is Exchange 2010 and than Exchange 2013.

Cheers,

It seems to be similar as I find on Spiceworks : http://community.spiceworks.com/topic/727090-migrating-window-server-2003-domain-controller-and-exchange-2003-to-2012-and-203?page=1#entry-4170160

There are some good opinions suggested by experts on the mentioned thread. Please check if it helps you.

Exchange 2013 Migration:

Option:1 
Exchange 2003 to 2013 Migration is not possible directly:
First you need upgrade exchange 2003 to 2007/2010 after that from 2010 you can migrate to Exchange 2013 easily.

Option:2
Build new Exchange 2013 (Export/import all dta to your new environment ---> But you will have more issues qith MX repoint domain change etc - not recommended)

Microsoft best recommended option to migrate Exchange 2010 and move to Exchange 2013

i have an exchange server 2003 and windows server 2003 domain controller on a single forest.

i want to implement windows server 2012 and exchange server 2013. and then migrate the mail boxes from windows server 2003 to 2013.

Most recommendation are

1. Double Hop migration - Time consuming

2. PST - Multiple Errors

What i am thinking is to create a separate forest and do a cross forest trust

Question 1. how to i migrate the 2003 domain controller to the new windows server 2012 domain controller?

Question 2. migrating the mailboxes isn't much of a task to 2013 as i will be using a 3rd party software

Worries. Having a second forest and domain worries me, because the client still want to maintain the current forest and domain.

How do i overcome this.

Honestly, standing up a whole separate forest just so you don't have to do a double hop migration is going to create headaches in the long run.  Now you're going to have a whole separate forest just for email?  That doesn't make even the least bit of sense from a management perspective. If I were in your shoes, I would do the doublehop migration.  Sure it's going to take some more time, but I think it's easier to manage in the long run.  As for your questions, please see below:

Question 1. how to i migrate the 2003 domain controller to the new windows server 2012 domain controller?

While this question really is better off being asked in the Directory Services forums, it just so happens to be I have done a few of these along away.  Do you have multiple Domain Controllers? If you do, then I would stand up a brand new Windows 2012R2 server first, join it to the domain, install all the required roles (ADDS, DHCP, and DNS and whatever else this machine needs), don't promote it just yet to a DC.  Demote the old DC and change the IP.  Now give the new  DC the IP of the old DC and promote.  Make sure AD replication is working correctly and you should be good to go (and configure other roles).  This method makes it so you don't have to update every single machine in your environment with the new DNS server.  It also makes sure you don't have to update your DHCP relays with an IP of a DHCP Server.  

If you only have 1 DC, then install the required roles make sure replication does its thing, migrate FSMO Roles, and decomm old DC.  Just make sure you update all the machines in your environmnet with the new DNS Server. 

Question 2. migrating the mailboxes isn't much of a task to 2013 as i will be using a 3rd party software

I'm not really sure what you are asking here, but I tend to move the mailboxes myself.  I figure a 3rd party tool is just doing fancy New-MoveRequests that I can easily script if I need to.

Hi Hello005,

Thank you for your question.

Question 1. how to i migrate the 2003 domain controller to the new windows server 2012 domain controller?

A: we could use ADMT to migrate 2003 domain to 2012 domain, we could refer to the following link:

https://social.technet.microsoft.com/Forums/en-US/bd1b0df5-c96b-420f-8a29-e4fdc934a1a8/using-admt-with-complete-domain-migrationmove-2003-to-2012-r2?forum=winserverMigration

Question 2. migrating the mailboxes isn't much of a task to 2013 as i will be using a 3rd party software?

A: In order to migrate Exchange 2003 to Exchange 2013, firstly, we must migrate Exchange 2003 to Exchange 2007 SP3 or Exchange 2010, then migrate to Exchange 2013, we suggest we could migrate Exchange 2003 to Exchange 2010 then to Exchange 2013. We could refer to the following link:

http://blogs.technet.com/b/mconeill/archive/2013/04/03/migration-from-exchange-2003-to-2013-a-no-go.aspx

If we choose to migrate cross forest, before the mail migrate new domain, we need to migrate AD account to new domain, then the client should be joined the new domain instead of the former domain.

In this case, we recommend to do the following steps to solve this migraate:

1. Migrate AD and DC.

2. Install new Exchange 2010 in the same forest.

3. Migrate Exchange 2003 to 2010

4. Install Exchange 2013.

5. Migrate 2010 to 2013

6. Retired the old servers

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Thanks to everyone who had assisted in answering my questions. Your answer are very appreciated.

I would have preferred the cross forest migration. but the issue with the cross forest migration is that i would need to create a new forest and domain. In my situation, i would like to retain the old domain and forest. if it were possible to have the same forest and domain in a cross forest migration, this would have solved my problem

Anyway i will be migrating to 2010 then to 2013 using the same forest and domain.

Thank you

• Edited by Hello005 7 hours 35 minutes ago