10. Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange Server 2003 RTM6870 Exchange Server 2003 SP16870 Exchange Server 2003 SP26870 Exchange Server 2007 RTM10637 Exchange Server 2007 SP111116 Exchange Server 2007 SP214622 Exchange Server 2007 SP314625 Exchange Server 2010 RTM14622 ExchangeServer 2010 SP114726 Exchange Server 2010 SP214732 Exchange Server 2010 SP314734 Exchange Server 201315137 Exchange Server 2013 CU115254 Exchange Server 2013 CU215281

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

15. SP3 E2010 CAS E2010 HUB E2010 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 Servers SP3 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 4. Switch primary namespace to Exchange 2013 CAS E2013 fields all traffic, including traffic from Exchange 2010 users Validate using MCA and ExRCA 5. Move Mailboxes Build out DAG Move E2010 users to E2013 MBX 6. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers SP3 E2013 CAS E2013 MBX 3. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers 12 4 3 5 6

16. RU E2007 SP3 CAS E2007 SP3 HUB E2007 SP3 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2007 SP3 Servers RU 1. Prepare Install Exchange 2007 SP3 + RU across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA and ExRCA 6. Move Mailboxes Build out DAG Move E2007 users to E2013 MBX 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers RU E2013 CAS E2013 MBX 3. Create Legacy namespace Create DNS record to point to legacy E2007 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 legacy.contoso.com3 1 2 5 4 6 7

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

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

20. Setup.exe /mode:install /roles:clientaccess Setup.exe /mode:install /roles:mailbox Setup.exe /mode:install /roles:ManagementTools /IAcceptExchangeServerLicenseTerms

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

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

27. E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets 6. Move Mailboxes 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 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 legacy.contoso.com 3. Create Legacy namespace SP/RU 5

29. Layer 4 LB Layer 7 LB mail.contoso.com HTTP PROXY RPC/HTTP Clients 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 PROX Y 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 Client Auth: Basic IIS Auth: Basic NTLM E2013 CU1 CAS E2013 CU1 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.

30. E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets 6. Move Mailboxes Build out DAG Move users to E2013 MBX 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 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 legacy.contoso.com 3. Create Legacy namespace SP/RU 6

35. Legacy Public FoldersModern Public Folders Content storagePublic Folder databasePublic Folder mailbox Public Folder content replicationCan be replicated between databasesReplication is not possible High availabilityPF replicationDAG PF Hierarchy storageOne per PF database, multi-masterPer PF mailbox, one master only PF Hierarchy synchronizationBased on e-mailDirect mailbox sync SearchItems onlyItems and attachments (full-text) Public Folder permission management Access Control Lists (ACLs)Role-based Access Control (RBAC) Public Folder Client permissionsAccess Control Lists (ACLs) Admin PlatformPF Management Console + EMSEAC + EMS Outlook client supportAny Outlook versionOutlook 2007 - 2013 OWA supportOWA 2007, OWA 2010OWA 2013 Exchange Server supportExchange 2010 or earlierExchange 2013

36. 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 2013 Verify PF health (replication, mail flow, etc.) 4. 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 1 2 4 6 MBX 6. Validate Check and verify destination folders PF dbase 2 PF dbase 3 E2007 SP3 or E2010 PF Exchange 2013 CU1 PF mbx 1PF mbx 2 MB X 5 PF dbase 1 PFs PF mbx 3 3 RU1 0 SP3

52. Questions?