upgrading and coexisting with exchange 2010
Post on 23-Feb-2016
46 Views
Preview:
DESCRIPTION
TRANSCRIPT
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
TechNet goes virtual
Upgrading and Coexisting with Exchange 2010Ilse Van Criekinge
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Content
• Introduction• Supported coexistence scenarios• Upgrade and coexistence Exchange
2003• Upgrade and coexistence Exchange
2007
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Introduction
Exchange version Mainstream support phase
Extended support phase
Exchange Server 5.5 12/31/2003 1/10/2006
Exchange 2000 Server 12/31/2005 1/11/2011
Exchange Server 2003 4/14/2009 4/8/2014
Exchange 2007 4/10/2012 4/11/2017
Source: http://support.microsoft.com/lifecycle
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Supported Coexistence Scenarios
Exchange version Exchange organization coexistence
Exchange Server 5.5 Not supported
Exchange 2000 Server Not supported
Exchange Server 2003 Supported
Exchange 2007 Supported
Mixed Exchange 2007 and Exchange Server 2003 organization
Supported
In-Place Upgrade NOT possible!
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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)
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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)
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Supported client access methods
• Desktop– Microsoft Office Outlook 2003 and later– POP/IMAP– Entourage
• Web– Internet Explorer– Mozilla– Safari
• Mobile– EAS + Third-Party vendors
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Management Interfaces
Domain Partition
Configuration Partition
Schema Partition
Exchange 2003 Exchange 2007 Exchange 2010
ADUC / ESM
ESM
EMS/EMC RBACEMS/EMC/ECP
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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)
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Start = Mix of E2003 and E2007
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Introducing Exchange 2010
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Mix of E2003 and E2007 and E2010
ESME2003
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Mix of E2003 and E2007 and E2010
EMCE2007
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Mix of E2003 and E2007 and E2010
EMS E2007
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Mix of E2003 and E2007 and E2010
EMCE2010
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Mix of E2003 and E2007 and E2010
EMS E2010
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Namespaces and URLsHostnames and services exposed to Internet
(c) http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032416709&CountryCode=US
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Remote Connectivity Analyzerhttps://www.testexchangeconnectivity.com
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Transition to E2010 CAS
1. Configure reverse proxy or external DNS– Point legacy.contoso.com to FE2003/CAS2007
2. Transition from E2003: Ensure OWA can redirect user to correct URL– Configure Exchange2003URL parameter on
CAS2010 OWA virtual directory (https://legacy.contoso.com/exchange)
3. 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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Transition to E2010 CAS ... Cont’d
4. 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
5. Configure reverse proxy or DNS
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
Transition to UM2010
• No 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
• With OCSStep 1. Introduce UM2010
with new dial planStep 2. Remove UM2007 after
UM-enabled mailboxes have been moved
Click to edit Master title style
TechNet goes virtual©2009 Microsoft Corporation. All Rights Reserved.
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
top related