Migrating to Exchange Server 2016 is supported from Exchange Server 2010 SP3 RU 11 and Exchange Server 2013 CU10.
Upgrading from earlier versions is not supported, but it is possible to have a mix of 20 Exchange Server variants coexisting with Exchange Server 2016.
Those who can remember extremely long Power Shell strings will note that this is the same list of features required for Exchange 2013. You need to change this immediately to stop Outlook clients connecting to it and getting a certificate warning when they are presented with the default self-signed certificate that is installed by Exchange.
Install-Windows Feature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-Cmd Interface, RSAT-Clustering-Mgmt, RSAT-Clustering-Power Shell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDSThe Service Connection Point (SCP) is an attribute on the Exchange server object stored in AD which directs domain-joined Outlook clients to a URL to retrieve autodiscover settings. We’ll configure the SCP to reference our Exchange 2013 endpoint, in this case https://mail.litwareinc.com/autodiscover/autodiscover.xml: At the end of the first part, we’ve now prepared for and installed Exchange 2016 into our Exchange 2013 environment and configured the SCP.
Use the below command to install the required Windows features.
This command needs to be run on a single line and run from a Power Shell window with elevated privileges.
namespace issues, version control, and certificate problems.The recommendation from Microsoft for Exchange 2013 was to install multi-role servers but with Exchange 2016, the CAS and MBX roles have been merged so installing multi-role servers is no longer possible.For the first Exchange server in the organization, the user that performing the install must be a member of the Enterprise Admins and Schema Admins group in AD and a member of the local admins group on the server you are installing Exchange on.This must be executed in the AD site which contains the Schema Master operation role.AD also needs to be prepared for the installation of Exchange Server 2016.As for Mac clients, you need Outlook for Mac 2011 or Outlook for Mac for Office 365. You’ll note here that Outlook 2007 was supported for Exchange 2013 but is no longer supported for Exchange 2016. Now that all the reading is out the way, (if you didn’t read it, shame on you!