This topic explains how to use Setup in Microsoft Exchange Server 2010 to install the first Exchange 2010 server in an existing Exchange organization where both Exchange Server 2003 and Exchange Server 2007 are present.

You can't perform an in-place upgrade from Exchange 2003 or Exchange 2007 to Exchange 2010. However, you can install an Exchange 2010 server into the existing Exchange organization, and then move or create the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2010.

After you perform this procedure, you will be running in a coexistence mode. You can maintain this mode for an indefinite period of time, or you can immediately complete the upgrade to Exchange 2010 by moving all resources from Exchange 2003 and Exchange 2007 to Exchange 2010 and then decommissioning the Exchange 2003 and Exchange 2007 servers. For more information about removing your Exchange 2003 and Exchange 2007 servers, see the following topics:

Exchange Server 2010 introduces the Exchange Server Deployment Assistant, or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment.

If this is the first instance of Exchange 2010 that you're installing into your existing organization, make sure that you install the Client Access server role first, followed by the Hub Transport server role, followed by the Unified Messaging server role, and lastly, the Mailbox server role.

To perform the following procedure, the account you use must be delegated membership in the Schema Admins group if you haven't previously prepared the Active Directory schema. If you're installing the first Exchange 2010 server in the organization, the account you use must have membership in the Enterprise Admins group. If you have already prepared the schema and aren't installing the first Exchange 2010 server in the organization, the account you use must be delegated the Delegated Setup role group.

Insert the Exchange 2010 DVD into the DVD drive. When the AutoPlay dialog box appears, click Run Setup.exe under Install or run program. If the AutoPlay dialog box doesn't appear, navigate to the root of the DVD and double-click Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and double-click Setup.exe.

The Exchange Server 2010 Setup welcome screen appears. In the Plan section, you can follow the links to read overview information regarding Exchange 2010, deploying languages, and the Exchange 2010 release notes. In the Enhance section, you can read more information about Microsoft Forefront Protection 2010. In the Install section, the software listed for Step 1: Install .NET Framework 3.5 SP1 and Step 2: Install Windows PowerShell v2 was installed with the Exchange 2010 prerequisites. However, if these prerequisites aren't already installed, click the appropriate step to install them.
For more information about Windows PowerShell installation, see Install Windows Management Framework.

When Step 1 and Step 2 are shown as Installed, click Step 3: Choose Exchange language option to expand the Exchange language options, and then choose the appropriate option:

Install all languages from the language bundle This option installs all the Exchange 2010 languages from an Exchange 2010 language bundle. You can connect to the Internet to download the latest applicable language bundle or to use a previously downloaded language bundle on a local drive or network share. Internet connectivity is required for Exchange Setup to download the language pack bundle.

Install only languages from the DVD This option installs only the languages included with the Setup DVD. The installation of additional languages support requires installing the languages from the language bundle.
For more information about Exchange language options, see Exchange 2010 Language Support.

On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and then click Next.

On the Error Reporting page, click Yes, and then click Next.

On the Installation Type page, click Typical Exchange Server Installation. If you want to change the path for the Exchange 2010 installation, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next.

Note:

If you choose the Typical Exchange Server Installation option, you won't be able to install the Unified Messaging server role or Edge Transport server role during this installation. You can add additional server roles later if you choose not to install them during this installation.

On the Configure Client Access Server external domain page, enter a domain name to use to configure your Client Access servers. For more information about configuring Client Access servers, see Managing External Client Access. Click Next.

On the Customer Experience Improvement page, choose the appropriate selection for your organization, and then click Next.

On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they have completed successfully, click Install to install Exchange 2010.

Finally, be sure to perform the tasks described in Finalize Deployment Tasks that are required for the server roles that you have installed.

Important:

Exchange 2010 now creates system address lists in a new container. Recipients created or modified using Exchange 2003 or Exchange 2007 management tools won’t be stamped with these system address lists. As a result, they won’t be seen by the Get-Recipient cmdlet.
To fix this issue, you must enable Active Directory virtual list view (VLV). After you have completed the upgrade of an existing Exchange 2003 organization to Exchange 2010 and have decommissioned your Exchange 2003 servers, you must enable Active Directory VLV. To enable VLV for Exchange 2010, run the Enable-AddressListPaging cmdlet. For more information, see Enable-AddressListPaging.