1 / 55

Upgrading and Coexisting with Exchange 2010

Upgrading and Coexisting with Exchange 2010. Content. Introduction Supported coexistence scenarios Upgrade and coexistence Exchange 2003 Upgrade and coexistence Exchange 2007. Introduction. Source: http://support.microsoft.com/lifecycle. Supported Coexistence Scenarios.

alka
Download Presentation

Upgrading and Coexisting with Exchange 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upgrading and Coexisting with Exchange 2010

  2. Content • Introduction • Supported coexistence scenarios • Upgrade and coexistence Exchange 2003 • Upgrade and coexistence Exchange 2007

  3. Introduction Source: http://support.microsoft.com/lifecycle

  4. Supported Coexistence Scenarios In-Place Upgrade NOT possible!

  5. General Prerequisites • Exchange • Exchange 2003 Sp2 • Exchange 2007 Sp2 • Exchange organization in native mode • Active Directory • In every site 1 Global Catalog Win 2003 Sp2 or later • At least Windows Server 2003 forest functionality mode • Schema Master Win 2003 Sp2 or later

  6. Exchange Server Supportability Matrix • Exchange Server 2003 is not supported in Active Directory environments whose domain/forest functional levels have been raised beyond Windows Server 2003. However, Exchange Server 2003 SP2 can function against Windows Server 2008 Active Directory servers. • Exchange Server 2007 is not supported on Windows Server 2008 R2. However, Exchange 2007 SP1 RU9 and SP2 are supported against Windows Server 2008 R2 Active Directory servers. In addition, Exchange 2007 SP1 RU9 and SP2 are supported in Active Directory environments whose domain/forest functional levels have been raised to Windows Server 2008 R2. • Exchange 2007 SP2 is supported with PowerShell 2.0. http://msexchangeteam.com/archive/2009/09/09/452361.aspx

  7. Planning Roadmap for Upgrade and Coexistence • Be aware of new features • Be aware of dropped features • Understanding coexistence • Management interfaces • Server role features • Routing differences • The order • Active Directory sites • Server roles

  8. New from E2003 to E2007 • From 2 server roles to 5 server roles: Client Access, Hub Transport, Edge Transport, Mailbox, Unified Messaging • 64-bit only for production • AD Sites replace Routing Groups • Exchange Web Services & Autodiscover • Unified Messaging • New admin tools

  9. New from E2007 to E2010 • On-Premise & In-The-Cloud • High Availability solution for mailboxes is Database Availability Groups (DAG) • RPC Client Access Service • Management Tools (Exchange Binaries) are 64-bit only

  10. Exchange 2003 Dropped Features • Routing groups • Administrative groups • Link state routing • Exchange Installable File System (ExIFS) • Event service • ExMerge • Outlook Mobile Access (OMA) • Network News Transfer Protocol (NNTP)

  11. Exchange 2007 Dropped Features • Local Continuous Replication • Fax services • Single copy clusters (SCC) and along with them:: • Shared storage • Pre-installing a cluster • Clustered mailbox servers • Running setup in cluster mode • Moving a clustered mailbox server • Storage groups • Properties moved to database objects • Two copy limitation of CCR • Streaming Backup • WebDAV, ExOLEDB, CDOEx (“Entourage EWS” uses EWS)

  12. Supported Client Access Methods • Desktop • Microsoft Office Outlook 2003 and later • POP/IMAP • Entourage • Web • Internet Explorer • Mozilla • Safari • Mobile • EAS + Third-Party vendors

  13. Management Interfaces Exchange 2003 Exchange 2007 Exchange 2010 Domain Partition ADUC / ESM RBAC EMS/EMC/ECP EMS/EMC Configuration Partition ESM Schema Partition

  14. Management Console Interoperability • Actions that create new objects, such as new mailboxes or a new Offline Address Book, can only be performed on a version of the Exchange Management Console that is the same as the target object. • Exchange 2007 Mailbox databases cannot be managed from the Exchange 2010 Management Console, although these databases can be viewed. • Exchange 2010 Management Console can't enable or disable Exchange 2007 Unified Messaging mailboxes. • Exchange 2010 Management Console can't manage Exchange 2007 mobile devices. • Actions that require management can be performed on Exchange 2007 objects from the Management Console in Exchange Server 2010. These actions cannot be performed from the Management Console in Exchange 2007 on objects from Exchange Server 2010.

  15. Management Console Interoperability ...2 • Actions that require viewing of objects can be performed from any version of the Exchange Management Console to any version of Exchange objects with a few exceptions. • Exchange 2007 and Exchange 2010 transport rule objects can only be viewed from the corresponding version of the Exchange Management Console. • Exchange 2007 and Exchange 2010 servers can only be viewed from their corresponding version of the Exchange Management Console. • Exchange 2010 Management Console's Queue Viewer tool can't connect to an Exchange 2007 server to view queues or messages.

  16. Upgrade Step-by-Step • Start = internet accessible Active Directory sites first • Step 1. Upgrade existing servers to SP2 • Step 2. Deploy E2010 servers • CAS first, MBX last • Start with a few, add more as you move mailboxes • Step 3. Legacy hostname for old FE/CAS • SSL cert purchase • End Users don’t see this hostname • Used when autodiscover and redirection from CAS 2010 tell clients to talk to FE2003/CAS2007 for MBX2003/MBX2007 access

  17. Upgrade Step-by-Step ...cont’d • Step 4. Move • Internet hostnames to CAS2010 • UM phone numbers to UM 2010 • SMTP end point to HUB 2010 • Step 5. Move Mailboxes • Step 6. Decommission old servers • Upgrade internal sites second (repeat same steps)

  18. Start = Mix of E2003 and E2007

  19. Introducing Exchange 2010

  20. Mix of E2003 and E2007 and E2010 ESM E2003

  21. Mix of E2003 and E2007 and E2010 EMC E2007

  22. Mix of E2003 and E2007 and E2010 EMS E2007

  23. Mix of E2003 and E2007 and E2010 EMC E2010

  24. Mix of E2003 and E2007 and E2010 EMS E2010

  25. Namespaces and URLsHostnames and services exposed to Internet (c) http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx? culture=en-US&EventID=1032416709&CountryCode=US

  26. Remote Connectivity Analyzerhttps://www.testexchangeconnectivity.com

  27. Certificates ... • Best practice: minimize the number of certificates • 1 certificate for all CAS servers + reverse proxy + Edge/HUB • Use “Subject Alternative Name” (SAN) certificate which can cover multiple hostnames • Wildcard Certificates • Yes • But: Windows Mobile 5 + Outlook Anywhere • Certificate Wizard in E2010

  28. Transition to E2010 CAS • Configure reverse proxy or external DNS • Point legacy.contoso.com to FE2003/CAS2007 • Transition from E2003: Ensure OWA can redirect user to correct URL • Configure Exchange2003URL parameter on CAS2010 OWA virtual directory (https://legacy.contoso.com/exchange) • Test before switching over • Legacy.contoso.com works for Internet Access • Use the Exchange Remote Connectvity Analyzer (c) http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx? culture=en-US&EventID=1032416709&CountryCode=US

  29. Transition to E2010 CAS ... Cont’d • Transition from E2007: Tell CAS2010 how to send users to CAS2007: • Configure externalURL parameters on CAS2007 virtual directories (OWA,EAS,EWS,OAB etc.) to point to legacy URL • Test that CAS2010 is redirecting/proxying to CAS2007 • Configure reverse proxy or DNS

  30. Transition to E2010 HUB • Step 1. Upgrade existing E2003 and E2007 servers to SP2 • Step 2. Install HUB and MBX 2010 • Step 3. Switch Edgesync + SMTP to go to HUB2010 • Step 4. Install Edge2010 • Step 5. Switch internet email submission to Edge2010

  31. Transition to E2010 HUB ...cont’d • HUB2007-HUB2010: SMTP • HUB2007-MBX2007: RPC • HUB2007-MBX2010: NO • HUB2010-MBX2007: NO • HUB2010-MBX2010: RPC • EDGE2010-HUB2007Sp1: EdgeSync Yes

  32. Transition to UM2010 • No OCS Step1. Introduce UM2010 to existing dial plan Step 2. Route IP GW/PBX calls to UM2010 for dial plan Step 3. Remove UM2007 after UM-enabled mailboxes have been moved • With OCS Step 1. Introduce UM2010 with new dial plan Step 2. Remove UM2007 after UM-enabled mailboxes have been moved

  33. Move Mailboxes: Online & Offline • Online = minimal user disruption (briefly disconnected as recently received messages are copied over) • Online: • E2007 SP2, E2010 -> E2010, Exchange Online • Offline: • E2003 -> E2010 • E2010 -> E2003/E2007

  34. Introducing BPOS

  35. SOFTWARE • Best of both worlds • User managed • Deployment choices SERVICES • Extending tools and platform to cloud • Experience across multiple devices • Existing software skills applied to the cloud

  36. Microsoft Online Services • Enterprise class software delivered via subscription services hosted by Microsoft and sold with partners Microsoft Online Services --- Business Productivity Online Suite

  37. Standard and Dedicated Versions Dedicated Standard • Single customer per architecture • Businesses greater than 5,000 seats • Optimize for 20,000+ • Customer needs most server features • Multiple customers, one architecture • Customer needs rapid deployment • No seat limit • Cost efficiency a key focus

  38. Migration Scenario Service Source Platform On-Premise Exchange 200x Domino GroupWise Generic (POP/IMAP) SharePoint Hosted Premium (Hosted Exchange) ISP (POP/IMAP) Webmail Hotmail Gmail/GAPE SharePoint

  39. Migration Options • Green Field *Big-Bang* migration • End-User *Big-Bang* migration • Minimal *Big-Bang* migration • Admin ‘Quick’ migration with min Coexistence • Classic migration with long-term coexistence • Just provision users and GO ! • Everyone moved at once • No retention of legacy mailbox data • Pro: Easy to deploy for large groups • Con: Loss of old content. • Provision users, and provide end users with migration tools. • Everyone moved at once • Users are given tools/options to access and migrate legacy mail themselves • Pro: Easy to scale to large groups. • Con: Difficult to manage end user tools. • Con: End user sat with extra work. • Provision users and just migrate core content (Calendar, contacts, etc.) • Can be combined with end-user migration. • Everyone moved at once • Pro: Can scale to large groups and preserves some data • Con: End-user sat with missing data. • Admin provisions and migrates groups of users to new service as fast as possible • All mailbox content is preserved • Only minimal coexistence is offered • Pro: Full data fidelity • Con: May not be possible for large orgs • Admin provisions and migrates groups of users to new service. • All mailbox content is preserved. • Long-term coexistence is offered • Pro: Support for large scale migrations • Pro: Includes coexistence • Con: Not all coexistence features may be available • Con: Admin work to coordinate group/moves.

  40. Exchange Migration Process Verify SMTP Domain AD Clean up Exchange Consideration Sign Up for Trial Set up Mail Coexist. Bulk Account Creation Exchange Mailbox Cleanup Account Management Install On Premise Tools Establish Dir Sync Activate & Migrate Pilot Users Pilot Verification Activation Notification ID Pilot Group Mailbox Migration End User Configuration MX Record Switch Over On Premise Exchange Management

  41. Exchange Online Highlights • Business Messaging Capabilities • Email, shared calendar and contacts • Flexible mailbox sizes • Anywhere Access • Mobility with Active Sync devices • Security and Availability • Built in anti-virus and anti-spam • Multi-layer data protection • Compliance archiving • Email encryption • Flexible Deployment • Online & on-premises co-existence • Active Directory synchronization • Data migration • Information & desk-less worker • Simplified Management • Unified administration center • 24x7 support • 99.9% service level agreement • Always up to date software

  42. Business Messaging CapabilitiesFlexible Mailbox Sizes and Policies • 5GB allocationper standard user license (25GB Maximum) • Pooled storage at company level • Assign different mailbox size limits per user • Additional storage available for purchase • Flexible send warning policy

More Related