As many organizations are thinking of skipping Exchange 2007 & moving directly to Exchange 2010 from 2003, I thought it is a good time to go through the process. The entire topic will be covered through multi part posts. I will base the entire series on my environment. Details of my network is listed below.
- Domain HEW.LOCAL (How Exchange Works)
- Domain Controller – 2003DC, running Windows 2003 R2 SP2
- Exch 2003 Back End – 2003BE, Exchange 2003 SP2 running on Windows 2003 R2 SP2
- Exch 2003 Front End – 2003FE, Exchange 2003 SP2 running on Windows 2003 R2 SP2
- Exch 2010 CAS&HUB; – CASHUB, Exchange 2010 running on Windows 2008 R2
- Exch 2010 Mailbox – 2010MBX, Exchange 2010 running on Windows 2008 R2
- 2003 OWA URL – mail.howexchangeworks.com/exchange
- 2010 OWA URL – webmail.howexchangeworks.com/owa
In this post, we will discuss the requirements for Exchange 2010 to coexist with 2003 in the same active directory domain. I already have a 2003 domain up and running with Exchange 2003 Front/Back End configuration. I have also installed two member servers with 2008 R2 (CASHUB & 2010MBX). Before we introduce an Exchange 2010 server, the following points have to be checked.
1. The AD forest & domain functional level has to be atleast Windows 2003. Launch AD Domains & Trust, select the domain name, right click & select properties. Make sure the forest & domain functional level reads “Windows 2003” or higher. In my environment, I have both functional level at Windows 2003.
If the functional level is below Windows 2003, raise both forest & domain functional level using the same interface. Right click “AD Domains & Trust” and select “Raise Forest Functional Level” & raise it to Windows 2003 or higher.
To raise domain functional level, right click the domain name and select “Raise Domain Functional Level” & raise it to Windows 2003 or higher.
2. The Global Catalog and Schema Master should be running atleast Windows 2003 SP1 or 2003 R2.
3. The Exchange 2003 Organization should be running in “Native Mode”. To check, launch System Manager & right click the root (Exchange Org name) and select properties. By default, it will be in mixed mode. Click the “change mode” button to change it to native. It is a one way process.
4. Disable link state updates on all Exchange 2003 servers (to make sure that routing loops won’t occur) with a registry edit. Exchange 2010 doesn’t use a link state routing table and don’t support relaying of link state information. If you don’t suppress minor link state updates, routing loops may occur. Follow the technet article for the registry edit. The first routing group connector is created when the first 2010 Hub server role is installed in the Exchange 2003 organization. The registry edit forces earlier versions of Exchange to use least cost routing and not to calculate an alternative route.
As a final step, use the Exchange 2010 Pre-Deployment Analyzer to make sure that your environment is ready to have an Exchange 2010 deployment.
In the next part, I will discuss the pre-requisites for Exchange 2010 & installation steps for introducing your first 2010 server to the 2003 organisation. Stay tuned!