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
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
An upgrade of a computer running a previous Exchange Server version to a newer version of Exchange software on a single computer (not supported in Exchange Server 2010)
Upgrade is recommended whenever possibleUpgrade is recommended whenever possible
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:
• Schema master must be running Windows Server 2003 SP2 or newer
• At least one global catalog server running Windows Server 2003 SP2 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
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
• 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
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 servers11
Mailbox servers33
Unified Messaging servers 44
Hub Transport servers22
• 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 serverExchange 2003 front-end server
Outlook Web Access clientOutlook Web Access client
Exchange Server 2010Exchange
Server 2010
Exchange Server 2003Exchange
Server 2003
HTTPHTTP
Outlook RPC
Outlook RPC
Exchange ActiveSync client
Exchange ActiveSync client
Exchange Server 2010Exchange
Server 2010
RPCRPC
https://legacy.contoso.com https://legacy.contoso.com External URL:
https://mail.contoso.comExternal URL:
https://mail.contoso.com
HTTPHTTP
Implementing Client Access Coexistence
To implement client access coexistence:
Obtain the required server certificates11
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
22
33
44
55
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
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
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
• 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 servers
• 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
11
33
22
44
55
How Client Access Works During Coexistence
Outlook Anywhere client
Outlook Anywhere client
Exchange Server 2007Exchange Server 2007
RPCRPC
External URL: $nullExternal URL: $nullhttps://legacy.contoso.comhttps://legacy.contoso.com
Exchange 2007 SP2Exchange 2007 SP2Exchange
Server 2010Exchange
Server 2010
Exchange Server 2010Exchange Server 2010
Exchange ActiveSync client
Exchange ActiveSync client
Outlook Web Access clientOutlook Web Access client
RPCRPC
Exchange 2007 SP2Exchange 2007 SP2
Exchange Server 2007Exchange Server 2007
RPCRPC
HTTPSHTTPS
https://mail.contoso.comhttps://mail.contoso.com
Exchange ActiveSync/WS Proxy
Exchange ActiveSync/WS Proxy
HTTPSHTTPS
Outlook Web Access/Exchange ActiveSync
/WS Proxy
Outlook Web Access/Exchange ActiveSync
/WS Proxy
Outlook RPC
Outlook RPC Outlook
RPCOutlook
RPC
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 33
22
11
44
55
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 serversRemove all mailboxes and connectors from the Exchange Server 2007 servers before decommissioning the servers
Client Access servers44
33
11
22
Module Review and Takeaways
• Review Questions
• Common Issues and Troubleshooting Tips
• Real-World Issues and Scenarios
• Best Practices
• Tools
Course Evaluation
Top Related