Solved

Moving Exchange 2003 to Exchange 2010

Posted on 2012-03-28
5
482 Views
Last Modified: 2013-01-21
I am about to begin the process of moving Exchange 2003 to Exchange 2010. I understand that they will exist as separate servers but will work together. Can someone give a little more detail to this? How exactly do the work together during this transition? For example, if I enter a setting incorrectly or have to shutdown the server for maintenance for a day will it effect anything? Will the external access or OWA be affected?
0
Comment
Question by:aando
5 Comments
 
LVL 3

Accepted Solution

by:
y4utech earned 0 total points
ID: 37779464
First you need to install Exchange 2010 in existing exchange organization. Once you installed Exchange 2010 successfully then need to move the database & other required setting from Exchange 2003 to 2010. Once you configured the all required changes on Exchange 2010 then shutdown the Exchange 2003 server for some days to check the dependency. If you not found any dependency on Exchange 2003 server & found everything ok then you can uninstalled exchange 2003 from exchange organization.

Use the attached file for transition from Exchange 2003 to Exchange 2010.
Rapid-transition-guide-from-Exch.pdf
0
 
LVL 5

Assisted Solution

by:Guyver-it
Guyver-it earned 250 total points
ID: 37779480
Hi,

Firstly moving or migrating from Excgange 2003 to 2010 is a major task but can be easily achieved if done properly. I would suggest re-creating your environment virtually (VMWare, HyperV etc..,) to pre-empt problems that may arise as a result in moving to 2010.

Things to consider:

Ensure you have recent valid backup of your existing Exchange server including mailboxes and system state (AD, Schema master etc...)

Ensure you have completed all pre-reqs of Exchange 2010 before even running the set up exe.

Exchange 2010 will automatically upgrade your existing Active Directory Schema as part of the install process, once this is complete you cannot go back without risking corruption of the AD database.

Both Exchange 2003 and 2010 can co-exist on different servers. Exchange 2010 will automatically pickup the structure. You will notice when using Exchange 2010 console that there are a number of changes to its layout - read up on these.

Whilst in this co-existive state, Exchange 2003 is still your native version so any maintenance you intend to do on this server will affect the operation of email to users unless you migrate the mailboxes accross to the Exchange 2010 server.

You need to bear in mind that any email relate DNS entries made originally will need to be changed when you are ready to migrate for instance the Autodiscover service.

The OWA url will also need to be considered. If you have not already consider changing it to something like: mail.yourdomain.com.

Here are some useful guides to digest and are very recommended.
http://technet.microsoft.com/en-us/library/bb124008%28EXCHG.140%29.aspx
http://www.networkworld.com/community/node/47632

Hope you will find my tips above useful.
0
 
LVL 38

Assisted Solution

by:Adam Brown
Adam Brown earned 250 total points
ID: 37779502
Generally the way coexistence works is when a user connects to the 2010 CAS server and their mailbox is mounted on the 2003 server, they are forwarded to the Exchange 2003 server for access. Essentially the Exchange 2003 server will operate as normal, but the Exchange 2010 system will more or less coordinate and control the user interaction with the system. This is why you have to stand up (at a minimum) an Exchange 2010 CAS server before bringing a hub/mailbox server online (More often, though, you just bring up an entire Exchange 2010 server, since it's perfectly okay to have all three roles on one server).

The interaction between Exchange 2010 and 2003 is handled with a Legacy.domain.com DNS record for the Exchange 2003 server. You move all your mail.domain.com and autodiscover.domain.com DNS records to point to the new server (or just switch your port forwards) and the Exchange 2010 server will handle mail flow and user access, redirecting users to legacy.domain.com if their mailbox is on the 2003 server. If the 2003 server goes down for some reason, users with mailboxes on that server will no longer have access to their mailboxes and their incoming mail will stop, but users on the 2010 mailbox server will still have access and mail. If the 2010 server goes down, the same will happen to those users, but users on the 2003 server will still be able to access their mail from the legacy.domain.com URLs.
0
 

Author Comment

by:aando
ID: 37781662
Thanks

Just to be clear, until I make the changes to my DNS or port forwards, my new Exchange 2010 install will have no effect on my current Exchange 2003 server or mail flow?
0
 
LVL 38

Expert Comment

by:Adam Brown
ID: 37784630
Sorry. Yes, until you make port forwards to Exchange 2010, you'll see no difference in the way things work. However, if you move any mailboxes to the Exchange 2010 system, those users will only be able to access their mailbox through the Exchange 2010 CAS server. Exchange 2003 doesn't forward users to newer mail systems.
0

Featured Post

Want to promote your upcoming event?

Attending an event? Speaking at a conference? Or exhibiting at a tradeshow? Easily inform your contacts by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
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…

747 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

12 Experts available now in Live!

Get 1:1 Help Now