Install Exchange 2013 in an Existing Exchange 2007 Organization
Applies to: Exchange Server 2013
Topic Last Modified: 2013-11-05
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place upgrade from Exchange 2007 to Exchange 2013.
|Have you heard about the Exchange Server Deployment Assistant? It's a free online tool that helps you quickly deploy Exchange 2013 in your organization by asking you a few questions and creating a customized deployment checklist just for you. If you want to learn more about it, go to Exchange Server Deployment Assistant.|
After you install Exchange 2013, your organization will be running in a coexistence mode. You can maintain this mode indefinitely, or you can immediately complete the upgrade to Exchange 2013 by moving all resources from Exchange 2007 to Exchange 2013, and then decommissioning the Exchange 2007 servers.
|You can install Exchange 2013 in a native mode Exchange organization. However, if you create a forest in which to install Exchange 2013, you can't later add earlier versions of Exchange.|
|Are you installing Exchange 2013 into a mixed Exchange 2007 and Exchange 2010 organization? If so, then you first need to follow the steps in Install Exchange 2013 in an Existing Exchange 2007 Organization to create a new legacy namespace to coexist with Exchange 2013.|
You’ll need to install Update Rollup 10 (RU10) for Exchange 2007 Service Pack 3 (SP3) on all the Exchange 2007 servers in your organization before you can install Exchange 2013. The service pack is available in the Microsoft Download Center at Microsoft Exchange Server 2010 Service Pack 3 (SP3). The update rollup is available in the Microsoft Download Center at Update Rollup 10 for Exchange Server 2007 Service Pack 3 (KB2788321). Also, be sure to see Release Notes for Exchange Server 2010 SP3 and Upgrade Exchange 2010 to Exchange 2010 SP1, SP2, or Exchange 2010 SP3. For more information, see How to Upgrade to Exchange 2007 SP1. While this topic is not an exact match, you can reference it for steps about how to upgrade to Exchange 2007 SP3.
In terms of the order in which to upgrade your sites, the guidance is similar to that of the past in that, assuming you have Exchange servers in more than one site, you will want to start with any Internet-facing Active Directory sites first, followed by the internal sites. The first site you will want to upgrade is the one where AutoDiscover requests from the Internet come in.
You must ensure that each of the servers meets the appropriate prerequisites and system requirements before you begin your installation. For more information, see the following topics:
In order for Exchange 2013 to coexist with Exchange 2007, all your Exchange 2013 servers must be running Cumulative Update 2 (CU2) or later for Exchange 2013.
For more information about Exchange 2013 cumulative updates, see Cumulative Updates for Exchange 2013.
If you're installing the first Exchange 2013 server in the organization, and the Active Directory preparation steps have not been performed, the account you use must have membership in the Enterprise Administrators group. If you haven't previously prepared the Active Directory Schema, the account must also be a member of the Schema Admins group. If you have already performed the Schema and Active Directory preparation steps, the account you use must be a member of the Delegated Setup management role group or the Organization Management role group.
After you have downloaded Exchange 2013 CU2, log on to the computer on which you want to install Exchange 2013.
Navigate to the network location of the Exchange 2013 installation files.
Start Exchange 2013 Setup by double-clicking
Important: If you have User Access Control (UAC) enabled, you must right-click
Setup.exeand select Run as administrator.
On the Check for Updates page, choose whether you want Setup to connect to the Internet and download product and security updates for Exchange 2013. If you select Connect to the Internet and check for updates, Setup will download updates and apply them prior to continuing. If you select Don't check for updates right now, you can download and install updates manually later. We recommend that you download and install updates now. Click Next to continue.
The Introduction page begins the process of installing Exchange into your organization. It will guide you through the installation. Several links to helpful deployment content are listed. We recommend that you visit these links prior to continuing setup. Click Next to continue.
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 Recommended settings page, select whether you want to use the recommended settings. If you select Use recommended settings, Exchange will automatically send error reports and information about your computer hardware and how you use Exchange to Microsoft. If you select Don't use recommended settings, these settings remain disabled but you can enable them at any time after Setup completes. For more information about these settings and how information sent to Microsoft is used, click ?.
On the Server Role Selection page, select both Mailbox role and Client Access role. If this is the first Exchange 2013 server deployment in your organization, you will need to deploy both an Exchange 2013 Client Access Server and an Exchange 2013 Mailbox Server into the organization. Exchange 2013 is simply an authentication and proxy/redirection server. All data processing (including the execution of remote PowerShell cmdlets) occurs on the Mailbox server. You cannot manage your Exchange 2013 environment until you install both roles. The management tools are installed automatically when you install any other server role.
Select Automatically install Windows Server roles and features that are required to install Exchange Server to have the Setup wizard install required Windows prerequisites. You may need to reboot the computer to complete the installation of some Windows features. If you don't select this option, you must install the Windows features manually.
Click Next to continue.
Note: This option installs only the Windows features required by Exchange. You must install other prerequisites manually. For more information, see Exchange 2013 Prerequisites.
On the Installation Space and Location page, either accept the default installation location or click Browse to choose a new location. Make sure that you have enough disk space available in the location where you want to install Exchange. Click Next to continue.
On the Malware Protection Settings page, choose whether you want to enable or disable malware scanning. If you disable malware scanning, it can be enabled in the future. Unless you have a specific reason to disable malware scanning, we recommend that you keep it enabled. Click Next to continue.
On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they haven't completed successfully, you must resolve any reported errors before you can install Exchange 2013. You don't need to exit Setup when resolving some of the prerequisite errors. After resolving a reported error, click Back and then click Next to run the prerequisite check again. Be sure to also review any warnings that are reported. If all readiness checks have completed successfully, click Install to install Exchange 2013.
On the Completion page, click Finish.
Restart the computer after Exchange 2013 has completed.
After installation is complete, you can view the Exchange setup log to verify your installation. See Verify an Exchange 2013 Installation for more information.
For Exchange 2013, management of Mailbox server certificates is no longer required, and we have introduced the new Certificate Wizard. For more information about configuring certificates, see Exchange 2013 Client Access Server Configuration.
You'll have to configure the Exchange 2013 Client Access server after you install digital certificates. See the “Upgrade from Exchange 2007 Client Access” section in Exchange 2013 Client Access Server Configuration for details.
You need to create a legacy domain name system (DNS) host name so your legacy Exchange environment (Exchange 2007) and Exchange 2013 can coexist. For example, if your domain name is currently contoso.com, you're likely using a host name of mail.contoso.com or www.contoso.com for external client access to Exchange.
During coexistence, we recommend creating and using, for example, a host name of legacy.contoso.com. This host name should be configured the same way your primary host name is configured. You'll associate the legacy host name with your existing Exchange server and associate your current host name (for example, mail.contoso.com) with your Exchange 2013 Client Access server. Your end users will not see or use the legacy host name. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.
All client connections will be redirected, including Exchange ActiveSync, Outlook Web App, POP3, and IMAP4. After the legacy host name has been configured, users will be able to access their mailbox regardless of whether it's on Exchange 2007 or Exchange 2013. If you're upgrading from Exchange 2007 to Exchange 2013, Availability service requests will also be redirected.
The exact steps for this procedure depend on your Internet service provider (ISP) and firewall configuration. Your actual steps may vary. In general, you need to perform the following steps:
Create a DNS host (A) record in your internal and external DNS servers that points to the IP address of your legacy Internet-facing Exchange server (for example, your Exchange 2007 Client Access server) in internal DNS or the public IP address on your reverse proxy or firewall solution (external DNS). The host name should be in the format of legacy.domain.com (for example, legacy.contoso.com).
Create a publishing rule for the legacy host name in your reverse proxy or firewall solution to point to your legacy Internet-facing Exchange server. Refer to your proxy or firewall solution's user instructions about how to do this.
Warning: Make sure you test that the legacy host name works correctly and the new publishing rules are working.
Configure the existing DNS host (A) record in your internal and external DNS servers for your original host name (for example, mail.contoso.com) to point to your Exchange 2013 organization; for example, the IP address of your Client Access server or array (internal DNS), or the public IP address on your reverse proxy or firewall solution (external DNS).
To verify that the legacy host name was created successfully, do the following from outside your firewall, using your specific domain name:
Navigate to https://legacy.contoso.com/exchange, and then verify that you can access Outlook Web App for a user whose mailbox is on a legacy Exchange server.
Navigate to https://mail.contoso.com/owa, and verify that you can access Outlook Web App for a user whose mailbox is on Exchange 2013.
You can also use the Remote Connectivity Analyzer (RCA), a free web-based tool provided by Microsoft. You can find ExRCA at: https://www.testexchangeconnectivity.com
You'll have to configure the Exchange 2007 Client Access server after you switch the primary DNS namespace. See the “Configure protocols on the Exchange 2007 Client Access servers” section in Exchange 2013 Client Access Server Configuration for details.
Navigate to https://mail.contoso.com/owa, and verify that you can access Outlook Web App for a user whose mailbox is on an Exchange 2013 server.
See the following topics to learn more about what’s new and what’s changed in Exchange 2013.
See what’s new in Exchange 2013.
Learn about new management features in Exchange 2013.
Learn about moving your mailboxes to Exchange 2013.
Learn about public folders in Exchange 2013.
See what’s new for Unified Messaging in Exchange 2013.
See what’s new for Transport Rules in Exchange 2013.
Learn how Microsoft SharePoint 2013 and Microsoft Lync 2013 integrate with Exchange 2013.
Learn about anti-spam and anti-malware features in Exchange 2013.