Exchange 2013 Migration & Coexistence
•Als PPTX, PDF herunterladen•
4 gefällt mir•5,120 views
Attention Session en Anglais, animée par Scott Schnoll, Senior Content Developer à Microsoft Corp. Cette session vous expliquera comment architecturer une migration vers Exchange 2013 depuis d'ancienne versions d'Exchange avec comme speaker Scott Schnoll, Gourou Exchange en provenance directe de Redmond. La coexistence de serveurs de versions différentes sera aussi abordée. Speaker : Scott Schnoll (Microsoft)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Exchange 2013 Migration & Coexistence
Ähnlich wie Exchange 2013 Migration & Coexistence (20)
Mehr von Microsoft Technet France
Mehr von Microsoft Technet France (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Exchange 2013 Migration & Coexistence
- 2. Exchange Server 2013 Migration and Coexistence Scott Schnoll Senior Content Developer Microsoft Corporation scott.schnoll@microsoft.com http://aka.ms/Schnoll Twitter: @Schnoll Infrastructure, communication & collaboration
- 3. Upgrade Approach Preparing for Exchange 2013 Upgrade and Coexistence Moving Mailboxes Public Folders Managing Coexistence Quotas
- 4. Exchange 2010 Architecture Exchange 2013 Architecture L4 LB Hardware Load Balancer Client Access Hub Transport, Unified Messaging Mailbox L7 LB AuthN, Proxy, Re-direct Client Access AuthN, Proxy, Re-direct Protocols, API, Biz-logic Assistants, Store, CI Protocols, Assistants, API, Biz-logic Store, CI Mailbox
- 5. 1. Prepare Verify prerequisites Install Exchange 2010 SP3 or later across ORG Prepare AD with Exchange 2013 schema Validate existing client access 2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS roles Clients autodiscover.contoso.com mail.contoso.com 2 1 E2010 HUB E2010 CAS 3 4 E2013 CAS Exchange 2010 Servers SP3 SP3 Intranet site 6 5 E2010 MBX E2013 MBX Internet-facing site – upgrade first 3. Obtain and deploy certificates Obtain and deploy certs on Exchange 2013 CAS 4. Switch primary namespace to Exchange 2013 CAS Exchange 2013 fields all traffic, including traffic from Exchange 2010 users Validate using Remote Connectivity Analyzer 5. Move Mailboxes Build out DAG Move Exchange 2010 users to Exchange 2013 MBX Migrate Legacy Public Folders to Modern Public Folders 6. Repeat for additional sites
- 6. 1. Prepare Verify prerequisites Install Exchange 2007 SP3 + RU10 or later across ORG Prepare AD with Exchange 2013 schema Validate existing client access 2. Deploy Exchange 2013 servers Clients autodiscover.contoso.com mail.contoso.com 3 legacy.contoso.com 2 1 E2007 SP3 CAS E2007 SP3 HUB 4 5 E2013 CAS Install both Exchange 2013 MBX and CAS servers 3. Create legacy namespace Create DNS record pointing to Exchange 2007 CAS Exchange 2007 Servers RU10 RU10 RU10 Intranet site 7 6 E2007 SP3 MBX E2013 MBX Internet-facing site – upgrade first 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 CAS Deploy certificates on Exchange 2007 CAS 5. Switch primary namespace to Exchange 2013 CAS Validate using Remote Connectivity Analyzer 6. Move mailboxes Build out DAG Move Exchange 2007 users to Exchange 2013 MBX Migrate legacy Public Folders to Modern Public Folders 7. Repeat for additional sites
- 7. 1 1
- 8. 1 Exchange Server 2010 SP3 and later Exchange Server 2007 SP3 RU10 and later RPC over HTTP is only method of connectivity for Outlook clients Entourage 2008 for Mac, Web Services Edition Outlook for Mac 2011 Outlook Version Minimum Supported Version Recommended Version* Outlook 2013 RTM August 2013 update Outlook 2010 SP1 + Nov 2012 Update June 2013 update Outlook 2007 SP3 + Nov 2012 Update August 2013 update (14.0.6126.5000 or later) (12.0.6665.5000 or later) *Recommended Updates fix an issue with Outlook using the wrong Exchange 2013 Internal/External settings 1
- 9. 1 Windows Server 2008 R2 SP1 or later Standard or Enterprise Standard - for Exchange 2013 Client Access servers and standalone Mailbox servers Enterprise - for Exchange 2013 Mailbox servers in a DAG Windows Server 2012 RTM or later Standard or Datacenter Windows Server 2012 R2 (support coming in Exchange Server 2013 SP1) 1
- 10. 1 Install Exchange 2010 SP3 or Exchange 2007 SP3 RU10 to all servers Extend the AD schema for Exchange Server 2013 setup /PrepareSchema or /ps Prepare the Exchange organization for Exchange Server 2013 setup /PrepareAD or /p Prepare remaining AD domains that have or will have any mail enabled objects for Exchange Server 2013: Local domain setup /PrepareDomain or /p Remote domains one at a time setup /PrepareDomain:FQDN.of.domain or /p:FQDN.of.domain Or do them all at once setup /PrepareAllDomains or /pad Validate existing client access using Remote Connectivity Analyzer and test cmdlets 1
- 11. 2 2
- 12. 2 2 Install both MBX and CAS Servers CAS is proxy only MBX performs PowerShell commands Use the latest CU package No more SP then RU install Exchange 2013 Setup GUI and command line options Command line parameters New parameter for license terms acceptance After the Fact You cannot remove roles in Exchange 2013 Setup.exe /mode:install /roles:c,m,mt /IAcceptExchangeServerLicenseTerms
- 13. 3
- 14. 3 1 Used to access Exchange 2007 mailboxes and public folders during coexistence Legacy.contoso.com http://www.exrca.com
- 15. 31 4
- 16. 31 Export with private key and import to other CAS from the UI Assign services right from the UI First notification shown 30 days prior to expiration Subsequent notifications provided daily 4
- 17. 31 4
- 18. 31 Use split DNS or pinpoint DNS for Exchange host names mail.contoso.com for Exchange connectivity on intranet and Internet mail.contoso.com has different IP addresses in intranet/Internet DNS zones This is not a requirement, some customers may have unique environments where different names would be helpful Don’t list machine host names in certificate host name list Use load-balanced (LB) arrays for intranet and Internet access to servers Use “Subject Alternative Name” (SAN) certificate Public CA providers are beginning to restrict the issuing of certs with invalid DNS names 4
- 19. 4 5
- 20. 4 Layer 7 load balancers no longer required for an Exchange 2013 namespace Layer 4 (aka no-affinity/persistence) and Layer 7 are supported for Exchange 2013 namespace Validate creation with https://www.exrca.com/ Legacy namespace should begin or continue to use Layer 7 load balancing Script the change for legacy namespaces (and have a script to revert back if required) Update mail and Autodiscover DNS records to point to a Exchange 2013 CAS server Exchange 2007 and Exchange 2010 Autodiscover will redirect to Exchange 2013 CAS for Exchange 2013 mailbox 5
- 21. Switching to CAS 2013 4 5 Outlook Anywhere Clients mail.contoso.com RPC/HTTP Layer 7 LB Layer 4 LB RPC/HTTP HTTP PROXY E2007/E2010 CAS OA Enabled Client Auth: Basic IIS Auth: Basic NTLM RPC E2013 CAS OA Enabled Client Settings IIS Auth: NTLM RPC HTTP PROX Y 1. Enable Outlook Anywhere on all legacy CAS 2. IIS Authentication Methods E2007/E2010 CAS Disabled OA Enabled Client Settings IIS Auth:NTLM RPC IIS Auth must have NTLM enabled on all legacy CAS 3. Client Settings Make legacy OA settings the same as 2013 CAS so all clients get the same proxy hostname 4. DNS Cutover A low TTL on the existing record the days prior to the cutover is a good idea E2007/E2010 MBX E2013 Internet facing site MBX E2007/E2010 MBX Intranet facing site
- 23. 3 2013 to 2007 in the same AD site 2013 to 2007 in a different AD site 2013 to 2010 in a different AD site 2013 to 2013 in a different AD site
- 24. Exchange 2010 Coexistence OWA mail.contoso.com paris.mail.contoso.com Layer 4 LB E2010 CAS HTTP Proxy E2013 CAS RPC Site Boundary Protocol Head IIS Layer 7 LB Protocol Head E2010 CAS RPC Store Protocol Head Store DB DB DB E2010 MBX E2013 MBX E2010 MBX Cross-Site Proxy Request Cross-Site Silent Redirect
- 25. Exchange 2007 Coexistence Same-Site Silent Redirect Request OWA Legacy.contoso.com mail.contoso.com paris.mail.contoso.com Layer 7 LB Layer 4 LB Layer 7 LB E2007 CAS HTTP Proxy E2013 CAS RPC Site Boundary Protocol Head IIS Protocol Head E2007 CAS RPC Store Protocol Head Store DB DB DB E2007 MBX E2013 MBX E2007MBX Cross-Site Proxy Request Cross-Site Silent Redirection
- 26. Protocol Exchange 2007 user accessing Exchange 2010 namespace Exchange 2007 user accessing Exchange 2013 namespace Exchange 2010 user accessing Exchange 2013 namespace Requires Legacy namespace Legacy namespace No additional namespaces OWA • Same AD site: silent or SSO FBA redirect • Externally facing AD site: manual or silent/SSO Cross-site redirect • Internally facing AD site: proxy Silent redirect to CAS 2007 ExternalURL in same or different AD site. • Same AD Site: Proxy to CAS 2010 EAS • EAS v12.1+ : Autodiscover & redirect • Older EAS devices: proxy Proxy to MBX 2013 Proxy to CAS 2010 - all noted protocols Outlook Anywhere Direct CAS 2010 support Proxy to CAS 2007 Autodiscover Exchange 2010 answers Autodiscover query for 2007 User Exchange 2013 answers Autodiscover query for 2007 User EWS Uses Autodiscover to find CAS 2007 EWS External URL Uses Autodiscover to find CAS 2007 EWS External URL POP/IMAP Proxy Proxy to CAS 2007 OAB Direct CAS 2010 support Proxy to CAS 2007 RPS n/a n/a ECP n/a n/a • Different AD Site: Cross-site silent redirect to ExternalURL • Same AD Site: Proxy to CAS 2010 • Different AD Site: Cross-site silent redirect to ExternalURL
- 27. 5 6
- 28. 56 Batch management Reporting Retry semantics Uses Mailbox Replication Service (MRS) internally New-MigrationBatch Get-MigrationUserStatistics WLM will throttle moves to maintain a good user experience 6
- 30. Existing Public Folders can be migrated to Exchange 2013 Public Folder Replication is removed End user experience doesn’t change Exchange 2013 users can access Exchange 2010/Exchange 2007 Public Folders Exchange 2010/Exchange 2007 users cannot access Exchange 2013 Public Folders Migration of Public Folders is a cut-over migration Similar to online mailbox moves
- 31. Tool available to analyze existing Public Folder hierarchy to determine how many Exchange 2013 Public Folder mailboxes are recommended Users continue to access existing Public Folder deployment while data is copied Data migration happens in the background There will be a short downtime while the migration is finalized Once migration completes, everyone switches at the same time Can switch back, but any post migration Public Folder changes are lost
- 32. Public Folder Migration from Exchange 2007 or Exchange 2010 Public Folders 1. Prepare Outlook Clients Install Exchange SP and/or updates across the ORG Migrate all users that require access to Exchange 2013 2. Analyze 4 E2007 SP3 RU1 or E2010 SP3 0 1 Exchange 2013 Map PF folders to PF mailboxes 2 PF dbase 1 4. Begin Migration Request PF MB MB X X PFs PF dbase 2 PF dbase 3 3. Create new Public Folder mailboxes Set to HoldForMigration Mode, mailboxes invisible to clients PF mbx 1 3 MBX Take snapshot of existing PF folder structure, statistics and permissions 5 PF mbx 2 PF mbx 3 6 Clients continue to access and create new data during copy After copy is complete migration request status is AutoSuspended 5. Finalize Migration Request Update snapshot of existing PF folder structure, statistics and permissions Lock source, clients logged off, final sync occurs 6. Validate Check and verify destination folders
- 34. Manage Exchange 2013 mailboxes Manage Exchange 2013 certificates Manage Exchange 2013 servers Manage some Exchange 2007/2010 server attributes View and update Exchange 2010/2007 mailboxes and properties (with a few limitations)
- 36. This is due to more accurate space usage calculation of items within the database compared to previous versions Expectation is 30% increase in quota hit, but will vary based on the content types May want to increase the quotas of any user using 75% or more of their quota prior to moving their mailbox to Exchange 2013 The database size on disk does NOT increase
- 37. QUESTIONS? Thank you! #mstechdays Infrastructure, communication & collaboration
- 38. Related Content • Exchange 2013 Haute disponibilité et tolérance aux sinistres (Session 1/2 première partie) – 12/02/14 - 15:15-16:00, salle 351 • Exchange 2013 Haute disponibilité et tolérance aux sinistres (Session 2/2 première partie) – 12/02/14 - 16:30-17:15, salle 253 #mstechdays Infrastructure, communication & collaboration
- 39. Related Content • Exchange 2013 Bonnes pratiques – 12/02/14 – 12:15-13:00, salle 252B • Exchange 2013 Dimensionnement et Performance – 12/02/14 – 17:45-18:30, salle 252B #mstechdays Infrastructure, communication & collaboration
- 40. APPENDIX – RESOURCES #mstechdays Infrastructure, communication & collaboration
- 41. Office-related Blogs • • • • • • Office Blogs – http://blogs.office.com/ Exchange Team Blog – http://aka.ms/ehlo Lync Team Blog – http://aka.ms/lyncblog SharePoint Blog – http://aka.ms/spblog Yammer Blog – http://aka.ms/yammerblog Outlook Blog – http://aka.ms/outlookblog #mstechdays Infrastructure, communication & collaboration
- 42. Office-related Blogs • Excel Blog – http://aka.ms/excelblog • Power Bi Blog – http://aka.ms/pbiblog • Office 365 for Business Blog – http://aka.ms/o365fbblog • Project Blog – http://aka.ms/msprojectblog • OneNote Blog – http://aka.ms/onenoteblog #mstechdays Infrastructure, communication & collaboration
- 43. Office-related Blogs • • • • • Access Blog – http://aka.ms/accessblog OneDrive Blog – http://blog.onedrive.com/ PowerPoint Blog – http://aka.ms/pptblog Word Blog – http://aka.ms/wordblog Office for Mac Blog – http://aka.ms/ofmblog #mstechdays Infrastructure, communication & collaboration
- 44. Promote with customers www.iammec.com Internal site for all info aka.ms/MECfield Sign up for the newsletter <mecupdates> Join the conversation #iammec
Hinweis der Redaktion
- Invalid name examples - (such as .local, .internal, etc…)
- Enable Outlook Anywhere on all legacy CAS to allow 2013 CAS to discover and proxy through rpcproxy.dllEnsure IIS Authentication Methods on legacy CAS have NTLM enabledMake sure external hostname matches for legacy CAS and 2013 CAS
- Make sure to point out 2007 EAS users are proxied 2013 CAS 2013 mailbox 2007 CAS 2007 mailbox
- Batching capabilities is now extended to Exchange On Prem (just like we have had in O365 for some time).Allows for retry semantics and ability to batch users for moves to Exchange 2013.Workload Manager will throttle moves to maintain a positive end user experience. This can reduce the rate of user mailbox moves.
- Now let us look at the steps for migrating public folders from 2007 or 2010 to 2013. This is an overview and we have interactive session where we can go into details on a specific step.Up here you have the 2007 and 2010 PF deployment which we will migrate to a 2013 PF deployment.1. PreparationThe first step of preparation is about ensuring that the existing Exchange environments is prepared to handle the migration. The coexistence updates are needed on all 2007 and 2010 servers across the organization. All users who require PF access should first be moved to 2013 servers.2. AnalyzeNext you should analyze the existing public folder deployment. Like the structure, item counts in public folders, permissions. We recommend taking a snapshot of this information so you can validate it later when the data is moved to 2013. A mapping then needs to be created where public folders are mapped to their host mailboxes. Things to consider when assigning public folders to mailboxes are existing size, room for future growth, proximity to clients. At release we will have some scripts which will help you create the mapping.3. Create PF mailboxesOnce the mapping is done, the PF mailboxes need to be created on the 2013 servers. In order to distinguish between mailboxes being created pre and post migration, they need to be stamped with a HoldForMigration attribute.4. Start the migrationNow we are ready to begin the migration. This is done by creating a migration request. The input to the migration request is the mapping which we created in step 2. This begins a data copy from the public folder databases to the mailboxes. It happens in the backgound and clients will still continue to access the existing PF deployment. Once the copy is complete the migration request gets into an AutoSuspended state where it will remain till the administrator takes the next step which is to finalize the migration request.5. FinalizationNow the finalization step will need to be planned over a downtime. First a quick update to the snapshot which we took in step 2 is recommended. Then the finalization will happen in two steps. First the administrator will set a flag locking the source public folders. This will trigger a logoff of all user clients. Following that the administrator needs to wait for replication to complete. Then the second step would be to initiate a finalization of the migration request. This will do a final sync to make the 2013 data current and complete the switch over of clients to 2013.6. ValidateThe last step is q validation to make sure all data has been migrated. The snapshot data from the earlier steps can be used to validate this.-----------------------------------For QA and more detailafter migration is possible, but performing this step could lead to a loss of public folder data since any changes to public folders after the Exchange 2013 Preview migration was finalized will not be reflected in the Exchange 2010 public folders. In addition, as part of the rollback, we recommend that you remove any Exchange 2013 Preview public folders that were created as part of the migration process.For the migration of a geo-distributed hierarchy, how can I ensure that the public folders are created in the location nearest to the target users?As part of the migration process, a CSV file is generated (using the publicfoldertomailboxmapgenerator.ps1 script) which contains the folder to mailbox mapping for the new hierarchy. You can then use this CSV to create public folder mailboxes in the appropriate geographic location and modify the CSV file to have the required folders in the appropriate mailbox so they are near the target users.Draft PF FAQ, document any additional questions that are not on this list for Andreahttp://technet.microsoft.com/en-us/library/jj552408(v=exchg.150) SP3 is required to migrate from 2010 and coexistence RU is required to migrate from E12. It contains code in store which triggers during migration to kick off clients and keep them out till the migration is complete. It also has code to send clients to Exchange 2013 after migration is complete. It also has code to allow transport to understand Exchange 2013 PFs when delivering mail to mail enabled PFs in Exchange 2013.