overview. presentation introduction supported coexistence scenarios upgrade and...
Post on 11-Jan-2016
Embed Size (px)
Upgrading and Coexisting with Exchange 2010Presentation
2ContentIntroductionSupported coexistence scenariosUpgrade and coexistence Exchange 2003Upgrade and coexistence Exchange 2007
3IntroductionExchange versionMainstream support phaseExtended support phaseExchange Server 5.512/31/20031/10/2006Exchange 2000 Server12/31/20051/11/2011Exchange Server 20034/14/20094/8/2014Exchange 20074/10/20124/11/2017Source: http://support.microsoft.com/lifecycle
4Supported Coexistence ScenariosExchange versionExchange organization coexistenceExchange Server 5.5Not supportedExchange 2000 ServerNot supportedExchange Server 2003SupportedExchange 2007SupportedMixed Exchange 2007 and Exchange Server 2003 organizationSupportedIn-Place Upgrade NOT possible!
5General PrerequisitesExchangeExchange 2003 Sp2Exchange 2007 Sp2Exchange organization in native modeActive DirectoryIn every site 1 Global Catalog Win 2003 Sp2 or laterAt least Windows Server 2003 forest functionality modeSchema Master Win 2003 Sp2 or later
6Exchange Server Supportability MatrixExchange 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.aspx7Planning Roadmap for Upgrade and CoexistenceBe aware of new featuresBe aware of dropped featuresUnderstanding coexistenceManagement interfacesServer role featuresRouting differencesThe orderActive Directory sitesServer roles
8New from E2003 to E2007From 2 server roles to 5 server roles: Client Access, Hub Transport, Edge Transport, Mailbox, Unified Messaging64-bit only for productionAD Sites replace Routing GroupsExchange Web Services & AutodiscoverUnified MessagingNew admin tools
9New from E2007 to E2010On-Premise & In-The-CloudHigh Availability solution for mailboxes is Database Availability Groups (DAG)RPC Client Access ServiceManagement Tools (Exchange Binaries) are 64-bit only
10Exchange 2003 Dropped FeaturesRouting groupsAdministrative groupsLink state routingExchange Installable File System (ExIFS)Event serviceExMergeOutlook Mobile Access (OMA)Network News Transfer Protocol (NNTP)
11Exchange 2007 Dropped FeaturesLocal Continuous ReplicationFax servicesSingle copy clusters (SCC) and along with them::Shared storagePre-installing a clusterClustered mailbox serversRunning setup in cluster modeMoving a clustered mailbox serverStorage groupsProperties moved to database objectsTwo copy limitation of CCRStreaming BackupWebDAV, ExOLEDB, CDOEx (Entourage EWS uses EWS)
12Supported Client Access MethodsDesktopMicrosoft Office Outlook 2003 and laterPOP/IMAPEntourageWebInternet ExplorerMozillaSafariMobileEAS + Third-Party vendors
13Management InterfacesDomain PartitionConfiguration PartitionSchema PartitionExchange 2003Exchange 2007 Exchange 2010ADUC / ESMESMEMS/EMCRBACEMS/EMC/ECP
14Management Console InteroperabilityActions 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.
15Management Console Interoperability ...2Actions 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.
16Upgrade Step-by-StepStart = internet accessible Active Directory sites firstStep 1. Upgrade existing servers to SP2Step 2. Deploy E2010 serversCAS first, MBX lastStart with a few, add more as you move mailboxesStep 3. Legacy hostname for old FE/CASSSL cert purchaseEnd Users dont see this hostnameUsed when autodiscover and redirection from CAS 2010 tell clients to talk to FE2003/CAS2007 for MBX2003/MBX2007 accessStep 4. MoveInternet hostnames to CAS2010UM phone numbers to UM 2010SMTP end point to HUB 2010Step 5. Move MailboxesStep 6. Decommission old serversUpgrade internal sites second (repeat same steps)
17Start = Mix of E2003 and E2007
Introducing Exchange 2010
27Mix of E2003 and E2007 and E2010
28Mix of E2003 and E2007 and E2010
29Mix of E2003 and E2007 and E2010
30Mix of E2003 and E2007 and E2010
31Mix of E2003 and E2007 and E2010
32Namespaces and URLsHostnames and services exposed to Internet
33Remote Connectivity Analyzerhttps://www.testexchangeconnectivity.com
34Remote Connectivity AnalyzerDemo
Certificates ...Best practice: minimize the number of certificates1 certificate for all CAS servers + reverse proxy + Edge/HUBUse Subject Alternative Name (SAN) certificate which can cover multiple hostnamesWildcard CertificatesYesBut: Windows Mobile 5 + Outlook AnywhereCertificate Wizard in E2010
36Transition to E2010 CASConfigure reverse proxy or external DNSPoint legacy.contoso.com to FE2003/CAS2007Transition from E2003: Ensure OWA can redirect user to correct URLConfigure Exchange2003URL parameter on CAS2010 OWA virtual directory (https://legacy.contoso.com/exchange)Test before switching overLegacy.contoso.com works for Internet AccessUse 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 URLTest that CAS2010 is redirecting/proxying to CAS2007Configure reverse proxy or DNS
37Transition to E2010 HUB Step 1. Upgrade existing E2003 and E2007 servers to SP2Step 2. Install HUB and MBX 2010Step 3. Switch Edgesync + SMTP to go to HUB2010Step 4. Install Edge2010Step 5. Switch internet email submission to Edge2010HUB2007-HUB2010: SMTPHUB2007-MBX2007: RPCHUB2007-MBX2010: NOHUB2010-MBX2007: NOHUB2010-MBX2010: RPCEDGE2010-HUB2007Sp1: EdgeSync Yes
38No OCSStep1. Introduce UM2010 to existing dial planStep 2. Route IP GW/PBX calls to UM2010 for dial planStep 3. Remove UM2007 after UM-enabled mailboxes have been moved Transition to UM2010With OCSStep 1. Introduce UM2010 with new dial planStep 2. Remove UM2007 after UM-enabled mailboxes have been moved
39Move Mailboxes: Online & OfflineOnline = minimal user disruption (briefly disconnected as recently received messages are copied over)Online:E2007 SP2, E2010 -> E2010, Exchange OnlineOffline:E2003 -> E2010E2010 -> E2003/E2007
Exchange Deployment Assistant
http://technet.microsoft.com/en-us/exdeploy2010/default(EXCHG.140).aspx#HomeExchange Deployment AssistantDemo
Exchange 2010 :High Availability
11/1/2010 11:22 AM 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
43AgendaExchange 2010 High Availability FundamentalsHigh Availability Management Storage ImprovementsEnd-to-End Availability ImprovementsHigh Availability Design Examples
44Improved failover granularitySimplified administrationIncremental deploymentUnification of CCR + SCREasy stretching across sitesUp to 16 replicated copies
High Availability ImprovementsEasier & cheaper to deployEasier & cheaper to manageBetter SLAsReduced storage costsLarger mailboxesFurther IO reductions RAID-less / JBOD supportKey benefitsImproved transport resiliencyOnline mailbox movesEasier & cheaper to manageBetter SLAsImproved mailbox uptimeMore storage flexibilityBetter end-to-end availability
Evolution of Continuous Replication technologyCombines the capabilities of CCR and SCR into one platformEasier than traditional clustering to deploy and manageAllows each database to have up to 16 replicated copiesProvide