Exchange 2016 (Preview) - original blog post on preview version
Here is the link to the Exchange 2016 system requirements:
Exchange 2016 system requirements
No significant changes
Windows 10 is now supported for Management Tools.
Coexistence with previous versions of Exchange
The minimal versions of Exchange 2010 and 2013 are currently:
- Exchange 2010 SP3 Rollup 11 (Rollup 15 is the latest rollup at the time of this writing)
- Exchange 2013 CU10
Step 1 - Install required roles and features
On the future Exchange server, we open a PowerShell prompt and execute the following command:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, 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-ADDS
Note: yes, you can copy and paste. No need to retype!
Step 2 - Install .NET Framework 4.5.2
.NET 4.5.2 Offline Installer
Step 3 - Install "Unified Communications Managed API"
Unified Communications Managed API 4.0 Runtime
Step 4 - Prepare the Active Directory schema
Cumulative Update 3 for Exchange Server 2016 (KB3152589)
After navigating to the location where we saved the files, we execute this command:
setup /ps /IAcceptExchangeServerLicenseTerms
Note: /ps is a shortcut for /PrepareSchema.
At first, I attempted to install Exchange 2016 CU3 in an existing Exchange 2010 SP3 / Office 365 hybrid environment and encountered an error:
Error when you run Setup /PrepareSchema to prepare the schema for an existing Exchange hybrid environment
So we have to do two things:
- Create the MyTenantOrganizationConfig.xml file.
- Re-run the command with the /p (or /PrepareAD switch) instead of the /ps switch AND add the /TenantOrganizationConfig switch, designating the .xml file created in step 1.
This was the detailed solution:
Exchange 2010 hybrid environment - Get-OrganizationConfig
But I was still not able to upgrade the schema and prepare Active Directory.
Once again, I will refer the reader to the TechNet discussion that finally resulted in a solution:
However, I will summarize...
After consultation with someone from Microsoft, I disabled the hybrid detection function with a registry change at the following location on the (future) Exchange server:
Note: create the keys when necessary.
Here is the registry change (yes, REG_SZ):
Disabling hybrid detection allowed the setup /PrepareAD command to complete.
I have to hope this will not cause other problems in the future.