Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
Gilt für: Exchange Server 2010
Letztes Änderungsdatum des Themas: 2010-01-22
You can deploy Microsoft Exchange Server 2010 in an existing Microsoft Exchange Server 2003 organization that's operating in native mode. Coexistence with these two Exchange versions is supported. This topic provides an overview of the planning considerations and configuration steps that you must take when Exchange 2010 will coexist with Exchange 2003.
Any organization that is upgrading from Exchange 2003 will experience a period of coexistence. In a coexistence scenario, any combinations of the following versions of Microsoft Exchange are deployed in a single Exchange organization: Exchange Server 2003, Exchange Server 2007 and Exchange 2010. These multiple versions of Exchange are able to communicate with each other and share data resources, recipient information, and configuration information. Parts of the organization still use Exchange 2003 functionality and other parts have completed the upgrade to Exchange 2010.
|You can only install more Exchange 2003 servers in your organization if you had an Exchange 2003 server there when the first Exchange 2010 server was installed.|
Here are a few things about coexistence that you should be aware of:
Active Directory and Domains When upgrading from Exchange Server 2003 to Exchange Server 2010, you must first grant specific Exchange permissions in each domain in which you have run Exchange 2003 DomainPrep. To do this, you run the
setup /PrepareLegacyExchangePermissionscommand. Granting these permissions is part of preparing Active Directory and your domains for installing Exchange Server 2010. For detailed instructions, see Vorbereiten von Active Directory und Domänen.
Management interfaces In Exchange 2010, you can manage Exchange 2010 servers and mailboxes by using either the Exchange Management Console (EMC) or the Exchange Management Shell. You can also use the EMC to view some attributes on Exchange 2003 servers. For more information, see Exchange-Verwaltungskonsole – Interoperabilität.
Server role features The Exchange 2010 server role features that are available to clients in the Exchange organization during the coexistence period depend on the version of the Exchange server where the user's mailbox is stored and the version of the e-mail client application that is used to access Exchange.
Routing groups A large organization that has many routing groups must plan their routing topology to maintain mail flow during the coexistence period. When you plan for a period of coexistence between Exchange 2003 and Exchange 2007, you need to understand the differences in how each version determines its routing topology. For more information about routing and coexistence, see Upgrade des Exchange 2003-Transports.
Native Mode You can only deploy Exchange 2010 in an Exchange 2003 organization that operates in native mode. For more information about how to change your Exchange 2003 organization to native mode, see Upgrade to Exchange 2010.
When you are ready to begin upgrading your organization to Exchange 2010, you must begin with your servers in the internet accessible Active Directory sites first, and then upgrade your internal Active Directory sites. This is because Client Access server to Client Access server proxying is only supported from the newer CAS versions (Exchange 2010) to older CAS versions (Exchange 2007) and not the other way around. The following figure illustrates the overview of the upgrade process from Exchange 2003 to Exchange 2010.
Within the first Active Directory site or sites you are upgrading, the first Exchange 2010 server role you will install will be the Client Access server role. When you are ready to begin your deployment, it is recommended to upgrade a single Active Directory site at a time to Exchange 2010. Depending on the size of your Active Directory site, this might be a single Client Access server computer or a load balanced array of Exchange 2010 Client Access servers. The recommended order to install the Exchange 2010 server roles is the following:
Client Access Server role
Hub Transport Server role
Unified Messaging (UM) Server role
Mailbox Server role
|When upgrading to Exchange 2010, you can't perform an in-place server upgrade on an existing Exchange server.|
For detailed information about upgrading the above, relevant server roles, see the following topics:
Upgrade von Exchange 2003 für den Clientzugriff
Upgrade des Exchange 2003-Transports
Upgrading from Exchange 2003 Mailbox
Installing Exchange 2010 in an Existing Exchange 2003 Organization
You can select to deploy a typical Exchange installation, which includes the following server roles installed on a single server:
Client Access Server role
Hub Transport Server role
Mailbox Server role
You can also choose to add the Unified Messaging server role by selecting a custom Exchange installation.
|You must deploy the Edge Transport server role in the perimeter network and outside the secure Active Directory forest.|
Wenn Sie bereit für ein Upgrade einer gemischten Umgebung sind, aktualisieren Sie jeden Active Directory-Standort einzeln. Wenn Sie über Active Directory-Standorte verfügen, die ausschließlich Exchange 2007 oderExchange 2003 verwenden, folgen Sie für diesen Active Directory-Standort den Anweisungen für ein Upgrade von dieser Version. Wenn Sie beispielsweise in Active Directory-Standort A Exchange 2007 verwenden, folgen Sie den Anweisungen für ein Upgrade von Exchange 2007. Wenn Sie in Active Directory-Standort B Exchange 2003 installiert haben, folgen Sie den Anweisungen für ein Upgrade von Exchange 2003. Weitere Informationen zum Aktualisieren Ihrer Exchange 2003- und Exchange 2007-Versionen finden Sie unter Upgrade to Exchange 2010.
Wenn Sie über Active Directory-Standorte verfügen, in denen sowohl Exchange 2003 als auch Exchange 2007 installiert ist, folgen Sie den Upgradeanweisungen für Exchange 2003 und Exchange 2007, und führen Sie die für beide Versionen erforderlichen Upgradeschritte aus. Weitere Informationen zu einem Upgrade auf Exchange 2010 in diesem Szenario finden Sie unter den folgenden Themen:
Exchange Server 2003 uses Administrative Groups to organize Exchange objects for the purposes of delegating permission to manage those objects. Exchange 2010 does not use Administrative Groups as a logical management unit for administrative delegation. However, to support coexistence between Exchange Server 2003 and Exchange 2010, all Exchange 2010 servers are automatically put in a single Administrative Group when Exchange 2010 is installed. This Administrative Group is recognized in the Exchange System Manager of earlier versions of Exchange as Exchange Administrative Group (FYDIBOHF23SPDLT).
|Do not move Exchange 2010 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) and do not rename Exchange Administrative Group (FYDIBOHF23SPDLT) by using a low-level directory editor. Exchange 2010 must use this administrative group for configuration data storage. We do not support moving Exchange 2010 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) or renaming of Exchange Administrative Group (FYDIBOHF23SPDLT).|
You must use the Exchange Server 2003 System Manager and utilities to manage the Exchange Server 2003 servers. In Exchange 2010, you must manage Exchange 2010 servers and mailboxes by using the Exchange Management Console or the Exchange Management Shell. However, you can use the Exchange Management Console to view some attributes on Exchange Server 2003 servers. For more information about Exchange management console interoperability, see Exchange-Verwaltungskonsole – Interoperabilität.
When you plan for a period of coexistence with Exchange 2010 and Exchange Server 2003, you must understand the differences in how each version determines its routing topology.
For more information about routing and coexistence, see Upgrade des Exchange 2003-Transports.
The Client Access server role provides the functionality that was provided by a front-end server in Exchange 2003 and more. All client connectivity (including Outlook MAPI connectivity) now goes through the Client Access server role. There are no longer any clients directly connecting to the mailbox server role. The Client Access server role can coexist with Exchange Server 2003 servers. The following list describes the Exchange 2010 dependencies and requirements for coexistence with Exchange Server 2003.
Whether a user sees the Outlook Web Access client of Exchange Server 2003 or Exchange 2010 depends on the location of the user's mailbox. For example, if the user's mailbox is located on an Exchange Server 2003 back-end server and the Client Access server is running Exchange 2010, the user will see the Exchange Server 2003 version of Outlook Web Access.
The version of Exchange ActiveSync that clients use also depends on the server version that is hosting the user's mailbox. The user's mailbox must be located on a server that is running Exchange Server 2003 Service Pack 2 or Exchange 2010 to have Direct Push enabled for Exchange ActiveSync.
When you perform a upgrade from Exchange Server 2003 to Exchange 2010, you will typically upgrade all the Exchange servers in a particular routing group or Active Directory site to Exchange 2010 at the same time, configure coexistence, and then upgrade the next site.
Wichtig: When upgrading an Exchange 2003 organization, an Exchange 2003 Front End server is required in order to support the upgrade. For each Exchange 2010 Client Access server, you can only configure one Outlook Web Access 2003 URL for redirection. You can accomplish this with a single Exchange 2003 Front End server or a load balanced array of Exchange 2003 Front End servers.
Exchange 2007 introduced the Autodiscover and Availability services. The Autodiscover service configures client computers that are running Outlook 2007, Outlook 2010, Entourage, and other client applications. The Autodiscover service can also configure supported mobile devices. The Autodiscover service provides access to Microsoft Exchange features for Outlook 2007 and later clients that are connected to your Microsoft Exchange messaging environment. The Availability service improves information workers' calendaring and meeting scheduling experience by providing secure, consistent, and up-to-date free and busy information to computers running Outlook 2007 and later. For more information about the Autodiscover service, see Grundlegendes zum AutoErmittlungsdienst. For more information about the Availability service, see Grundlegendes zum Verfügbarkeitsdienst. For more information about Client Access server coexistence between Exchange Server 2003 and Exchange 2010, and new Exchange 2010 features, see Upgrade von Exchange 2003 für den Clientzugriff.
The Hub Transport server role is designed to handle all mail flow for the Exchange organization. It is also responsible for handling Transport Rules, Journaling policies and message delivery. This server is deployed in the Active Directory forest and is required for Exchange 2010 mailboxes to send and receive messages. Messages that are sent to the Internet are relayed by the Hub Transport server to the Edge Transport server or a third-party smart host.
You can add an Exchange 2010 Hub Transport server to an existing Exchange organization after you successfully deploy Exchange 2010 CAS servers. When you introduce Exchange 2010 Hub servers in your Exchange 2003 environment, all Exchange 2010 Hub servers are placed in a single separate routing group. To enable mail flow between the Exchange 2010 deployment and your existing Exchange 2003 organization, you need to create a Routing Group connector. This Routing Group connector is created during the setup of your first Exchange 2010 Hub Transport server.
To learn more about introducing Exchange 2010 Hub Transport servers to your Exchange 2003 organization, see Upgrade des Exchange 2003-Transports.
The Mailbox server role can coexist with Exchange Server 2003 mailbox servers. For Exchange 2010 and Exchange Server 2003 mailbox servers to coexist, you must be able to send mail among the mailboxes. Exchange 2010 uses the Hub Transport server to send mail. An Exchange 2010 Hub Transport server must be deployed in each Active Directory site that contains an Exchange 2010 Mailbox server. You also need a Client Access server in each Active Directory site where there is a Mailbox server. For more information about the upgrading to Exchange 2010 Mailbox Server, see Upgrading from Exchange 2003 Mailbox.
If you move a mailbox from Exchange Server 2003 to Exchange 2010, and the mailbox is part of an e-mail address policy, the e-mail addresses for that mailbox is automatically updated based on the configuration of the e-mail address policy. If the mailbox had a primary SMTP address that differs from the e-mail address that is enforced by the e-mail address policy, that SMTP address becomes a secondary SMTP address and the e-mail address generated by the e-mail address policy becomes the primary SMTP address. For information about how to move mailboxes, see Verwalten von Verschiebungsanforderungen.
You can replicate public folder data between Exchange 2010 and Exchange Server 2003 public folder databases. To do this, you must create a replica of the public folder using the Exchange Server 2003 System Manager. For more information about Exchange 2010 and Exchange Server 2003 public folder coexistence, see Grundlegendes zu Öffentlichen Ordnern.
The Edge Transport server role is designed to provide improved antivirus and anti-spam protection for the Exchange organization. The Edge Transport server also applies policies to messages in transport between organizations. This server role is deployed in the perimeter network and outside the Active Directory forest. The Edge Transport server can be deployed as a smart host and SMTP-relay server for an existing Exchange Server 2003 organization.
You can add an Edge Transport server to an existing Exchange organization without upgrading the internal Exchange servers or making any organizational changes. You do not have to perform any Active Directory preparation steps when you install the Edge Transport server. If you are using the Exchange Intelligent Message Filter in Exchange Server 2003 to perform anti-spam tasks, you can use the Edge Transport server to provide an additional layer of anti-spam protection. The Edge Transport server provides antivirus and anti-spam protection as messages enter the network.
When an Edge Transport server is deployed to support an Exchange organization that has not yet deployed Exchange 2010, a limited set of features are available. You can't create an Edge Subscription in this scenario. Therefore, you can't use the Recipient Lookup or safelist aggregation features. For more information about Edge Transport servers and coexistence, see Upgrade des Exchange 2003-Transports.
The Unified Messaging server role is designed to provide Unified Messaging (UM) for Exchange 2010 recipients. UM combines voice messaging, and e-mail messaging into one store that can be accessed from a telephone, a user's computer, and a mobile device. Users can access voice messages, e-mail, and calendar information that are located in their Exchange 2010 mailbox from e-mail clients, such as Outlook and Outlook Web Access.
The Unified Messaging server depends on the Hub Transport server and Mailbox server. All SMTP mail submitted from a Unified Messaging server must be submitted to an Exchange 2010 Hub Transport server. For a recipient to use Unified Messaging, they must have an Exchange 2010 mailbox.
Exchange 2010 supports the following topologies:
Single forest, multiple Active Directory sites.
Multiple forests (resource forest model), multiple Active Directory sites.
Single Active Directory site.
Exchange 2010 doesn't support the following topologies:
Coexistence with Exchange 2000 server or earlier.
Coexistence with Exchange 2003 versions prior to Service Pack 2 (SP2).
Installing older version of Exchange into a newly created Exchange 2010 organization.
For more information about deploying in these topologies, see Deploy Multiple Forest Topologies.
Möchten Sie an der Umfrage teilnehmen?