Your SlideShare is downloading. ×
0
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Exchange Server 2013 : upgrade migration et co-existence avec les anciennes versions - ce qu'il faut absolument savoir

3,472

Published on

Vous souhaitez tester / installer la toute nouvelle version d'Exchange 2013... mais quelles sont les implications à connaitre pour effectuer un upgrade depuis les anciennes versions d'Exchange ou …

Vous souhaitez tester / installer la toute nouvelle version d'Exchange 2013... mais quelles sont les implications à connaitre pour effectuer un upgrade depuis les anciennes versions d'Exchange ou encore pour mettre en place une infrastructure mixte avec coexistence d'anciennes versions des serveurs ? Cette session est animée par Scott Schnoll, Principal Technical Writer dans l'équipe Exchange à Microsoft Corp. Vous aurez en direct les conseils et les meilleures pratiques prodigués par l'expert mondial sur Exchange. Attention session technique en anglais.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,472
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
184
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Intro Serveurs / Entreprise / Reseaux / IT
  • Transcript

    • 1. Exchange Server 2013Upgrade and CoexistenceScott SchnollPrincipal Technical WriterMicrosoft CorporationServeurs / Entreprise / Réseaux / ITTwitter: SchnollBlog: http://aka.ms/Schnoll
    • 2. • Fundamentals of Deployment• Upgrade and Coexistence• Public Folder Migrations• Managing CoexistenceAgenda
    • 3. FUNDAMENTALS OF DEPLOYMENT
    • 4. • Supported coexistence scenarios– Exchange Server 2010 SP3– Exchange Server 2007 SP3 RU10• Supported client access methods– Microsoft Outlook:• Outlook Anywhere only: Outlook 2013, Outlook 2010,Outlook 2007– Outlook for Mac 2011– Entourage 2008 for Mac, Web Services EditionExchange Server 2013 Prerequisites
    • 5. • Active Directory– Windows Server 2003 forest functional level or higher– At least one Windows 2003 SP2 or later GC/DC in each site– No support for RODC or ROGC• Namespaces– Contiguous– Non-contiguous– Single label domain– DisjointExchange Server 2013 Prerequisites
    • 6. • Operating System– Windows Server 2008 R2 SP1 Standard or Enterprise– Windows Server 2012 Standard or Datacenter• Other Components– IIS and OS components– .NET Framework 4.5– Windows Management Framework 3.0– Unified Communications Managed API (UCMA) 4.0Exchange Server 2013 Prerequisites
    • 7. UPGRADE AND COEXISTENCE
    • 8. Functional 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 LB
    • 9. Upgrade from Exchange 2010 to Exchange 2013SP3E2010CASE2010HUBE2010MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010ServersSP31. PrepareInstall Exchange 2010 SP3 across the ORGValidate existing Client Access using ExRCA and built-in TestcmdletsPrepare AD with E2013 schema4. Switch primary namespace to Exchange 2013 CASE2013 fields all traffic, including traffic from Exchange2010 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 serversSP3SP3E2013CASE2013MBX3. Obtain and Deploy CertificatesObtain and deploy certificates on E2013 Client AccessServers1 2 435 6
    • 10. Upgrade from Exchange 2007 to Exchange 2013RUE2007SP3 CASE2007SP3 HUBE2007SP3MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2007SP3 ServersRU1. 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 DAGMove E2007 users to E2013 MBX7. Repeat for additional sites2. Deploy Exchange 2013 serversInstall both E2013 MBX and CAS serversRURUE2013CASE2013MBX3. Create Legacy namespaceCreate DNS record to point to legacy E2007 CAS4. Obtain and Deploy CertificatesObtain and deploy certificates on E2013 Client Access Serversconfigured with legacy namespace, E2013 namespace andAutodiscover namespaceDeploy certificates on Exchange 2007 CASlegacy.contoso.com 31 2 546 7
    • 11. Upgrade to Exchange Server 2013SP/RUE2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 ServersSP/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 sites3. Create Legacy namespace4. Obtain and Deploy Certificates1 2. Deploy Exchange 2013 servers
    • 12. • Install coexistence update on all existingExchange servers– For Exchange 2010, this would be SP3– For Exchange 2007, this would be SP3 RU10• Prepare Active Directory with Exchange 2013schema extensions• Validate existing client access– Remote Connectivity Analyzer (http://www.exrca.com) andTest cmdletsPrepare for Exchange Server 2013
    • 13. Upgrade to Exchange Server 2013SP/RUE2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 ServersSP/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 serversE2013CASE2013MBX3. Create Legacy namespace4. Obtain and Deploy Certificates2 2. Deploy Exchange 2013 serversInstall both E2013 MBX and CAS servers
    • 14. • Install both MBX and CAS Servers– MBX performs PowerShell commands– CAS is proxy only• Setup provides GUI or command line– No in-place upgrade• New parameter for license termsacceptanceSetup.exe /mode:install /roles:C,M /IAcceptExchangeServerLicenseTermsExchange Server 2013 Setup
    • 15. Upgrade to Exchange Server 2013E2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 Servers1. 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 serversE2013CASE2013MBX4. Obtain and Deploy Certificateslegacy.contoso.com 33. Create Legacy namespaceSP/RUSP/RU
    • 16. • Required only for Exchange 2007coexistence• Create DNS record in internal and externalDNS for legacy namespace• Validate legacy namespace using ExRCACreate Legacy Namespace
    • 17. Upgrade to Exchange Server 2013E2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 Servers1. 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 serversE2013CASE2013MBX4. Obtain and Deploy CertificatesObtain and deploy certificates on E2013 Client Access Serversconfigured with legacy namespace, E2013 namespace andautodiscover namespaceDeploy certificates on Exchange 2007 CASlegacy.contoso.com43. Create Legacy namespaceSP/RUSP/RU
    • 18. • Minimize the number of certificates• Minimize number of hostnames– Use split DNS for Exchange hostnames– Don’t list machine hostnames in certificate hostnamelist• Use Subject Alternative Name (SAN)certificateCertificate Best Practices for Exchange 2013
    • 19. • End to End certificate wizard in the EAC• EAC notifies you when a certificates isabout to expire– 1st notification shown 30 days prior to expiration– Subsequent notifications provided dailyCertificate Management in Exchange 2013
    • 20. CERTIFICATE MANAGEMENTExchange Server 2013
    • 21. Upgrade to Exchange Server 2013E2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 Servers1. 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 serversE2013CASE2013MBX4. Obtain and Deploy CertificatesObtain and deploy certificates on E2013 Client Access Serversconfigured with legacy namespace, E2013 namespace andautodiscover namespaceDeploy certificates on Exchange 2007 CASlegacy.contoso.com3. Create Legacy namespaceSP/RUSP/RU5
    • 22. • Validate legacy namespace creation• Configure Load balancing– Layer 7 load balancers no longer required for primarynamespace– Layer 4 is supported and recommended– Legacy namespace is separate VIP with Layer 7 loadbalancer– Configure AutoDiscoverServiceInternalUri on Exchange 2013CAS to LB value– Configure AutoDiscoverSiteScopeSwitch Primary Namespace
    • 23. • Update DNS to point Mail andAutodiscover to CAS 2013– Update both internal and external DNS• Update publishing rules for legacynamespace– Use Remote Connectivity Analyzer to test access to allCAS servers– Test both externally and internallySwitch Primary Namespace
    • 24. Upgrade to Exchange Server 2013E2010 or2007CASE2010 or2007HUBE2010 or2007MBXClientsInternet facing site – Upgrade firstautodiscover.contoso.commail.contoso.comIntranet siteExchange 2010 or2007 Servers1. 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 DAGMove users to E2013 MBX7. Repeat for additional sites2. Deploy Exchange 2013 serversInstall both E2013 MBX and CAS serversE2013CASE2013MBX4. Obtain and Deploy CertificatesObtain and deploy certificates on E2013 Client Access Serversconfigured with legacy namespace, E2013 namespace andautodiscover namespaceDeploy certificates on Exchange 2007 CASlegacy.contoso.com3. Create Legacy namespaceSP/RUSP/RU6
    • 25. • New Migration Service– Provides functionality to orchestrate moves such as batchmanagement– Provides migration reporting– Provides retry semantics• New cmdlets– New-MigrationBatch– Get-MigrationUserStatistics• Also available from EACMoving Mailboxes
    • 26. PUBLIC FOLDER MIGRATIONS
    • 27. • Database-centered architecture replaced bymailbox– Existing public folders can be migrated to Exchange 2013– End user experience doesn’t change– Public folder replication is removed• Migrate Public Folder users before Public Folders– Exchange 2013 users can access Exchange 2010/2007 PublicFolders– Exchange 2010/2007 users cannot access Exchange 2013 PublicFolders– Migration of Public Folders is a cut-over migration– Similar to online mailbox movesExchange Server 2013 Modern Public Folders
    • 28. • Analyze existing Public Folders– Tool available to analyze existing Public Folder hierarchy to determinehow many Exchange 2013 Public Folder mailboxes are recommendedCopy Public Folder data• Users access existing Public Folder deployment whiledata is copied– Data migration happens in the background• Switch clients to Exchange 2013 Public Folders– There will be a short downtime while the migration is finalizedOnce migration completes, everyone switches at the same time– Can switch back, but any post migration Public Folder changes arelostPublic Folder Migration Process
    • 29. MANAGING COEXISTENCE
    • 30. • Use Exchange Administration Center to:– Manage Exchange 2013 mailboxes– View and update Exchange 2010/2007 mailboxes andproperties (with a few limitations)• Use Exchange Management Console to:– Create mailboxes– Perform new operations on those versionsCoexistence Object Management
    • 31. CLIENT ACCESS FLOW
    • 32. OWA Client Connectivity – Exchange 2010Layer 4 LBE2013 CASIISHTTP ProxyProtocol HeadDBE2010 CASProtocolHeadE2010 MBXStoreDBSiteBoundaryE2010 CASProtocolHeadE2010 MBXStoreDBRPC RPCCross-Site Proxy RequestLayer 7 LBCross-SiteRedirectRequestOWAeurope.mail.contoso.commail.contoso.comE2013 MBX
    • 33. OWA Client Connectivity – Exchange 2007Layer 4 LBE2013 CASIISHTTP ProxyProtocol HeadDBE2007 CASProtocolHeadE2007 MBXStoreDBSiteBoundaryE2007 CASProtocolHeadE2007MBXStoreDBRPC RPCLayer 7 LBCross-SiteRedirectRequestOWALayer 7 LBLegacy.contoso.com mail.contoso.com europe.mail.contoso.comCross-Site Proxy RequestE2013 MBX
    • 34. Client Protocol Connectivity – CoexistenceProtocol Exchange 2007 user / Exchange 2013 namespace Exchange 2010 user / Exchange 2013 namespaceRequires Legacy Namespace No additional namespacesOWA Non-silent redirect (not SSO) to CAS2007 externallyfacing URL• Proxy to CAS2010• Cross-site silent redirect (not SSO) which mayredirect to CAS2010 or CAS2013EAS Proxy to MBX2013 Proxy to CAS2010Outlook Anywhere Proxy to CAS2007 Proxy to CAS2010Autodiscover Redirect to CAS2007 externally facing URL Proxy to CAS2010EWS Autodiscover Proxy to CAS2010POP/IMAP Proxy to CAS2007 Proxy to CAS2010OAB Proxy to CAS2007 Proxy to CAS2010RPS n/a Proxy to CAS2010ECP n/a • Proxy to CAS2010• Cross-site redirect which may redirect to CAS2010or CAS2013
    • 35. SUMMARY
    • 36. • Updates are required for coexistence• Exchange 2007 requires a legacynamespace• Certificate management is improved• Public Folder migration is cutover processSummary
    • 37. Scott SchnollPrincipal Technical Writerscott.schnoll@microsoft.comhttp://aka.ms/schnollschnollQuestions?
    • 38. Formez-vous en ligneRetrouvez nos évènementsFaites-vous accompagnergratuitementEssayer gratuitement nossolutions ITRetrouver nos expertsMicrosoftPros de l’ITDéveloppeurswww.microsoftvirtualacademy.comhttp://aka.ms/generation-apphttp://aka.ms/evenements-developpeurshttp://aka.ms/itcamps-franceLes accélérateursWindows Azure, Windows Phone,Windows 8http://aka.ms/telechargementsLa Dev’Team sur MSDNhttp://aka.ms/devteamL’IT Team sur TechNethttp://aka.ms/itteam

    ×