Upgrading from Exchange 2007 to Exchange 2010

Posted on 2014-11-14
Last Modified: 2014-12-03
We have an existing Windows 2003 server running Exchange 2007 and a Windows 2003 domain controller.  We have two Windows 2008 servers loaded with all MS updates and would like to perform an upgrade of both the domain controller and the Exchange server to Exchange 2010.  The Exchange server is running out of space and there have been some issues with named properties quota being maxed out so we would like to replace the Exchange server first.  Both servers are on the domain, the new DC being a member server for now, and Exchange 2010 has not been loaded on the other server as of yet.  Ideally, we would like to install Exchange2010 on the new server while keeping the old Exchange server up and running, then move mailboxes at our convenience.  Is there a best practices process to get this done?  Also, do you think we should upgrade the domain controller first or does it matter?
Question by:carilou
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
LVL 33

Expert Comment

ID: 40443859
Exchange 2007 and Exchange 2010 can coexist.  But you will have to upgrade the Active Directory Schema, Forest Configuration and Domain Configuration.  This does not mean that you have to implement a 2008DC.

You can also read more on Exchange 2007/2010 Co-existence here:
and here:

LVL 31

Expert Comment

by:Gareth Gudger
ID: 40445280
Hey Carilou,

Any reason you are not going straight to Exchange 2013?

Author Comment

ID: 40452171
We bought the software 2 years ago.  More of a financial decision than anything.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 40452182
In looking through the articles, it seems that having the 2 Exchange servers coexisting is more work than necessary.  I would like to get any feedback on a clear upgrade path of a 2003 server with Exchange 2007 to a different 2008 R2 server with Exchange 2010 that can be completed over a weekend.  The path of least resistance is what we are looking for, as this is a small organization with 25 mailboxes, many users remoting in through a RDP server and all needing their smart phones accessing email.
LVL 33

Accepted Solution

it_saige earned 500 total points
ID: 40452317
Whether you do it over the weekend or take a staged/staggered approach, you will still have to perform the steps to allow co-existence.  These steps are still needed so that you can employ the migration techniques.


Author Comment

ID: 40452451
Thank you Saige that is good to know.  We also are preparing to move to a new 2008 Domain Controller (currently our DC is a 2003 server).  Would you suggest we perform the domain controller move first, before we bring the new exchange server into the mix?
LVL 33

Expert Comment

ID: 40452531
According to the Exchange Server Supportability Matrix;

Exchange 2007 SP3 RU13 or later, is supported in environments where the AD Controller(s) are all running Windows Server 2003 SP1 (or later) with a minimum domain functional level of Windows Server 2003 and a maximum domain functional level of Windows Server 2012; and a minimum forest functional level of Windows Server 2003 and a maximum forest functional level of Windows Server 2012.

Exchange 2010 SP2, is supported in environments where the AD Controller(s) are all running a minumum of Windows Server 2003 SP2 with no Windows Server 2012 R2 servers; with a domain and forest functional level that is constrained by the same supported levels as Exchange 2007.

Exchange 2010 SP3 RU5 or later, has the same requirements of Exchange SP2 with the exception that it is supported in environments with Windows Server 2012 R2 servers; and has no constraints with regards to the domain and forest functional levels as long as they are, at a minimum, Windows Server 2003 or higher.

In short, you do not have to add your Windows Server 2008 Active Directory server first, but there would be nothing wrong with doing so.  Just make sure that the functional levels of your Active Directory domain and forest are set properly.


Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
unable to book room mailbox after get moved to Office365 6 46
Exchange 2013 windows CU or windows update first 3 19
Cannot create 365 Migration Endpoint 11 79
exchange 7 22
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
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 …
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

749 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