<img height="1" width="1" src="https://www.facebook.com/tr?id=1529264867168163&amp;ev=PageView &amp;noscript=1">

Exchange Migration Guide 2010 - Part 2


In Part 1 of the Exchange 2010 Migration Guide, we discussed new features, discontinued features, Exchange Server Role Concepts, and Exchange Server 2010 Editions.  Part 2 of the guide will provide basic knowledge about the installation of Exchange Server 2010 with co-existence of Exchange 2003, how to move mailboxes, public folders, OAB, creation of a connector in Exchange Server 2010 and how to decommission the Exchange 2003 server from one organization.

This is purely lab environment testing designed to give a basic idea of how to do a transition from Exchange 2003 to Exchange 2010.

My Current Setup:
I have 2 domains: (1) Happy Domain (2) Smile Domain
In Happy Domain I have 2 computers
Computer-1: E2K3 (computer name) : this is DC\GC, DNS and plus it is having Exchange 2003 Server installed with mailboxes, DL & Public Folders.
IP address:

Computer-2: Edge (computer name) : This computer is kept in the dmz network which is possessing two nic card, one for happy domain and another for smile domain.
1st nic card : & 2nd nic card :
Smile Domain:

In Smile Domain I have only 1 computer

Ex2k3 (computer name) : this is DC\GC, DNS and plus it is having Exchange 2003 Server installed with mailboxes, DL & Public Folders for smile domain.

Both Happy and Smile Domain are able to send and receive e-mail as I have created an SMTP connector. I won’t discuss how to setup the Mail Flow between two Exchange 2003 server organizations, if you would like to know about the setup for the Mail Flow please refer to http://exchangeserverinfo.com

How to Setup Mail Flow between two different Forests in a Lab using VMWare

Created Users, DL, Security Group and Public folders in Exchange 2003 of happy.com

Overview of upgrade steps from Exchange 2003 to Exchange 2010

  • Upgrade the Exchange 2003 with SP2 (if your exchange server 2003 does not have sp2)
  • Deploy the Exchange Server 2010 in the following series:
    • Client Access Server Role
    • Hub Transport Server Role
    • Unified Messaging Server Role
    • Mailbox Server Role
    • Edge Transport Server (During Any Phase)
  • Configure legacy host name for front-end server and CAS role
  • Move the internet host name to CAS 2010
  • SMTP end point to Hub 2010
  • PBX/GW pointers for voicemail to UM 2010
  • Move the mailboxes to Exchange Server 2010 Mailbox Server Role

Installation of Exchange Server 2010

Installation of Exchange Server 2010 is very similar to Exchange Server 2007. Whenever we are thinking of an Exchange 2010/Exchange 2007 installation there are two major places where we need to focus – the first one is Active Directory Preparation and the second one is Local Server Preparation.

Before the installation of Exchange Server 2010, it is very important to develop a proper plan.  In order to do that, use the following tools:

  1. Cost Savings Calculator
  2. Deployment Assistant Tool
  3. Planning for Active Directory
  4. Planning for Mailbox Server Role

Active Directory Preparation for Exchange 2010:

  • Schema Master: Schema Master should be one of the following:
    • Windows Server 2003 Standard or Enterprise Edition with Service Pack 1 (SP1) or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 Standard or Enterprise Edition or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 R2 Standard or Edition
  • Global Catalog Server : Schema Master should be one of the following:
    • Windows Server 2003 Standard or Enterprise Edition with Service Pack 1 (SP1) or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 Standard or Enterprise Edition or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 R2 Standard or Edition.
  • Domain Controller :
    • Windows Server 2003 Standard or Enterprise Edition with Service Pack 1 (SP1) or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 Standard or Enterprise Edition or later. This can be either 32-bit or 64-bit.
    • Windows Server 2008 R2 Standard or Edition
  • Active Directory Forest: Active Directory Forest must be at least Windows Server 2003 functional level.

Co-existence of Exchange Server 2010 will be supported in one of the following:

  • Exchange 2003 with Service Pack2: Exchange 2003 should be in native mode only.
  • Exchange Server 2007 with Service Pack2: Note - When you install Exchange 2007 Service Pack2 it will extend the schema for Exchange Server 2010 level as well. So whenever you are deploying Exchange Server 2010 at that time you don’t need to extend the schema once again.

Note: Current Scenario – We have Exchange 2003 with SP2

Exchange Server Preparation:

  • Hardware :
    • Processor: Intel 64-bit Processor\ AMD64 Processor.
    • Page File Size : The page file size minimum and maximum must be set to physical RAM plus 10 MB
    • Memory: Depends upon the actual requirement, minimum 2 GB plus 2\3.5\4 MB per mailbox and can be support up to 64 GB.
    • Disk Space: 1.2 GB free for the drive where we are installing the Exchange, 500 MB more space if we are installing UM, 200 MB free on the system drive and 500 MB free space for Transport Server role
    • Drive: DVD-ROM or Network Access.
  • Hardware Virtualization:
    Microsoft supports Exchange 2010 in production on hardware virtualization software only when all the following conditions are true:
    The hardware virtualization software is running:
    • Windows Server 2008 with Hyper-V technology
    • Windows Server 2008 R2 with Hyper-V technology
    • Microsoft Hyper-V Server 2008
    • Microsoft Hyper-V Server 2008 R2

Any third-party hypervisor can be utilized that has been validated under the Windows Server Virtualization Validation Program.

  • Mailbox server memory recommendations :

User Type

Mailbox Server Memory Recommendation


2 GB plus 2 Mb per Mailbox


2 GB plus 3.5 Mb per Mailbox


2 GB plus 4 Mb per Mailbox


  • Operating System: Windows Server 2008 Standard or Enterprise with SP2 or R2 Edition or just to install the console Vista with latest SP is supported.
  • Other Software Requirement: there may be other software required depending upon which roles you are installing. Exchange2010 Prerequisites:

My requirement is very simple, clean installation of Exchange 2010 on windows server 2008 R2 where I will install all the Exchange Server roles except Edge Transport Server Role & Unified Server Role.

As I said earlier this Exchange server is going to part of an existing Exchange organization, so in order to welcome this new server I need to run the following commands:
Ø setup /PrepareLegacyExchangePermissions
Ø setup /PrepareSchema
Ø Setup /PrepareAD

  1. Setup /PrepareLegacyExchangePermissions:
    This is the first command you will run when you are going to bring Exchange Server 2010 into the Exchange 2003 Organization. The reason we need to run this command is to ensure that Recipient Update Service for Exchange 2003 will function properly.
    Note: This command needs to be run on the domain where you have run /domainprep
  2. Setup /PrepareSchema:
    This is the second command which needs to be run after preparelegacy.  It will import the LDIF file to update the schema with Exchange 2010 attributes.
  3. Setup /PrepareAD:
    PrepareAD is the third command line which needs to run. It will accomplish the following tasks before the actual installation of Exchange Server 2010:
    Ø It will create Microsoft Exchange Security Group
    Ø It will create Microsoft Exchange Container under Configuration Partition
    Ø Assignment of proper permission for Microsoft Exchange Container under Configuration Partition.
    Note: I have made my domain as Windows 2003 Functional Level and Exchange 2003 as native mode.

Once you execute the entire command above, run exbpa tool and select Exchange Server 2010 readiness. Ensure that it is showing a green signal. And if you have more than one routing group then suppress the link state information.
Note: Link State Suppression is not enabled by default. Before introducing Exchange Server 2010 into existing topology, the 'SuppressStateChanges' configuration parameter should be set to '1' on server e2k3.happy.com. This parameter is essential if you plan to create multiple connectors to the dedicated Exchange 2007 routing group.
Reason: In earlier versions of Exchange, when a target server was unreachable, the down connector state was propagated throughout the Exchange organization by link state updates, and an alternative route was calculated. In Exchange 2007, when a message can't be relayed directly to the target server because of network problems, no alternative route is calculated. The message queues on a Hub Transport server in the closest reachable site to the point of failure. The purpose of this procedure is to make sure that routing loops cannot occur. So that’s why we need to set it to value 1 in the registry.

In order to set the registry, follow these steps:
1. Open Registry Editor.
2. Locate HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters.
3. Right-click Parameters and select New | DWORD value. Name the new DWORD value SuppressStateChanges.
4. Double-click SuppressStateChanges.
5. In the Value data field, enter 1.
6. Close Registry Editor and then restart the Simple Mail Transfer Protocol (SMTP) service, the Microsoft Exchange Routing Engine service, and the Microsoft Exchange MTA Stacks services for the change to take effect.
Note: You have to do this on each Exchange 2000\2003 server if you have more than one routing group connector.
Now before we execute the above 3 commands we need to ensure that we have .Net Framework 3.5 & Windows PowerShell 2.0 if you are installing Exchange Server 2010 on Windows Server Sp2. Since we are using Windows Server 2008 R2 this prerequisite is already met.  All we need to do is install the .net framework 3.5 sp1 via feature.
If you are using Windows Server 2008 with SP2 then you need to download the .net framework 3.5: click here

Setup.com /preparelegacyexchangepermssions:

Part2 1 resized 600

Setup.com /PrepareSchema:
PrepareSchema needs to be run if you Exchange Server 2003 with SP2 or Exchange Server 2007 or Exchange Server 2007 with SP1. If you have Exchange Server 2007 with SP2 you don’t need to run prepareschema, because Exchange Server 2007 SP2 has already extended the schema.
Figure 2:

Part2 2 resized 600

Setup.com /prepareAD

Part2 3 resized 600

Server Specification Requirements for All roles are:

Ø .NET Framework 3.5
Ø RSAT-ADDS" : These components are required for RBAC remoting on all server roles except Edge
Ø Web-Server : IIS
Ø Web-Basic-Auth
Ø Web-Windows-Auth
Ø Web-Metabase
Ø Web-Net-Ext
Ø Web-Lgcy-Mgmt-Console
Ø WAS-Process-Model
Ø RSAT-Clustering
Ø RSAT-Web-Server

Client Access server role prerequisites
Ø Web-Digest-Auth
Ø Web-Dyn-Compression
Ø NET-HTTP-Activation
Ø RPC-over-HTTP-proxy

Edge server role prerequisites

Unified Messaging server role prerequisites
Ø Desktop-Experience
Ø ServerManagerConfiguration

When Microsoft released Exchange Server 2007 it was difficult to ensure that all the server-level prerequisites were met because  each task needed to be done one by one.  Now in Exchange Server 2010 it is not a requirement to create our own script or batch file. In order to complete the prerequisite we need to call one answerable xml file which is called as Exchange-All.xml, Exchange-typical.xml and each role prerequisite from the command prompt and the command which needs to executed is ServerManagerCmd -ip Exchange-typical.xml

Figure 4:

Part2 4 resized 600

Two other prerequisites need to be considered before the installation:

  1. Set Net.Tcp Port Service Automatic
  2. Install 2007 Office system converter.

Once we meet the above prerequisites, we are ready to install the Exchange Server 2010 without any issues.
The very first screen of the setup is introduction screen, click on NEXT

Part2 5 resized 600

Then EULA, Select I Accept and click on NEXT

Part2 6 resized 600

Then Error Reporting, if it is a production environment would recommend to select “YES” and if it is a lab environment it is optional:

Part2 7 resized 600

Then after the error reporting, Installation Type:
Select as per your requirement, as it is my lab environment I selected Typical

Part2 8 resized 600

Then configuring the Client Access Server external domain:
This is the place where you will define the access of CAS from Exchange ActiveSync, Outlook Anywhere and OWA from outside the domain.

Part2 9 resized 600

After this “Mail Flow Settings”:
Need to set the bridgehead server for the Mail Flow.

Part2 10 resized 600

Customer Experience Improvement Program (Optional):

Part2 11 resized 600

Then it will do a readiness check:

Part2 12 resized 600

Note: In the above figure, we are being informed that if we are using Outlook 2003 we need to replicate free/busy folder to Exchange Server 2010 because Outlook 2003 free busy information will be provided by system folder i.e. free/busy data which is  inside the Public folder database. For Outlook 2007 and Outlook 2010, it doesn’t require relying on free/busy folder as it will be updated by Users Mailbox.

Once you click on Install, it will install all the respective roles. Now let me show you the legacy exchange mailboxes.

Part2 13 resized 600

If you see the above figure there is a difference between the mailboxes which I marked, Discovery search mailbox is the one which is created in Exchange Server 2010 and rest of the mailboxes are still lying there in Exchange Server 2010

Or else if you want to know the status of the mailbox from the PowerShell you can run this following command: get-mailbox | fl alias recipienttypedetails

This article guided you through the steps necessary to begin the installation of Exchange 2010 and the roadmap for implementing a smooth transition from Exchange 2003.

In our next article, we will discuss the steps necessary for moving mailboxes, public folder replication, and system folders.  Check back for Part 3 of the series or even better just subscribe by email to the blog and you will receive articles as soon as they are published.