Module 11

Upgrading to Microsoft® Exchange Server 2010

Module Overview

• Overview of Upgrading to Exchange Server 2010

• Planning the Upgrade from Exchange Server 2003 to Exchange Server 2010

• Planning the Upgrade from Exchange Server 2007 to Exchange Server 2010

Lesson 1: Overview of Upgrading to Exchange Server 2010

• Supported Upgrade Scenarios

• Choosing an Upgrade Strategy

• Components of a Coexistence and Upgrade Strategy

• Planning a Multi-Site Upgrade

• Options for Supporting Deprecated Features

Supported Upgrade Scenarios

Exchange Server version Exchange Server organization upgrade

Exchange 2000 Server Not 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:• Windows Server 2003 SP1 global catalog servers

• Windows Server 2003 forest and domain functional level

Choosing an Upgrade Strategy

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 location or site at a time

• Enables an incremental upgrade spread over a longer period of time

• Decreases risk for the organization

• May require an extended period of coexistence

Components of a Coexistence and Upgrade Strategy

During the upgrade, you must ensure:

• Public folder contents are accessible• Message delivery is not interrupted • Global address list includes all recipients• Meeting Free/Busy information is available

• Exchange administration is not affected

Planning a Multi-Site Upgrade

Upgrade Internet-facing sites first

Deploy all required Exchange Server 2010 server roles in Internet-facing sites before deploying roles in non Internet-facing sites

Complete the upgrade in one site before starting the upgrade on the next site

Options for Supporting Deprecated Features

Previous Exchange Server versions included options that are not available in Exchange Server 2010Previous Exchange Server versions included options that are not available in Exchange Server 2010

Exchange Server 2003 features not supported in Exchange Server 2010:

• Novell GroupWise connector

• NNTP

• Office Outlook Mobile Access

• Inter-Organization Replication Tool

Exchange Server 2007 features not supported in Exchange Server 2010:

• SCC, LCR, CCR and SCR

• Microsoft Transporter Suite for Lotus Domino

• Programmatic access to Exchange by using ExOLEDB, WebDAV, or CDOEX

Lesson 2: Planning the Upgrade from Exchange Server 2003 to Exchange Server 2010

• Prerequisites for Installing Exchange Server 2010 in an Exchange Server 2003 Organization

• Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization

• Designing the Client Access Server Upgrade

• Designing the Client Services Coexistence

• Designing the Message Transport Upgrade

• Designing the Upgrade of Administrative Roles

• Planning Exchange 2003 Servers Removal

• Troubleshooting the Exchange Server 2010 Upgrade

Prerequisites for Installing Exchange Server 2010 in an Exchange Server 2003 Organization

• Schema master and at least one global catalog server in each site must be running Windows Server 2003 (SP1) or newer

• Domain and forest functional levels must be at least Windows Server 2003

• Exchange Server 2003 servers must be running Exchange Server 2003 SP2

• Exchange organization must be in native mode

Setup parameters DescriptionPrepareLegacyExchangePermissions

Required to ensure that the Recipient Update Service functions correctly

PrepareSchema Prepares the schema for the Exchange Server 2010 installation

PrepareAD • Creates the global Exchange objects

• Creates the Exchange universal security groups in the root domain

• Prepares the current domain

Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization

Deploy Exchange Server 2010 server roles in the following order:

Client Access servers11

Mailbox servers33

Unified Messaging servers 44

Hub Transport servers22

Upgrade Internet-facing accessible sites firstUpgrade Internet-facing accessible sites first

Designing the Client Access Server Upgrade

To implement client access coexistence:

Client requests may be:

• Redirected to Exchange 2003 servers (Outlook Web App)

• Proxied to Exchange 2003 servers (Exchange ActiveSync, Outlook Anywhere, POP3/IMAP4)

• Configure Autodiscover to use Exchange Server 2010 Client Access servers

• Obtain SSL certificates with current and legacy server names

• Configure external DNS and firewall or reverse proxy access

• Configure the Exchange2003URL parameter

During coexistence, Office Outlook 2007 or newer clients are configured by Exchange 2010 AutodiscoverDuring coexistence, Office Outlook 2007 or newer clients are configured by Exchange 2010 Autodiscover

Designing the Client Services Coexistence

Consider the following for client services 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

Plan for Client Access Server capacity

Enable external access to new Exchange Server virtual directories

Designing the Message Transport Upgrade

To upgrade external connectivity:

• Replace Exchange 2003 bridgehead servers with Exchange Server 2010 Hub Transport servers

• Configure Exchange Server 2010 Send connectors with lower costs

• Implement an Edge Transport server

If you have multiple routing groups:

• Disable link-state routing table updates

• Create additional routing group connectors

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

Designing the Upgrade of Administrative Roles

Exchange Server 2003 administration assignment options

Exchange Server 2010 equivalent

Exchange Server Full Administrator role at the organization level

Add users or groups to the Exchange Organization Administrators role group

Exchange Server Administrator role at the organization level

No Exchange Server Administrator role group equivalent, so create a management role group with restricted permissions

Exchange Server View Administrator role at the organization level

Add users or groups to the Exchange View-Only Administrators-role group

Exchange Server Full Administrator role at the administrative group level

Create a management role group with a limited scope

Exchange Server View Administrator role at the administrative group level

Create a new role group with View-Only permissions and a limited scope

Recipient administrators with Exchange View Administrator role and Active Directory permissions

Add users and groups to the Exchange Recipient Administrator role group

Planning the Removal of Exchange 2003 Servers

Remove Exchange Server 2003 servers in the following order:

back end servers

front end servers

Bridgehead servers

• Consider removing Exchange 2003 servers incrementally as you move mailboxes

• Retain Exchange Server 2003 servers if functionality is required

• Consider removing Exchange 2003 servers incrementally as you move mailboxes

• Retain Exchange Server 2003 servers if functionality is required

11

22

33

Remove all mailboxes and connectors from the Exchange Server 2003 servers before decommissioning the serversRemove all mailboxes and connectors from the Exchange Server 2003 servers before decommissioning the servers

Troubleshooting the Exchange Server 2010 Upgrade

Common installation problems and solutions:

Incorrect DNS configuration

Incorrect forest or domain functional level

Insufficient Active Directory permissions

Insufficient Exchange Server permissions

Missing software components

• Try re-installing the server role

• If necessary, roll back Active Directory to a point prior to the upgrade

• Try re-installing the server role

• If necessary, roll back Active Directory to a point prior to the upgrade

If you experience problems while deploying server roles:

Lesson 3: Planning the Upgrade from Exchange Server 2007 to Exchange Server 2010

• Prerequisites for Installing Exchange Server 2010 in an Exchange Server 2007 Organization

• Process for Installing Exchange Server 2010 in an Exchange Server 2007 Organization

• Designing the Client Access Server Upgrade

• Designing the Message Transport Upgrade

• Designing the Administrative Roles Upgrade

• Planning Exchange 2007 Servers Removal

• Troubleshooting the Exchange 2010 Upgrade

Prerequisites for Installing Exchange Server 2010 in an Exchange Server 2007 Organization

• The schema master and at least one global catalog server in each site must be running Windows Server 2003 (SP1) or newer

• Domain and forest functional levels must be at least Windows 2003

• Exchange Server 2003 servers must be running Exchange Server 2003 SP2

Setup parameters Description

PrepareSchema Prepares the schema for the Exchange Server 2010 installation

PrepareAD • Creates the global Exchange Server objects

• Creates the Exchange Server universal security groups in the root domain

• Prepares the current domain

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

Mailbox servers

Unified Messaging servers

Hub Transport servers

Update all Exchange Server 2007 computers to Exchange Server 2007 SP2Update all Exchange Server 2007 computers to Exchange Server 2007 SP2

Edge Transport servers

11

33

22

44

55

Designing the Client Access Server Upgrade

To implement client access coexistence:

• Obtain the required server certificates

• Install and configure the Exchange Server 2010 Client Access server

• Modify the external URLs

• Configure external DNS and firewall/reverse proxy

• Disable Outlook Anywhere on the Exchange Server 2007 Client Access server

Designing the Message Transport Upgrade

Consider the following for message transport coexistence:

Exchange Server 2007 Mailbox servers require Exchange Server 2007 Hub Transport servers in the same Active Directory site

Exchange Server 2007 Hub and Edge Transport servers can coexist with Exchange Server 2010 Hub and Edge Transport servers

Edge subscriptions must be reconfigured during an Edge Transport server upgrade

Remove the last Exchange Server 2007 Hub Transport server only after removing all mailbox and public folders from Exchange Server 2007 Mailbox servers

Designing the Administrative Roles Upgrade

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

Exchange Server 2007 security groups are upgraded to Exchange Server 2010 management role groups during the upgrade

Planning Exchange 2007 Servers Removal

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 serversRemove all mailboxes and connectors from the Exchange Server 2007 servers before decommissioning the servers

Client Access servers44

33

11

22

Troubleshooting the Exchange Server 2010 Upgrade

Common installation problems and solutions:

Attempt to re-deploy server roles that fail

If required, roll back AD DS to a point prior to the upgrade

Ensure your Exchange server organization meets prerequisites

Lab: Upgrading to Exchange Server 2010

• Exercise 1: Discussion: Reviewing the Exchange Server 2010 Design

• Exercise 2: Designing an Exchange Server 2010 Upgrade Strategy

Estimated time: 60 minutes

Lab Scenario

You are a messaging engineer for A. Datum Corporation, an enterprise-level organization with multiple locations. A. Datum Corporation is an international corporation involved in technology research and investment, and is planning to upgrade from Exchange Server 2003 to Exchange Server 2010.

The A. Datum Corporation headquarters and two remote locations are running Exchange Server 2003 and Office Outlook 2003. A. Datum Corporation will be adding two new locations, and within the next six months plans to migrate all existing users to Exchange Server 2010 and Office Outlook 2007. Much of the Exchange Server 2010 messaging system design is complete.

The Trey Research location continues to run a POP3/SMTP messaging system, which you need to migrate to Exchange Server 2010 and integrate with the rest of the Exchange organization. The Trey Research domain already has been deployed as a separate tree in the A. Datum forest.

Lab Review

• In exercise 2, you identify the steps required to upgrade the organization to Exchange Server 2010. The first step is to prepare the Schema. What command would you use to perform this task?

• Which permissions would you need to prepare the schema?

Module Review and Takeaways

• Review Questions

• Common Issues and Troubleshooting Tips

• Best Practices