gwavacon 2015: microsoft mvp - what's new in exchange server 2016?
TRANSCRIPT
What’s new in Exchange Server 2016?Dave StorkArchitect @ OGD ict-dienstenExchange MVP
@dmstork – bit.ly/dmstorkwww.theUCarchitects.com
Disclaimer: Everything is subject to change
Except the name Exchange Server 2016Some slides and images from Microsoft
Agenda
New Features & capabilitiesWhat’s gone?– Removed & De-emphasized features
Topology requirementsFocus:– Office Web App Server– MAPI/HTTP
Preferred Architecture 2016Questions
New Features
A lot of smaller improvements– From Office 365
Online Office 365 Hybrid Configuration Wizard– From Exchange 2013 CU8 +– Decoupled from Exchange build– Improved error handling & tips
New Outlook on the web (Ootw)– Sweep, Pin, Undo, Inline reply and much more– Modern Attachments: enhanced collaboration through the new
Office Web App server– Add-in model
New Features
MAPI over HTTP Outlook protocol will be standard– Instead of RPC over HTTP, but this will remain
fallback– Unless Exchange 2013 already existed without MAPI
over HTTP
Improved Search– Outlook 2016 search now always server-side– Calendar Search in Outlook on the Web– Index now built from passive copy database and not
transferred over WAN
New Features
Enhanced Data Loss Prevention– 30 new information types– Support for third party classification– Custom email notification
Improved eDiscovery– Faster, more reliable, improved scale– Support for Public Folders
New Features
REST API– Mail, Calendar and Contacts API– Next to Exchange Web Services (EWS)– https://dev.outlook.com/
Auto-expanding archives– After 100GB, additional archive mailboxes are auto
provisioned in 50GB increments
Single role– No more separate roles (exception Edge Transport)
New Features
IPless DAG is now default– No more Cluster Node Object / Admin Access point– This was optional with Exchange 2013
Easier migration (from 2013)– 2013 roles can up-proxy– Can coexists with 2013 servers in same load balancer VIP
Faster failover & Lower IOPS – 33% faster; 8 sec.– 22% less IOPS than Exchange 2013
Removed
Third party DAG replication
Cluster Node Object & Administrative Access point for DAGs– Check your backup vendor
No more MAPI/CDO support– Check your third party applications
Built-in web preview of Office docs
De-emphasized
RPC over HTTP– Still used when client does not support MAPI/HTTP
Exchange Web Services (EWS)– Not de-emphasized but Microsoft has stated that
investments will probably go more into REST than and less in EWS
Public Fold… no just kidding
Topology requirements
Exchange 2016 supports coexistence with– Exchange 2010 SP3 RU11– Exchange 2013 CU10
Exchange 2016 is supported on– Windows Server 2012– Windows Server 2012 R2– Windows Server 2016 ?
Topology requirements
Exchange 2016 requires– Windows Server 2008 FFM/DFM and later– Windows Server 2008 AD servers and later
Desktop Outlook client requirements– Outlook 2010 SP2 (with KB2965295) or later– Outlook 2013 SP1 (with KB3020812) or later– Outlook 2016 (which should be GA today!)
Office Web App Server 2016
Office Web Apps Server
Exchange uses Office Web Apps Server– High fidelity viewing of Office documents
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 is authorized by Exchange via an OAuth token
Fully on-premises (documents stored in SharePoint 2016)
On-premises
Exchange Server 2016
Office Web Apps Server 2016
Hybrid (documents stored in Office 365)
On-premises
Exchange Server 2016
Office 365
Office Web Apps Server 2016
OneDrive for Business
SharePoint Server2016
MAPI/HTTP
The default connectivity mechanism– No longer uses intermediary RPC components
(on client or server)– Standard HTTP pattern instead of two long-lived
HTTP connections
Advertised via Autodiscover
MAPI/HTTP
Enabled by default– Per-user settings control– If there is no 2013 environment with MAPI/HTTP disabled
Requires– Exchange 2013/2016 mailbox– Supported Outlook version– Client restart (delayed)
MAPI/HTTP benefits
Provides more reliable connection– 80% of users connect in 5s or less
Removes RPC stack dependency
Better diagnostics– Header information
Common authentication scheme across protocol stack– Multi Factor Authentication
Preferred Architecture 2016
Similar as the PA for Exchange 2013No more Client Access Role -> enforces PANo more Administrative Access Point (IP less DAG)Volumes formatted with ReFS instead of NTFSOffice Web App server in each datacenter with bound namespace (i.e. unique per data center) whereas Exchange remains unboundType Data center Data center 2
Exchange webmail.contoso.com webmail.contoso.com
OWAS owasdc1.contoso.com owasdc2.contoso.com
Note: Today at 15:10 in Zurich Room: Exchange Architecture & Sizing
Public Preview
Final release
Technology Adoption Program kickoff
Summer 2015 Fall/Winter 2015Feb 2015
First dogfoodmailbox deployed
Nov 2014 May 2015
YOU ARE HERE
Microsoft Ignite
Exchange Server 2016 Preview
http://blogs.technet.com/b/exchange/archive/2015/07/22/announcing-exchange-server-2016-preview.aspx
https://www.microsoft.com/en-us/download/details.aspx?id=48210
Microsoft Ignite 2015 sessions
Meet Exchange Server 2016Exchange Server Preferred ArchitectureDeploying Exchange Server 2016Exchange on IaaS: Concerns, Tradeoffs, and Best Practices
https://channel9.msdn.com/Events/Ignite/2015