Existing Exchange Server 2007 and Exchange Server 2010
installations can coexist with Exchange Server 2013 installations.
Generally, you do this by integrating Exchange Server 2013 into your
existing Exchange Server 2007 or Exchange Server 2010 organization.
Integration requires the following:
-
Preparing Active Directory and the domain for the extensive Active
Directory changes that will occur when you install Exchange Server 2013.
-
Configuring Exchange Server 2013 so that it can communicate with servers running Exchange Server 2007 and Exchange Server 2010.
If you need a legacy server, you need to keep or add it to the
Exchange organization before adding the new Exchange 2013 servers.
Then, you have a coexistence implementation. You cannot upgrade
existing Exchange Server 2007 or Exchange Server 2010 servers to
Exchange Server 2013. You must install Exchange Server 2013 on new
hardware, and then move the mailboxes from your existing installations
to the new installation.
As an alternative to coexistence, you can deploy a new Exchange 2013
organization. After you deploy a new Exchange 2013 organization, you
can’t add servers that are running earlier versions of Exchange to the
organization. Adding earlier versions of Exchange to an Exchange 2013
organization is not supported.
Coexistence and Active Directory
For coexistence with legacy Exchange Server versions, Exchange
Server 2013 Cumulative Update 1 (CU1) is the minimum version. Exchange
Server 2013 (Release to Manufacturer) RTM doesn’t support legacy
Exchange organizations. Keep the following in mind:
-
Exchange 2003 and earlier versions are not supported for coexistence.
-
Exchange
2007 is supported for coexistence only when all Exchange 2007 servers
are running Rollup 10 for Exchange 2007 SP3 or later.
-
Exchange 2010 is supported for coexistence only when all Exchange 2010 servers are running SP3 or later.
Before you install any build of Exchange Server 2013 in a legacy
Exchange Server organization, ensure that Exchange Server 2010 is fully
deployed. The reason for this is that you can install additional
Exchange Server 2010 servers running a particular server role only if
you’ve deployed a server with one of these roles prior to installing
Exchange Server 2013. Therefore, if you haven’t previously deployed all
four Exchange Server 2010 server roles in your legacy Exchange Server
organization, you may want to do so prior to installing any build of
Exchange Server 2013.
Exchange Server 2013 contains extensive Active Directory schema
changes and other Active Directory updates, so you might want to
prepare Active Directory and the domain for these changes prior to
installing Exchange Server 2013 for the first time, especially in a
large enterprise.
To do this, follow these steps:
-
Prepare the schema by running the following command prior to executing the Exchange Server 2013 Setup:
setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
This command connects to the schema master and imports the LDAP data
interchange format files that are used to update the schema with
Exchange 2013 specific attributes. Optionally, use the
/DomainController parameter to specify the name of the schema master.
You must run this command on a 64-bit computer in the same domain and
site as the schema master. If schema needs to be updated and you
haven’t previously prepared schema, you must ensure the account you use
is delegated membership in the Schema Admins group. Wait for the
changes to replicate before continuing.
-
Prepare Active Directory for Exchange 2013 by running the following command prior to executing the Exchange Server 2013 Setup:
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
You must run this command in the same domain and site as the schema
master. This computer must be able to connect to all domains in the
forest on TCP port 389. To run this command, you must be a member of
the Domain Admins groups for the local domain or the Enterprise Admins
group. Wait for the changes to replicate before continuing.
The PrepareAD option performs a number of tasks:
-
Creates the Microsoft Exchange container and the Exchange
organization container in the directory if they don’t exist, such as
when you are installing a new Exchange organization. Here, you must set
a name for the organization using the /OrganizationName parameter.
-
Verifies that the schema has been updated for Exchange 2013. It does
this by checking the objectVersion property for the Exchange
configuration container and ensuring the value is 15449 or higher. The
command also sets the Exchange product ID of the Exchange organization
to that of the version you are installing. The base value for Exchange
2013 RTM is 15.00.0516.032. This value is incremented when you deploy
Cumulative Updates to Exchange.
-
Creates any containers that are required in Active Directory for
Exchange 2013, creates the default Accepted Domains entry if a default
was not previously set, and imports the Rights.ldf file to add the
extended rights required for Exchange to the directory.
-
Creates the Microsoft Exchange Security Groups organizational unit
in the root domain of the forest and then creates the following
management role groups used by Exchange to this organizational unit if
these haven’t been previously created: Compliance Management, Delegated
Setup, Discovery Management, Help Desk, Hygiene Management,
Organization Management, Public Folder Management, Recipient
Management, Records Management, Server Management, UM Management, and
View-Only Organization Management. As necessary, also adds these groups
to the otherWellKnownObjects attribute on the Exchange Services
Configuration container.
-
Creates the Unified Messaging Voice Originator contact in the
Microsoft Exchange System Objects container of the root domain and then
prepares the local domain for Exchange 2013.
-
The domain in which you ran setup.exe /PrepareAD
is already prepared. For all other domains that will have mail-enabled
users or in which you will install Exchange 2013, you must log in and
run:
setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms.
You also can specify the name of the domain in which you want to run the command, such as:
setup.exe/PrepareDomain:Tech.Pocket-Consultant.com
/IAcceptExchangeServerLicenseTerms
Alternatively, you can run:
setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms
to prepare all domains in the forest. To run this command, you
normally must be a member of the Domain Admins groups for the local
domain or the Enterprise Admins group. However, if the domain was
created after running /PrepareAD, the account you use must be a member
of the Exchange 2013 Organization Management role group and the Domain
Admins groups in the domain.
For new organizations, this command creates the Microsoft Exchange
System Objects container and sets its permissions. For all
organizations, this command:
-
Sets the objectVersion property in the Microsoft Exchange System
Objects container so that it references the version of domain
preparation for Exchange 2013, which is 13236 or higher.
-
Creates
a domain global group in the current domain called Exchange Install
Domain Servers and adds this group in the Microsoft Exchange System
Objects container as well as the Exchange Servers group in the root
domain.
-
Assigns permissions in the domain for the Exchange Servers group and the Organization Management group.
Although Exchange Server 2013 Setup can perform these processes for
you during the upgrade, the changes can take some time to replicate
throughout a large organization. By performing these tasks manually,
you can streamline the upgrade process. You also can ensure the tasks
are run with accounts that have appropriate permissions.
As a prerequisite for installing Exchange Server 2013, Active
Directory must be at Windows Server 2003 forest functionality mode or
higher. Additionally, the schema master for the Active Directory forest
along with at least one global catalog server and at least one domain
controller in each Active Directory site must be running one of the
following operating systems:
-
Windows Server 2012 RTM or R2 Standard or Datacenter
-
Windows Server 2008 R2 Standard or Enterprise
-
Windows Server 2008 R2 Datacenter RTM or later
-
Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
-
Windows Server 2008 Datacenter RTM or later
-
Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
-
Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)
When you deploy IPv6, Exchange 2013 servers can send data to and
receive data from devices, servers, and clients that use IPv6
addresses. However, Exchange 2013 supports IPv6 only when IPv4 is also
installed. Further, although you can disable IPv4 so that only IPv6 is
enabled, Exchange still requires that IPv4 be installed.
