PowerPoint Presentation
Exchange Server 2013Upgrade and CoexistenceScott
SchnollPrincipal Technical WriterMicrosoft CorporationServeurs /
Entreprise / Rseaux / IT
Twitter: SchnollBlog: http://aka.ms/Schnoll
Intro Serveurs / Entreprise / Reseaux / IT
1Fundamentals of DeploymentUpgrade and CoexistencePublic Folder
MigrationsManaging CoexistenceAgendaFundamentals of
DeploymentSupported coexistence scenariosExchange Server 2010
SP3Exchange Server 2007 SP3 RU10
Supported client access methodsMicrosoft Outlook:Outlook
Anywhere only: Outlook 2013, Outlook 2010, Outlook 2007Outlook for
Mac 2011Entourage 2008 for Mac, Web Services EditionExchange Server
2013 PrerequisitesActive DirectoryWindows Server 2003 forest
functional level or higherAt least one Windows 2003 SP2 or later
GC/DC in each siteNo support for RODC or
ROGCNamespacesContiguousNon-contiguousSingle label
domainDisjointExchange Server 2013 PrerequisitesOperating
SystemWindows Server 2008 R2 SP1 Standard or EnterpriseWindows
Server 2012 Standard or DatacenterOther ComponentsIIS and OS
components.NET Framework 4.5Windows Management Framework 3.0Unified
Communications Managed API (UCMA) 4.0Exchange Server 2013
PrerequisitesUpgrade and CoexistenceFunctional DifferencesAuthN,
Proxy, Re-directProtocols, API, Biz-logicAssistants, Store,
CIExchange 2010ArchitectureAuthN, Proxy, Re-directStore,
CIProtocols, Assistants, API, Biz-logicExchange
2013ArchitectureClient AccessMailboxClient AccessHub
Transport,Unified MessagingMailboxL4 LBL7 LBUpgrade from Exchange
2010 to Exchange 2013SP3
E2010 CASE2010 HUBE2010 MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 Servers
SP31. PrepareInstall Exchange 2010 SP3 across the ORGValidate
existing Client Access using ExRCA and built-in Test cmdletsPrepare
AD with E2013 schema4. Switch primary namespace to Exchange 2013
CASE2013 fields all traffic, including traffic from Exchange 2010
usersValidate using Remote Connectivity Analyzer5. Move
MailboxesBuild out DAGMove E2010 users to E2013 MBX6. Repeat for
additional sites2. Deploy Exchange 2013 serversInstall both E2013
MBX and CAS serversSP3SP3
E2013 CASE2013MBX
3. Obtain and Deploy CertificatesObtain and deploy certificates
on E2013 Client Access Servers
124356
Upgrade from Exchange 2007 to Exchange 2013RU
E2007 SP3 CASE2007 SP3 HUBE2007 SP3 MBXClientsInternet facing
site Upgrade firstautodiscover.contoso.commail.contoso.comIntranet
siteExchange 2007 SP3 Servers
RU1. PrepareInstall Exchange 2007 SP3 + RU across the ORGPrepare
AD with E2013 schema and validate5. Switch primary namespace to
Exchange 2013 CASValidate using Remote Connectivity Analyzer6. Move
MailboxesBuild out DAG Move E2007 users to E2013 MBX7. Repeat for
additional sites2. Deploy Exchange 2013 serversInstall both E2013
MBX and CAS serversRURU
E2013 CASE2013MBX
3. Create Legacy namespaceCreate DNS record to point to legacy
E2007 CAS4. Obtain and Deploy CertificatesObtain and deploy
certificates on E2013 Client Access Servers configured with legacy
namespace, E2013 namespace and Autodiscover namespaceDeploy
certificates on Exchange 2007 CASlegacy.contoso.com3
125467
Upgrade to Exchange Server 2013SP/RU
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
SP/RU1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CAS6. Move Mailboxes7. Repeat for
additional sites
3. Create Legacy namespace4. Obtain and Deploy Certificates12.
Deploy Exchange 2013 servers
Install coexistence update on all existing Exchange serversFor
Exchange 2010, this would be SP3For Exchange 2007, this would be
SP3 RU10Prepare Active Directory with Exchange 2013 schema
extensionsValidate existing client accessRemote Connectivity
Analyzer (http://www.exrca.com) and Test cmdletsPrepare for
Exchange Server 2013Upgrade to Exchange Server 2013SP/RU
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
SP/RU1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CAS6. Move Mailboxes7. Repeat for
additional sites2. Deploy Exchange 2013 serversInstall both E2013
MBX and CAS servers
E2013 CASE2013MBX
3. Create Legacy namespace4. Obtain and Deploy Certificates22.
Deploy Exchange 2013 serversInstall both E2013 MBX and CAS
servers
Install both MBX and CAS ServersMBX performs PowerShell
commandsCAS is proxy onlySetup provides GUI or command lineNo
in-place upgradeNew parameter for license terms acceptanceSetup.exe
/mode:install /roles:C,M /IAcceptExchangeServerLicenseTerms
Exchange Server 2013 SetupUpgrade to Exchange Server 2013
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CAS6. Move Mailboxes7. Repeat for
additional sites2. Deploy Exchange 2013 serversInstall both E2013
MBX and CAS servers
E2013 CASE2013MBX
4. Obtain and Deploy Certificateslegacy.contoso.com33. Create
Legacy namespaceSP/RU SP/RU
Required only for Exchange 2007 coexistenceCreate DNS record in
internal and external DNS for legacy namespaceValidate legacy
namespace using ExRCACreate Legacy NamespaceUpgrade to Exchange
Server 2013
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CAS6. Move Mailboxes7. Repeat for
additional sites2. Deploy Exchange 2013 serversInstall both E2013
MBX and CAS servers
E2013 CASE2013MBX
4. Obtain and Deploy CertificatesObtain and deploy certificates
on E2013 Client Access Servers configured with legacy namespace,
E2013 namespace and autodiscover namespaceDeploy certificates on
Exchange 2007 CASlegacy.contoso.com43. Create Legacy namespaceSP/RU
SP/RU
Minimize the number of certificatesMinimize number of
hostnamesUse split DNS for Exchange hostnamesDont list machine
hostnames in certificate hostname listUse Subject Alternative Name
(SAN) certificateCertificate Best Practices for Exchange 2013End to
End certificate wizard in the EACEAC notifies you when a
certificates is about to expire1st notification shown 30 days prior
to expirationSubsequent notifications provided dailyCertificate
Management in Exchange 2013Certificate ManagementExchange Server
2013demoUpgrade to Exchange Server 2013
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CASValidate using Remote Connectivity
Analyzer6. Move Mailboxes7. Repeat for additional sites2. Deploy
Exchange 2013 serversInstall both E2013 MBX and CAS servers
E2013 CASE2013MBX
4. Obtain and Deploy CertificatesObtain and deploy certificates
on E2013 Client Access Servers configured with legacy namespace,
E2013 namespace and autodiscover namespaceDeploy certificates on
Exchange 2007 CASlegacy.contoso.com3. Create Legacy namespaceSP/RU
SP/RU5
Validate legacy namespace creationConfigure Load balancingLayer
7 load balancers no longer required for primary namespaceLayer 4 is
supported and recommendedLegacy namespace is separate VIP with
Layer 7 load balancerConfigure AutoDiscoverServiceInternalUri on
Exchange 2013 CAS to LB valueConfigure AutoDiscoverSiteScopeSwitch
Primary NamespaceUpdate DNS to point Mail and Autodiscover to CAS
2013Update both internal and external DNSUpdate publishing rules
for legacy namespaceUse Remote Connectivity Analyzer to test access
to all CAS servers Test both externally and internallySwitch
Primary NamespaceUpgrade to Exchange Server 2013
E2010 or 2007CASE2010 or 2007 HUBE2010 or 2007
MBXClientsInternet facing site Upgrade
firstautodiscover.contoso.commail.contoso.comIntranet siteExchange
2010 or 2007 Servers
1. PrepareInstall Exchange SP and/or updates across the
ORGPrepare AD with E2013 schema and validate5. Switch primary
namespace to Exchange 2013 CASValidate using Remote Connectivity
Analyzer6. Move MailboxesBuild out DAG Move users to E2013 MBX7.
Repeat for additional sites2. Deploy Exchange 2013 serversInstall
both E2013 MBX and CAS servers
E2013 CASE2013MBX
4. Obtain and Deploy CertificatesObtain and deploy certificates
on E2013 Client Access Servers configured with legacy namespace,
E2013 namespace and autodiscover namespaceDeploy certificates on
Exchange 2007 CASlegacy.contoso.com3. Create Legacy namespaceSP/RU
SP/RU6
New Migration ServiceProvides functionality to orchestrate moves
such as batch managementProvides migration reportingProvides retry
semanticsNew
cmdletsNew-MigrationBatchGet-MigrationUserStatisticsAlso available
from EACMoving MailboxesPublic Folder MigrationsDatabase-centered
architecture replaced by mailboxExisting public folders can be
migrated to Exchange 2013End user experience doesnt changePublic
folder replication is removedMigrate Public Folder users before
Public FoldersExchange 2013 users can access Exchange 2010/2007
Public FoldersExchange 2010/2007 users cannot access Exchange 2013
Public FoldersMigration of Public Folders is a cut-over
migrationSimilar to online mailbox movesExchange Server 2013 Modern
Public FoldersAnalyze existing Public Folders Tool available to
analyze existing Public Folder hierarchy to determine how many
Exchange 2013 Public Folder mailboxes are recommendedCopy Public
Folder dataUsers access existing Public Folder deployment while
data is copiedData migration happens in the backgroundSwitch
clients to Exchange 2013 Public Folders There will be a short
downtime while the migration is finalizedOnce migration completes,
everyone switches at the same timeCan switch back, but any post
migration Public Folder changes are lostPublic Folder Migration
ProcessManaging CoexistenceUse Exchange Administration Center
to:Manage Exchange 2013 mailboxesView and update Exchange 2010/2007
mailboxes and properties (with a few limitations)Use Exchange
Management Console to:Create mailboxesPerform new operations on
those versionsCoexistence Object ManagementClient Access FlowOWA
Client Connectivity Exchange 2010Layer 4 LBE2013 CASIISHTTP
ProxyProtocol HeadDBE2010 CASProtocol HeadE2010 MBXStoreDBSite
BoundaryE2010 CASProtocol HeadE2010 MBXStoreDBRPCRPC
Cross-Site Proxy RequestLayer 7 LBCross-SiteRedirect
RequestOWA
europe.mail.contoso.commail.contoso.comE2013 MBXOWA Client
Connectivity Exchange 2007Layer 4 LBE2013 CASIISHTTP ProxyProtocol
HeadDBE2007 CASProtocol HeadE2007 MBXStoreDBSite BoundaryE2007
CASProtocol HeadE2007MBXStoreDBRPCRPC
Layer 7 LBCross-SiteRedirect RequestOWA
Layer 7
LBLegacy.contoso.commail.contoso.comeurope.mail.contoso.comCross-Site
Proxy RequestE2013 MBXClient Protocol Connectivity
CoexistenceProtocolExchange 2007 user / Exchange 2013
namespaceExchange 2010 user / Exchange 2013 namespaceRequiresLegacy
NamespaceNo additional namespacesOWANon-silent redirect (not SSO)
to CAS2007 externally facing URLProxy to CAS2010Cross-site silent
redirect (not SSO) which may redirect to CAS2010 or CAS2013
EASProxy to MBX2013Proxy to CAS2010Outlook AnywhereProxy to
CAS2007Proxy to CAS2010AutodiscoverRedirect to CAS2007 externally
facing URLProxy to CAS2010EWSAutodiscoverProxy to
CAS2010POP/IMAPProxy to CAS2007Proxy to CAS2010OABProxy to
CAS2007Proxy to CAS2010RPSn/aProxy to CAS2010ECPn/aProxy to
CAS2010Cross-site redirect which may redirect to CAS2010 or CAS2013
SummaryUpdates are required for coexistenceExchange 2007 requires a
legacy namespace Certificate management is improvedPublic Folder
migration is cutover processSummary
Scott SchnollPrincipal Technical
[email protected]://aka.ms/schnoll
schnollQuestions?
Formez-vous en ligneRetrouvez nos vnementsFaites-vous
accompagner gratuitementEssayer gratuitement nos solutions
ITRetrouver nos experts MicrosoftPros de
lITDveloppeurswww.microsoftvirtualacademy.comhttp://aka.ms/generation-apphttp://aka.ms/evenements-developpeurshttp://aka.ms/itcamps-franceLes
acclrateursWindows Azure, Windows Phone, Windows
8http://aka.ms/telechargementsLa DevTeam sur
MSDNhttp://aka.ms/devteamLIT Team sur
TechNethttp://aka.ms/itteamCall to action
38Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
Mailbox Server
