Transitioning from Exchange 2007 to Exchange 2010—-Step by Step

Exchange Server 2007 and Exchange Server 2010 are similar in architecture so the transition process is more straightforward. The following procedure illustrates a typical transition from Exchange Server 2007 to Exchange 2010:




clip_image001 Run Dcdiag, Netdiag and check FSMO roles functioning perfect.

clip_image001[1] All domains in an existing Active Directory forest have to be running in native mode.

clip_image001[2] The Active Directory forest has to be running on a Windows Server 2008 forest functionality level.

clip_image001[3] Each site in Active Directory should have at least one PDC, schema master and the Global Catalog server on a Windows Server 2008 SP2 level. It is recommended to have 64-bit type Domain Controllers and Global Catalog Servers for optimal performance preferably Windows Server 2008 x64 SP2 or Windows Server 2008 R2

clip_image001[4] All Exchange Server 2007 servers must have Exchange Service Pack 2 installed.

clip_image001[5] The Internet facing Active Directory sites must be the first sites that will be migrated to Exchange Server 2010.

clip_image001[6] Windows Server 2008 SP2 64 bit or Windows Server 2008 R2.

clip_image001[7] Internet Information Server needs to be installed for CAS.

clip_image001[7]Web Certificates must be installed in server holding CAS

clip_image001[8] Windows Remote Management (WinRM) 2.0

clip_image001[9] PowerShell 2.0 (Windows Server 2008 feature if R2 version)

clip_image001[10] .NET Framework 3.5 (Windows Server 2008 feature)

clip_image001[11] Desktop Experience (Windows Server 2008 feature)

clip_image001[12] Net. TCP Services started and set automatic (services.msc)

clip_image001[13] Disable TCP/IP6 from Registry (if you use tcp/ip4)

clip_image001[14] 2007 Office System Converter

clip_image001[14]Better to Prepare a document showing task list and systems build info. Tick one after one when finishing a task accordingly.


clip_image001[15] Backup Active Directory global Catalog servers, Exchange servers and Servers that interoperate with Exchange Server, such as gateway systems or replicated directory servers. It is also a best practice to turn off any replication to other environments during the transition process, such as Forefront Identity Manager (previously named ILM, MIIS, IIFP, and MMS).

clip_image001[16] Please bear in mind that an in-place upgrade to Exchange Server 2010 in any scenario is NOT supported!

clip_image001[17] Please be aware that Win2k8 AD and Exchange 2010 (HT, MT, CAS, ET Role, Unified Messaging) are based on 64 bit architecture.

Migration from Windows 2003 AD Forest to Windows 2008 AD Forest and Forest Preparation

clip_image001[18] Create user with domain admin, schema admin and enterprise admin role from existing AD

clip_image001[19] Log on using new user name

clip_image001[20] Bring the AD forest and domains to Windows Server 2003 Functional Level

clip_image001[21] Insert Win2k8 Server DVD into Win2k3 DC

clip_image001[22] Use elevated command prompt using domain\username (where user name must be above mentioned) Start Menu>Run type runas /user:domain\username cmd.exe

clip_image001[23] Provide Password

clip_image001[24] d:\sources\adprep\adprep.exe /forestprep where d: is DVD ROM

clip_image001[25] d:\sources\adprep\adprep.exe /domainprep /gpprep

clip_image001[26] d:\Setup and select upgrade option to use existing DC

clip_image001[27] Transfer FSMO Roles for a new Win2k8 DC with new Hardware

clip_image001[28] Make one DC as GC

clip_image001[29] Replicate AD database, GPO or wait tomstone to replicate

clip_image001[30] Retire Windows 2003 DC

clip_image001[31] Run DCPROMO (Uncheck this is last remaining DC)

clip_image001[32] Raise new Domain Functional level to Win2k8

clip_image001[33] Insert Exchange 2010 DVD into DC to upgrade AD

clip_image001[34] Open command prompt and change directory to DVD rom

clip_image001[35] Type /PrepareSchema

clip_image001[36]Type .\Setup /PrepareAD /OrganizationName:organisation_name


Transition Sequencing:

Once you have finished prerequisite, you have to take the installation order of the Exchange Server 2010 servers into account to minimize the impact:

clip_image001[37] Exchange Server 2010 Client Access Server. The Client Access Server can work with an Exchange Server 2007 Mailbox Server as well as an Exchange Server 2010 Mailbox Server.

clip_image001[38] Exchange Server 2010 Hub Transport Server (New Internal and External Connector). Documents all the policies you have in existing HT and apply same in new HT server.

clip_image001[39] Exchange Server 2010 Mailbox Server. After you have installed the Mailbox Server role and established a proper Public Folder replication between Exchange Server 2007 and Exchange Server 2010, you can start moving mailboxes to the new Exchange 2010 Mailbox Server. Of course, the Public Folder replication needs only be configured when Public Folders are used in Exchange Server 2007.

clip_image001[40] The Edge Transport Server can be installed at any time, since an Exchange Server 2010 Edge Transport Server can be subscribed to an Exchange Server 2007 SP2 Hub Transport Server. Use Export and Import option for all policies applied in previous ET server.

clip_image001[41] Finally Unified Messaging


Transitioning from Exchange Server 2007 to Exchange Server 2010

1. Prepare Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010

2. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).

3. Install necessary prerequisites (WWW for CAS server role) including web certificates.

4. Install CAS server role servers and configure per 2010 design. Validate functionality.

5. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.

6. Install Hub Transport role and configure per 2010 design.

7. Transfer inbound and outbound mail connector to the new 2010 HT servers.

8. Install mailbox servers and configure Databases (DAG if needed).

9. Create public folder replicas on Exchange 2010 servers using Exchange 2010 Public Folder tool.

10. Move mailboxes to Exchange 2010 using Move Mailbox Wizard.

11. Re-home the Offline Address Book (OAB) generation server to Exchange Server 2010.

12. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder stores.

13. Delete Public and Private Information Stores from Exchange 2007 servers.

14. Remove Exchange 2007 Edge Transport subscription

15. Uninstall all Exchange 2007 servers.

Test Procedure:

clip_image001[42] Double check Exchange Roles and services are started

clip_image001[43] Check event logs

clip_image001[102] Check internal and external connector

clip_image001[44] Test OWA and Email using test user

clip_image001[45] Run BPA

 clip_image001[45]Verify with the system build info you created at beginning to check what you might have missed out or not!

Key Factors:

The following key factors differentiate a 2007 to 2010 transition from a 2003 to 2010 transition:

clip_image001[46] Exchange admin groups and routing groups are already out of the picture.

clip_image001[47] The Recipient Update Service is no longer part of the transition process.

clip_image001[49] The public folder hierarchy does not need to be re-homed. Indeed, because public Folders are not required for Exchange Server 2007, they might not even be part of the transition.

One added advantage of transition from Exchange Server 2007 to Exchange Server 2010: if Outlook clients are at 2007 levels or above, the move mailbox process does not result in downtime, making the end user transition experience completely transparent.

Further Study

Transition from Exchange 2003 to Exchange 2010 

Watch TechNet Video on Transition from Exchange 2007 to Exchange 2010

21 thoughts on “Transitioning from Exchange 2007 to Exchange 2010—-Step by Step

  1. Hi,

    Thanks for the steps.

    Do the “System Public Folders” of the 2010 need to be added as replica’s to 2007 and their conents manually migrated before removing the public folder db from 2007?

    Kind Regards


  2. Hello Deniz,
    There are few component of system Public folder such as EFORMS REGISTRY, Events Root,Offline Address Book and Schedule+ Free Busy, OWAScratchPad, StoreEvents. These folders are created when you installed Exchange 2007/2010 First Organisation and exchange server use it for itself not visible to user. EFFORMS and Offline Address book useful for legacy mail client and used by Exchange 2007 itself. I reckon, you don’t have legacy mail client. You don’t need to migrate these folders to new exchange 2010 specially don’t modify StoreEvents in exchange 2010. When you migrate public folders, it should automatically create necessary database in it.



  3. 7. Transfer inbound and outbound mail traffic to the 2010 HT servers.

    What did you mean by this? I know there is a send connector for outbound but I tried switching that over and it does not work… Is there anything special that needs to be done to get this send connector working with the new server?


    • Hello Adam,
      My Apology it should be connector. You can do through Exchnage management tools. You have to create new connector thats all. It worked for me, can you explain your situation a bit? Are you using both 2007 and 2010 connector or de-commisioned 2007. I used new connector.


    • Hello Nick,
      Outlook Anywhere:
      Go to Microsoft Exchange\Microsoft Exchange On-Premises\Server
      Configuration\Client Access.
      Select the CAS server that you are enabling Outlook Anywhere on and, in the
      actions pane on the right side, select Enable Outlook Anywhere.
      Define the External host name. This is the name that users will use to connect to the
      Exchange Server. In our example we use

      Similarly configure OWA and ActiveSync (for mobile devices) using Exchange Management console. Check using mail client.
      You may configure additional settings like favourites, public folder in OWA. Its not like mailbox transfer. just pointing new CAS server. I hope, this hint will work.


  4. Hi Raihan,

    This step by step guide will be very useful to me for upgrading our Exchange 2007 messaging infr to Exchange 2010.

    Thanks & Regards,

    Suresh Majagar4


  5. hi,

    my current exchange 2007 server using as owa adress. about the OWA transfer to exchange 2010, what if i wanan use the same address ( in exchange 2010 server?

    many thank
    gee sing


  6. Hi,

    thanks for replied

    which i can ignore the owa address at exchange 2007 and configure same owa address at new exchange 2010? following configure send and receive connector and mailbox migration?

    Thank you,



  7. Hi

    I thought exchange 2010 requires the AD forest & domain functional level to be at least Windows server 2003. In your guide you say that “he Active Directory forest has to be running on a Windows Server 2008 forest functionality level.” Is this correct?

    Thank you


  8. Hello Raihan,

    Thanks for the article, very detailed! I have an issue:

    I am planning a clients migration from exchange 2007 to 2010 and ran into issues as I upgrade the current exchange 2007 servers to SP2.

    Current setup is 2 node single copy cluster + 1 CAS server. Running on Windows 2003 Enterprise SP2, 64Bit. I upgraded the cas to SP2, that went well.

    I then upgraded the passive node, which went well and moved the cluster to it and ran CMS upgrade which completed as well… it shows its running sp2 and is servicing clients/users.

    Now, 2nd host in the cluster, I am not able to upgrade. Would I be able to transition to 2010 if I go ahead with the upgrade using the node which is currently sp2?

    Is it a MUST to upgrade the node which is passive now?

    The hardware and setup for 2010 is ready and standing by so we can start…

    thanks for the help!


    • Please go ahead and install Exchange 2010 on separate server. Make sure you update AD, schema and follow thr steps in exchange server. You can create similar cluster in exchange 2010 using exchange management console. Good Luck


  9. Hello,
    Could you please explain or provide more details about
    “Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers” What do you it mean?


  10. Hi,

    We plan to migrate from Exchange 2007 sp2 «single copy cluster» to Exchange 2010 “Database availability Group”
    Our current messaging platform is composed of two server Hub /cas and two mailbox servers in a Single Copy Cluster

    Our Target platform well be composed of two server Hub /cas in a load balancing “NLB” and two mailbox servers part of a DAG
    Our goal is to live the two-mode environments transitioning then remove the cluster exchange 2007 from Active Directory database

    thank you to tell me the steps to ensure a smooth transitioning.


    • above steps shows how to impliment a single HUB, CAS, MBX server. Adding additional servers into those steps would serve your purpose. I do not have any steps for your specific need. you need to do some home work for that.


  11. I have Exchange 2007 with PF and users. I have created new Exchange 2010 with PF in the same exchange organization, I did not setup PF replica from 2007 to 2010. When I moved test users from 2007 to 2010 they can’t see free busy information users on 2007.
    Please advise what I should do.

    Thank you


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.