1. Module 12Upgrading fromExchange Server 2003 orExchange
Server 2007 toExchange Server 2010
2. 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 3.
Lesson 1: Overview of Upgrading toExchange Server 2010 Upgrade
Options for Exchange Server Supported Upgrade Scenarios Upgrade
Strategies Migration Preparation Tools 4. Upgrade Options for
Exchange Server An upgrade of an existing Exchange organization
toExchange Server 2010 in which you move data
andUpgradefunctionality from the existing Exchange servers to
newExchange Server 2010 servers Replacing a non-Exchange messaging
system withExchange Server 2010 or replacing an existing
ExchangeMigration organization with a new Exchange organization,
withoutretaining any of the configuration dataUpgrade is
recommended whenever possibleIn-place upgrade is not supported for
Exchange Server 2010 5. Supported Upgrade ScenariosActive Directory
requirements: Schema master must be running Windows Server 2003SP1
or newer At least one global catalog server running WindowsServer
2003 SP1 or newer in each site Windows Server 2003 forest and
domain functionallevelExchange Server VersionExchange Server
Organization UpgradeExchange 2000 Server Not supportedExchange
Server 2003 with SP2 or SupportednewerExchange Server 2007 with SP2
or SupportednewerMixed Exchange Server 2003 and SupportedExchange
Server 2007 6. Upgrade Strategies Single-phase upgrade: Multiphase
upgrade with coexistence: Replaces existing Upgrades one
servermessaging system or site at a time Moves required data
Enables anand functionality to incremental upgradethe new system
spread over a longerwithout configuringperiod of timeintegration
betweenthe two systems Decreases risk for the organization Has no
period ofcoexistence orinteroperability 7. Migration Preparation
ToolsThe migration preparation tools are: Exchange Server Best
Practices Analyzer: Checks compliance against Microsoft best
practices 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 8. Lesson 2: Upgrading from Exchange Server
2003to 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 9. Preparing
the Exchange Server 2003Organization for Exchange Server 2010After
updating the Active Directory schema forExchange Server 2010, run
Setup with thePrepareLegacyExchangePermissions parameter to
ensurethat the Recipient Update Service functions correctlyThe
PrepareAD command creates the following groups toenable coexistence
between Exchange Server versions: Active Directory universal
security groupExchangeLegacyInterop Exchange Server 2010
Administrative group Exchange Server 2010 Routing group 10. Process
for Installing Exchange Server 2010 in anExchange Server 2003
OrganizationDeploy Exchange Server 2010 server roles in the
followingorder: 1 Client Access servers 2 Hub Transport servers 3
Mailbox servers 4 Unified Messaging servers Deploy Edge Transport
servers at any time Upgrade Internet-accessible Active Directory
sites first Implement the upgrade one Active Directory site at a
time 11. How Client Access Works During Coexistence ExchangeOutlook
Web ActiveSync clientOutlookAccess client Anywhere clientExchange
2003 Exchangefront-end server Server 2010HTTPRPCHTTP Outlook
ExchangeRPCExchangeServer 2003Server 2010External URL:
https://legacy.contoso.com https://mail.contoso.com 12.
Implementing Client Access CoexistenceTo implement client access
coexistence:1 Obtain the required server certificatesInstall and
configure the Exchange 2010 Client Access2 server3 Configure
DNSRemove the Exchange 2003 from the RPC over HTTP4 configuration5
Test all client access scenarios 13. Considerations for Outlook
Client CoexistenceConsider 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 14. Considerations for Message Transport
CoexistenceConsider 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 15. Considerations for Administration
CoexistenceExchange 2003Exchange Server 2010
EquivalentAdministrationAssign Exchange Server Add users or groups
to the ExchangeFull Administrator role at Organization
Administrators role groupthe organization levelAssign Exchange
Server No Exchange Administrator role groupAdministrator role at
theequivalent, so create a managementorganization level role group
with restricted permissionsAssign Exchange Server Add users or
groups to the ExchangeView Administrator roleView-Only
Administrators role groupat the organization levelAssign Exchange
Server Create a management role group withFull Administrator at
thea limited scopeadministrative grouplevel 16. Completing the
MigrationBefore you remove Exchange Server 2003 from
yourorganization, make sure that you: Upgrade email address
policies Upgrade address list objects Modify message routing
infrastructure Create Send connector Set authentication options on
receive connector 17. Process for Removing Exchange Server 2003from
the Organization Remove all mailboxes and connectors from the
ExchangeServer 2003 servers before decommissioning the
serversRemove Exchange Server 2003 servers in the following order:
1 Back-end servers 2 Bridgehead servers 3 Front-end servers Retain
Exchange Server 2003 servers if functionality isrequired 18. Lesson
3: Upgrading from Exchange Server 2007to 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 19.
Process for Installing Exchange Server 2010 in anExchange Server
2007 Organization Update all Exchange Server 2007 computers to
ExchangeServer 2007 with SP2Deploy Exchange Server 2010 server
roles in the followingorder: 1 Client Access servers 2 Hub
Transport servers 3 Unified Messaging servers 4 Mailbox servers 5
Edge Transport servers Upgrade Internet-accessible Active Directory
sites first Implement the upgrade one Active Directory site at a
time 20. How Client Access Works During Coexistence OutlookAnywhere
client Exchange Outlook WebActiveSync client Access client Exchange
Exchange 2007 SP2Server 2010Exchange 2007 SP2 HTTPS HTTPSExchange
ActiveSyncOutlook Web Access /WS Proxy/Exchange ActiveSync/WS
ProxyRPCRPC RPCOutlookRPC OutlookRPCExchange Server 2007Exchange
Server 2010Exchange Server
2007https://legacy.contoso.comhttps://mail.contoso.com External
URL: $null 21. Implementing Client Access CoexistenceTo implement
client access coexistence: 1 Obtain the required server
certificates Install and configure the Exchange 2010 Client Access
2 server Modify the external URL for the Exchange 2007 Client 3
Access server 4 Configure DNS 5 Test all client access scenarios
22. Considerations for Message Transport CoexistenceConsider 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 23.
Considerations for Administration CoexistenceConsider the following
for administration coexistence:The Exchange Management Console for
each version canbe used to manage some settings for both
versionsSome tasks require the specific version of
ExchangeManagement ConsoleExchange Server 2007 administration
delegation isbased on Exchange Server Security groups or onExchange
Server level delegationIn Exchange Server 2010, you can assign
users to theExchange Server Security role groups, or
configurecustom role groups 24. Process for Removing Exchange
Server 2007from the Organization Remove all mailboxes and
connectors from the Exchange Server 2007 servers before
decommissioning the serversRemove Exchange Server 2007 servers in
the following order: 1 Mailbox servers 2 Unified Messaging servers
3 Hub Transport servers 4 Client Access servers 25. Module Review
and Takeaways Review Questions Common Issues and Troubleshooting
Tips Real-World Issues and Scenarios Best Practices Tools
