Installing Exchange Server 2010 in Mixed Mode Environment – Part 1

Per the latest news from MS Exchange Team Exchange 2010 is out to manufacturing. With that said, it will be available for the production deployments very soon. In this series of posts I am covering the installation of Exchange 2010 in a mixed mode environment.

Though it can be installed with the legacy version of Exchange there are certain pre-requisites you must fulfil. In this post we are trying to uncover the installation method of Exchange 2010 in an existing Exchange 2003 Organization. So, even before you start installing Exchange 2010 you have to do some preparation on your Exchange 2003 side. Very important and must be understood fact about Exchange 2010 is it can not be installed with any other version of Exchange prior to Exchange Server 2003 SP2. So, if you have an Exchange 2000 Server and planning to transit to Exchange 2010 you must upgrade it to Exchange 2003 SP2 first. Following table illustrates the supportability of co-existence:

Version of Exchange Exchange Organization Co-Existence
Exchange 2000 Not Supported
Exchange 2003 Supported
Exchange 2007 Supported
Exchange 2003 and 2007 together Supported

 

Once you have understood the supportability of the Exchange 2010 setup and you think that you are good to go, you will have to work a little bit on your Exchange 2003 organization first of all. So, this work out will contain raising the AD DFL, AD FFL and Exchange 2003 org functional level.

1. The first step would be raise your AD Forest Functional Level and AD Domain Functional Level to Windows Server 2003 at least. After changing the DFL or FFL you may need to wait till the replication in your entire AD forest completes.

2. You must change your Exchange 2003 org to operate only in Native Mode. That means it simply discards the support to any Exchange 5.5 servers in your Exchange 2003 org. If you are still running Exchange 5.5 site with your Exchange 2003 it must be migrated over to Exchange 2003 and then decommissioned before changing your Exchange 2003 org mode. To change your Exchange 2003 org to native mode, right click on your Org Name in ESM and select Properties. The Org Properties dialog box appears. Click on the Change Mode button. You will be warned that this setting is irreversible.

image

3. Considering your AD health, replication and DNS are working absolutely fine you can now think of starting for Exchange 2010 preparation. So what we need here to install Exchange 2010 is either Windows Server 2008 SP2 or Windows Server 2008 R2 which is available only in 64 bit flavour and of course powerful enough hardware to install a 64 bit architecture OS on it. The minimum and recommended system requirements can be found at: http://technet.microsoft.com/en-in/library/aa996719(en-us,EXCHG.149).aspx

4. Assuming that you have already setup a Windows Server box installed Windows Server 2008 SP2 or Windows Server 2008 R2 on it, its time to configure it to install Exchange 2010 on it. Here, you might notice that Exchange 2010 will still support Windows Server 2008 but it must be installed with SP2. Exchange 2010 can support both of these operating system versions. Yet, the OS configuration part varies due to changes in architecture of both versions. Though the software component prerequisites remain the same on both versions they have their own ways to configure these components. Microsoft already has a publication on technet which talks about the ways to install these software prerequisites. They can be found at Exchange 2010 Prerequisites. It is highly recommended that you should run Windows Update before starting an install of Exchange 2010. Windows update will download all the latest updates for the software components.

Natively, Exchange 2010 will require following software installed on a Windows box:

1. .Net Framework 3.5 SP1 – Exchange code base is built on .Net Framework 3.5 where the Exchange 2007 had it built around 2.0 (Not required to be installed on Windows 2008 R2)

2. Windows Remote Management Tools 2.0 and Power shell V2 (Not required to be installed on Windows 2008 R2)

3. 2007 Office System Converter: Microsoft Filter Pack. (Required to be installed on the servers hosting mailbox server role or hub transport server role)

Apart from these additional software below is the list of required software components need to be installed:

5. As you already have an Exchange 2003 organization setup and running, its now time to setup your first Exchange 2010 server in co-existence. If you have already worked a Exchange 2007 setup you might have been knowing to run the legacy exchange permissions preparation. Yes, in Exchange 2010 you still need to run that switch with setup.com to prepare the legacy exchange permissions. There is a known issue detected when Exchange 2007 was a RTM release that the direct install of Exchange 2007 will break the RUS permissions on Exchange 2003. Which results into RUS not stamping email addresses on new Exchange objects. The detailed information is give at Preparing Legacy Exchange Permissions

image_preparelegacyExchangePermissions

6. Wait for replication to complete and then you can go ahead with another step of preparing the forest schema. Indeed that’s again similar to Exchange 2007 /PrepareSchema.

image

You can see the new schema objects being inserted into the Schema partition while the setup goes on or after its completion.

image 7. Once you are done with all above steps now its time to install Exchange Binaries which actually form a Windows Server 2008 box to an Exchange server. At this stage you can either chose to go with the GUI based installation or simply with the command prompt. GUI based installation is always simpler method to go with as it avoids confusions many times. I prefer using command like but for those who are not very comfortable with powershell or command line tools its a good practice to use GUI as far as possible.

Now, before you start installing make sure that you have met all the software component prerequisites on the exchange 2010 box. Again, you may refer the link Exchange 2010 Prerequisites

In the next part of this post I will explain on how to install and what to configure on Exchange 2010 side as there isn’t much that you have to modify in an existing Exchange 2003 server. So stay tuned and do post your comments and your opinion about this post.

 

 Related Posts:

Installing Exchange Server 2010 in Mixed Mode Environment – Part 2

.

Changing OWA time out on an Exchange 2007 and 2010 Computers

Exchange Server 2007 OWA will automatically time out for the security purposes. This feature has been designed to restrict unauthorized access to any mailbox when the user is using a public or shared computer. You can select this option before you logon to your mailbox:

Though this feature is good for security reasons it may be annoying for many users who use OWA regularly and they may not want to enter the password several times after the time out. This can settled down with a simple registry tweak on the CAS box that runs your Internet facing OWA site. This can be done by following registry modification.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeOWA

Name: PublicTimeout

Type: DWORD

Value: {value in minutes} (This value is 15 minutes by default)

image0041255958448201

The above suggestion applies only when the user selects the Public Computer option from the OWA logon screen. For the user who select the Private Computer from the logon screen you might want to modify:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchange OWA

Name: PrivateTimeout

Type: DWORD

Value: {value in minutes} (This value is 8 hours by default)

If you don’t see the DWORD values named, PublicTimeout and PrivateTimeout then you have create then manually.

What happened to System Attendant Mailbox in Exchange 2010?

A one word answer to this question is: REMOVED.

As we all know that System Attendant mailbox was used to publish the free/busy info and the link monitoring service in earlier versions of Exchange. In Exchange 2010 it the mailbox object for System Attendant has been removed. Yet, you can locate the directory object for System Attendant in Active Directory. Per a post published by Dave, the mailbox object for system attendant has been removed but can be seen in AD. This change was done due to the new high availability architecture of Exchange 2010. They observed problems in failovers while having the mailbox object for System Attendant.

How will this affect:

If you are running an application that uses System Attendant to connect to the servers/databases you will still be able to connect but not logon. That means you wont be able to open the system attendant mailbox anymore as the actual related mailbox doesn’t exist.

The way around it:

1. Use the per mailbox database System mailbox (See Additional Resources for more information about this mailbox).

2. Change your application to rely on a user created account and mailbox.

This has been described pretty well at he System Attendant mailbox has been removed from Exchange 2010

And do read the additional resource section to understand the facts about special mailboxes in Exchange.