10135 b 12

495 views

Published on

  • Be the first to comment

  • Be the first to like this

10135 b 12

  1. 1. Module 12 Upgrading fromExchange Server 2003 orExchange Server 2007 to Exchange Server 2010
  2. 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. 3. Lesson 1: Overview of Upgrading toExchange Server 2010• Upgrade Options for Exchange Server• Supported Upgrade Scenarios• Upgrade Strategies• Migration Preparation Tools
  4. 4. Upgrade Options for Exchange Server • An upgrade of an existing Exchange organization to Exchange Server 2010 in which you move data andUpgrade functionality from the existing Exchange servers to new Exchange Server 2010 servers • Replacing a non-Exchange messaging system with Exchange Server 2010 or replacing an existing ExchangeMigration organization with a new Exchange organization, without retaining any of the configuration dataUpgrade is recommended whenever possibleIn-place upgrade is not supported for Exchange Server 2010
  5. 5. Supported Upgrade ScenariosActive 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 levelExchange Server Version Exchange 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. 6. Upgrade Strategies Single-phase upgrade: Multiphase upgrade with coexistence: • Replaces existing • Upgrades one server messaging system or site at a time • Moves required data • Enables an and functionality to incremental upgrade the new system spread over a longer without configuring period of time integration between the two systems • Decreases risk for the organization • Has no period of coexistence or interoperability
  7. 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. 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. 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 group ExchangeLegacyInterop • Exchange Server 2010 Administrative group • Exchange Server 2010 Routing group
  10. 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. 11. How Client Access Works During Coexistence Exchange Outlook Web ActiveSync client Outlook Access client Anywhere clientExchange 2003 Exchangefront-end server Server 2010 HTTP RPC HTTP Outlook Exchange RPC Exchange Server 2003 Server 2010 External URL: https://legacy.contoso.com https://mail.contoso.com
  12. 12. Implementing Client Access CoexistenceTo implement client access coexistence: 1 Obtain the required server certificates Install and configure the Exchange 2010 Client Access 2 server 3 Configure DNS Remove the Exchange 2003 from the RPC over HTTP 4 configuration 5 Test all client access scenarios
  13. 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. 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. 15. Considerations for Administration CoexistenceExchange 2003 Exchange 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 the equivalent, so create a managementorganization level role group with restricted permissionsAssign Exchange Server Add users or groups to the ExchangeView Administrator role View-Only Administrators role groupat the organization levelAssign Exchange Server Create a management role group withFull Administrator at the a limited scopeadministrative grouplevel
  16. 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. 17. Process for Removing Exchange Server 2003from the Organization• Remove all mailboxes and connectors from the Exchange Server 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 is required
  18. 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. 19. Process for Installing Exchange Server 2010 in anExchange Server 2007 Organization • Update all Exchange Server 2007 computers to Exchange Server 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. 20. How Client Access Works During Coexistence Outlook Anywhere client Exchange Outlook WebActiveSync client Access client Exchange Exchange 2007 SP2 Server 2010 Exchange 2007 SP2 HTTPS HTTPS Exchange ActiveSync Outlook Web Access /WS Proxy /Exchange ActiveSync /WS Proxy RPC RPC RPC Outlook RPC Outlook RPC Exchange Server 2007 Exchange Server 2010 Exchange Server 2007 https://legacy.contoso.com https://mail.contoso.com External URL: $null
  21. 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. 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. 23. Considerations for Administration CoexistenceConsider the following for administration coexistence: 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 administration delegation is based on Exchange Server Security groups or on Exchange Server level delegation In Exchange Server 2010, you can assign users to the Exchange Server Security role groups, or configure custom role groups
  24. 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. 25. Module Review and Takeaways• Review Questions• Common Issues and Troubleshooting Tips• Real-World Issues and Scenarios• Best Practices• Tools

×