Exchange 2013 Upgrade and Coexistence Peter Schmidt Solution Architect, MCSM: Exchange, Exchange MVP peter.schmidt@eg.dk - EG A/S

Speaker Peter Schmidt (peter.schmidt@eg.dk) Solution Architect at EG A/S Microsoft Certified Solution Master: Exchange Microsoft MVP: Exchange (2011 – Present) Microsoft MVP: IIS (2008 – 2011) Moderator/Part of the core crew of IT-Experts.dk (Danish IT Pro Community) Founder of CoLabora.dk (Microsoft Unified Communications User Group) UC User Group: http://www.colabora.dk Blog: http://www.msdigest.net Twitter: @petsch

EG in one slide Established 1977 in Herning 25 offices in the Nordic region Approx. 1300 Full Time Employees Revenue 1,5 mia. DKK Full service provider

Agenda Deployment Fundamentals Upgrade and Coexistence Public Folder Migrations Unified Messaging Managing Coexistence Summary

Deployment Fundamentals

Exchange Server 2013 Prerequisites 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 Edition

Exchange Server Schema Version http://support.microsoft.com/kb/556086 Exchange Server version Forest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM 4397 Exchange 2000 Server SP3 4406 Exchange Server 2003 RTM 6870 Exchange Server 2003 SP1 Exchange Server 2003 SP2 Exchange Server 2007 RTM 10637 Exchange Server 2007 SP1 11116 Exchange Server 2007 SP2 14622    Exchange Server 2007 SP3 14625 Exchange Server 2010 RTM 14622 ExchangeServer 2010 SP1 14726 Exchange Server 2010 SP2 14732 Exchange Server 2010 SP3 14734 Exchange Server 2013 15137 Exchange Server 2013 CU1 15254

Exchange 2013 Prerequisites Active Directory Windows Server 2003 forest functional level or higher At least one Windows 2003 SP2 or later GC/DC in each site with Exchange installed No support for RODC or ROGC Supported Namespaces Contiguous Dis-contiguous (also known as Non-Contiguous) Disjoint Single label domain Definitions: http://technet.microsoft.com/en-us/library/cc731125(v=WS.10).aspx 19-11-2018

Exchange 2013 Prerequisites Operating System (64-bit) Windows Server 2008 R2 SP1 Standard or Enterprise Standard - for Exchange 2013 Client Access servers Enterprise - for Exchange 2013 Mailbox servers in a DAG Windows Server 2012 Standard or Datacenter IIS and OS components .NET Framework 4.5 Windows Management Framework 3.0 Unified Communications Managed API (UCMA) 4.0 Pre-requirements script: http://www.testlabs.se/blog/2013/04/05/exchange-2013-script-automatic-installation-of-prerequisites/ 19-11-2018

Servicing Exchange 2013 Security Updates Cumulative Updates (CU’s) Security updates will be delivered via independent packages that can be applied to a previously released CU or installed during the upgrade to the current CU Cumulative Updates (CU’s) Routine product updates will be distributed via quarterly (CU’s) The version of Exchange shipped to on-premises customers in each CU will be the same version we use to host Exchange Online in Office 365 A CU is serviced for a period of 3 months after the release date of next CU Service Packs Periodic service pack releases rolling up CU’s and new features

Cumulative Updates Benefits of new model Predictable release cadence (4x a year) Dedicated security releases Datacenter scale validation Improved support for hybrid deployments More rapid changes to language resources Differences between CUs and RUs Larger update packages Loss of server customization Installation failure recovery Server version number will be updated with CU install

Cumulative Updates CU1 is a full Exchange install Full build uninstall/reinstall (just like Service Packs) Customized per-server web.config settings overwritten; admins must reconfigure Required for coexistence with Exchange 2010/2007 If CU1 install fails, you must use /RecoverServer

Preparing for Exchange Server 2013 Ensure that all Exchange 2003 servers are removed from the domain Install coexistence update on all Exchange servers in the organization Install Exchange 2010 SP3 using same steps as previous Exchange 2010 Service Packs Install Exchange 2007 SP3 + coexistence RU using same steps as previous Exchange 2007 RUs Prepare Active Directory with Exchange 2013 schema 19-11-2018

Upgrade and Coexistence

Functional Layering L7 LB Client Access AuthN, Proxy, Re-direct Exchange 2010 Architecture Exchange 2013 Architecture L4 LB L7 LB Hardware Load Balancer AuthN, Proxy, Re-direct Client Access AuthN, Proxy, Re-direct Client Access Hub Transport, Unified Messaging Protocols, API, Biz-logic Protocols, Assistants, API, Biz-logic Mailbox Assistants, Store, CI Store, CI Mailbox

Upgrade from Exchange 2010 to Exchange 2013 1. Prepare Install Exchange 2010 SP3 across the ORG Validate existing Client Access using MCA and ExRCA and built-in Test cmdlets Prepare AD with E2013 schema Clients autodiscover.contoso.com mail.contoso.com 4 1 2 E2013 CAS E2013 MBX 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers Exchange 2010 Servers E2010 HUB E2010 CAS 3 3. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers SP3 SP3 SP3 SP3 4. Switch primary namespace to Exchange 2013 CAS E2013 fields all traffic, including traffic from Exchange 2010 users Validate using MCA and ExRCA Intranet site 5 6 E2010 MBX 5. Move Mailboxes Build out DAG Move E2010 users to E2013 MBX Internet facing site – Upgrade first 6. Repeat for additional sites

Upgrade from Exchange 2007 to Exchange 2013 Clients 1. Prepare Install Exchange 2007 SP3 + RU across the ORG Prepare AD with E2013 schema and validate autodiscover.contoso.com mail.contoso.com 3 legacy.contoso.com 5 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers 1 2 E2013 CAS E2013 MBX 3. Create Legacy namespace Create DNS record to point to legacy E2007 CAS Exchange 2007 SP3 Servers E2007 SP3 HUB E2007 SP3 CAS 4 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS RU RU RU RU Intranet site 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA and ExRCA 6 7 E2007 SP3 MBX 6. Move Mailboxes Build out DAG Move E2007 users to E2013 MBX Internet facing site – Upgrade first 7. Repeat for additional sites

Upgrade to Exchange Server 2013 Clients 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate autodiscover.contoso.com mail.contoso.com 1 2. Deploy Exchange 2013 servers 3. Create Legacy namespace Exchange 2010 or 2007 Servers 4. Obtain and Deploy Certificates E2010 or 2007 HUB E2010 or 2007 CAS 5. Switch primary namespace to Exchange 2013 CAS SP/RU SP/RU 6. Move Mailboxes Intranet site 7. Repeat for additional sites E2010 or 2007 MBX Internet facing site – Upgrade first

Prepare for Exchange Server 2013 Install coexistence update on all existing Exchange servers For Exchange 2010, this would be SP3 For Exchange 2007, this would be SP3 RU10 Prepare Active Directory with Exchange 2013 schema extensions Validate existing client access Microsoft Connectivity Analyzer - https://testconnectivity.microsoft.com/?tabid=client Remote Connectivity Analyzer - http://www.exrca.com Built-in Test cmdlets

Upgrade to Exchange Server 2013 Clients 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate autodiscover.contoso.com mail.contoso.com 2 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers 2. Deploy Exchange 2013 CU1 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 3. Create Legacy namespace Exchange 2010 or 2007 Servers E2010 or 2007 HUB E2010 or 2007 CAS 4. Obtain and Deploy Certificates SP/RU 5. Switch primary namespace to Exchange 2013 CAS SP/RU Intranet site 6. Move Mailboxes 7. Repeat for additional sites E2010 or 2007 MBX Internet facing site – Upgrade first

Deploy Exchange Server 2013 Install both MBX and CAS Servers MBX performs PowerShell commands CAS is proxy only Exchange 2013 Setup GUI or command line In-place upgrades are not supported Updated to reflect Exchange 2013 roles Parameters New required parameter for license terms acceptance Install Setup.exe /mode:install /roles:clientaccess Setup.exe /mode:install /roles:mailbox Setup.exe /mode:install /roles:ManagementTools Other required parameter - /IAcceptExchangeServerLicenseTerms

Upgrade to Exchange Server 2013 Clients 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate autodiscover.contoso.com mail.contoso.com 3 legacy.contoso.com 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX Exchange 2010 or 2007 Servers 3. Create Legacy namespace E2010 or 2007 HUB E2010 or 2007 CAS 4. Obtain and Deploy Certificates SP/RU SP/RU 5. Switch primary namespace to Exchange 2013 CAS Intranet site 6. Move Mailboxes 7. Repeat for additional sites E2010 or 2007 MBX Internet facing site – Upgrade first

Create Legacy Namespace Required for Exchange 2007 coexistence only Create DNS record in internal and external DNS for legacy namespace Validate legacy namespace using MCA, ExRCA and built-in Test cmdlets

Upgrade to Exchange Server 2013 Clients 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate autodiscover.contoso.com mail.contoso.com legacy.contoso.com 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 3. Create Legacy namespace Exchange 2010 or 2007 Servers E2010 or 2007 HUB E2010 or 2007 CAS 4 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and autodiscover namespace Deploy certificates on Exchange 2007 CAS SP/RU SP/RU Intranet site 5. Switch primary namespace to Exchange 2013 CAS E2010 or 2007 MBX 6. Move Mailboxes 7. Repeat for additional sites Internet facing site – Upgrade first

Certificates End-to-End certificate wizard in the EAC EAC notifies you when a certificates is about to expire 1st notification shown 30 days prior to expiration Subsequent notifications provided daily Best Practices Minimize the number of certificates Minimize number of hostnames Use split DNS for Exchange hostnames Don’t list machine hostnames in certificate hostname list Use Subject Alternative Name (SAN) certificate

Upgrade to Exchange Server 2013 Clients autodiscover.contoso.com mail.contoso.com 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate legacy.contoso.com 5 E2013 CAS E2013 MBX 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers Exchange 2010 or 2007 Servers 3. Create Legacy namespace E2010 or 2007 HUB E2010 or 2007 CAS 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS SP/RU SP/RU Intranet site 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets E2010 or 2007 MBX 6. Move Mailboxes Internet facing site – Upgrade first 7. Repeat for additional sites

Switch Primary Namespace Validate legacy namespace creation Configure Load balancing Legacy namespace is separate VIP with Layer 7 load balancer Configure AutoDiscoverServiceInternalUri on Exchange 2013 CAS to LB FQDN Configure AutoDiscoverSiteScope Update DNS Mail and Autodiscover namespaces should point to CAS 2013 Update publishing rules for legacy namespace Use MCA and ExRCA to test access externally and internally

Switching OA to CAS 2013 Clients Layer 7 LB Layer 4 LB mail.contoso.com RPC/HTTP Layer 7 LB Layer 4 LB RPC/HTTP HTTP PROXY 1. Enable Outlook Anywhere on all legacy CAS 2. IIS authentication methods IIS Auth must have NTLM enabled on all legacy CAS HTTP PROXY E2007/E2010 CAS E2007/E2010 CAS E2013 CU1 CAS OA Enabled Disabled Enabled OA Enabled Client Settings IIS Auth: NTLM OA Client Settings IIS Auth: Client Auth: Basic 3. Client settings Make legacy OA settings the same as 2013 CAS so all clients get the same proxy hostname NTLM IIS Auth: Basic NTLM RPC RPC RPC 4. DNS cutover A low TTL on the existing record the days prior to the cutover is a good idea. E2007/E2010 MBX E2013 CU1 MBX E2007/E2010 MBX Internet-facing site Intranet-facing site

Upgrade to Exchange Server 2013 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate Clients autodiscover.contoso.com mail.contoso.com legacy.contoso.com 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 3. Create Legacy namespace 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS Exchange 2010 or 2007 Servers E2010 or 2007 HUB E2010 or 2007 CAS SP/RU SP/RU Intranet site 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets 6 6. Move Mailboxes Build out DAG Move users to E2013 MBX E2010 or 2007 MBX Internet facing site – Upgrade first 7. Repeat for additional sites

Moving Mailboxes New Migration Service New cmdlets Provides functionality to orchestrate moves such as batch management Provides migration reporting Provides retry semantics New cmdlets New-MigrationBatch Get-MigrationUserStatistics Also available from EAC

Public Folder Migrations

Public Folder Roadmap

Modern Public Folders Database-centered architecture replaced by mailbox 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 Public Folders Exchange 2010/2007 users cannot access Exchange 2013 Public Folders Migration of Public Folders is a cut-over migration Similar to online mailbox moves

Public folder migration from Exchange 2007 or Exchange 2010 Public Folders 1. Prepare Install Exchange SP and/or updates across the ORG Migrate all users that require access to Exchange 2013 Outlook clients 2. Analyze Take snapshot of existing PF folder structure, statistics and permissions Map PF folders to PF mailboxes 4 E2007 SP3 or E2010 RU10 SP3 Exchange 2013 CU1 1 2 3. Create new public folder mailboxes Set to HoldForMigration Mode, mailboxes invisible to clients PF dbase 1 PFs PF mbx 1 4. Begin migration request Clients continue to access and create new data during copy After copy is complete migration request status is AutoSuspended 3 MBX MBX MBX 5 PF dbase 2 PF mbx 2 5. Finalize migration request Update snapshot of existing PF folder structure, statistics and permissions Lock source, clients logged off, final sync occurs PF mbx 3 PF dbase 3 PF 6 6. Validate Check and verify destination folders

Public Folder Migration Process Analyze existing Public Folders Tool available to analyze existing Public Folder hierarchy to determine how many Exchange 2013 Public Folder mailboxes are recommended Copy Public Folder data Users access existing Public Folder deployment while data 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 finalized Once migration completes, everyone switches at the same time Can switch back, but any post migration Public Folder changes are lost

Public Folder Migrations Mail-enabled public folders Legacy and Modern Public Folders cannot coexist; messages routed to one place Public Folders locked for last phase of migration Messages sent while locked get stuck in queue with an error message: Failed to process message due to a transient exception with message Cannot open mailbox Forcing connection/message retry won’t fix this After migration is complete, restart Transport service on servers with stuck messages Messages will be redirected to modern PFs Subsequent messages sent to legacy folders will be redirected to modern PFs In both cases, redirect event logged in message tracking

Public Folders – Exchange 2007/2010

Public Folders – Exchange 2013

Public Folder Scripts Option 1. Exchange 2013 CU1: $exscripts

Public Folder Scripts Option 2. Download http://www.microsoft.com/en-us/download/details.aspx?id=38407

Get-OrganizationConfig Exchange 2007 Exchange 2010

Get-OrganizationConfig Exchange 2013

Unified Messaging

Upgrade Unified Messaging Download and install the required UM language packs on every mailbox server Export/Import auto attendant custom greetings, announcements, menus, and prompts (.\MigrateUMCustomPrompts.ps1) Export and import certificates Configure UM startup mode on Client Access servers (TCP/TLS/Dual)

Upgrade Unified Messaging ...cont’d Configure UM startup mode on Mailbox servers (TCP/TLS/Dual) Create/configure existing UM dial plans Create/configure existing UM IP gateways Create a new UM hunt group Create/configure UM auto attendant Create/configure UM mailbox policies

Upgrade Unified Messaging Move existing UM-enabled mailboxes to Exchange 2013 Enable new users for UM or configure settings for an existing UM-enabled user Configure your VOIP gateways, IP PBXs, and SIP-enabled PBXS to send all incoming calls to the Exchange 2013 Client Access servers Disable call answering on Exchange 2007/2010 UM Remove Exchange 2007/2010 from dial plans

Lync and Exchange Possibilities Lync 2010 and 2013 IM integration into Exchange 2013 OWA Configuring Exchange 2013 Unified Messaging for Lync 2010 and 2013 Voicemail access

Managing Coexistence

Management Tools Coexistence Use the Exchange Administration Center (EAC) to: Manage Exchange 2013 mailboxes View and update Exchange 2010/2007 mailboxes and properties (with a few limitations) Use Exchange Management Console (EMC) to: Create mailboxes Perform new operations on those versions

Summary

Summary Updates are required for coexistence Exchange 2007 requires a legacy namespace Certificate management is improved Public Folder migration is cutover process

CAS 2013 Client Protocol Connectivity Flow Exchange 2007 user accessing Exchange 2010 namespace Exchange 2007 user accessing Exchange 2013 namespace Exchange 2010 user accessing Exchange 2013 namespace Requires 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 Non-silent redirect (not SSO) to CAS 2007 externally facing URL Proxy to CAS 2010 Cross-site silent redirect (not SSO), which may redirect to CAS 2010 or CAS 2013 EAS EAS v12.1+ : Autodiscover & redirect Older EAS devices: proxy Proxy to MBX 2013 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 POP/IMAP Proxy OAB RPS n/a ECP Cross-site redirect, which may redirect to CAS 2010 or CAS 2013

Protocol Flow Summary Basic principles to apply are: Co-existence with 2010 – CAS 2013 proxies all traffic to CAS 2010 Co-existence with 2007 – CAS 2013 redirects OWA to CAS 2007, proxies AutoDiscover, POP, IMAP and OA, and relies on AutoDiscover for EWS We no longer do HTTP 451 redirects We hand out site specific URL’s if they are set, but if a client comes to the wrong place, Exchange just proxy

Public Folders Summary Public Folder migration is similar to online mailbox moves Users continue to access existing Public Folder deployment while data is copied Make sure replication between source public folder databases is healthy Migrate users first Users with Exchange 2007 and 2010 mailboxes will not have access to Public Folders after migration completes All Public Folders cut over to Exchange 2013 together Migrate users first ! There will be a short downtime while the migration is finalized Once migration completes, everyone switches at the same time Can revert, but any post migration Public Folder changes are lost

Planning for Exchange 2013 Exchange 2013 Deployment Assistant Exchange 2013 Planning TechNet – Planning and Deployment Exchange Team Blog Server Role Requirements Calculator 19-11-2018 EG Copyright

Questions?

Match of technical Level Evaluation Scale: 1 = Very bad 2 = Bad 3 = Relevant 4 = Good 5 = Very Good! Questions: Speaker Performance Relevance according to your work Match of technical level according to published level Comments Evaluation Create a Text message on your phone and send it to 1919 with the content: UC305 5 5 5 I liked it a lot Session Code Peter Performance (1 to 5) Relevance (1 to 5) Match of technical Level (1 to 5) Comments (optional)

Thank you © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation.  Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.  MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.