1 / 104

Exchange 2010

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

craig
Download Presentation

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. Exchange 2010 Overview

  2. Upgrading and Coexisting with Exchange 2010 Presentation

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

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

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

  6. 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

  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 2007 Exchange 2010 Exchange 2003 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 • 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)

  17. Start = Mix of E2003 and E2007

  18. Introducing Exchange 2010

  19. Mix of E2003 and E2007 and E2010 ESM E2003

  20. Mix of E2003 and E2007 and E2010 EMC E2007

  21. Mix of E2003 and E2007 and E2010 EMS E2007

  22. Mix of E2003 and E2007 and E2010 EMC E2010

  23. Mix of E2003 and E2007 and E2010 EMS E2010

  24. Namespaces and URLsHostnames and services exposed to Internet

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

  26. Remote Connectivity Analyzer Demo

  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 • 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

  29. 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 • HUB2007-HUB2010: SMTP • HUB2007-MBX2007: RPC • HUB2007-MBX2010: NO • HUB2010-MBX2007: NO • HUB2010-MBX2010: RPC • EDGE2010-HUB2007Sp1: EdgeSync Yes

  30. 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

  31. 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

  32. Exchange Deployment Assistant http://technet.microsoft.com/en-us/exdeploy2010/default(EXCHG.140).aspx#Home

  33. Exchange Deployment Assistant Demo

  34. Exchange 2010 :High Availability

  35. Agenda • Exchange 2010 High Availability Fundamentals • High Availability Management • Storage Improvements • End-to-End Availability Improvements • High Availability Design Examples

  36. High Availability Improvements Key benefits Improved mailbox uptime • Improved failover granularity • Simplified administration • Incremental deployment • Unification of CCR + SCR • Easy stretching across sites • Up to 16 replicated copies • Easier & cheaper to deploy • Easier & cheaper to manage • Better SLAs More storage flexibility • Reduced storage costs • Larger mailboxes • Further IO reductions • RAID-less / JBOD support • Easier & cheaper to manage • Better SLAs Better end-to-end availability • Improved transport resiliency • Online mailbox moves

  37. Unified Platform for High Availability and Disaster Recovery Replicate databases to remote datacenter • Evolution of Continuous Replication technology • Combines the capabilities of CCR and SCR into one platform • Easier than traditional clustering to deploy and manage • Allows each database to have up to 16 replicated copies • Provides full redundancy of Exchange roles on two servers Mailbox Server Mailbox Server Mailbox Server DB1 DB1 DB1 Recover quickly from disk and database failures DB2 DB2 DB2 DB3 DB3 DB3 DB4 DB4 DB4 DB5 DB5 DB5 Dallas San Jose

  38. Exchange 2010 High Availability Overview AD site: Dallas All clients connect via CAS servers Client Access Server DB1 Client DB3 Mailbox Server 6 AD site: San Jose DB5 Client Access Server Easy to stretch across sites Failover managed within Exchange Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 5 Database Availability Group DB1 DB1 DB1 DB4 DB2 DB5 DB3 DB2 DB5 DB3 DB4 DB1 Database centric failover DB3 DB1 DB2 DB5 DB4

  39. High Availability Fundamentals • Database Availability Group (DAG) • Mailbox Servers • Mailbox Database • Database Copy • Active Manager RPC Client Access Service Active Manager Active Manager Active Manager • RPC Client Access Service (Active Manager Client) DB1 DB1 DB1 DB2 DB2 DB2 DB3 DB3 DB3 Database Availability Group

  40. Exchange 2010 HA Fundamentals:Database Availability Group (DAG) • Group of up to 16 servers • Wraps a Windows Failover Cluster • Defines the boundary of replication and failover/switchover Mailbox Servers …. • Host the active and passive copies of multiple mailbox databases • Support up to 100 Databases per server

  41. Exchange 2010 HA FundamentalsMailbox Databases and Copies • Mailbox Database • Unit of Failover/Switchover • 30 second Database Failover/Switchover • Database names are unique across an forest • Mailbox Database Copy • A database has 1 Active copy in a DAG • A server may not host more than 1 copy of a given database • Replication of copies using Log Shipping • System tracks health of each copy

  42. Exchange 2010 HA FundamentalsMailbox Database Copy Status • Mounted • Dismounted • Disconnected • FailedandSuspended • Resynchronizing • Seeding • ActivationSuspended Healthy Initializing Failed Suspended

More Related