Programs Be first in line Exchange amp SharePoint OnPremises Programs Customers get Early access to new features Opportunity to shape features Close relationship with the product teams ID: 277387
Download Presentation The PPT/PDF document "Pre-Release" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1Slide2
Pre-Release
Programs
Be first in line!
Exchange & SharePoint On-Premises Programs
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
Slide3
Exchange Server 2016 ArchitectureRoss Smith IVPrincipal Program ManagerMicrosoftBRK3197Slide4
AgendaFundamentalsClient connectivityNamespace planning and principlesPreferred architectureSlide5
Exchange fundamentalsSlide6
Exchange 2016 server role architecture
AD
Web
browser
Outlook
(remote user)
Mobile
phone
Office Web Apps Server farm
Outlook
(local user)
External
SMTP servers
Exchange Online Protection
ENTERPRISE NETWORK
Phone system
(PBX or VOIP)
Edge T
ransport
Routing and AV/AS
Single building block
Client access proxy
components
Includes core server
protocols
Database
availability
group
Loosely coupled
Functionality
Versioning
User partitioning
Geo affinity
MBX
MBX
MBX
MBX
MBX
DAG
Load BalancerSlide7
Every server is an island
E2010
Banned
Server1 (
V
n
)
Server2 (V
n+1
)
PROTOCOLS,
SERVER AGENTS
EWS
RPC CA
Transport
Assistants
MRS
MRSProxy
Transport
Assistants
EWS
RPC CA
MRS
MRSProxy
BUSINESS LOGIC
XSO
Mail
item
Other API
CTS
XSO
Mail
item
Other API
CTS
STORAGE
Store
Content index
File
system
ESE
Store
Content index
File
system
ESE
SMTP
MRS proxy protocol
EWS protocol
Custom WSSlide8
The key to enlightenment…For a given mailbox’s connectivity,
the protocol being used is
always served by the protocol instance that is local to the active database copyEach
MBX determines the right end
point
for the traffic, and so all
sessions—regardless
of where they
started—end
up in the same
place
This means that the rendering for clients
like OWA occurs on the
mailbox server
,
transport transcoding
is occurring on the
mailbox
server, etc
.
MBX CAS
COMPONENTS
USER
DAG1
MBX-A
MBX-BSlide9
Topology requirementsExchange 2016 supports coexistence withExchange 2010 SP3 RU11 and later*Exchange 2013 CU10 and later*Exchange 2016 is supported onWindows Server 2012 R2
Windows Server 10Exchange 2016 requiresWindows Server 2008 R2 FFM/DFM and later
Windows Server 2008 R2 AD servers and laterDesktop Outlook client requirementsOutlook 2010 SP2 (with KB2956191 and KB2965295)* or laterOutlook 2013 SP1 (with KB3020812)* or laterOutlook 2016* Subject to changeSlide10
What is the Mailbox server role?A server that houses the logic to route a specific protocol request to the “correct” destination end pointA server that hosts all the components that process, render, and store the data
Clients do not connect directly to MBX2016 back-end end points; connectivity is through client access servicesEvolution of E2010 DAG
Collection of servers that form a HA unitDatabases are replicated between servers in a given DAGServers can be in different locations, for site resiliencyMaximum of 16 mailbox servers
100 database
copies/server
Database failovers are 33% fasterSlide11
Announcing…The Exchange storage engine moves to…Just Kidding.
Remember kiddos, SQL squeals like a pig, while our storage engine is both ESE and roars like a JET engine
SQuea
LSlide12
Search architecture improvementsMBX2016
Transport
Mailbox
DB
Idx
ExSearch
CTS
Store
Index
node
Transport
Content
transformation
Service
Local
delivery
Log
Reliable
event
Read
content
MBX2016
Mailbox
DB
Idx
Passive
LogSlide13
Lagged copy enhancementsWhen ReplayLagManager is enabled, lagged copies play down under the following condition:Copy
health statusLagged copies also play down under the following conditions:
Capacity concernsPhysical corruption detectedIn 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 concernSlide14
What is the Office Web Apps Server role?Exchange server now leverages the Office web appsUsers get rich browser based viewing in Word, Excel, PowerPoint, and OneNote web appsDelivered via Office Web Apps infrastructure
Cannot coexist on Exchange servers
Enables side-by-side viewing and edit & reply capabilities for OWAAccess to the document is authorized by Exchange via an OAuth tokenSlide15
The extensibility future: REST APIsREST APIs simplify programming against Exchange 2016 and Office 365Mail 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 contactsEnables access from solutions across all mobile, web, and development platformsBased 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
Does not break existing apps that use EWSSlide16
Where art thou, MAPI/CDO?The MAPI/CDO library has enjoyed a long life, but all good things must come to an endExchange 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 ServicesSlide17
Client connectivitySlide18
Client protocol architecture
MBX16
Telephony
IMAP
SMTP
OWA
EAS
EAC
Outlook
PowerShell
Load
balancer
Redirect
SIP + RTP
RPC CA
IIS
RPS
OWA, EAS, EWS, ECP,
OAB, MAPI
POP IMAP
Transport
UM
RpcProxy
MDB
MailQ
HTTP Proxy
IIS
POP
IMAP
SMTP
UM
HTTP
POP IMAP
SMTPSlide19
MAPI/HTTP baby!The default connectivity mechanismNo longer uses intermediary RPC components
(
on client or server)ROPs are still used, just sent to Exchange directly over HTTP
Standard HTTP pattern instead of two long-lived
HTTP connections
Advertised via
Autodiscover
Client advertises support and server returns
configuration settings
Enabled
by default (E2016
)
Per-user
settings
control
Requires
Exchange
2013/2016
mailbox
Supported Outlook version
Client
restart (delayed)
Provides more reliable connection
80% of users connect in 5s or less
Removes
RPC stack dependencyBetter diagnosticsHeader informationCommon authentication scheme across protocol stackSlide20
Outlook MAPI/HTTP connections
MBX
2016
HTTP Proxy
IIS
LB
HTTPS
Req
/Response
HTTPS
Req
/Response
HTTPS
Req
/Response
HTTPS
Hanging Notification
HTTP
MAPI
Only one
wrapper:
yay!
MAPI HTTP Handler
IIS
MDB
HTTP
Outlook
HTTPS
Req
/Response
HTTPS
Req
/Response
HTTPS
Req
/Response
HTTPS
Hanging NotificationSlide21
MBX2016
LOAD BALANCER
HTTP
proxy
IIS
DB
Protocol
head
HTTP
Legacy proxy request
Cross-site legacy proxy request
CAS2010
IIS
Middle
tier layer
LOAD BALANCER
Cross-site OWA redirect request
CAS2010
IIS
MBX2010
LOAD BALANCER
DB
Middle tier layer
Client protocol connectivity flow
Exchange 2010 coexistence
MBX2010
DB
IIS
Site
boundarySlide22
Site boundary
MBX2013
CAS2013
LOAD BALANCER
HTTP
proxy
IIS
DB
Protocol
head
HTTP
Proxy Request
MBX2016
DB
Cross-site proxy request
IIS
HTTP proxy
LOAD BALANCER
Cross-site OWA redirect request
MBX2016
LOAD BALANCER
DB
HTTP
proxy
IIS
Protocol
head
Protocol
head
Client protocol connectivity flow
Exchange 2013 coexistence (phase 1)Slide23
Site
boundary
MBX2016
LOAD BALANCER
HTTP
proxy
IIS
DB
Protocol
head
HTTP
Legacy proxy request
MBX2013
DB
Cross-site legacy proxy request
CAS2013
IIS
HTTP
proxy
LOAD BALANCER
Cross-site OWA redirect request
MBX2013
CAS2013
LOAD BALANCER
DB
HTTP
proxy
IIS
Protocol
head
Protocol
head
Client protocol connectivity flow
Exchange 2013 coexistence (phase 2)Slide24
Outlook Web Apps Server connectivity flow
Exchange uses discovery URL to ask
OWAS which files types it can view and edit
OWAS returns
table of supported file
types
User
opens
mail with attachment that matches one of the file types
OWAS supports
and OWA requests document URLs for supported types
Exchange builds URL with
Auth
token,
app
URL, and Attachment ID and returns it to OWA
User clicks attachment within OWA and spawns an
iFrame
on client to load the
URL
returned by Exchange
OWAS retrieves
document content from Exchange
OWAS renders
content in
OWAS client (e.g., Word Web App)
Exchange 2016
Office Web Apps Server
OWA
3
4
57
1
2
6Slide25
Namespace planning principlesSlide26
Exchange namespace planningExchange 2016 no longer needs all the namespaces that Exchange 2010 requiredTwo namespace models you can deployBound modelUnbound model
Can still deploy regional namespaces to control trafficCan still have specific namespaces for protocols
Leverage split-DNS to minimize namespaces and control connectivityDeploy separate namespaces for internal and external Outlook (OA, MAPI/HTTP) host namesSlide27
Bound model
DAG1
DAG2
Passive
Active
Active
Passive
DNS Resolution
east
VIP
DNS Resolution
east.contoso.com
west.contoso.com
Sue
(somewhere
in
NA)
Jane
(
somewhere in NA)
west
VIPSlide28
Unbound model
Round robin between
# of VIPs
DNS
resolution
DAG
Sue
(somewhere in NA)
VIP #1
VIP #2
DAG
mail.contoso.comSlide29
Load balancing ExchangeLike 2013, Exchange 2016 does not require session affinity at the load balancing layerFor a given protocol session, MBX now maintains a 1:1 relationship with the server hosting the user’s dataRemember to configure health probes to monitor healthcheck.htm, otherwise LB
and MA will be out of syncLoad balancer configuration and health probes will factor into namespace design
Single Namespace / Layer 7 (No Session Affinity) is the preferred approachSlide30
Exchange connection managementRecommendation is to use one of two typesRound robinLeast connectionsLeast connections has fast convergence timeLeast connections can lead to server instability if “least” server in the pool is inundated with requests
Use “slow start” feature to mitigate thisRound robin has slow convergence time with
long-lived connections (RPC/HTTP)MAPI/HTTP is not affectedSlide31
Single namespace/layer 4
MBX
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
autodiscover.contoso.com
USER
Layer 4LB
mail.contoso.com
health checkSlide32
Single namespace/layer 7 (no session affinity)
MBX
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
autodiscover.contoso.com
USER
Layer 7LB
mail.contoso.com
health check
Health check executes against each virtual directorySlide33
Multiple namespaces/layer 4mapi.contoso.com
USER
Layer 4LB
mail.contoso.com
ecp.contoso.com
ews.contoso.com
eas.contoso.com
oab.contoso.com
oa.contoso.com
MBX
OWA
ECP
EWS
EAS
OAB
MAPI
RPC
AutoD
autodiscover.contoso.comSlide34
Exchange load balancing options
Generalist IT admin
Those with increased network flexibility
Those who want
to
maximize
server
availability
Plus(
es
):
+
Simple, fast, no affinity LB
+ Single, unified namespace
+ Minimal networking
skillset
Minus(
es
):
– Per server availability
Plus(
es
):
+
Per protocol availability
+ Single, unified
namespace
Minus(
es
):
–
SSL
termination
at
LB
–
Requires
increase networking skillset
Plus(
es
):
+
Simple, fast, no affinity LB
+ Per protocol
availability
Minus(
es
):
– One
namespace per
app protocol
–
One
VIP per protocol
SIMPLICITY
FUNCTIONALITY
WHO’S
IT FOR?
TRADE-OFFSSlide35
OWAS namespace planning and load balancing
Always deploy a separate namespace for OWAS
For site resilience, follow a bound namespace model for OWASEven when Exchange leverages an unbound namespaceNamespace manipulation during datacenter activation is not required
Requires persistence at the load balancer
DAG
OWAS
owas-east.contoso.com
owas-west.contoso.com
mail.contoso.com
OWAS
mail VIP
mail
VIP
West
EastSlide36
The 2016 preferred architectureThe only on-premises architecture we want you to deploySlide37
Preferred architectureNamespace designFor a site resilient datacenter pair, a single namespace / protocol is deployed across both datacenters
autodiscover.contoso.comHTTP: mail.contoso.comIMAP: imap.contoso.com
SMTP: smtp.contoso.comFor Outlook Web Apps Server, a namespace is deployed per datacenterLoad balancer configurationFor Exchange VIPs: no session affinity, one VIP/datacenter, per-protocol health checking
For OWAS VIPs: session affinity
Round robin, geo-DNS, or other solutions are used to distribute Exchange traffic equally across both datacenters
DC2
DC1
mail VIP
mail VIPSlide38
DC2
DC1
mail VIP
mail VIP
Preferred architecture
DAG design
DAG
DC
3/
Azure
Witness Server
Each datacenter should be its own Active Directory site
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
Utilize a third datacenter or Azure for Witness server placement, if possible
Database configuration
Deploy four copies, two copies in each datacenter
Distribute active copies across all servers in the DAG
One
copy is a lagged copy (seven days) with automatic play down enabled
Native Data Protection is
utilizedSlide39
Preferred architectureServer designServers are deployed on commodity hardwareDual-socket systems only (20-24 cores total, mid-range processors)
Up to 196GB of memoryAll servers handle both client connectivity and mailbox dataJBOD storage
Large capacity 7.2k SAS disksBattery-backed cache controller (75/25)Multiple databases/volumeAutoReseed
with hot spare
Data volumes are formatted with
ReFS
Data volumes are encrypted with BitLocker
DAG
mail VIPSlide40
Preferred architecture
Sue
(somewhere
in NA)
DNS Resolution
DAG
na
VIP
na
VIP
DNS Resolution
DAG
eur
VIP
eur
VIP
Jane
(
somewhere
in
Europe)
mail.contoso.com
na.contoso.com
eur.contoso.comSlide41
Large mailboxes for the win!Large mailbox size 100 GB+Aggregate mailbox = primary mailbox + archive mailbox + recoverable items1–2 years of mail (minimum)1 million items/folder
Increased knowledge worker productivityEliminate or reduce PST reliance
Eliminate or reduce third-party archive solutionsOutlook 2013+ allows you to control OST size!Gives more options around mailbox deployments
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 GBSlide42
SummaryBuilding block architecture provides flexibility in load balancing, namespace planning, and high availabilityExchange 2016 coexistence rocksTake advantage of large, low-cost mailboxes by utilizing large capacity 7.2k RPM disksSimpler is better!Slide43
Sessions to attendBRK2189 - Desktop Outlook: Evolved and RedefinedBRK3102 - Experts Unplugged: Exchange Server High Availability and Site ResilienceBRK3125 - High Availability and Site Resilience: Learning from the Cloud and Field
BRK3129 - Deploying Exchange Server 2016BRK3138 - Exchange Design Concepts and Best Practices
BRK3147 - Meeting Complex Security Requirements for Publishing ExchangeBRK3160 - Mail Flow and Transport Deep DiveBRK3163 - Making Managed Availability Easier to Monitor and TroubleshootBRK3173 - Experts Unplugged: Exchange Server Deployment and ArchitectureBRK3178 - Exchange on IaaS: Concerns, Tradeoffs, and Best PracticesBRK3180 - Tools and Techniques for Exchange Performance TroubleshootingBRK3186 - Behind the Curtain: Running Exchange OnlineBRK3206 - Exchange Storage for Insiders: It’s ESE
BRK4105 - Under the hood with DAGs
BRK4115 - Advanced Exchange Hybrid TopologiesSlide44
Visit
Myignite
at
http://myignite.microsoft.com
or download and use the
Ignite
Mobile
App
with
the QR code above.
Please evaluate
this
session
Your feedback is
important to us!Slide45