Scott Schnoll m Microsoft Corporation

Exchange 2013 Architecture Architecture Changes CAS, Hub, UM Mailbox Layer 7 Load Balancer Exchange 2010 Architecture Auth, Proxy, Redirect Protocols, API, Biz-logic Assistants, Store, CI Layer 7 or Layer 4 Load Balancer Auth, Proxy, Redirect Client Access Store, CI Protocols, API, Business Logic Mailbox

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers E2010 HUB Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site E2010 Servers 1. Prepare Verify prerequisites Install Exchange 2010 SP3 across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 4. Switch primary namespace to Exchange 2013 CAS Exchange 2013 fields all traffic, including traffic from Exchange 2010 users Validate client access 5. Move Mailboxes Build out DAG Move Exchange 2010 users to Exchange 2013 MBX 6. Repeat for additional sites 3. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 CAS E2010 CAS E2010 MBX E2013 CAS E2013 MBX SP

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers E2007 SP3 HUB Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site E2007 SP3 Servers 1. Prepare Verify prerequisites Install Exchange 2007 SP3 + RU10 across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS Validate client access 6. Move Mailboxes Build out DAG Move Exchange 2007 users to Exchange 2013 MBX 7. Repeat for additional sites 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 CAS Deploy certificates on Exchange 2007 CAS E2007 SP3 CAS E2007 SP3 MBX E2013 CAS E2013 MBX RU Create Legacy namespace Create DNS record to point to legacy Exchange 2007 CAS legacy.contoso.com 3

2. Deploy Exchange 2013 servers Upgrading to Exchange Server 2013 E2010 or E2007 HUB Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site E2010 or E2007 Servers 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 4. Obtain and Deploy Certificates 1 E2010 or E2007 CAS E2010 or E2007 MBX SP/RU 3. Create Legacy namespace

1

1

1

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and Client Access servers Upgrading to Exchange Server 2013 Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 4. Obtain and Deploy Certificates 2 3. Create Legacy namespace E2010 or E2007 HUB E2010 or E2007 Servers E2010 or E2007 CAS E2010 or E2007 MBX E2013 CAS E2013 MBX

Exchange Server 2013 Setup 2 Setup.exe /mode:install /roles:c,m /IAcceptExchangeServerLicenseTerms

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers Upgrading to Exchange Server 2013 Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 4. Obtain and Deploy Certificates 3. Create Legacy namespace Create DNS record to point to legacy Exchange 2007 CAS legacy.contoso.com 3 E2010 or E2007 HUB E2010 or E2007 Servers E2010 or E2007 CAS E2010 or E2007 MBX E2013 CAS E2013 MBX

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and Client Access servers Upgrading to Exchange Server 2013 Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 CAS Deploy certificates on Exchange 2007 CAS 4 3. Create Legacy namespace Create DNS record to point to legacy Exchange 2007 CAS legacy.contoso.com E2010 or E2007 HUB E2010 or E2007 Servers E2010 or E2007 CAS E2010 or E2007 MBX E2013 CAS E2013 MBX

Certificates End-to-end wizard in the Exchange Admin Center (EAC) Export and import with private key to all other CAS from the UI Assign services right from the UI EAC provides notification when a certificate is about to expire First notification 30 days prior to expiration Subsequent notifications every 24 hours 4

4

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers Upgrading to Exchange Server 2013 Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS Validate client access 6. Move Mailboxes 7. Repeat for additional sites 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 Client Access Servers Deploy certificates on Exchange 2007 CAS 5 3. Create Legacy namespace Create DNS record to point to legacy Exchange 2007 CAS legacy.contoso.com E2010 or E2007 HUB E2010 or E2007 Servers E2010 or E2007 CAS E2010 or E2007 MBX E2013 CAS E2013 MBX

Switching to CAS 2013 Configure load balancing Layer 7 load balancers are no longer required for the primary Exchange 2013 namespace Layer 4 is supported for the Exchange 2013 namespace Legacy namespace Validate creation with Configure legacy namespace to use layer 7 load balancing Switch namespaces to CAS 2013 Update mail and Autodiscover DNS records to point to CAS 2013 Configure Outlook Anywhere 5

OWA Redirect in CU2 OWA Single-Sign-On Silent Redirects are back! 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! Does rely on Exchange handling FBA itself 3

Layer 4 LB E2013 CAS IIS HTTP Proxy E2013 MBX Protocol Head DB E2010 CAS Protocol Head E2010 MBX Store DB Site Boundary E2010 CAS Protocol Head E2010 MBX Store DB Cross-Site Proxy Request Layer 7 LB Cross-Site Redirect Request Silent SSO in CU2! OWA europe.mail.contoso.commail.contoso.com 24

Layer 4 LB E2013 CAS IIS HTTP Proxy E2013 MBX Protocol Head DB E2007 CAS Protocol Head E2007 MBX Store DB Site Boundary E2007 CAS Protocol Head E2007MBX Store DB RPC Layer 7 LB Cross-Site Redirect Request Silent SSO in CU2! OWA Layer 7 LB legacy.contoso.commail.contoso.comeurope.mail.contoso.com Cross-Site Proxy Request 25 Same-Site Redirect Request Silent SSO in CU2!

ProtocolExchange 2007 user accessing Exchange 2010 namespace Exchange 2007 user accessing Exchange 2013 namespace Exchange 2010 user accessing Exchange 2013 namespace RequiresLegacy namespace No additional namespaces OWA Same AD Site: Silent SSO FBA redirect Externally facing AD site: manual or silent/SSO Cross-site redirect Internally facing AD site: proxy to CAS 2007 Silent SSO redirect to CAS 2007 externally facing URL in same-site or cross-site Same AD Site: Proxy to CAS 2010 or Different AD Site: Silent SSO cross-site redirect EAS EAS v12.1+ : Autodiscover & redirect Older EAS devices: proxy Proxy to MBX 2013Proxy to CAS 2010 Outlook Anywhere Direct CAS 2010 supportProxy to CAS 2007 AutodiscoverExchange 2010 answers Autodiscover query for 2007 User Exchange 2013 answers Autodiscover query for 2007 User EWSUses Autodiscover to find CAS 2007 EWS External URL POP/IMAPProxy to CAS 2007 OABDirect CAS 2010 supportProxy to CAS 2007 RPSn/a ECP Proxy to CAS 2010 or Cross-site redirect, which may redirect to CAS 2010 or CAS 2013

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

2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers Upgrading to Exchange Server 2013 Internet-facing site autodiscover.contoso.com mail.contoso.com Intranet site 1. Prepare Verify prerequisites Install Exchange SP and/or updates across the ORG Prepare AD (Exchange 2013 schema, Org, Domains) Validate existing client access 5. Switch primary namespace to Exchange 2013 CAS Validate client access 6. Move Mailboxes Build out DAG Move users to Exchange 2013 MBX 7. Repeat for additional sites 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 Client Access Servers Deploy certificates on Exchange 2007 CAS 6 3. Create Legacy namespace Create DNS record to point to legacy Exchange 2007 CAS legacy.contoso.com E2010 or E2007 HUB E2010 or E2007 Servers E2010 or E2007 CAS E2010 or E2007 MBX E2013 CAS E2013 MBX

6

Exchange Server 2013 Public Folders Database-centric architecture replaced by mailbox End user experience doesn’t change Public Folder replication is removed Existing Public Folders must be migrated to Exchange Server 2013 Migration of Public Folders is a cut-over migration Similar to online mailbox moves Migrate Public Folder users before Public Folders Exchange Server 2013 users can access down level Public Folders Exchange Server 2010/2007 users cannot access Exchange Server 2013 Public Folders Public Folders have limited OWA support in Exchange 2013 RTM CU1/CU2

2. Analyze Take snapshot of existing PF folder structure, statistics and permissions Map PF folders to PF mailboxes Outlook Clients 1. Prepare Install Exchange SP and/or updates across the ORG Migrate all users that require access to Exchange Begin Migration Request 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 3. Create new Public Folder mailboxes Set to HoldForMigration Mode, mailboxes invisible to clients MBX 6. Validate Check and verify destination folders PF dbase 2 PF dbase 3 E2007 SP3 or E2010 PF Exchange 2013 PF mbx 1PF mbx 2 MBX 5 PF dbase 1 PFs PF mbx 3 3 RU10SP3

EWS Clients and Legacy Public Folders EWS clients with mailboxes on 2013 will not be able to access legacy PFs Entourage 2008 EWS Edition Outlook for Mac 2011 Custom EWS scripts accessing PF data

Publishing Exchange to the Internet Continue to use TMG/UAG if you already have one deployed Continue to use whatever 3 rd party solution if it’ll work 7/17/life-in-a-post-tmg-world-is-it-as-scary-as-you- think.aspx

Managing Coexistence Use the Exchange Admin Center (EAC) to: Manage Exchange 2013 mailboxes View/update Exchange 2010/2007 mailbox properties (with a few limitations) Use the Exchange Management Console (EMC) to: Create mailboxes on legacy Exchange versions (Exchange 2007/2010)

Quota Calculations Mailbox and Public Folder data moved from legacy Exchange 2013 will appear to grow 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 them to The database size on disk does NOT increase

Upgrade and Coexistence Summary Updates are required for Exchange Server 2013 coexistence Exchange Server 2010 SP3 or 2007 SP3 RU10 are required, including Edge Transport servers Exchange 2007 requires a legacy namespace for coexisting with Exchange 2013 OWA SSO redirects are back in RTM CU2 Exchange 2013 Public Folders utilize the mailbox architecture Migration planning is required and it is big-bang cutover migration TMG/UAG Publishing Slight modifications required to work with Exchange Server 2013 Exchange Server 2013 Deployment Assistant

1. Download both Exchange Server 2013 and Lync Server 2013 and try in your own environmentExchange Server 2013 Lync Server Trial Exchange and Lync Online Trial Exchange and Lync Online 3. Contact your Microsoft or Partner Account Manager to arrange a time test drive Exchange and Lync in one of our Customer Immersion Experience Centres 4. Contact your Microsoft or Partner Account Manager to get a Lync business value assessment or an Exchange and Lync technical briefing