Spark the future.

May 4 8, 2015
Chicago, IL
Pre-Release Programs Exchange & SharePoint On-
Premises Programs
Be first in line! Customers get:
Early access to new features
Opportunity to shape features
Close relationship with the product teams
Opportunity to provide feedback
Technical conference calls with members of
the product teams
Opportunity to review and comment on
documentation
Get selected to be in a program:
Sign-up at Ignite at the Preview Program
desk
OR
Fill out a nomination: http://aka.ms/joinoffice
Questions:
Visit the Preview Program desk in the Expo
Hall
Contact us at:
ignite2015taps@microsoft.com
BRK3197

Exchange Server 2016

Architecture
Ross Smith IV
Principal Program Manager
Microsoft
Agenda
Fundamentals
Client connectivity
Namespace planning and principles
Preferred architecture
Exchange
fundamentals
Exchange 2016 server role
architecture ENTERPRISE
Single building NETWORK
block Exchange Edge
Transport
DAG
Online Routing
Client access proxy Protection and AV/AS MBX AD
components

Load Balancer
Includes core server MBX
protocols
Database availability External MBX

group SMTP
servers MBX

Loosely coupled Mobile MBX

Functionality phone

Versioning Web
browser Office
User partitioning Web Phone
Outlook Apps system
Geo affinity (remote Server (PBX or
Outlook (local farm
user) VOIP)
user)
Every server is an island EWS protocol
MRS proxy protocol
SMTP

MRS MRS
EWS Transport Custom WS Transport EWS
PROTOCOLS, MRSProxy MRSProxy
SERVER AGENTS
RPC CA Assistants Assistants RPC CA

XSO Mail item XSO Mail item

BUSINESS LOGIC Banned
E2010
CTS Other API CTS Other API

Content Content
Store Store
index index
STORAGE
File File
ESE ESE
system system

Server1 Server2
(Vn) (Vn+1)
The key to enlightenment
For a given mailboxs USER
connectivity,
the protocol being used is always
served by the protocol instance
that MBX CAS
is local to the active database COMPONENTS
copy
Each MBX determines the right end
point for the traffic, and so all sessions DAG1
regardless of where they startedend up in
the same place
This means that the rendering for clients MBX-A MBX-B

like OWA occurs on the mailbox server,

transport transcoding is occurring on the
mailbox server, etc.
Topology requirements
Exchange 2016 supports coexistence with
Exchange 2010 SP3 RU11 and later*
Exchange 2013 CU10 and later*

Exchange 2016 is supported on

Windows Server 2012 R2
Windows Server 10

Exchange 2016 requires

Windows Server 2008 R2 FFM/DFM and later
Windows Server 2008 R2 AD servers and later

Desktop Outlook client requirements

Outlook 2010 SP2 (with KB2956191 and KB2965295)* or later
Outlook 2013 SP1 (with KB3020812)* or later
* Subject to change
Outlook 2016
What is the Mailbox server role?
A server that houses the logic to route a specific
protocol request to the correct destination end
point
A server that hosts all the componentsthat
process,
render, and store the data
Clients do not connect directly to MBX2016 back-
end end points; connectivity is through client
access services
Evolution of E2010 DAG
Collection of servers that form a HA unit
Announcing
The Exchange storage engine moves to

SQL uea

Just Kidding.
Remember kiddos, SQL squeals like a pig, while our
Search architecture improvements
MBX2016 MBX2016
Transport
Transport Content transformation

Service

Mailbox Local delivery Mailbox

Store ExSearch CTS Index node Passive

DB Idx
Reliabl Read Log
e content
DB event Idx
Log
Lagged copy enhancements
When ReplayLagManager is enabled, lagged
copies play down under the following condition:
Copy health status

Lagged copies also play down under the following

conditions:
Capacity concerns
Physical corruption detected

In Exchange 2016, play down is now tied to the

health of the disk (IO latency)
Enabled by default
Ensures active copies on the same disk are not impacted by play down
Delay is enacted if latency is above 20ms
Delay is deactivated when latency is 20ms or less, or if capacity is a concern
What is the Office Web Apps Server
role?
Exchange server now
leverages the Office web
apps
Users get rich browser based viewing in Word,
Excel, PowerPoint, and OneNote web apps

Delivered via Office Web

Apps infrastructure
Cannot coexist on Exchange servers

Enables side-by-side
viewing and edit & reply
capabilities for OWA
Access to the document
The extensibility future: REST APIs
REST APIs simplify programming against
Exchange 2016 and Office 365
Mail API provides ability to read, compose, and send messages, as well as, manage folders and
attachments
Calendar API provides access to calendar data
Contacts API provides access to contacts

Enables access from solutions across all mobile,

web, and development platforms
Based on open standards (JSON, OAUTH 2.0, ODATA 4.0)
Development platforms: .NET, iOS, Android, NodeJS, Ruby, Python, Cordova, etc.

Provides granular, tightly scoped permission to

access user data
Where art thou, MAPI/CDO?
The MAPI/CDO library has enjoyed a
long life, but all good things must
come to an end
Exchange 2016 will not support
connectivity via the MAPI/CDO library
Told you at MEC 2012, did I. Yes, hmmm.

App development should utilize

either:
REST APIs
Exchange Web Services
Client connectivity
Client protocol architecture
OWA Outlook EAS EAC PowerShell IMAP SMT Telephony
SIP
P +
RTP

Load Redirect
balancer
IIS
POP
SMTP UM
IMAP
HTTP Proxy

MBX16 HTTP POP SMTP

IMAP
Transpo
IIS POP IMAP UM
rt
RpcProxy
OWA, EAS, EWS, ECP, OAB,
RPS MDB Mail
MAPI
RPC CA Q
MAPI/HTTP baby!
The default connectivity Provides more reliable
mechanism connection
No longer uses intermediary RPC components 80% of users connect in 5s or less
(on client or server)
ROPs are still used, just sent to Exchange directly Removes RPC stack
overHTTP dependency
Standard HTTP pattern instead of two long-lived
HTTPconnections Better diagnostics
Header information
Advertised via Autodiscover
Client advertises support and server returns Common authentication
configuration settings
scheme across protocol
Enabled by default (E2016) stack
Per-user settings control

Requires
Outlook MAPI/HTTP connections
Outlook
Only one wrapper:
yay!
MAPI
HTTPS HTTPS HTTPS HTTPS
LB Req/Response Req/Response Req/Response Hanging Notification

HTTP
IIS

HTTP Proxy

MBX
2016 HTTP

IIS
MDB
MAPI HTTP Handler
Client protocol connectivity flow
Exchange 2010 coexistence

HTTP

LOAD BALANCER LOAD BALANCER LOAD BALANCER

boundary
Site
MBX2016 CAS2010 CAS2010
IIS IIS IIS

HTTP proxy Middle tier layer Middle tier layer

MBX2010 MBX2010
Protocol head

DB DB DB

Legacy proxy request Cross-site legacy proxy request

Cross-site OWA redirect request
Client protocol connectivity flow
Exchange 2013 coexistence (phase 1)

HTTP

LOAD BALANCER LOAD BALANCER LOAD BALANCER

CAS2013 MBX2016 MBX2016

boundary
Site
IIS IIS IIS

HTTP proxy HTTP proxy HTTP proxy

MBX2013
Protocol head Protocol head Protocol head

DB DB DB

Proxy Request Cross-site proxy request

Cross-site OWA redirect request
Client protocol connectivity flow
Exchange 2013 coexistence (phase 2)

HTTP

LOAD BALANCER LOAD BALANCER LOAD BALANCER

boundary
Site
MBX2016 CAS2013 CAS2013
IIS IIS IIS

HTTP proxy HTTP proxy HTTP proxy

MBX2013 MBX2013
Protocol head Protocol head Protocol head

DB DB DB

Legacy proxy request Cross-site OWA

legacy
redirect
proxy request
request
Outlook Web Apps Server connectivity
flow Exchange
2016
1. Exchange uses discovery URL to ask
OWAS which files types it can view and
edit
2. OWAS returns table of supported file 3
types
3. User opens mail with attachment that OWA 4 1 2 6
matches one of the file types OWAS
supports and OWA requests document
URLs for supported types
5
4. Exchange builds URL with Auth token,
app URL, and Attachment ID and returns
it to OWA 7

5. User clicks attachment within OWA and

spawns an iFrame on client to load the
URL returned by Exchange Office Web Apps
Server
6. OWAS retrieves document content from
Exchange
Namespace
planning principles
Exchange namespace planning
Exchange 2016 no longer needs all the
namespaces that Exchange 2010 required
Two namespace models you can deploy
Bound model
Unbound model

Can still deploy regional namespaces to

control traffic
Can still have specific namespaces for
protocols
Leverage split-DNS to minimize namespaces
Bound model
Sue east.contoso.com Jane
(somewhere in NA) west.contoso.co (somewhere in
DNS Resolution DNS Resolution NA)
m

west VIP east VIP

DAG1

Active Passive

DAG2

Passive Active
Unbound model
Sue
(somewhere in mail.contoso.com
NA) DNS resolution
Round robin between # of VIPs

VIP #1 VIP #2

DAG

DAG
Load balancing Exchange
Like 2013, Exchange 2016 does not require
session affinity at the load balancing layer
For a given protocol session, MBX now maintains a 1:1 relationship with
the server hosting the users data

Remember to configure health probes to

monitor healthcheck.htm, otherwise LB
and MA will be out of sync
Load balancer configuration and health
probes will factor into namespace design
Single Namespace / Layer 7 (No Session Affinity) is the preferred approach
Exchange connection management
Recommendation is to use one of two types
Round robin
Least connections

Least connections has fast convergence time

Least connections can lead to server
instability if
least server in the pool is inundated with
requests
Use slow start feature to mitigate this

Round robin has slow convergence time with

Single namespace/layer 4
MBX
OWA
health check

ECP
USER

Layer 4LB
mail.contoso.com EWS

EAS
autodiscover.contoso.
com
OAB

RPC

MAP
I
Auto
D
Single namespace/layer 7 (no session
affinity)
MBX
Health check
OWA executes against
health check each virtual
directory
ECP
USER

Layer 7LB
mail.contoso.com EWS

EAS
autodiscover.contoso.
com
OAB

RPC

MAP
I
Auto
D
Multiple namespaces/layer 4
USER MBX
mail.contoso.com
OWA

ecp.contoso.com
ECP

ews.contoso.com
EWS

Layer 4LB
eas.contoso.com
EAS

oab.contoso.com
OAB

oa.contoso.com
RPC
mapi.contoso.com
MAP
I
autodiscover.contoso. Auto
com D
Exchange load balancing options
WHOS
IT FOR? Generalist IT admin Those with Those who want
increased network to maximize
flexibility server availability
TRADE-
Plus(es): Plus(es): Plus(es):
OFFS
+ Simple, fast, no + Simple, fast, no affinity + Per protocol
affinity LB LB availability
+ Single, unified + Per protocol availability + Single, unified
namespace namespace
Minus(es):
+ Minimal networking Minus(es):
One namespace per
skillset
appprotocol SSL termination at LB
Minus(es): One VIP per protocol Requires increase
FUNCTIONALITY
Per server availability networking skillset
SIMPLICITY
OWAS namespace planning and load
balancing
Always deploy a mail.contoso.com

separate namespace for

OWAS Wes
t
mail VIP East mail VIP

For site resilience, follow

DAG
a bound namespace
model for OWAS
Even when Exchange leverages an
unbound namespace OWAS OWAS
Namespace manipulation during
datacenter activation is not required
owas- owas-
Requires persistence at west.contoso.com east.contoso.com

the load balancer

The 2016 preferred
The only on-premises architecture we want you to
architecture
deploy
Preferred architecture
Namespace design
For a site resilient datacenter pair, a single mail mail
DC1 VIP DC2 VIP
namespace / protocol is deployed across
both datacenters
autodiscover.contoso.com
HTTP: mail.contoso.com
IMAP: imap.contoso.com
SMTP: smtp.contoso.com

For Outlook Web Apps Server, a namespace is

deployed per datacenter
Load balancer configuration
For Exchange VIPs: no session affinity, one VIP/datacenter,
per-protocol health checking
For OWAS VIPs: session affinity

Round robin, geo-DNS, or other solutions

areused to distribute Exchange traffic equally
Preferred architecture
DAG design
mail mail
Each datacenter should be its own Active DC1 VIP DC2 VIP
Directory site
DAG
Increase DAG size density before creating new
DAGs
DAG configuration
Unbound, symmetrical DAG model spanning across
datacenters
No administrative access point
Single network for replication and client traffic
DC3/Azure
Utilize a third datacenter or Azure for Witness server Witnes
placement, if possible s
Server
Database configuration
Deploy four copies, two copies in each datacenter
Distribute active copies across all servers in the DAG
Preferred architecture
Server design
mail VIP
Servers are deployed on
commodity hardware DAG
Dual-socket systems only (20-24 cores total, mid-range
processors)
Up to 196GB of memory

All servers handle both client

connectivity and mailbox data
JBOD storage
Large capacity7.2k SAS disks
Battery-backed cache controller (75/25)
Multiple databases/volume
AutoReseed with hot spare
Data volumes are formatted withReFS
Data volumes are encrypted with BitLocker
Preferred architecture
Sue na.contoso.com Jane
mail.contoso.co
(somewhere in eur.contoso.co (somewhere
NA) DNS Resolution m DNS Resolution in Europe)
m

na VIP na VIP eur VIP eur VIP

DAG DAG
Large mailboxes for the win!
TIME ITEMS MAILBOX SIZE
Large mailbox size 100 GB+
Aggregate mailbox = primary mailbox + 1 day 150 11 MB
archive mailbox + recoverable items 1 month 3300 242 MB
12 years of mail (minimum)
1 year 39000 2.8 GB
1 million items/folder
2 years 78000 5.6 GB
Increased knowledge worker 4 years 156000 11.2 GB
productivity
Eliminate or reduce PST reliance
Eliminate or reduce third-party
archive solutions
Outlook 2013+ allows you to
control OST size!
Gives more options around mailbox deployments
Summary
Building block architecture provides
flexibility in load balancing, namespace
planning, and high availability
Exchange 2016 coexistence rocks
Take advantage of large, low-cost mailboxes
by utilizing large capacity 7.2k RPM disks
Simpler is better!
Sessions to attend
BRK2189 - Desktop Outlook: Evolved and Redefined
BRK3102 - Experts Unplugged: Exchange Server High Availability and Site Resilience
BRK3125 - High Availability and Site Resilience: Learning from the Cloud and Field
BRK3129 - Deploying Exchange Server 2016
BRK3138 - Exchange Design Concepts and Best Practices
BRK3147 - Meeting Complex Security Requirements for Publishing Exchange
BRK3160 - Mail Flow and Transport Deep Dive
BRK3163 - Making Managed Availability Easier to Monitor and Troubleshoot
BRK3173 - Experts Unplugged: Exchange Server Deployment and Architecture
BRK3178 - Exchange on IaaS: Concerns, Tradeoffs, and Best Practices
BRK3180 - Tools and Techniques for Exchange Performance Troubleshooting
BRK3186 - Behind the Curtain: Running Exchange Online
BRK3206 - Exchange Storage for Insiders: Its ESE
BRK4105 - Under the hood with DAGs
BRK4115 - Advanced Exchange Hybrid Topologies
Please evaluate this
session
Your feedback is important to us!

Visit Myignite at
http://myignite.microsoft.com
or download and use the Ignite Mobile
 2015 Microsoft Corporation. All rights reserved.