Existing Exchange Server 2003 and Exchange Server 2007 installations can coexist with
Exchange Server 2010 installations. Generally, you do this by
integrating Exchange Server 2010 into your existing Exchange Server 2003
or Exchange Server 2007 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 2010.
Configuring Exchange Server 2010 so that it can communicate with servers running Exchange Server 2003 and Exchange Server 2007.
If you need a legacy
server, you need to keep or add it to the Exchange organization before
adding the new Exchange 2010 servers. Then, you have a coexistence
implementation. You cannot upgrade existing Exchange Server 2003 or
Exchange Server 2007 servers to Exchange Server 2010. You must install
Exchange Server 2010 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 2010 organization. After you
deploy a new Exchange 2010 organization, you can't add servers that are
running earlier versions of Exchange to the organization. Adding earlier
versions of Exchange to an Exchange 2010 organization is not supported.
Note:
You can deploy Exchange 2010 only in an Exchange 2003 organization that operates in native mode. To use Exchange System Manager to change the Exchange organization to native
mode on an Exchange 2003 server, click Start, point to Programs, point
to Microsoft Exchange, and then click System Manager. Next, right-click
the organization, and then click Properties. On the General tab, under
Change Operations Mode, click Change Mode. Click Yes if you are sure
that you want to permanently switch the organization's mode to native
mode.
1. Preparing Active Directory for Exchange Server 2010
Exchange Server 2010 can be integrated into
Exchange Server 2003 and Exchange Server 2007 organizations. If you
have any servers running Exchange Server 2003, Exchange Server 2007, or
both, you might want to prepare Active
Directory and the domain for the extensive Active Directory changes
that will occur when you install Exchange Server 2010. If so, complete
the procedure in this section. Alternatively, if you run the Exchange
2010 Setup
Wizard with an account that has the permissions required to prepare
Active Directory and the domain, the wizard automatically prepares
Active Directory and the domain and you do not need to perform the
procedure in this section. However, in a large enterprise, these updates
could take a long time to complete.
You can prepare Active
Directory by running Exchange Server 2010 setup at an elevated,
administrator command prompt with various options. The steps to complete
are as follows:
To prepare legacy Exchange permissions in every domain in the forest that contains Exchange Enterprise Servers and Exchange Domain Servers groups, run Setup with the /PrepareLegacyExchangePermissions option on any server running Windows Server 2003 Service Pack 1 or later. Note the following:
To
successfully run this command, you must be a member of the Enterprise
Admins groups and the domain in which you run this command must be able
to contact all domains in the forest.
If
the forest has only one domain, you must be delegated the Exchange Full
Administrator role and you must be a member of the Domain Admins group
in the domain that you will prepare.
If
the server cannot contact a domain that must have legacy Exchange
permissions prepared, it prepares the domains that it can contact and
then returns an error message that it was unable to contact some
domains.
After all permissions have replicated across your entire Exchange organization, run Setup with the /PrepareSchema
option to connect to the schema master and update the schema with
attributes for Exchange Server 2010. To run this command, you must be a
member of the Schema Admins group and the Enterprise Admins group. You
must run this command on a computer in the same Active Directory domain
and same Active Directory site as the schema master. The schema master
is located in the forest root domain.
Tip:
If you have trouble preparing the schema, try logging on with a local administrator account on a domain controller in the forest root domain and then running Exchange Server 2010 setup with the /PrepareSchema option.
After all schema changes have been made, run Setup with the /PrepareAD option to configure global Exchange objects in Active Directory, create Exchange Universal Security groups in the root domain, and prepare the current domain for Exchange Server 2010. You must also use the /OrganizationName
option to specify the name of your Exchange organization. To run this
command, you must be a member of the Enterprise Admins group. You must
run this command on a computer in the same Active Directory domain and
same Active Directory site as the schema master. The schema master is
located in the forest root domain.
When this step is completed, the root domain should have a new organizational unit called Microsoft Exchange Security Groups, and this organizational unit should contain the following groups: Exchange All Hosted Organizations, Exchange Organization Administrators, Exchange Public Folder Administrators, Exchange Recipient Administrators, Exchange Self-Service Administrators, Exchange Servers, Exchange Trusted Subsystem, Exchange View-Only Administrators, Exchange Windows Permissions, and ExchangeLegacyInterop.
Finalize security settings for Exchange Server 2010 by preparing the local domain by running Setup with the /PrepareDomain option, or by preparing all domains by running setup with the /PrepareAllDomains
option. To run this command, you must be a member of the Domain Admins
groups for the local domain or the Enterprise Admins group.
If
the domain that you are preparing was created after you ran Setup with
the /PrepareAD option, you must be a member of the Exchange Organization
Administrators
group, and you must be a member of the Domain Admins group in the
domain. You must run Setup with the /PrepareAD option in every domain in
which you will install Exchange 2010. You must also run this command in
every domain that will contain mail-enabled users, even if the domain
does not have Exchange 2010 installed.
2. Configuring Exchange Server 2010 for Use with Existing Exchange Organizations
All the Exchange 2010 server
roles are supported for coexistence with a native-mode Exchange 2003 or
2007 organization. In the Exchange System Manager for Exchange Server
2003, all Exchange servers are displayed as members of the Exchange Administrative Group. Exchange Server 2010 servers are also displayed as members of the Exchange
Routing Group. These groups are created only for the purpose of
coexistence with Exchange Server 2003 and are not applicable to Exchange
Server 2007.
When managing Exchange servers, you should use the administrative tools for that Exchange Server version. Exchange Server 2010 doesn't use Active Directory Users And Computers for recipient management,
and instead uses only the Exchange Management Console and the Exchange
Management Shell for this purpose. The Exchange Management Console and
the Exchange Management Shell are the primary management tools for
Exchange Server 2010.
Mailboxes located on Exchange Server 2003 and
Exchange Server 2007 servers are also displayed in the Exchange
Management Console. You can manage the Exchange 2003 or 2007 mailbox
properties using the Exchange Management Console or the Exchange
Management Shell. You can use either tool to move mailbox recipients
from Exchange 2003 or Exchange 2007 to Exchange 2010.
When deploying Exchange 2010 in an Exchange 2003 or Exchange 2007 organization, keep the following in mind:
If you want to use the Exchange Server 2010 Client Access server role, you must deploy the Client Access server role
in each Active Directory site that contains the Mailbox server role.
Clients will see the Outlook Web App or Exchange ActiveSync version that
is on their mailbox store. With Client Access arrays, the Client Access
servers must all be members of the same Active Directory site and the servers cannot also have the Mailbox role.
If you want to use the Hub Transport server role, you must configure a two-way routing group connector from the Exchange
Routing Group to each Exchange Server 2003 routing group that
communicates directly with Exchange Server 2010. You must also suppress
link state updates for each Exchange Routing Group that communicates
with Exchange Server 2010. This does not apply to Exchange 2007.
If
you want to use the Unified Messaging server role, you must deploy the
Exchange Server 2010 Hub Transport server role in the same Active
Directory site as the Unified Messaging server role. Keep in mind that
while Exchange 2003 mailboxes
cannot be enabled with unified messaging, Exchange 2007 mailboxes can
be enabled with unified messaging, but they will need an Exchange 2007
Unified Messaging server.
If
you want to use the Mailbox server role, you must deploy the Exchange
Server 2010 Hub Transport server role in the same Active Directory site
as the Mailbox server role.
If
you want to use the Edge Transport server role, you must configure SMTP
connectors to accept mail from and send mail to the Internet. With
Exchange 2003, four connector configurations are needed: Internet Send Connector, Internet Receive Connector, Legacy Send Connector, and Legacy
Receive Connector. The legacy connectors are not needed for Exchange
2007. Other modifications are required to mail Exchange and smart host
records. Further, you can synchronize the Edge Transport server's AD LDS
data with Active Directory only if the Exchange Server 2010 Active
Directory preparation process has been performed.
3. Moving to Exchange Server 2010
Most
organizations have existing Exchange installations. When moving Exchange
2003 or Exchange 2007 installations to Exchange Server 2010, you cannot
perform an in-place upgrade. Instead, you must install new Exchange
Server 2010 servers into the existing organization and then either
migrate or transition to Exchange Server 2010. Keep the following points
in mind regarding migration and transitioning:
Migration
from Exchange 2003 or Exchange 2007 to Exchange 2010 involves installing
Exchange Server 2010 on new hardware and then moving the mailboxes and
public folders from your existing installations to the new installation.
In a migration, only mailbox and public folder data is moved and any
Exchange configuration data is not maintained.
Transitioning
from Exchange Server 2003 or Exchange 2007 to Exchange Server 2010 is a
multiple-phase process that allows for the retention of Exchange
configuration data as well as mailbox and public folder data. During
these transitioning processes, the Exchange organization is considered
to be operating in a coexistence mode.
3.1. Migrating to Exchange Server 2010
Migration from Exchange Server
2003 or Exchange 2007 to Exchange 2010 moves the mailboxes from your
existing installations to your new Exchange Server 2010 installations.
In a migration, only mailbox and public folder data is moved and any
Exchange configuration data is not maintained.
With Exchange Server 2003,
your servers must have Exchange Server 2003 Service Pack 2 or later
installed. In each Active Directory site, you must have at least one Global
Catalog server running Windows Server 2003 Service Pack 2 or later.
Active Directory must be in Windows Server 2003 functional mode or
higher.
With Exchange Server 2007,
your servers must have Exchange Server 2007 Service Pack 2 or later
installed. In each Active Directory site, you must have at least one
Global Catalog server running Windows Server 2003 Service Pack 2 or
later. Active Directory must be in Windows Server 2003 functional mode
or higher.
The steps you perform to migrate from Exchange 2003 or Exchange 2007 to Exchange 2010 are as follows:
Plan
to transition all Exchange servers in a particular routing group or
site to Exchange 2010 at the same time. You must start with
Internet-accessible Active Directory sites and then migrate internal
Active Directory sites. With Exchange 2003, an Exchange 2003 front-end
server is required to support the transition. For each Exchange 2010
Client Access server, you can configure only one Outlook Web App URL for
redirection.
Install
Exchange Server 2010 on new hardware, and make it a member of the
appropriate domain in the forest. You should install the Client Access
server role first and then install and transition other roles in the
following order: the Hub Transport server role, the Unified Messaging
server role, the Mailbox server role. You can install these roles on a
single server or on multiple servers. You must deploy an Exchange 2010
Hub Transport server in each Active Directory site that has an Exchange
2010 Mailbox server.
If
you plan to have an Edge Transport server in your Exchange 2010
organization, you must install the Edge Transport server role on a
separate computer. With Exchange 2003 organizations, you can add
Exchange 2010 Edge Transport servers without having to upgrade internal
servers. However, when Edge Transport servers are deployed in an
Exchange organization that has not yet deployed Exchange 2010, you can't
create an Edge subscription, and a limited set of features are available. If you are using the Exchange
Intelligent Message Filter for antispam features, the Edge Transport
servers will provide an additional layer of protection until the
transition is complete.
With
Exchange 2007 organizations, you should install your Exchange 2010 Hub
Transport servers first because Exchange 2010 Hub Transport servers can
sync with Exchange 2007 Edge Transport servers. Then you install the
Exchange 2010 Edge Transport servers. Afterward, you should remove the
Exchange 2007 Edge Transport servers and related subscriptions, and then
subscribe your Exchange 2010 Edge Transport servers to the Exchange
2010 Hub Transport servers.
Move mailboxes
and public folders from your existing Exchange 2003 or Exchange 2007
installations to the new Exchange Server 2010 Mailbox server or servers.
If you move a mailbox that is part of an e-mail address policy, the
e-mail address for the mailbox is automatically updated based on the
settings in the e-mail address policy. In this case, the new e-mail
address becomes the primary address, and the old e-mail address becomes
the secondary address.
During
a transition, the version of a CAS feature such as Outlook Web App that
a user sees depends on where the user's mailbox is located. If the
user's mailbox is on an Exchange 2003 server, she sees Exchange 2003
versions of CAS features. When you move the user's mailbox to Exchange 2010, she will see Exchange 2010 versions of CAS features.
Note:
REAL WORLD You move mailboxes
from Exchange 2003 SP2 to Exchange 2010 by using an offline move
process. Users will not be able to access their mailboxes during the
move. Perform the move from the Exchange 2010 server using move mailbox
requests, either with the Exchange Management Shell or the Exchange
Management Console. You can't use the Exchange System Manager on the
Exchange 2003 server to move mailboxes. You can't move mailboxes from
Exchange 2003 SP1 or earlier.
You can move mailboxes from
Exchange 2007 SP2 to Exchange 2010 by using an online move, and this
approach allows users to access their mailboxes during the move. Perform
the move from the Exchange 2010 server by using move mailbox requests,
either with the Exchange Management Shell or the Exchange Management
Console. You can't use the Exchange Management Console on the Exchange
2007 server to move mailboxes. You can't move mailboxes from Exchange
2007 SP1 or earlier.
If
you want to remove your Exchange 2003 servers, you must first remove
Exchange Server 2003 routing groups and all connectors to these routing
groups. Also, keep in mind that Exchange Server 2010 does not support
the Novell GroupWise connector for Exchange Server 2003 or the use of the Inter-Organization
Replication tool to share free/busy and public folder data across
forests. If you require these features, you must keep at least one
Exchange Server 2003 server in your organization.
Remove your old Exchange 2003 or Exchange 2007 server from the organization.
Warning:
Before removing
the last Exchange 2007 server, you must be sure that you will never
need to introduce an Exchange 2007 server again. Once you remove the
last Exchange 2007 server, you can never add another one. The same goes
for Exchange 2003. Once you remove the last Exchange 2003 server, you
can never add another one.
3.2. Transitioning to Exchange Server 2010
The steps you perform to
transition from Exchange 2003 or Exchange 2007 to Exchange 2010 depend
on the forest configuration. To transition from an Exchange 2003 or
Exchange 2007 single forest organization to an Exchange 2010 single
forest organization or to deploy Exchange Server 2010 in an Exchange
resource forest and then transition to Exchange Server 2010, follow
these steps:
Install
Exchange Server 2010 on new hardware, and make it a member of the
appropriate domain in the forest. At a minimum, you should install the
Client Access server role, the Hub Transport server role, and the
Mailbox server role. You can install these roles on a single server or
on multiple servers. If you plan to have an Edge Transport server in
your Exchange 2010 organization, you must install the Edge Transport
server role on a separate computer.
When Mailbox servers have been deployed, you can move mailboxes from Exchange 2003 or Exchange 2007 to Exchange 2010.
For
any public folders in your existing Exchange 2003 or Exchange 2007
organization that you want to maintain, create a replica on your
Exchange Server 2010 Mailbox server or servers. For Exchange 2003, you
must create the replica using Exchange
System Manager in the Exchange 2003 organization. Exchange then
replicates the public folder data to the Exchange Server 2010 Mailbox
server or servers.
Note:
You do not need to create replicas for the offline address book (OAB) or free/busy system folders. When you install the first Exchange Server 2010 server, Exchange creates these replicas.
If
you want to remove your Exchange 2003 servers, you must first remove
Exchange Server 2003 routing groups and all connectors to these routing
groups. Also, keep in mind that Exchange Server 2010 does not support
the Novell GroupWise connector for Exchange Server 2003 or the use of the Inter-Organization
Replication tool to share free/busy and public folder data across
forests. If you require these features, you must keep at least one
Exchange Server 2003 server in your organization.
When you are absolutely certain that you don't need your old Exchange 2003 or Exchange 2007 server, you can remove it from the organization. Once you remove it, you can never add it back again.
In some cases, you might want
to have one or more forests that contain accounts and a separate
resource forest for your Exchange organization. Although configuring a
separate resource forest provides clear separation between accounts and
your Exchange organization, it requires a great deal of predeployment
planning and additional work to maintain. In the Exchange forest, you
must disable any user accounts with mailboxes and then associate these
disabled user accounts, and all other user accounts, with the user
accounts in your other forests. To do this, you must install a Microsoft identity integration solution, and then use its GAL Synchronization feature to create mail-enabled contacts that represent recipients from other forests.
To transition from a single forest organization to a resource forest organization, follow these steps:
Create
a new Active Directory forest, and then create a one-way, outgoing
forest trust from this forest to your existing forest. This ensures that
the Exchange Server 2010 resource forest trusts the existing forest.
You need the trust so that you can move mailboxes from servers in the
existing forest to servers in the Exchange Server 2010 forest.
In
the Exchange Server 2010 forest, install Exchange Server 2010 on new
hardware, and make it a member of the appropriate domain in this forest.
At a minimum, you should install the Client Access server role, the Hub
Transport server role, and the Mailbox server role. You can install
these roles on a single server or on multiple servers. If you plan to
have an Edge Transport server in your Exchange Server 2010 organization,
you must install the Edge Transport server role on a separate computer.
Move
all mailboxes from the existing forest to the Exchange Server 2010
forest. You must move all mailboxes. If you do not move all mailboxes,
you will be in an unsupported hybrid forest scenario.
To complete the transition, follow steps 3 through 5 from the procedure previously described in this section.
