Ilse Van Criekinge Content Introduction Supported coexistence scenarios Upgrade and coexistence Exchange 2003 Upgrade and coexistence Exchange 2007 Introduction Exchange version Mainstream support phase ID: 531912
Download Presentation The PPT/PDF document "Upgrading and Coexisting with Exchange 2..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Upgrading and Coexisting with Exchange 2010
Ilse Van CriekingeSlide2
Content
Introduction
Supported coexistence scenarios
Upgrade and coexistence Exchange 2003
Upgrade and coexistence Exchange 2007Slide3
Introduction
Exchange version
Mainstream support phase
Extended support phase
Exchange Server 5.5
12/31/20031/10/2006Exchange 2000 Server12/31/20051/11/2011Exchange Server 20034/14/20094/8/2014Exchange 20074/10/20124/11/2017
Source: http://support.microsoft.com/lifecycleSlide4
Supported Coexistence Scenarios
Exchange version
Exchange organization coexistence
Exchange Server 5.5
Not supported
Exchange 2000 ServerNot supportedExchange Server 2003SupportedExchange 2007SupportedMixed Exchange 2007 and Exchange Server 2003 organizationSupported
In-Place Upgrade NOT possible!Slide5
General Prerequisites
Exchange
Exchange 2003 Sp2
Exchange 2007 Sp2
Exchange organization in native mode
Active DirectoryIn every site 1 Global Catalog Win 2003 Sp2 or laterAt least Windows Server 2003 forest functionality modeSchema Master Win 2003 Sp2 or laterSlide6
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.aspxSlide7
Planning Roadmap for Upgrade and Coexistence
Be aware of new features
Be aware of dropped features
Understanding coexistence
Management interfaces
Server role featuresRouting differencesThe orderActive Directory sitesServer rolesSlide8
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 MessagingNew admin toolsSlide9
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 onlySlide10
Exchange 2003 Dropped Features
Routing groups
Administrative groups
Link state routing
Exchange Installable File System (ExIFS)
Event serviceExMergeOutlook Mobile Access (OMA)Network News Transfer Protocol (NNTP)Slide11
Exchange 2007 Dropped Features
Local Continuous Replication
Fax services
Single copy clusters (SCC) and along with them::
Shared storage
Pre-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)Slide12
Supported client access methods
Desktop
Microsoft Office Outlook 2003 and later
POP/IMAP
Entourage
WebInternet ExplorerMozillaSafariMobileEAS + Third-Party vendorsSlide13
Management Interfaces
Domain Partition
Configuration Partition
Schema Partition
Exchange 2003
Exchange 2007 Exchange 2010ADUC / ESM
ESM
EMS/EMC
RBAC
EMS/EMC/ECPSlide14
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.Slide15
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.Slide16
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 mailboxesStep 3. Legacy hostname for old FE/CASSSL cert purchaseEnd Users don’t see this hostnameUsed when autodiscover and redirection from CAS 2010 tell clients to talk to FE2003/CAS2007 for MBX2003/MBX2007 accessSlide17
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 MailboxesStep 6. Decommission old serversUpgrade internal sites second (repeat same steps)Slide18
Start = Mix of E2003 and E2007Slide19
Introducing Exchange 2010Slide20Slide21Slide22Slide23Slide24Slide25Slide26Slide27Slide28
Mix of E2003 and E2007 and E2010
ESM
E2003Slide29
Mix of E2003 and E2007 and E2010
EMC
E2007Slide30
Mix of E2003 and E2007 and E2010
EMS E2007Slide31
Mix of E2003 and E2007 and E2010
EMC
E2010Slide32
Mix of E2003 and E2007 and E2010
EMS E2010Slide33
Namespaces and URLsHostnames and services exposed to Internet
(c)
http
://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?
culture=en-US&EventID=1032416709&CountryCode=USSlide34
Remote Connectivity Analyzer
https://www.testexchangeconnectivity.comSlide35
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
YesBut: Windows Mobile 5 + Outlook AnywhereCertificate Wizard in E2010Slide36
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 overLegacy.contoso.com works for Internet AccessUse the Exchange Remote Connectvity Analyzer(c) http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032416709&CountryCode=USSlide37
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 DNSSlide38
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 Edge2010Slide39
Transition to E2010 HUB ...cont’d
HUB2007-HUB2010: SMTP
HUB2007-MBX2007: RPC
HUB2007-MBX2010: NO
HUB2010-MBX2007: NO
HUB2010-MBX2010: RPCEDGE2010-HUB2007Sp1: EdgeSync YesSlide40
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 OCSStep 1. Introduce UM2010 with new dial planStep 2. Remove UM2007 after UM-enabled mailboxes have been movedSlide41
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 -> E2010E2010 -> E2003/E2007