Microsoft. Exchange Referent: Daniel Glomb System Architect

Transcription

1 Microsoft Exchange 2013 Referent: Daniel Glomb System Architect

2 Agenda What s new Architecture Client Access Server Mailbox Server Migration Outlook 2013 / OWA

3 What s new in Exchange 2013 Exchange Administration Center (EAC) Public Folder Security in Exchange 2013 Data Loss Prevention (DLP) ediscovery Updates Cumulative Updates (CU) Security Updates

4 Exchange 2013 Prerequisites Server Operating Systems Windows Server 2008 R2 (Enterprise with DAG) Windows Server 2012 Supported Client Access Methods Outlook 2013, 2010, 2007 RPC over HTTP is only method of connectivity for Outlook clients Web Services Entourage 2008 for Mac, Outlook for Mac 2011 Supported Coexistence scenarios Exchange Server 2010 SP3, Exchange Server 2007 SP3 (+ coexistence RU 10) No Exchange 2003 or older Exchange systems are supported, No in-place upgrades MAPI / CDO Exchange Server 2013 last version with support

5 Administration Tools Exchange admin center (EAC) Webfrontend URL: Mailbox Server required Public Folder integration Exchange Management Shell (EMS) PowerShell with CMDlet for Exchange Exchange Toolbox Templates Editor Remote Connectivity Analyzer Queue Viewer

6 DEMO Exchange Admin Tools

7 Exchange 2010 Server Role Architecture Client Access for client connectivity and web services Forefront Online Protection for Exchange Internal Network Phone system (PBX or VOIP) Mailbox for storage of data Edge Transport Routing and AV/AS Hub Transport Routing and policy Hub Transport for internal routing and policy enforcement Edge Transport for routing and anti-malware from the edge of the organization External SMTP Server Mobile phone Web browser Layer 7 LB Mailbox Stores mailbox and public folder items Client Access Client connectivity Web services Unified Messaging Voice mail and voice access Unified Messaging for voice mail and voice access Outlook (remote user) Outlook (local user) Line of business application AD

8 Layer 4 LB Exchange 2013 Server Role Architecture 2 building blocks Client Access Array Evolution of E2010 CAS Array SMTP Front-End Database Availability Group Evolution of E2010 DAG Includes core server protocols External SMTP Server Exchange Online Protection Internal Network CAS Array DAG AD Mobile device Web browser Outlook (remote user) Outlook (local user) Line of business application Phone system (PBX or VOIP)

9 Functional Layering E2010 Architecture E2013 Architecture Hardware LB L7 LB L4 LB AuthN, Proxy, Re-direct CAS2013 CAS, HT, UM AuthN, Proxy, Re-direct Protocols, API, Biz-logic Protocols, Assistants, API, Biz-logic MBX2013 MBX Assistants, Store, CI Store, CI

10 Exchange access path EWS protocol MRS proxy protocol SMTP Protocols, Server Agents EWS RPC CA MRS MRSProxy Assistants Transport Custom WS Transport Assistants MRS MRSProxy RPC CA EWS Business Logic XSO CTS MailItem Other API E2010 Banned XSO CTS MailItem Other API Storage Store ESE Content index File system Store ESE Content index File system Server1 (V n ) Server2 (V n+1 )

11 Client Protocol Architecture in Exchange 2013 Outlook Web App Outlook EAS EAC PowerShell POP/IMAP SMTP SIP + RTP HTTP SIP Load Balancer Client Access IIS HTTP Proxy POP, IMAP POP, IMAP SMTP SMTP UM Redirect RPS RpcProxy RPC CA IIS OWA, EAS, EWS, ECP, OAB POP IMAP Transport UM Mailbox MDB MailQ

12 Load Balancing 4 LB (protocol layer) no IP/Cookie affinity required no Layer 7 LB required (application layer) availability probe Connection forwarding / proxy independent from Client Access Server LB detects CAS maintenance DNS Round Robin no fault detection

13 CAS consequences Outlook Anywhere is default No RPC between Client and CAS No RPC between CAS and MBX CAS Array exists no longer Outlook Server is Mailbox GUID (msexchang boxguid) 13

14 Mailbox Server - Database Extensible Storage Engine (ESE) own worker process multiple store threads I/O reduction, since Exchange 2003 ca. 97 % Mailbox 100GB+ Public Folder 14

15 Mailbox Server - High Availability Database Availability Group Can have a maximum of 16 Mailbox Servers DAG members can be in different sites 50% I/O reduction on the passive copy Auto Reseed Feature Managed Availability Self Monitoring Workload Management Restart Failover / Reboot Escalate

16 Public Folders Architectural bet Public folders are based on the mailbox architecture Details Hierarchy is stored in PF mailboxes (one writeable) Content can be broken up and placed in multiple mailboxes The hierarchy folder points to the target content mailbox Uses same HA mechanism as mailboxes No separate replication mechanism Single-master model Similar administrative features to current PFs (setting quota, expiry, etc.) No end-user changes (looks just like today s PFs)

17

18 Use proximity searches to understand context Fine tune complex queries Get instant statistics Query results across Exchange, Lync & SharePoint Laser focused refiners to help find the data you need

19 Who What Where

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

21 Upgrading to Exchange 2013 from an existing Exchange 2007 environment E2007 SP3 HUB E2007 SP3 MBX Clients autodiscover.contoso.com mail.contoso.com legacy.contoso.com 1 2 RU E2007 SP3 CAS Internet facing site Upgrade first E2013 CAS Exchange 2007 Servers RU Intranet site 6 7 E2013 MBX 1. Prepare Install Exchange 2007 SP3 + RU10 across the ORG Prepare AD with E2013 schema and validate 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers 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 5. Switch primary namespace to Exchange 2013 CAS Validate using Remote Connectivity Analyzer 6. Move Mailboxes Build out DAG Move E2007 users to E2013 MBX 7. Repeat for additional sites

22 DEMO Outlook 2013 / OWA

23