Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010

Module Overview Overview of Upgrading to Exchange Server 2010 Upgrading from Exchange Server 2003 to Exchange Server 2010 Upgrading from Exchange Server 2007 to Exchange Server 2010

Lesson 1: Overview of Upgrading to Exchange Server 2010 Upgrade Options for Exchange Server Supported Upgrade Scenarios Upgrade Strategies Migration Preparation Tools

Upgrade Options for Exchange Server Upgrade An upgrade of an existing Exchange organization to Exchange Server 2010 in which you move data and functionality from the existing Exchange servers to new Exchange Server 2010 servers Migration Replacing a non-Exchange messaging system with Exchange Server 2010 or replacing an existing Exchange organization with a new Exchange organization, without retaining any of the configuration data In-place upgrade is not supported for Exchange Server 2010 Upgrade is recommended whenever possible

Supported Upgrade Scenarios Exchange Server VersionExchange Server Organization Upgrade Exchange 2000 ServerNot supported Exchange Server 2003 with SP2 or newer Supported Exchange Server 2007 with SP2 or newer Supported Mixed Exchange Server 2003 and Exchange Server 2007 Supported Active Directory requirements: Schema master must be running Windows Server 2003 SP1 or newer At least one global catalog server running Windows Server 2003 SP1 or newer in each site Windows Server 2003 forest and domain functional level

Upgrade Strategies Single-phase upgrade: Replaces existing messaging system Moves required data and functionality to the new system without configuring integration between the two systems Has no period of coexistence or interoperability Multiphase upgrade with coexistence: Upgrades one server or site at a time Enables an incremental upgrade spread over a longer period of time Decreases risk for the organization

Migration Preparation Tools The migration preparation tools are: Exchange Deployment Assistant: Web-based tool that helps deploy Exchange Server in the cloud and on-premise Exchange Pre-Deployment Analyzer: Identifies issues that can prevent Exchange Server installation Exchange 2010 Mailbox Server Role Requirements Calculator: Excel-based tool that helps with Mailbox server configuration Exchange Server Best Practices Analyzer: Checks compliance against Microsoft best practices

Lesson 2: Upgrading from Exchange Server 2003 to Exchange Server 2010 Preparing the Exchange Server 2003 Organization for Exchange Server 2010 Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization How Client Access Works During Coexistence Implementing Client Access Coexistence Considerations for Outlook Client Coexistence Considerations for Message Transport Coexistence Considerations for Administration Coexistence Completing the Migration Process for Removing Exchange Server 2003 from the Organization

Preparing the Exchange Server 2003 Organization for Exchange Server 2010 The PrepareAD command creates the following groups to enable coexistence between Exchange Server versions: Active Directory universal security group ExchangeLegacyInterop Exchange Server 2010 Administrative group Exchange Server 2010 Routing group After updating the Active Directory schema for Exchange Server 2010, run Setup with the PrepareLegacyExchangePermissions parameter to ensure that the Recipient Update Service functions correctly

Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization Deploy Exchange Server 2010 server roles in the following order: Client Access servers 1 1 Mailbox servers 3 3 Unified Messaging servers 4 4 Hub Transport servers 2 2 Deploy Edge Transport servers at any time Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time Deploy Edge Transport servers at any time Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time

How Client Access Works During Coexistence Outlook Anywhere client Outlook Anywhere client Exchange 2003 front-end server Exchange 2003 front-end server Outlook Web Access client Outlook Web Access client Exchange Server 2010 Exchange Server 2010 Exchange Server 2003 Exchange Server 2003 HTTP Outlook RPC Outlook RPC Exchange ActiveSync client Exchange ActiveSync client Exchange Server 2010 Exchange Server 2010 RPC External URL: External URL: HTTP

Implementing Client Access Coexistence To implement client access coexistence: Obtain the required server certificates 1 1 Install and configure the Exchange 2010 Client Access server Configure DNS Remove the Exchange 2003 from the RPC over HTTP configuration Test all client access scenarios

Considerations for Outlook Client Coexistence Consider the following for Outlook client access coexistence: Retain system folders for free/busy information Retain system folders and publication points for offline address book access Replicate public folders to Exchange Server 2010 mailbox servers if required Be aware of Outlook 2003 connection issues with Exchange Server 2010

Considerations for Message Transport Coexistence Consider the following for message transport coexistence: Exchange Server 2010 does not use routing groups All Exchange Server 2010 computers are installed in a single Exchange Server routing group A routing group connector is created by default when you specify a bridgehead server at the time the first Hub Transport server is installed If you have multiple routing groups: Disable link-state routing table updates Create additional routing group connectors

Considerations for Administration Coexistence Exchange 2003 Administration Exchange Server 2010 Equivalent Assign Exchange Server Full Administrator role at the organization level Add users or groups to the Exchange Organization Administrators role group Assign Exchange Server Administrator role at the organization level No Exchange Administrator role group equivalent, so create a management role group with restricted permissions Assign Exchange Server View Administrator role at the organization level Add users or groups to the Exchange View-Only Administrators role group Assign Exchange Server Full Administrator at the administrative group level Create a management role group with a limited scope

Completing the Migration Before you remove Exchange Server 2003 from your organization, make sure that you: Upgrade address policies Upgrade address list objects Modify message routing infrastructure Create Send connector Set authentication options on receive connector

Process for Removing Exchange Server 2003 from the Organization Remove Exchange Server 2003 servers in the following order: Back-end servers Front-end servers Bridgehead servers Retain Exchange Server 2003 servers if functionality is required Remove all mailboxes and connectors from the Exchange Server 2003 servers before decommissioning the servers

Lesson 3: Upgrading from Exchange Server 2007 to Exchange Server 2010 Process for Installing Exchange Server 2010 in an Exchange Server 2007 Organization How Client Access Works During Coexistence Implementing Client Access Coexistence Considerations for Message Transport Coexistence Considerations for Administration Coexistence Process for Removing Exchange Server 2007 from the Organization

Process for Installing Exchange Server 2010 in an Exchange Server 2007 Organization Deploy Exchange Server 2010 server roles in the following order: Client Access servers Unified Messaging servers Mailbox servers Hub Transport servers Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time Update all Exchange Server 2007 computers to Exchange Server 2007 with SP2 Edge Transport servers

How Client Access Works During Coexistence Outlook Anywhere client Outlook Anywhere client Exchange Server 2007 RPC External URL: $null Exchange 2007 SP2 Exchange Server 2010 Exchange Server 2010 Exchange Server 2010 Exchange ActiveSync client Exchange ActiveSync client Outlook Web Access client Outlook Web Access client RPC Exchange 2007 SP2 Exchange Server 2007 RPC HTTPS Exchange ActiveSync /WS Proxy HTTPS Outlook Web Access /Exchange ActiveSync /WS Proxy OutlookRPC OutlookRPC

Implementing Client Access Coexistence To implement client access coexistence: Obtain the required server certificates Install and configure the Exchange 2010 Client Access server Configure DNS Test all client access scenarios Modify the external URL for the Exchange 2007 Client Access server

Considerations for Message Transport Coexistence Consider the following for message transport coexistence: Exchange Server 2007 Mailbox servers require Exchange Server 2007 Hub Transport servers Exchange Server 2007 Hub and Edge Transport servers can coexist with Exchange Server 2010 Hub and Edge Transport servers

Considerations for Administration Coexistence Consider the following for administration coexistence: In Exchange Server 2010, you can assign users to the Exchange Server Security role groups, or configure custom role groups Exchange Server 2007 administration delegation is based on Exchange Server Security groups or on Exchange Server level delegation The Exchange Management Console for each version can be used to manage some settings for both versions Some tasks require the specific version of Exchange Management Console

Process for Removing Exchange Server 2007 from the Organization Remove Exchange Server 2007 servers in the following order: Mailbox servers Hub Transport servers Unified Messaging servers Remove all mailboxes and connectors from the Exchange Server 2007 servers before decommissioning the servers Client Access servers

Module Review and Takeaways Review Questions Common Issues and Troubleshooting Tips Real-World Issues and Scenarios Best Practices Tools

Notes Page Over-flow Slide. Do Not Print Slide. See Notes pane.