1. Deploy Microsoft Exchange Server 2016
Microsoft Ignite 2016
6/9/2018 7:26 AM
BRK3220
Deploy Microsoft Exchange Server 2016
Brian Day
Senior Program Manager, Exchange Customer Experience Team
Jeff Guillet
Exchange MVP & Principal Systems Architect at Strategic Products and Services
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Pre-Release Programs Team Be first in line!
Go to the Exchange booth and ask for a TAP PM
Tell us about your Office 365 environment/or on-premises plans
Get selected to be in a program
Try new features first and give us feedback!
Start now by ing or by visiting this blog post: Exchange On-Premises TAP Program accepting nominations

3. Preparing for Exchange 2016
6/9/2018 7:26 AM
Preparing for Exchange 2016
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4. Environmental and Client requirements
Exchange 2016 supports coexistence with
Exchange 2010 SP3 RU11 and later
Exchange 2013 CU10 and later
Exchange 2016 requires
Windows Server 2008 R2 Forest Functional Level
Windows Server 2008 and later Active Directory Global Catalog servers in all Exchange sites
Outlook client minimum requirements
Outlook 2010 SP2 (with KB and KB ) or later
Outlook 2013 SP1 (with KB ) or later
Outlook 2016
Outlook for Mac 2011 or later
No longer supported
Outlook 2007, Outlook for Mac 2008 EWS Edition
MAPI/CDO Package

5. Server requirements Exchange 2016 is supported on full GUI installs of
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016 (RTM only, no pre-release builds. Requires CU3 or later.)
Exchange 2016 requires
.NET Framework or 4.6.x (More on that later!)
Windows Management Framework 4.0
Unified Communications Managed API (UCMA) 4.0

6. Server requirements Optional Requirements
Office Online Server (Bits available only via Volume License Service Center)
Provides OWA the ability to preview attachments
No long using 3rd party licensed software to do previewing
SharePoint 2016
Provides the ability to use “cloudy attachments”
Send a link to a OD4B doc instead of a full file attachment.

7. .NET and 4.6.2
.NET supported if the following hotfixes are installed
Windows Server 2008 / 2008 R2 (For Exchange 2013 CU13 or later)
Windows Server 2012
Windows Server 2012 R2
.NET to become supported with 2013 CU15 and 2016 CU4.
No additional hotfixes required with 4.6.2
.NET to become mandatory with 2013 CU16 and 2016 CU5.
Setup will block installation if is not detected

8. Windows Management Framework
What should we expect to see?
Did the OS ship with it? It is supported.
e.g. Windows Server 2016 ships with WMF5, therefore Exchange 2016 CU3 or later can use WMF5 if installed on Windows Server 2016, but not if installed on Windows Server 2012 R2 as that OS did not ship with WMF5.
Do you have to install it to use it? Then it is not supported.

9. 6/9/2018 7:26 AM
Servicing Model
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Exchange 2016 Servicing Model
Microsoft Ignite 2016
6/9/2018 7:26 AM
Exchange 2016 Servicing Model
Exchange 2016 continues the Cumulative Update model as well as standalone critical updates for CUn and CUn-1 versions when applicable.
CUs are shipped quarterly and critical updates (e.g. security updates) will be released as needed on “patch Tuesday.”
Service packs will not be shipped for Exchange 2016.
Only versions CUn and CUn-1 will be serviced for product fixes.
Customers with hybrid relationships to O365 are required to be on one of the two most recent updates for their major Exchange version, be it 2010, 2013, or 2016 as of today.
Application bits are now distributed in ISO format.
Yes, you can mount/extract to a network share and then install.
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. 6/9/2018 7:26 AM
Virtualization
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Exchange 2016 Virtualization
A valid deployment model for some scenarios.
Stay true to the virtualization requirements.
Design as physical, deploy to virtual.

13. 6/9/2018 7:26 AM
Coexistence
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Exchange 2010 + Exchange 2016 Short version…
Same story as Exchange Exchange 2013
No legacy name spaces required
Exchange 2016 can proxy down to 2010
Exchange 2010 cannot up-level proxy to 2016
Deploy enough 2016 to cover all of 2010’s client load.

15. Exchange 2013 + Exchange 2016 Short version…
No legacy namespaces required
Exchange 2016 can proxy down-version to 2013
Exchange 2013 can proxy up-version to 2016

16. Coexisting with Exchange 2013 + 2016
Option 2, let Exchange 2016 down-version proxy.
Condensed steps
Prep your environment (server versions, DFL/FFL, schema, AD, domains, etc…)
Install 2016
Configure Exchange 2016 server URLs as you would have Exchange 2013
Import the certificate(s) to 2016 server(s)
Swing the load balanced namespaces over from 2013 to 2016
Setup your DAG(s)
Start moving mailboxes
Repeat for all Internet facing sites and then repeat for non-Internet facing
Move incoming mail flow to deliver to 2016 first once it makes sense (>50% moved)

17. Coexisting with Exchange 2013 + 2016
Option 1, let Exchange 2013 up-version proxy.
Condensed steps
Prep your environment (server versions, DFL/FFL, schema, AD, domains, etc…)
Install 2016 (I like to use a deployment AD site.)
Configure Exchange 2016 server URLs as you would have Exchange 2013
Import the certificate(s) to 2016 server(s)
Setup your DAG(s)
Start moving mailboxes
Repeat for all Internet facing sites and then repeat for non-Internet facing
Move incoming mail flow to deliver to 2016 first once it makes sense (>50% moved)
Swing the load balanced namespaces over from 2013 to 2016
Recommended: Gradually introduce 2016 servers into the existing LB pool.
Supported: Cutover to all 2016 servers at once

18. Client Connectivity Flow for 2013 + 2016
TechReady 17
6/9/2018
Client Connectivity Flow for
Protocol/App
Exchange 2013 user accessing an Exchange 2016 namespace
Exchange 2016 user accessing an Exchange 2013 namespace
Requires
No additional namespace
No additional namespaces
OWA/ECP
Mailbox mounted in the same AD Site: Exchange 2016 proxies to Exchange 2013 Mailbox Role server in the local AD site with the active DB copy
Mailbox mounted in an Internal only AD site: Exchange 2016 proxies to the Exchange 2013 Mailbox Role server in the remote AD site with the active DB copy
Mailbox mounted in an External facing AD site: Exchange 2016 proxies to the Exchange 2013 Mailbox Role server with the active DB copy, or issues a silent/SSO cross-site redirect to the site’s ExternalURL, your choice. *
* = The ExternalURL in the remote AD site could resolve to Exchange 2016 or 2013 as both are capable of getting the traffic to Exchange 2013 mailboxes in that site.
Mailbox mounted in the same AD Site: Exchange 2013 proxies to Exchange 2016 Mailbox server in the local AD site with the active DB copy
Mailbox mounted in an Internal only AD site: Exchange 2013 proxies to the Exchange 2016 Mailbox server in the remote AD site with the active DB copy
Mailbox mounted in an External facing AD site: Exchange 2013 proxies to the Exchange 2016 Mailbox server with the active DB copy, or issues a silent/SSO cross-site redirect to the site’s ExternalURL, your choice. *
* = The ExternalURL in the remote AD site could resolve to Exchange 2016 or 2013 as both are capable of getting the traffic to Exchange 2016 mailboxes in that site.
EAS
Outlook Anywhere
EWS
POP/IMAP
Remote PowerShell
MAPI/HTTP
Exchange 2016 proxies to Exchange 2013 Mailbox Role server with the Active DB copy
Exchange 2013 proxies to Exchange 2016 Mailbox server with the Active DB copy
Autodiscover
Exchange 2016 proxies the request to the Exchange 2013 Mailbox role server with the active DB copy
Exchange 2013 CAS proxies the request to the Exchange 2016 Mailbox server with the active DB copy
OAB
Exchange 2016 proxies the request to an OAB generation mailbox with the OAB or a shadow copy of the OAB
Exchange 2013 proxies the request to an OAB generation mailbox with the OAB or a shadow copy of the OAB
© 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. Exchange 2016/2013/2010 Coexistence
TechReady13
6/9/2018
Exchange 2016/2013/2010 Coexistence
Always hit the server with the active DB copy for that user.
OWA/ECP redirects where appropriate.
mail.contoso.com
europe.mail.contoso.com
Site Boundary
Layer 4 or 7 LB
Layer 7 LB
2016 Client Access Services
IIS
2016 Store
Protocol Head DB
2013 CAS
IIS
HTTP Proxy
2010 CAS
Protocol Head
2010 MBX
Store DB
HTTP Proxy
RPC
2013 MBX
Protocol Head DB
© 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.

20. Exchange 2016/2013/2010 Coexistence
TechReady13
6/9/2018
Exchange 2016/2013/2010 Coexistence
OWA/ECP redirects where appropriate.
europe.mail.contoso.com
mail.contoso.com
Site Boundary
Layer 7 LB
Layer 4 or 7 LB
Client Access Services
IIS
2016 Store
Protocol Head DB
MBX Server
2013 CAS
IIS
HTTP Proxy
2010 CAS
Protocol Head
2010 MBX
Store DB
HTTP Proxy
RPC
2013 MBX
Protocol Head DB
© 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.

21. Exchange 2016/2013/2010 Coexistence
TechReady13
6/9/2018
Exchange 2016/2013/2010 Coexistence
OWA/ECP redirects where appropriate.
europe.mail.contoso.com
mail.contoso.com
Site Boundary
Layer 7 LB
Layer 4 or 7 LB
Client Access Services
IIS
2016 Store
Protocol Head DB
MBX Server
2010 CAS
Protocol Head
2010 MBX
Store DB
HTTP Proxy
RPC
2013 MBX
Protocol Head DB
© 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.

22. CAS replacement process w/up-version proxy
LB is sending traffic to 2013 CAS services
Exchange 2016 is introduced
Exchange 2016 CAS services added to LB pool
Exchange 2013 CAS services removed from LB pool
More Exchange 2016 introduced and added into LB pool
More 2013 CAS services removed from LB pool
More Exchange 2016 introduced and added to LB pool
Final 2013 CAS services removed from LB pool
2013 CAS
2013 CAS
E13 CAS
2016
MBX
2016
MBX
2016
MBX
2013 MBX
2013 MBX
2013 MBX
2013 MBX
2016
MBX
LB to Client Access Services
Client Access Services to Mailbox
2013 Client Access to 2016 Mailbox
Not Shown: Intra-2016 Server Traffic

23. Hybrid Connectivity 6/9/2018 7:26 AM
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. Upgrading Exchange servers only for Hybrid?
Short answer:
It depends…
Long answer:
Only if using a shared SMTP namespace
Upgrade to 2016

25. Should I install 2013/2016 for hybrid?
Exchange 2010
MRS

26. Should I install 2013/2106 for hybrid?
Exchange 2013
MRS
Exchange 2010

27. Does the guidance change for 2016?
Add Servers when ready
Exchange 2013
MRS
2016

28. Namespace Planning and Load Balancer Recommendations
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29. What Namespace Models Do We Have
Microsoft Ignite 2015
6/9/2018 7:26 AM
What Namespace Models Do We Have
Unbound namespace
It does not matter what datacenter the client accesses to reach their mailbox.
Exchange is allowed to route the client traffic to the appropriate datacenter.
Proxying a heavy amount of client traffic between datacenters is expected/normal/ok.
Bound namespace
We force clients to connect to specific datacenters depending on where the mailbox is mounted.
Exchange is relieved of routing most client traffic between datacenters.
It is not expected to proxy a heavy amount of client traffic between datacenters.
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30. How Will You Be Load Balancing?
Microsoft Ignite 2015
6/9/2018 7:26 AM
How Will You Be Load Balancing?
This may affect your planned names. Know this ahead of time!
Layer-7 with SSL Bridging or (less likely) SSL pass-through or (even less likely) SSL offloading
All protocols/apps will likely share a name
Layer-4 with SSL pass-through
If you want service health awareness of each protocol/app then you will need additional names
e.g. owa.mail.contoso.com, ews.mail.contoso.com, ecp.mail.contoso.com, etc…
If you can live without service health awareness you can share a name across protocols/apps, but you reduce the LB’s ability to react to single services being offline and will impact users.
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31. Current Load Balancing Recommendation
Microsoft Ignite 2015
6/9/2018 7:26 AM
Current Load Balancing Recommendation
Unbound namespace
Layer-7 with SSL Bridging
Configured to watch the vDir /healthcheck.htm results
No Affinity for Exchange services
One Caveat: Use session affinity with the ‘ExchangeCookie’ when performing hybrid mailbox moves.
Affinity required for Office Online Server namespace connections
TCP timeout Longer than the OS under Exchange
e.g. if Exchange’s OS TCP timeout is 15 minutes, the LB cannot use 10 minutes.
Round Robin Load Distribution
Least Connections can be used, but is a far 2nd place and should only be used if your device supports a slow ramp feature
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

32. Exchange 2010 + 2016 Unbound Model
autodiscover.fabrikam.com
mail.fabrikam.com
mail.corp.fabrikam.com *
mail.fabrikam.com
mail.corp.fabrikam.com *
Exchange 2010
Multi-Role Server
Exchange 2010
Multi-Role Server
outlookrpc.us.corp.fabrikam.com*
outlookrpc.emea.corp.fabrikam.com*
oos.emea.fabrikam.com
oos.emea.corp.fabrikam.com*
Office Online Server
oos.us.fabrikam.com
oos.us.corp.fabrikam.com *
Office Online Server
* = Internal DNS Only

33. Exchange 2010 + 2016 Unbound Model
Internal Only DNS Records
mail.corp.fabrikam.com
outlookrpc.us.corp.fabrikam.com (Not on the certificate)
outlookrpc.emea.corp.fabirkam.com (Not on the certificate)
oos.us.corp.fabrikam.com
oos.emea.corp.fabrikam.com
Internal+External DNS Records
autodiscover.fabrikam.com
mail.fabrikam.com
oos.us.fabrikam.com
oos.emea.fabirkam.com
9 Names
7 Names on the certificate

34. Exchange 2013 + 2016 Unbound Model
When Using Up-Version Proxy
When Using Down-Version Proxy
Exchange 2013
Multi-Role Server
autodiscover.fabrikam.com
mail.fabrikam.com
mail.corp.fabrikam.com *
mail.fabrikam.com
mail.corp.fabrikam.com *
Exchange 2016
oos.emea.fabrikam.com
oos.emea.corp.fabrikam.com *
Office Online Server
oos.us.fabrikam.com
oos.us.corp.fabrikam.com *
Office Online Server
* = Internal DNS Only

35. Exchange 2013 + 2016 Unbound Model
Internal Only DNS Records
mail.corp.fabrikam.com
oos.us.corp.fabrikam.com
oos.emea.corp.fabrikam.com
Internal+External DNS Records
autodiscover.fabrikam.com
mail.fabrikam.com
oos.us.fabrikam.com
oos.emea.fabrkam.com
7 Names
7 Names on the certificate

36. Exchange 2010 + 2013 + 2016 Unbound When Using Up-Version Proxy
When Using Down-Version Proxy
When Using Up-Version Proxy
Exchange 2013
Multi-Role Server
mail.fabrikam.com
autodiscover.fabrikam.com
mail.corp.fabrikam.com *
mail.fabrikam.com
mail.corp.fabrikam.com *
Exchange 2010
Multi-Role Server
Exchange 2010
Multi-Role Server
Exchange 2016
outlookrpc.us.corp.fabrikam.com *
outlookrpc.emea.corp.fabrikam.com *
oos.emea.fabrikam.com
oos.emea.corp.fabrikam.com*
Office Online Server
oos.us.fabrikam.com
oos.us.corp.fabrikam.com *
Office Online Server
* = Internal DNS Only

37. Exchange 2010 + 2013 + 2016 Unbound Internal Only DNS Records
mail.corp.fabrikam.com
oos.us.corp.fabrikam.com
oos.emea.fabrikam.com
outlookrpc.corp.fabrikam.com (Not on the certificate)
outlookrpc.us.fabrikam.com (Not on the certificate)
outlookrpc.emea.fabrikam.com
Internal+External DNS Records
autodiscover.fabrikam.com
mail.fabrikam.com
oos.us.fabrikam.com
9 Names
7 Names on the certificate

38. OOS Namespace Logic in 2016 CU1 and later
Previously in 2016 RTM, we always used OOS’ external URL for attachment viewing. However, in CU1 and later…
OWA Virtual Directory Parameters
IsPublic: $True/$False
WacViewingOnPublicComputersEnabled: $True/False
Both $True = Use External OOS URL and/or External SharePoint URL instead of internal URLs.
IsPublic $True + WacViewingOnPublicComputersEnabled $False = Don’t allow OOS viewing if the client came in through this vDir.

39. 6/9/2018 7:26 AM
MAPI/HTTP
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

40. MAPI/HTTP … to enable or not to enable.
Microsoft Ignite 2016
6/9/2018 7:26 AM
MAPI/HTTP … to enable or not to enable.
The answer should always be yes!
MAPI/HTTP will be enabled by default when…
Exchange 2016 is the first Exchange server in a greenfield Exchange org
The first Exchange 2016 server is installed in an Exchange 2010-only org
The first Exchange 2016 server is installed in an Exchange 2013 org if MAPI/HTTP is already enabled
MAPI/HTTP will not be enabled by default when…
The first Exchange 2016 server is installed in an Exchange 2013 org when MAPI/HTTP is not already enabled
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

41. So MAPI/HTTP, how can I ease into it?
You want options? The MoMT team gave you options!

42. So MAPI/HTTP, how can I ease into it?
Microsoft Ignite 2016
6/9/2018 7:26 AM
So MAPI/HTTP, how can I ease into it?
Scenario… An Exchange 2013 org with MAPI/HTTP disabled is migrating to Exchange 2016.
Goal… only enable MAPI/HTTP for users as they are migrated to 2016
Leave the organization level MapiHttpEnabled as $False
Prior to moving mailboxes use Set-CasMailbox from the 2016 EMS to set MapiHttpEnabled to $True on the 2013 mailboxes.
Move the mailboxes to 2016
Once all mailboxes are on 2016, set MapiHttpEnabled to $True at the organization level
Use Set-CasMailbox on all 2016 mailboxes to set MapiHttpEnabled to $Null so the organization level value is inherited once again.
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

43. 6/9/2018 7:26 AM
Public Folders
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

44. Public Folders Changes
6/9/2018
Public Folders Changes
2016 CU2 or later support 1,000 PF mailboxes*
*= 99 allowed for hierarchy
EXO also now supports 1,000 PF mailboxes.
2016 CU2 and after use a push replication model for more predictable and hierarchy change sync.
© 2015 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.

45. Public Folders Changes
6/9/2018
Public Folders Changes
Outlook for Mac now supports legacy public folders with KB installed and 2016 CU2 or 2013 CU13.
More details at:
© 2015 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. Legacy Public Folders and Outlook 2016
6/9/2018
Legacy Public Folders and Outlook 2016
Outlook 2016 no longer respects ecWrongServer.
2013/2016 users must use a DefaultPublicFolderMailbox that resides in a 2007/2010 database with the same PublicFolderDatabase value configured.
© 2015 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. Outlook On The Web & Office Online Server
6/9/2018 7:26 AM
Outlook On The Web & Office Online Server
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

48. Office Online Server and OOtW
Exchange 2016
Exchange 2016
autodiscover.fabrikam.com
mail.fabrikam.com
mail.fabrikam.com
oos.us.fabrikam.com
oos.us.corp.fabrikam.com *
Office Online Server
oos.emea.fabrikam.com
oos.emea.corp.fabrikam.com *
Office Online Server
* = Internal DNS Only

49. Before Attachment Viewing is Configured
That’s all folks!
No Native App Installed
Native App Installed

50. Configuring Attachment Viewing
Configure the WAC discovery endpoint per mailbox server
Restart MSExchangeOWAAppPool
If you are missing WACDiscoveryEndpoint on Set-MailboxServer, run Setup /PrepareAd to update RBAC.
[PS] C:\>Get-MailboxServer E16LAB-2K | FL WACDiscovery*
WACDiscoveryEndpoint :
[PS] C:\>Set-MailboxServer E16LAB-E2K –WACDiscoveryEndpoint
[PS] C:\>Get-MailboxServer E16LAB-E2K | FL WACDisc*
WACDiscoveryEndpoint :

51. After Attachment Viewing is Configured
Look, Mom, two options now!
The new side-by-side (SxS) view

52. OOtW / OOS logical flow…
Exchange uses discovery URL to ask OOS which file types it can view and edit.
OOS returns table of supported file types
User opens mail with a supported file type. OWA requests doc URLs for the supported file 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
OOS retrieves document content from Exchange
OOS renders content to client in web client (e.g. Word Web App)
Exchange 2016 3
OWA Client 4 1 2 6 5
Office Online Server 7

53. What is WACDiscovery? It tells you “stuff.” Lots and lots of stuff.
Think of it like Office Web App Server’s version of Autodiscover.

54. For On-Premises Cloudy Attachments you’ll need…
OOS setup and working with Exchange
SharePoint 2016 configured for MySites
SharePoint WOPI Binding established with OOS via New-SPWOPIBinding
OAuth configured on SP to trust EX (Script available soon)
OAuth configured on EX to trust SP (Script shipped with Exchange)
Configure OWA Mailbox Policy InternalSPMySiteHostURL and ExternalSPMySiteHostURL values and policy assigned to users.
Or the OWA vDirs themselves if you need server-level granularity.

55. A few random nuggets. 6/9/2018 7:26 AM
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

56. Kerberos Authentication
Microsoft Ignite 2016
6/9/2018 7:26 AM
Kerberos Authentication
Exchange Exchange 2016
Follow the current Exchange 2010 / Exchange 2013 guidance
Exchange Exchange 2016
A single ASA used for both 2013 and 2016 servers in the same environment.
Exchange Exchange Exchange 2016
Two ASAs where one is 2010 and the other is shared with 2013 & 2016.
The 2010 ASA is for RPC connections
The 2013/2016 ASA is for all HTTP connections
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

57. Why are my databases moving around?
PreferenceMoveFrequency in 2016 CU2 DAGs
With all DAG nodes on CU2 or later the servers will periodically activate DB copies with the lowest Activation Preference number if a lossless activation is possible.
Prior to CU2 the script RedistributeActiveDatabases.ps1 had to be scheduled or run manually.
Can be disabled by setting PreferenceMoveFrequency to the value of [System.Threading.Timeout]::InfiniteTimeSpan

58. System Mailbox Moves After Install
Move all system mailboxes from 2010/2013 to 2016
SystemMailbox{1f05a927-d5d7-47a6-b498-f5266abdf909}
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
SystemMailbox{e0dc1c29-89c b678-e6c29d823ed9}
Federated .4c1f4d8b bf-00a95fa1e042
Migration.8f3e e4-96b1-aba62d229136
Can’t save admin tasks to the admin audit log or export it
Can’t start eDiscovery searches
Can’t start migration batches with 2016 target DBs
And more…

59. Pre-Release Programs Team Be first in line!
Go to the Exchange booth and ask for a TAP PM
Tell us about your Office 365 environment/or on-premises plans
Get selected to be in a program
Try new features first and give us feedback!
Start now by ing or by visiting this blog post: Exchange On-Premises TAP Program accepting nominations

60. Deploy, ramp-up on new services and onboard new users with Microsoft FastTrack:

61. Join the Microsoft Tech Community to collaborate, share, and learn from the experts:

62. Please evaluate this session
6/9/2018 7:26 AM
Please evaluate this session
Your feedback is important to us!
From your PC or Tablet visit MyIgnite at
From your phone download and use the Ignite Mobile App by scanning the QR code above or visiting
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

63. 6/9/2018 7:26 AM
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.