In part one of this series, we discussed the AD/Exchange requirements for 2003-2010 coexistence. In this part, we will look at preparing the Active Directory, Exchange 2010 pre-requisites and introduction of the first 2010 server into 2003 org.
There are two options for extending the AD schema & preparing AD to accept an Exchange 2010 Server.
- Easiest and my recommendation is to let Exchange 2010 setup extend the schema & prepare the AD/Domain. Run the 2010 setup and as part of the install, all preparation works will be completed. This is ideal for a single domain environment or small company.
- Do all the preparation works manually using Setup.com switches. We go down this route in large companies where an Exchange Administrator doesn’t have Enterprise Admin and Schema Admin rights. Hence, the task has to be passed to the AD Administrator.
Run the following commands as part of the manual preparation.
- Setup.com /PrepareLegacyExchangePermissions, if you have previous versions of Exchange already installed. This is required to have RUS & Email Address Policies coexist in the same AD domain.
- Setup.com /PrepareSchema, extends the schema with 2010 classes and attributes.
- Setup.com /PrepareAD, prepares the AD, upgrades the Exchange Organisation, creates a new Administrative Group.
- Setup.com /PrepareDomain, prepares the domain, creates Exchange 2010 universal security groups.
Now that the active directory has been prepared to accept Exchange 2010, we need to think about the 2010 specific requirements. The following are the pre-requisites for Exchange 2010.
- The base operating system that will run Exchange 2010 has to be either Windows 2008 SP2 or 2008 R2.
- Make sure that the server is fully patched.
- Install .Net Framework 3.5 with SP1 (Already in 2008 R2)
- Install Powershell 2.0 (Already in 2008 R2)
- Install Office Filter Pack on Hub & Mailbox servers.
- The startup mode of NetTcpPortSharing service has to be set to automatic (For CAS role). Run Set-Service NetTcpPortSharing –StartupType Automatic from the Powershell or set the startup type to automatic from the Services Console (services.msc).
The order of introducing 2010 server into the 2003 Org is CAS, HUB, UM, MAILBOX, EDGE. Certain components like IIS, RPC Proxy, Admin tools etc need to be installed before we start the 2010 setup. For that, launch Powershell and run Import-Module ServerManager.
Run the following command for each role.
For CAS Role:
For HUB Role:
For Mailbox Role:
In our environment, we will be installing CAS & HUB roles on the 2008 R2 server named CASHUB. I won’t go through the installation steps one by one, as everyone is familiar with the process. Launch Setup from the DVD and follow the wizard with a custom installation option to install CAS & HUB roles.
Configure the “CAS External Domain” when asked during the setup. Enter the domain name for external client access as webmail.theucguy.net (2010 OWA URL in my example). The only difference here from a standard 2010 installation is the addition of one more option in the setup, when the HUB server is introduced into 2003 org. The setup asks for a 2003 server to be selected to create a routing group connector.
I selected the 2003FE as the bridgehead server for routing.
Proceed with the setup and finish the installation. You now have a 2003 Org with a 2003 Frontend, 2003 Backend & 2010 CAS&HUB; combined server.
In the next part of the article, I will explain the changes in 2003 Org after the introduction of 2010 server, installation of 2010 Mailbox server & testing of email flow between 2003 & 2010.