1. Exchange Server 2013 Architecture
Peter O’Dowd
Datacom Systems (Wellington) Ltd
OFC306

2. Agenda Fundamentals Client Connectivity
Namespace Planning & Principles
Microsoft’s Preferred Deployment Architecture

3. Exchange Server 2013 Fundamentals

4. Exchange 2013 Server Role Architecture
2 building blocks:
Client Access Array
Database Availability Group
Edge Transport Role
Loosely coupled
Functionality
Versioning
User partitioning
Geo affinity
Enterprise Network AD
MBX
DAG
CAS
CAS Array
Exchange Online Protection
Edge Transport
Routing and AS
Layer 4 or Layer 7 LB
External
SMTP servers
Web
browser
Outlook
(remote user)
Mobile
phone
Outlook (local user)
Line of
business
application
Phone system (PBX or VOIP)

5. Every Server is an Island
EWS protocol
MRS proxy protocol
SMTP
Protocols,
Server Agents
EWS
RPC CA
Transport
Assistants
MRS MRSProxy
Custom WS
Business Logic
XSO
Mail Item
Other API
CTS
E2010
Banned
Storage
Store
Content index
File system
ESE
Server1 (Vn)
Server2 (Vn+1)

6. The key to enlightenment…
The protocol stack used to access a mailbox is always on the Mailbox server that hosts the active database copy
Each CAS determines the right endpoint for the traffic, so all sessions – regardless of where they start – end up in the same place
Rendering for clients like OWA, and Transport transcoding, occurs on the Mailbox server
User
CAS
DAG1
MBX-A
MBX-B

7. What is the Client Access server role?
TechReady13
4/24/2017
What is the Client Access server role?
Domain-joined machine in the corporate forest
Thin, stateless protocol proxy server
Comprised of three components:
Client Access Front End aka CAFÉ (HTTP, IMAP, and POP protocol proxy)
Front End Transport service (SMTP protocol stack and proxy)
UM Call Router
Provides unified namespace and authentication
Contains logic to route protocol requests to the appropriate destination endpoint
Capable of supporting legacy servers with redirect or proxy logic
© 2011 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.

8. What is the Mailbox server role?
Server that hosts all of the components that process, render and store Exchange data
Connectivity for mailbox access is via CAS to Mailbox*
Exchange 2013 evolves the DAG
DAG includes new repair and recovery features
DAG includes networking enhancements
DAG leverages Windows Server 2012 R2 features

9. >93% Exchange IOPS Trend reduction! DB IOPS/Mailbox 1 0.8 0.6 0.4
0.2
>93%
reduction!

10. ESE & Store Improvements
Microsoft Office365
4/24/2017
ESE & Store Improvements
Log checksum recovery from single-bit errors
8KB Page Size
32KB Page Size
Incremental Resync
Gap Coalescing
Lost Write Detection
Database Compression
1 Million Items / Folder
Fast Failover
TBA Store Maintenance
64-bit architecture
Improved Async Read Capability
100MB Checkpoint Depth on Active Copies
BDM for Active and Passives
Per-Mailbox Tables
Managed Store
Continuous Replication
STM Removed
AutoReseed
Tuned Maintenance Writes
50 Databases / server
Parallel Mounting
Improved IO Coalescing
Physical Contiguity Store Schema Changes
Pre-read Keys
Lazy View Update Changes
2013
2007
2010
Database Space Allocation Hints
B+ Tree Defrag
1MB Log Files
1:1 Read:Write Ratio
No more deferred content conversion
100,000 Items / Folder
Lazy Indexes
Database Cache Compression
Database Cache Priority
20,000 Items / Folder
Online Database Checksum
Online Page Zeroing
Single Page Restore
Multiple Databases / JBOD Disk
Smooth IO Writes
JBOD Support
Version Store Improvements
Lagged Copy Enhancements
1GB Mailboxes
Standby Continuous Replication
Page Dependency Removal
Support for 231 log generations
10GB Mailboxes
100 Databases / Server
Optimized for 7.2K RPM Disks
Hung IO and Bluescreen Support
100MB Checkpoint Depth on Passive Copies
Per-Database Process
Lost Log Resilience
Log Roll
Store Quarantine
Message properties stored as blobs
Cache Warming on Passive
Cache Maintained after Recovery
128MB Extent Size
OS Upgrade Support
100GB Mailboxes
Elimination of Partial B+ Merges
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

11. What is the Edge Transport server role?
Handles all Internet-facing mail flow
Designed to run in a perimeter network
Does not have to be joined to a domain
Uses EdgeSync process to provide one-way replication of recipient and configuration information
Communicates with FET when roles are co-located
Includes anti-spam, but no antivirus
PowerShell management only
Edge Transport Servers
Mail flow
Mailbox
Servers
EOP
EdgeSync
TCP 50636 AD
Client Access
Servers
External
SMTP servers

12. Transport Architecture
TechReady 16
4/24/2017
Transport Architecture
2 Recipients
DAG
CAS
CAS
Front-End Transport
Front-End Transport
MBX
MBX
Transport
Transport
MBX Transport
MBX Transport
MDB
MDB
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

13. Transport components Transport ships as part of 3 major components
TechReady 16
4/24/2017
Transport components
Transport ships as part of 3 major components
Front End Transport – Stateless SMTP service on client access role
Transport – Stateful SMTP service on mailbox role
Mailbox Transport – Stateless SMTP service on mailbox role
Transport responsibilities
Receive and deliver all inbound mail to the organization
Submit and deliver all outbound mail from the organization
Perform all message processing within the pipeline
Support extensibility within pipeline
Keep messages redundant until successfully delivered
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

14. Front End Transport … Enterprise Network Client Access Server (CAS)
TechReady 16
4/24/2017
Front End Transport AD
Web
browser
Outlook
(remote user)
Mobile
phone
Outlook (local user)
External
SMTP servers
Exchange Online Protection
Enterprise Network
Layer 4LB
CAS Array
CAS
DAG2
MBX …
DAG3
DAG1
Client Access Server (CAS)
Evolution of E2010 CAS Array
Now includes SMTP Frontend Transport
Primary function is to get the client to the right MBX server
Mailbox Server
Now includes all core messaging protocols
Now includes Transport and Mailbox Transport (Delivery & Submission)
Edge Transport Server
Perimeter network SMTP gateway
Front End Transport
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

15. TechReady 16
4/24/2017
Front End Transport
Authenticated
SMTP
Handles inbound and outbound external SMTP traffic (does not replace Edge Transport Server)
Listens on TCP25 and TCP587 and TCP717
Handles authenticated client submissions
Functions as a layer 7 proxy and has full access to protocol conversation (inbound)
Does not queue or bifurcate mail locally
All outbound traffic to next hop appears to come from the CAS2013
Anonymous
SMTP
SMTP Send
SMTP to
MBX 2013
External SMTP
Frontend Transport
:25
:587
SMTP Receive
Protocol Agents
Mailbox Selector
:717
MSExchangeFrontendTransport.exe
SMTP from MBX 2013
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

16. Front End Transport Features
TechReady 16
4/24/2017
Front End Transport Features
Network protection – centralized, load balanced egress/ingress point for the organization
Mailbox locator – avoids unnecessary hops by determining the best Mailbox to deliver the message
Provides unified namespace, for authenticated and anonymous mailflow scenarios
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

17. Transport* … Enterprise Network Client Access Server Mailbox Server
TechReady 16
4/24/2017
Transport*
*previously known as Hub Transport AD
Web
browser
Outlook
(remote user)
Mobile
phone
Outlook (local user)
External
SMTP servers
Exchange Online Protection
Enterprise Network
Layer 4LB
CAS Array
CAS
DAG2
MBX …
DAG3
DAG1
Client Access Server
Now includes SMTP Frontend Transport
Mailbox Server
Now includes all core messaging protocols
Now includes Transport and Mailbox Transport (Delivery & Submission)
Edge Transport Server
Perimeter network SMTP gateway
Transport
Transport
Transport
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

18. Delivery Agents *other protocols
TechReady 16
4/24/2017
Transport*
*previously known as Hub Transport
SMTP from CAS
SMTP to CAS, MBX, HUB
Processes all SMTP mail flow for the organization
Will queue and route messages in and out of the organization
Performs content inspection
Supports extensibility in SMTP and categorizer
Listens on TCP 25 (or TCP when co-located with CAS)
Transport
:25 or :2525
SMTP Receive
Protocol Agents
:25
SMTP Send
Submission Queue
Categorizer
Routing Agents
Delivery Queue
Pickup/Replay
Delivery Agents *other protocols
Mail.que
Delivery Queue
Edgetransport.exe
SMTP from MBX-Transport Submission
SMTP to MBX-Transport Delivery
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

19. TechReady 16
4/24/2017
Transport Pipeline
All incoming mail is stored in the mail.que database
All mail passes through the various stages of the categorizer
There is exactly one submission queue but multiple delivery queues (one per destination)
Agents subscribe to various events along the pipeline – Transport rules agent; Journaling agent; Malware agent; 3rd party agents
:25 or :2525
SMTP Receive
Protocol Agents
On Submitted
On Resolved
On Routed
On Categorized
:25
External Delivery Queue
SMTP Send
Resolve
Recipients
Internal Delivery Queue
Find Route for Recipient
Content Conversion
& Bifurcation
Mailbox Delivery Queue
Submission Queue
Categorizer
Mail.que
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

20. TechReady 16
4/24/2017
Transport Features
Performs all routing decisions for internal and external messages
Provides an extensibility platform for third-party agents to operate within the pipeline
Allows messages to be routed in or out through connectors for special handling
Protects messages by making messages highly available on ‘shadow’ servers
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

21. Mailbox Transport … Enterprise Network Client Access Server
TechReady 16
4/24/2017
Mailbox Transport AD
Web
browser
Outlook
(remote user)
Mobile
phone
Outlook (local user)
External
SMTP servers
Exchange Online Protection
Enterprise Network
Layer 4LB
CAS Array
CAS
DAG2
MBX …
DAG3
DAG1
Client Access Server
Now includes SMTP Frontend Transport
Primary function is to get the client to the right MBX server
Mailbox Server
Now includes all core messaging protocols
Now includes Transport and Mailbox Transport (Delivery & Submission)
Edge Transport Server
Perimeter network SMTP gateway
Mailbox
Transport
Mailbox Transport
Mailbox Transport
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

22. TechReady 16
4/24/2017
Mailbox Transport
SMTP from
Transport
Mailbox Transport
SMTP Send
SMTP Receive
Submission
Mailbox Assistants
MAPI
Store
SMTP to
Transport
Submit Agents
:475
MSExchangeDelivery.exe
MSExchangeSubmission.exe
Deliver Agents
Delivery
Handles mail submission and delivery from/to Store using two separate processes
Performs MIME to MAPI conversion (and vice versa)
Combines Mailbox Assistant and Store Driver functionality
Uses local MAPI/RPC for delivery to and submission from Store
Does not have persistent storage
Does not support any extensibility
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

23. Mailbox Transport Features
TechReady 16
4/24/2017
Mailbox Transport Features
Brings together all transport scenarios that access mailbox store under one component
Eliminates the three-party mail submission hand-shake
Helps realize the “every server is an island” vision by ensuring MAPI is not used across the server
Simplifies handling of mailbox database *overs
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

24. 4/24/2017 4:45 PM
Managed Availability
Integrated monitoring and recovery infrastructure that detects and recovers from issues as they are discovered
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

25. Managed Availability Stuff breaks but the User Experience does not
OWA send
OWA failure
OWA failure detected
OWA recycle AppPool
OWA recycle complete
OWA verified as healthy
OWA recycle AppPool failed
Failover server’s databases
OWA service restarts
Server becomes “good” failover target (again) LB
CAS1
DAG
MBX1
DB1
DB1
DB2
OWA
OWA
OWA
OWA
MBX2
DB1
DB1
DB2
OWA
CAS2
MBX3
DB1
DB2
OWA

26. Client Connectivity

27. Client Protocol Architecture
OWA
EAS
EAC
Outlook
PowerShell
POP | IMAP
SMTP
Telephony
SIP + RTP
Load Balancer
Redirect
HTTP Proxy
IIS
POP
IMAP
SMTP UM
CAS2013
POP
IMAP
HTTP
SMTP
IIS
POP
IMAP
Transport UM
MBX2013
RPS
RpcProxy
OWA, EAS, EWS, ECP, OAB
MDB
MailQ
RPC CA

28. Outlook Connectivity – RPC over HTTP
4/24/2017 4:45 PM
Outlook Connectivity – RPC over HTTP
Exchange 2013 does not support RPC/TCP
Why not?
RPC session is always on the MBX2013 server hosting the active database copy
Does not require a “RPC CAS array namespace” for the DAG
What changes?
RPC end point for Outlook client is now a GUID (and SMTP suffix)
Support for internal and external Outlook Anywhere namespaces
No longer have to worry about “The Exchange administrator has made a change that requires you to quit and restart Outlook” during mailbox moves or *over events
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

29. Outlook RPC over HTTP Connections
MAPI
Outlook LB
HTTPS
RPC_DATA_IN
HTTPS
RPC_DATA_OUT
HTTPS
RPC_DATA_IN
HTTPS
RPC_DATA_OUT
HTTPS
RPC_DATA_IN
HTTPS
RPC_DATA_OUT
HTTP Proxy
IIS
CAS2013
HTTP
IIS
MDB
MBX2013
RpcProxy
RPC CA

30. Outlook Connectivity – MAPI over HTTP
4/24/2017 4:45 PM
Outlook Connectivity – MAPI over HTTP
Why?
Provides more reliable connection
80% connect in 5s or less
82% resume from hibernate sync times of 30s or less
73% take 30s or less to start sync from boot
Standard HTTP pattern instead of two long-lived HTTP connections
Removes RPC stack dependency
Better diagnostics
Header information
Common authentication scheme across protocol stack
What is it?
New connectivity mechanism
No longer uses intermediary RPC components (on client or server)
ROPs are still used, just sent to Exchange directly over HTTP
Advertised via Autodiscover
Client advertises support and server returns configuration settings
Disabled by default
Requires
Exchange 2013 SP1 (or later)
Exchange 2013 SP1 mailbox
Outlook 2013 SP1 (or later)
Client restart
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

31. Outlook MAPI over HTTP ConnectionsLB
HTTPS
Req/Response
HTTPS
Req/Response
HTTPS
Req/Response
HTTPS
Hanging Notification
HTTP Proxy
IIS
CAS2013
HTTP
IIS
MDB
MBX2013
MAPI HTTP Handler

32. CAS2013 Client Protocol Connectivity Flow
Exchange 2007 Coexistence
MBX2007
CAS2007
Load Balancer
IIS DB
Middle Tier Layer
Site Boundary
HTTP
Load Balancer
CAS2013
CAS2007
IIS
Middle Tier Layer
HTTP Proxy
IIS
MBX2013
MBX2007 DB
Protocol Head DB
OWA Legacy Redirect Request
Cross-Site OWA Proxy Request
Outlook Anywhere Proxy Request
ActiveSync Proxy Request

33. CAS2013 Client Protocol Connectivity Flow
Exchange 2010 Coexistence
MBX2010
CAS2010
Load Balancer DB
Middle Tier Layer
IIS
Site Boundary
HTTP
Load Balancer
Load Balancer
CAS2013
CAS2010
IIS
Middle Tier Layer
HTTP Proxy
IIS
MBX2013
MBX2010 DB
Protocol Head DB
Legacy Proxy Request
Cross-Site Legacy Proxy Request
Cross-Site OWA Redirect Request

34. CAS2013 Client Protocol Connectivity Flow
End State
Site Boundary
MBX
CAS
Load Balancer
HTTP Proxy
IIS DB
Protocol Head
Site Boundary
CAS
HTTP Proxy
IIS
HTTP
HTTP
HTTP
Load Balancer
CAS
HTTP Proxy
IIS
HTTP
HTTP
HTTP
MBX
MBX DB
Protocol Head
Protocol Head DB
Local Proxy Request
OWA Cross-Site Redirect Request
Cross-Site Proxy Request

35. Namespace Planning & Principles

36. Namespace Planning No need for namespaces required by Exchange 2010
Can still deploy regional namespaces to control traffic
Can still have specific namespaces for protocols
Two namespace models
Bound Model
Unbound Model
Leverage split-DNS to minimize namespaces and control connectivity
Deploy separate namespaces for internal and external Outlook Anywhere host names

37. Bound Model Sue mail.contoso.com mail2.contoso.com Jane mail VIP
(somewhere in NA)
mail.contoso.com
mail2.contoso.com
Jane
(somewhere in NA)
DNS Resolution
DNS Resolution
mail VIP
mail2 VIP
DAG1
Active
Passive
DAG2
Passive
Active

38. Unbound Model Sue mail.contoso.com VIP #1 VIP #2 DAG DNS Resolution
(somewhere in NA)
mail.contoso.com
DNS Resolution
Round-Robin between # of VIPs
VIP #1
VIP #2
DAG

39. Load Balancing
Exchange 2013 no longer requires session affinity to be maintained on the load balancer
For each protocol session, CAS now maintains a 1:1 relationship with the Mailbox server hosting the user’s data
Load balancer configuration and health probes will factor into namespace design
Remember to configure health probes to monitor healthcheck.htm, otherwise LB and MA will be out of sync

40. Single Namespace / Layer 4
TechReady 16
4/24/2017
Single Namespace / Layer 4
CAS
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
health check
User
mail.contoso.com
Layer 4LB
autodiscover.contoso.com
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

41. Single Namespace / Layer 7
TechReady 16
4/24/2017
Single Namespace / Layer 7
CAS
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
Health check executes against each virtual directory
health check
User
mail.contoso.com
Layer 7LB
autodiscover.contoso.com
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

42. Multiple Namespaces / Layer 4
TechReady 16
4/24/2017
Multiple Namespaces / Layer 4
User
CAS
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
mail.contoso.com
ecp.contoso.com
ews.contoso.com
eas.contoso.com
Layer 4LB
oab.contoso.com
oa.contoso.com
mapi.contoso.com
autodiscover.contoso.com
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

43. Exchange Load Balancing Options
Generalist IT admin
Those with increased network flexibility
Those who want to maximize server availability
Who’s it for?
Functionality
Simplicity
+ Simple, fast, no affinity LB + Single, unified namespace + Minimal networking skillset - Per Server Availability
+ Simple, fast, no affinity LB + Per protocol availability - One namespace per app protocol - One VIP per protocol
+ Per protocol availability + Single, unified namespace - SSL LB - Requires increase networking skillset
Trade-Offs

44. The Preferred Architecture

45. Preferred Architecture Namespace Design
4/24/2017 4:46 PM
Preferred Architecture Namespace Design
For a site resilient datacenter pair, a single namespace / protocol is deployed across both datacenters
autodiscover.contoso.com
HTTP: mail.contoso.com
IMAP: imap.contoso.com
SMTP: smtp.contoso.com
Load balancers are configured without session affinity, one VIP / datacenter
Round-robin, geo-DNS, or other solutions are used to distribute traffic equally across both datacenters
mail VIP
mail VIP
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

46. Preferred Architecture DAG Design
4/24/2017 4:46 PM
Preferred Architecture DAG Design
Each datacenter should be its own Active Directory site
Deploy unbound DAG model spanning each DAG across two datacenters
Distribute active copies across all servers in the DAG
Deploy 4 copies, 2 copies in each datacenter
One copy will be a lagged copy (7 days) with automatic play down enabled
Native Data Protection is used
Single network is used for MAPI and replication traffic
Third datacenter used for Witness server, if possible
Increase DAG size density before creating new DAGs
mail VIP
mail VIP
DAG
Witness Server
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

47. Preferred Architecture Server Design
4/24/2017 4:46 PM
Preferred Architecture Server Design
mail VIP
Multi-role servers deployed on commodity hardware
JBOD storage utilizing large capacity 7.2K SAS disks
Multiple databases / volume
AutoReseed with hot spare
DAG
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

48. Larger Mailboxes are Better
TechReady13
4/24/2017
Larger Mailboxes are Better
Time
Items
Mailbox Size
1 Day
150
11 MB
1 Month
3300
242 MB
1 Year
39000
2.8 GB
2 Years
78000
5.6 GB
4 Years
156000
11.2 GB
Large Mailbox Size 100 GB+
Aggregate Mailbox = Primary Mailbox + Archive Mailbox + Recoverable Items
1-2 years of mail (minimum)
1 million items / folder
Increased knowledge worker productivity
Eliminate or reduce PST reliance
Eliminate or reduce third-party archive solutions
Outlook 2013 can control OST size
© 2011 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.

49. Preferred Architecture
Selina
(somewhere in NA)
Batman
(somewhere in Europe)
na.contoso.com
eur.contoso.com
DNS Resolution
DNS Resolution
na VIP
na VIP
eur VIP
eur VIP
DAG
DAG

50. Summary

51. Summary
New building block architecture provides flexibility in load balancing, namespace planning and high availability
Take advantage of large, low-cost mailboxes by utilizing large capacity 7.2K RPM disks
Simpler is better!

52. Questions? TechReady13 4/24/2017
© 2011 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.

53. Resources TechNet Virtual Labs Microsoft Virtual Academy
4/24/2017
Resources
Microsoft Virtual Academy
TechNet Virtual Labs
Free Online Learning
Free Virtual Hands-on Labs
TechNet & MSDN Flash
Subscribe to our fortnightly newsletter
Sessions on Demand
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

54. Complete your session evaluation now and win!
4/24/2017 4:46 PM
Complete your session evaluation now and win!
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

55. 4/24/2017 4:46 PM © 2014 Microsoft Corporation. All rights reserved.
Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.