Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

10135 a 12

•Download as PPT, PDF•
•
Bố Su
Bố Su

This document provides an overview of upgrading Exchange Server organizations from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010. It discusses the different upgrade options and supported scenarios. It also outlines the processes for installing Exchange Server 2010, implementing coexistence between the server versions, and removing the legacy servers from the organization. Considerations are provided for client access, message transport, and administration during the upgrade and coexistence phases.

1 of 25
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 is recommended whenever possible 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)
Supported Upgrade Scenarios 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 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
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
Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization Deploy Exchange Server 2010 server roles in the following order: Deploy Edge Transport servers at any time Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time Client Access servers 1 Mailbox servers 3 Unified Messaging servers 4 Hub Transport servers 2
How Client Access Works During Coexistence https://legacy.contoso.com External URL: https://mail.contoso.com Outlook Anywhere client Exchange 2003 front-end server Outlook Web Access client Exchange Server 2010 Exchange Server 2003 HTTP Outlook RPC Exchange ActiveSync client Exchange Server 2010 RPC HTTP
Implementing Client Access Coexistence To implement client access coexistence: Obtain the required server certificates 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 2 3 4 5
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: 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 Exchange Server 2010 does not use routing groups All Exchange Server 2010 computers are installed in a single Exchange Server routing group
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 1 2 3 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 Edge Transport servers 1 3 2 4 5 Update all Exchange Server 2007 computers to Exchange Server 2007 with SP2
How Client Access Works During Coexistence External URL: $null https://legacy.contoso.com HTTPS https://mail.contoso.com HTTPS Outlook Anywhere client Exchange Server 2007 RPC Exchange 2007 SP2 Exchange Server 2010 Exchange Server 2010 Exchange ActiveSync client Outlook Web Access client RPC Exchange 2007 SP2 Exchange Server 2007 RPC Exchange ActiveSync /WS Proxy Outlook Web Access /Exchange ActiveSync /WS Proxy Outlook RPC Outlook 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 3 2 1 4 5
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 4 3 1 2
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.
Course Evaluation

More Related Content

10135 a 12

  • 1. Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange 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 to Exchange Server 2010 Upgrade Options for Exchange Server Supported Upgrade Scenarios Upgrade Strategies
  • 4. Upgrade Options for Exchange Server Upgrade is recommended whenever possible 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)
  • 5. Supported Upgrade Scenarios 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 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
  • 6. 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
  • 7. 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
  • 8. 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
  • 9. Process for Installing Exchange Server 2010 in an Exchange Server 2003 Organization Deploy Exchange Server 2010 server roles in the following order: Deploy Edge Transport servers at any time Upgrade Internet-accessible Active Directory sites first Implement the upgrade one Active Directory site at a time Client Access servers 1 Mailbox servers 3 Unified Messaging servers 4 Hub Transport servers 2
  • 10. How Client Access Works During Coexistence https://legacy.contoso.com External URL: https://mail.contoso.com Outlook Anywhere client Exchange 2003 front-end server Outlook Web Access client Exchange Server 2010 Exchange Server 2003 HTTP Outlook RPC Exchange ActiveSync client Exchange Server 2010 RPC HTTP
  • 11. Implementing Client Access Coexistence To implement client access coexistence: Obtain the required server certificates 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 2 3 4 5
  • 12. 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
  • 13. Considerations for Message Transport Coexistence Consider the following for message transport coexistence: 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 Exchange Server 2010 does not use routing groups All Exchange Server 2010 computers are installed in a single Exchange Server routing group
  • 14. 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
  • 15. 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 1 2 3 Remove all mailboxes and connectors from the Exchange Server 2003 servers before decommissioning the servers
  • 16. 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
  • 17. 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 Edge Transport servers 1 3 2 4 5 Update all Exchange Server 2007 computers to Exchange Server 2007 with SP2
  • 18. How Client Access Works During Coexistence External URL: $null https://legacy.contoso.com HTTPS https://mail.contoso.com HTTPS Outlook Anywhere client Exchange Server 2007 RPC Exchange 2007 SP2 Exchange Server 2010 Exchange Server 2010 Exchange ActiveSync client Outlook Web Access client RPC Exchange 2007 SP2 Exchange Server 2007 RPC Exchange ActiveSync /WS Proxy Outlook Web Access /Exchange ActiveSync /WS Proxy Outlook RPC Outlook RPC
  • 19. 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 3 2 1 4 5
  • 20. 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
  • 21. 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
  • 22. 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 4 3 1 2
  • 23. Module Review and Takeaways Review Questions Common Issues and Troubleshooting Tips Real-World Issues and Scenarios Best Practices Tools
  • 24. Notes Page Over-flow Slide. Do Not Print Slide. See Notes pane.

Editor's Notes

  1. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A Presentation: 60 minutes After completing this module, students will be able to: Describe the general Microsoft® Exchange Server 2010 upgrade scenarios and strategies Upgrade from Microsoft Exchange Server 2003 to Exchange Server 2010 Upgrade from Microsoft Exchange Server 2007 to Exchange Server 2010 Required materials To teach this module, you need the Microsoft Office PowerPoint® file 10135A_12.ppt. Important: We recommend that you use PowerPoint 2002 or a later version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, all the features of the slides might not be displayed correctly. Preparation tasks To prepare for this module: Read all of the materials for this module. Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance. Make sure that students are aware that the Course Companion CD has additional information and resources for the module.
  2. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  3. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  4. This topic is intended to be an overview slide for lesson one. The second lesson describes how to perform a upgrade from Microsoft Exchange Server 2003 with Service Pack 2 (SP2) to Exchange Server 2010, and the third lesson focuses on how to perform a upgrade from Microsoft Exchange Server 2007 with Service Pack 2 (SP2) . Discuss the differences between a upgrade and a migration. In a upgrade, you install Exchange Server 2010 into an existing Exchange Server 2003 or Exchange Server 2007 organization. In a migration, you install Exchange Server 2010 into a new organization, and then migrate mailboxes and other objects from the current messaging system to Exchange Server 2010. Upgrades are usually easier to perform than migrations, but upgrades are limited to only Exchange Server 2003 or Exchange Server 2007 organizations. Mention that because this module covers the upgrading scenarios, it does not include a lab. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  5. Highlight the Active Directory ® Domain Services (AD DS) and Active Directory directory services requirements for performing a upgrade. All global catalog servers must be running the Windows Server ® 2003 SP2 or newer operating system, and the domain and forest functional levels must be running the Windows Server 2003 operating system or higher. Also stress that Service Pack 2 or newer is required for both Exchange Server 2003 and Exchange Server 2007 upgrades. Exchange Server 2010 setup will fail if the computers are not upgraded to SP2. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  6. As part of the overview for this module, this topic describes some of the upgrade strategies. Stress that in all but the smallest organizations, a single phase upgrade is not feasible. This means that in most upgrades, there is a short or extended period of coexistence between the Exchange Server versions. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  7. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  8. Mention that in order for Exchange Server 2010 to coexist with Exchange Server 2003, the Active Directory permissions assigned to Exchange servers must be modified. Running Exchange Server 2010 setup with the PrepareLegacyExchangePermissions command makes this change. Mention that students do not have to run setup with the /PrepareLegacyExchangePermissions parameter if they run setup with the /PrepareAD parameter. If /PrepareLegacyExchangePermissions has not been run, /PrepareAD applies the same changes. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  9. Stress that Client Access servers must be deployed first and that all client connections must be configured to connect to the Client Access server. Mention that although Exchange Server 2003 does not use Active Directory sites for message routing, Exchange Server 2010’s dependency on Active Directory sites for options such as message routing and client access mean that you have to consider Active Directory sites during the upgrade. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  10. Use the diagram describe the different scenarios that occur when the different messaging clients connect to the Exchange environment during coexistence. Emphasize the process used by Outlook Web Access, pointing out the requirement for two different URLs so that the client request can be referred to the Exchange Server 2003 front-end server if the mailbox is located on an Exchange 2003 server. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  11. For clients other than Outlook to connect to the user mailboxes and use the single sign-on feature, the clients must be configured to use the Exchange Server 2010 Client Access server as the first point of connection. The Client Access server may then redirect the client to an Exchange Server 2003 front-end server, or it may proxy the client request to an Exchange Server 2003 front-end server. Because you can redirect client requests from the Exchange Server 2010 Client Access server to an Exchange Server 2003 server, you will need to enable Internet access for multiple URLs. Stress the importance of using server certificates that support all of the URLs. Because all clients are connecting to an Exchange Server 2010 Client Access server when the user mailboxes are moved to Exchange Server 2010, you must plan for Client Access server capacity. In previous versions of Exchange Server, the recommended deployment ratio was one Client Access server processor core for every four Mailbox server processor cores. In Exchange Server 2010, the recommended ratio is 3 to 4. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  12. Consider discussing the differences between how Exchange Server 2003 and Office Outlook versions prior to Outlook 2007 access free/busy information and the offline address book. Because the Exchange Server and client version architectures differ significantly, you must retain both the Exchange Server 2003 and the Exchange Server 2010 options for accessing this information. Also mention that you can replicate public folders from Exchange Server 2003 servers to Exchange Server 2010 servers. As Exchange Server 2003 servers are removed from the organization, the Exchange Server 2010 servers can host all the public folders. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  13. Use a whiteboard diagram to show how a routing group connector is created when the first Exchange Server 2010 Hub Transport server is deployed in an Exchange Server 2003 organization. Consider extending the diagram to describe what happens as Hub Transport servers replace bridgehead servers across multiple Active Directory sites and routing groups. Because Exchange Server 2010 uses Active Directory sites rather than routing groups to manage routing, replacing bridgehead servers can change the routing topology significantly. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  14. Use the table to describe the options for configuring administrative permissions in Exchange Server 2003, and how those same permissions can be assigned in Exchange Server 2010. Stress that because using role-based access control (RBAC) to assign permissions is so flexible, you can duplicate any Exchange Server 2003 administrative permission configuration. Ask students if Exchange Server 2003 limited their ability to assign permissions. For example, did their organization have requirements for delegating administrative permissions that were not possible in Exchange Server 2003? Discuss whether the same limitations will apply in Exchange Server 2010. Stress the importance of managing each Exchange Server version with the correct version of management tools. Once Exchange Server 2010 is introduced into the organization, all organization-level settings should be configured using the Exchange Server 2010 tools, but all server-level administration settings should be performed using the management tools that come with each version. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  15. Stress the importance of removing the mailbox servers in the correct order when upgrading from Exchange Server 2003. Because of the changes to the Client Access architecture in Exchange Server 2010, an Exchange Server 2003 server that supports non-MAPI client connections must be retained until the last mailbox has been moved to an Exchange Server 2010 server. Review some of the functionality that was available in Exchange Server 2003 that is not available in Exchange Server 2010. Examples include the Novell GroupWise connector and the Inter-Organization Replication tool. Mention that some organizations may need to retain one or more Exchange Server 2003 servers to retain this functionality. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  16. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  17. Mention that the Exchange Server 2010 setup program checks the status of the current Exchange Server deployment. If SP2 is not installed on the Exchange 2007 servers, the installation will not complete. Emphasize that Exchange Server 2010 SP2 includes several schema updates. This means that the Service Pack deployment may be more complicated than most because of the requirement for testing schema updates in most organizations. Stress that Client Access servers must be deployed first and that all client connections must be configured to connect to the Client Access server. For most client connections, the Exchange Server 2010 Client Access Server will proxy the client request to the Exchange Server 2007 Client Access server. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  18. Use the diagram to describe the different scenarios that occur when the different messaging clients connect to the Exchange environment during coexistence. Emphasize the following differences from how the client access works with Exchange Server 2003: Exchange ActiveSync clients can connect to either the Exchange 2010 Client Access server or the Exchange 2007 Client Access server The Client Access servers can proxy Exchange ActiveSync and Web Services requests between versions. The Exchange 2010 Client Access server can proxy client requests to Exchange 2007 Client Access servers in sites that are not accessible from the Internet. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  19. Stress that because Exchange Server 2007 Mailbox servers require Exchange Server 2007 Client Access servers, the last Client Access servers cannot be removed until all of the mailboxes have been moved to Exchange Server 2010 Mailbox servers. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  20. Emphasize that Exchange Server 2007 Mailbox servers require Exchange Server 2007 Hub Transport servers in addition to Exchange Server 2007 Client Access servers. However, once all the mailboxes are moved to Exchange Server 2010 servers, you can remove the Exchange Server 2007 Hub Transport servers. You can do this on a per-site basis. For example, after moving all of the mailboxes to Exchange Server 2010, you can remove the Exchange Server 2007 Hub Transport server. The Exchange Server 2010 Hub Transport server in one site can send and receive e-mails with Exchange Server 2007 Hub Transport servers in the same or other sites. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  21. Review the list in the student manual of tasks that can be performed in each version of Exchange Management Console. Point out that the Exchange Management Console enforce the rules about what tasks can be performed on each version of Exchange server so there is no danger in inadvertently modifying a setting using the wrong version of Exchange Management Console. As you discuss the options for replicating the delegation of Administrative permissions in Exchange 2010, ask students how they have configured permissions in Exchange 2007 (if they are running Exchange 2007). You can then describe how they can replicate the permissions in Exchange 2010 using role groups. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  22. Stress the importance of removing the servers in the correct order when upgrading from Exchange Server 2007. Mention that once you have removed the last mailbox from the Exchange Server 2007 mailbox servers and moved all connectors to Exchange Server 2010, you can remove all other Exchange Server 2007 server roles because they are no longer used. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  23. Review Questions Your organization is deploying Exchange Server 2010 in an Exchange 2003 organization. You have made the changes to Active Directory. What is the first Exchange 2010 server role that you should deploy? How will this deployment change the user experience? Answer: You should deploy the Client Access server role first. However, this deployment will not change the user experience until you configure the non-MAPI clients to use the Client Access server for a mailbox access. Why do you need to configure a new external URL on Exchange Server 2007 Client Access servers when you deploy Exchange Server 2010 Client Access servers? Answer: The external URL redirects Outlook Web Access requests for users whose mailboxes are on Exchange 2007 Mailbox servers. The Autodiscover service on the Exchange 2010 Client Access server uses this URL to redirect the clients. Your organization includes two locations and Active Directory sites. You have deployed Exchange Server 2007 servers in both sites. You now are deploying Exchange Server 2010 servers in one of the sites and removing the Exchange Server 2007 servers. When can you remove the last Exchange 2007 Hub Transport server in the site? Answer: You can remove the last Hub Transport server when you move all of the mailboxes, public folders, and connectors from the Exchange Server 2007 servers in the site. As long as there is an Exchange 2007 Mailbox server in the site, you must maintain an Exchange 2007 Hub Transport server. . Common Issues Related to Desktop Application Support Identify the causes for the common issues related to upgrading to Exchange Server 2010 and fill in the troubleshooting tips. For answers, refer to relevant lessons in the module. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  24. Real-World Issues and Scenarios A. Datum has three office locations and three Active Directory sites. They have deployed Exchange Server 2003 servers in all offices, but have enabled Internet access to the servers only in the main office. What high-level process should A. Datum use to upgrade to Exchange Server 2010? Answer: They should upgrade the main office first, as this is the only site that is accessible from the Internet. After the upgrade in the main office is complete, they can upgrade the other offices. Your organization has deployed Forefront Threat Management Gateway (TMG) to secure access to the Client Access server deployment. You have completed all of the steps required to enable access to both the Exchange 2010 Client Access server and the Exchange 2007 Client Access server. What changes do you need to make on the TMG server? Answer: You need to configure TMG to forward all requests using the main Client Access server URL to the Exchange Server 2010 Client Access server. Then you need to configure Forefront TMG to forward requests sent to the alternate or legacy URL to the Exchange Server 2007 Client Access server. Your organization is deploying Exchange Server 2010 in an Exchange Server 2003 organization. Your organization does not provide Internet access to messaging clients, and all users are located in a single office. You deploy an Exchange Server 2010 server using a standard installation. What else do you need to do before you start moving mailboxes to the Exchange Server 2010 server? Users need to be able to access their mailboxes by using Outlook Web App and Outlook 2003. Answer: You do not need to do anything else before you start moving mailboxes. During the installation of the Hub Transport server role, you will be prompted for the Exchange Server 2003 server’s name that will be the routing group bridgehead server, to enable message flow. However, with this configuration, Exchange Server 2003 users need to use an Exchange Server 2003 front-end server to access their mailbox through Outlook Web Access, and they need to switch to the Exchange Server 2010 Client Access server when their mailbox moves. To enable the users to use the Exchange 2010 Client Access server while their mailbox is on the Exchange Server 2003 server, you need to add the Exchange 2003 URL to the Exchange 2010 Client Access server. Best Practices for Supporting Users Running Applications on Windows XP Help the students understand the best practices presented in this section. Ask students to consider these best practices in the context of their own business situations. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
  25. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A Remind students to complete the course evaluation.