This document provides an overview of upgrading to Exchange Server 2016. It discusses Exchange Server 2016 requirements and supported upgrade paths from previous versions such as Exchange Server 2010 and 2013. It also covers options for implementing Exchange Server 2016 such as an on-premises only or hybrid deployment. The document then discusses various topics related to planning and implementing the upgrade such as understanding client access and message transport coexistence, migrating public folders, and removing previous Exchange server versions.
4. What’s new in Exchange Server 2016
Client Access Server services now part of Mailbox server role
Single Mailbox server role deployment
Outlook Web App has been renamed to Outlook on the Web
Support for Modern Authentication (ADAL)
MAPI over HTTP is default modern protocol
Integration with OneDrive and Office Online Server
5. What’s new in Exchange Server 2016
Hybrid Configuration Wizard (HCW) is now a cloud-based app that is downloaded at runtime
Additional sensitive information types added to Data Leakage Prevention (DLP)
Transport rules contain new conditions and actions
Public folder support for In-Place eDiscovery and In-Place Hold
Enhanced compliance search added to PowerShell
Azure file share witness (FSW) support
7. Exchange 2016 Server Role Architecture
AD
Office
Online
Server
farm
Outlook (local user)
ENTERPRISE NETWORK
Phone
system (PBX
or VOIP)
Edge
Transport
Routing and
AV/AS MBX
MBX
MBX
MBX
MBX
LoadBalancer
10. Topics
Exchange Server 2016 Requirements
Options for implementing Exchange Server 2016
Supported upgrade scenarios
Choosing an upgrade strategy
Understanding client access server coexistence
1
2
3
4
5
Understanding message transport coexistence
Understanding Exchange Server 2016 public folders
Planning a multi-site upgrade
6
7
8
11. Environment Requirements
Exchange 2016 supports coexistence with
- Exchange 2010 SP3 RU11 and later
- Exchange 2013 CU10 and later
Exchange 2016 requires
- Windows Server 2008 FFL and later
- Windows Server 2008 DCsand later | Global Catalog servers in each site with Exchange installed
- Outlook clients minimum requirements
- Outlook 2010 SP2 (with KB2956191 and KB2965295) or later
- Outlook 2013 SP1 (with KB3020812) or later
- Outlook 2016
- Outlook for Mac 2011 or later
12. Server Requirements
Exchange 2016 is supported on full GUI installs of
- Windows Server 2012 R2
- Windows Server 2016
Exchange 2016 requires
- .NET Framework 4.6.2
- Windows Management Framework 4.0
- Unified Communications Managed API (UCMA) 4.0
- Office Online Server installed on separate server(s) for attachment rendering in Outlook on the web
Outlook on the web supports
- Microsoft Edge
- Internet Explorer 11
- Most recent versions of Mozilla Firefox, Google Chrome, and Safari
13. Existing Exchange Servers
All existing Exchange server versions must meet prerequisite levels
May need to recreate Edge Subscriptions before running Exchange 2016 Setup
[PS] C:>Get-ExchangeServer | FT Name,AdminDisplayVersion,ServerRole -AutoSize
Name
----
E2K10-EDG-001
E2K13-MLT-001
------------------- ----------
Version 15.0 (Build 1104.5) Mailbox, ClientAccess
Version 14.2 (Build 247.5) EdgeTransport
AdminDisplayVersion ServerRole
14. Offline Address Book
Exchange 2016 creates a new default OAB for the organization
Set legacy OAB on all existing databases before installing Exchange 2016
15. Topics
Exchange Server 2016 Requirements
Options for implementing Exchange Server 2016
Supported upgrade scenarios
Choosing an upgrade strategy
Understanding client access server coexistence
1
2
3
4
5
Understanding message transport coexistence
Understanding Exchange Server 2016 public folders
Planning a multi-site upgrade
6
7
8
17. Topics
Exchange Server 2016 Requirements
Options for implementing Exchange Server 2016
Supported upgrade scenarios
Choosing an upgrade strategy
Understanding client access server coexistence
1
2
3
4
5
Understanding message transport coexistence
Understanding Exchange Server 2016 public folders
Planning a multi-site upgrade
6
7
8
18. Supported Upgrade Paths
Exchange Server Version Organization Upgrade Comments
Exchange Server 2007 Not Supported
Upgrade to Exchange Server 2010 first
If Exchange Server 2003 still present, these
need to be removed
Mixed Exchange Server 2010 and
Exchange Server 2007
Not Supported
All Exchange 2007 servers need to be
decommissioned
Exchange Server 2010 SP3 UR11 or later Supported
All Exchange 2010 servers need to be
updated to SP3 UR 11, including Edge
servers
Exchange Server 2013 CU10 Supported
All Exchange 2013 servers need to be
updated to CU 10, including Edge servers
Mixed Exchange Server 2010 SP3 UR11
and Exchange Server 2013 CU10 Supported
In a multi AD site infrastructure all servers
in a single site need to be updated to the
respective Exchange 2010 UR or Exchange
2013 CU
22. MAPI/HTTP
The default connectivity mechanism
- No 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
Requirement
- 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 dependency
Better diagnostics
- Header information
Common authentication scheme across
protocol stack
29. Message Transport Coexistence
All supported Exchange Server versions use AD DS sites for message routing
Retain Hub Transport servers in all AD DS sites that still contain user mailboxes
Message flow requires transport components of the same version as the Mailbox servers
Message routing is possible to different Exchange Server versions between AD DS sites
Exchange 2016 Mailbox servers co-exists with Exchange 2010 or Exchange 2013 Edge Transport
servers
30. Topics
Exchange Server 2016 Requirements
Options for implementing Exchange Server 2016
Supported upgrade scenarios
Choosing an upgrade strategy
Understanding client access server coexistence
1
2
3
4
5
Understanding message transport coexistence
Understanding Exchange Server 2016 public folders
Planning a multi-site upgrade
6
7
8
31. Modern Public Folder
Switch to standard mailbox storage
- Robust mailbox based storage for high availability
- No separate replication mechanism
- Single-master model
- Hierarchy is stored in public folder mailboxes (one writeable Primary public folder mailbox)
- Each public folder mailbox has a read-only copy of the public folder hierarchy
Content can be placed in multiple mailboxes
Do not store content in primary public folder mailbox
Hierarchy folder points to target content mailbox
No changes to end user
Support On-Premises, Hybrid & Office 365
32. Modern Public Folders Architecture
Architecture
• Public folders are based on
mailbox architecture
• Hierarchy is stored in all
public folder mailboxes
• Content can be broken up
and placed across multiple
mailboxes
• Similar administrative
features
• Public Folder permission
management in RBACFolder 1
Folder 2
CAS 2016
Folder 2
Folder 4
Folder 3
PF
Logon
PF
Logon
PF Logon
Hierarchy Hierarchy
Secondary PF
Mailbox 1
Primary PF
Mailbox
Secondary PF
Mailbox 2
33. Public Folder Hierarchy Synchronization
CAS 2013
Hierarchy Hierarchy
Secondary PF
Mailbox 1
Primary PF
Mailbox
Secondary PF
Mailbox 2
Folder1
Folder2
Folder1Folder1
1. Client connects to a PF
mailbox
2. Client creates Folder2
3. Create request is
proxied via the primary
PF mailbox
4. PF hierarchy is
updated on all PF
mailboxes
• Within 15 mins
where users are
connected
• Within 24 hours
where no users are
connected
Folder2Folder2
34. Legacy vs. Modern Public Folders
Legacy Public Folders Modern Public Folders
Content storage Public Folder database Public Folder mailbox
Public Folder content replication Can be replicated between
databases
No replication
High availability PF replication DAG
PF Hierarchy storage One per PF database, multi-master Per PF mailbox, one master only
PF Hierarchy synchronization Based on e-mail Direct mailbox sync
Search Items only Items and attachments (full-text)
Public Folder Client permissions Access Control Lists (ACLs) Access Control Lists (ACLs)
Admin Platform PF Management Console + EMS EAC + EMS
35. Backup and restore of Public Folders
Supported restore scenarios
- Deleted secondary mailbox
- Disconnected mailbox
- Deleted folder
- Deleted item
Protecting your Primary mailbox
- Cmdlet deletion disallowed if secondary mailboxes present
- DAG usage recommended for on-premises
37. Planning a multi-site upgrade
When planning a multi-site upgrade, identify which sites have direct client access to Exchange
servers
Upgrade sites with direct client access first to enable client connection proxying and redirection
If all sites have direct client access, use other project factors to evaluate which site to upgrade
first
You can complete the upgrade one site at a time, or upgrade several sites at the same time
40. Topics
Exchange Server 2016 upgrade overview
Process for upgrading client access
Process for upgrading message transport
Process for migrating public folders
Removing previous versions of Exchange Server
1
2
3
4
5
41. Exchange 2016 upgrade overview
Document the current environment
Prepare the environment
Deploy the Exchange 2016 servers
Prepare the Exchange 2016 Mailbox servers
Switch client connections to Exchange 2016 Mailbox servers
Move mailboxes and public folders
Move transport components
Remove previous versions of Exchange server
42. Process for upgrading client access
Install the Exchange Server 2016 servers
Obtain public server certificates for the Mailbox servers
Configure the virtual directories for client access on the Mailbox servers, including the MAPI virtual
directory
Configure DNS
Test client connectivity
44. Topics
Exchange Server 2016 upgrade overview
Process for upgrading client access
Process for upgrading message transport
Process for migrating public folders
Removing previous versions of Exchange Server
1
2
3
4
5
45. Upgrade outbound or inbound message delivery by adding Exchange 2016 servers to existing
connectors or Edge subscriptions
- Optionally, create a new message delivery route
Upgrade internal message relay by configuring internal applications and services to use the Client
Front End receive connector on Exchange 2016 Mailbox servers
Upgrade external message relay by configuring authentication or creating a dedicated secured
receive connector with anonymous relay enabled
46. Topics
Exchange Server 2016 upgrade overview
Process for upgrading client access
Process for upgrading message transport
Process for migrating public folders
Removing previous versions of Exchange Server
1
2
3
4
5
47. Migrating from Legacy Public Folders
Mailboxes on Exchange 2010 cannot access Public Folders on Exchange 2016
- Exchange 2013 Mailboxes can access legacy Public Folders (but not both)
- No coexistence Migrate users first
Check that replication between source public folder databases is healthy
All Public Folders cut over to Exchange 2016 together
- Short downtime while migration is finalized
- When migration completes, everyone switches at the same time
- Admin can choose to switch some users first for validation
- Can revert, but post migration changes are lost
Public Folder Migration is similar to online mailbox moves
Ensure healthy replication
48. Prepare for Migration – 2010 Prerequisites
Perform Snapshot of Exchange 2007/2010 PF environment
Public Folder structure:
Get-PublicFolder -Recurse | ConvertTo-CSV C:PFMigrationEx2010_PFStructure.csv
Public folder statistics (item count, size and owner):
Get-PublicFolder -Recurse | Get-PublicFolderStatistics | ConvertTo-CSV
C:PFMigrationEx2010_PFStatistics.csv
Permissions:
Get-PublicFolder -GetChildren | Get-PublicFolderClientPermission | Select-Object
Identity,User -expandProperty AccessRights | ConvertTo-CSV
C:PFMigrationEx2010_PFPerms.csv
Verify that there is no previous migration recorded
Get-OrganizationConfig | FL PublicFoldersLockedforMigration,
PublicFolderMigrationComplete
49. Prepare for migration – 2016 Prerequisites
Remove any “old“ Public Folder migration request(s)
Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest -
Confirm:$false
Remove any Public Folder in Exchange 2013
Get-MailPublicFolder | where $_.EntryId -ne $null | Disable-MailPublicFolder -
Confirm:$false
Get-PublicFolder -GetChildren | Remove-PublicFolder -Recurse -Confirm:$false
Remove any Public Folder Mailboxes in Exchange 2013
Get-Mailbox -PublicFolder |Remove-Mailbox -PublicFolder -Confirm:$false
50. Topics
Exchange Server 2016 upgrade overview
Process for upgrading client access
Process for upgrading message transport
Process for migrating public folders
Removing previous versions of Exchange Server
1
2
3
4
5
51. Removing previous versions of Exchange Server
Verify that all required data and functionality has been moved to Exchange Server 2016
As mailboxes and public folders are moved, remove Mailbox servers
Remove legacy Client Access and Hub Transport servers when load decreases
Do not remove the last Hub Transport and Client Access server in an Active Directory site
until all mailboxes have been moved
Remove previous versions of Exchange one AD DS site at a time
Remove the Exchange Servers by uninstalling Exchange
- Use the ADSIEdit Uninstall Option as the very last option