Exchange 2016 Product Version Numbers

Updated on 18 October 2018


  • With CU11 for Exchange 2016…
    • .NET Framework 4.7.2 is now supported and will be a requirement with CU13 (anticipated release in Jun 2019);
    • Visual C++ 2013 Runtime is still a requirement; and
    • Visual C++ 2012 Runtime is a new requirement.
  • With CU8 for Exchange 2016, .NET Framework 4.7.1 is now supported and will be a requirement with CU10 (anticipated release in Jun 2018).
  • .NET Framework 4.7.0 is not–and will not–be supported for Exchange 2016.
  • With CU5 for Exchange 2016 and newer, .NET Framework 4.6.2 is a requirement.
  • For coexistence with Exchange 2016 RTM, Exchange 2013 requires CU10 and Exchange 2010 requires SP3 UR11. Exchange 2007 cannot coexist with Exchange 2016.


To get the product version number of the currently installed version of Exchange Server 2016, open the Exchange Management Shell and run one of the following commands and the output provided will look similar to this…

[PS] C:\>Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

Name                : EXCH1
Edition             : Standard
AdminDisplayVersion : Version 15.1 (Build 225.42)


[PS] C:\>Get-Command ExSetup.exe | % {$_.FileVersionInfo}

ProductVersion   FileVersion      FileName
--------------   -----------      --------
15.01.0225.042   15.01.0225.042   C:\Program Files\Microsoft\Exchange Server\V15\bin\ExSetup.exe


For this example, using the number associated with “ProductVersion” from the output (15.01.0225.042)…

  • “15” in the first number group refers to the Exchange “major” version. Version “15” is either Exchange Server 2013 or 2016.
  • “01” in the second number group refers to the “minor” version installed. “01” in this case is Exchange Server 2016.
  • “0225” in the third number group refers to the “build” version installed. “0225” is Exchange Server 2016 RTM.
  • “042” in the fourth number group refers to an Exchange team internal “revision” version. “042” refers to the RTM internal revision number.

Given that information, the table below displays the product version numbers associated with each service pack and update rollup for Exchange Server 2016.

NOTE: Unlike with previous of Exchange, if we run “Get-ExchangeServer | FL Name,Edition,AdminDisplayVersion” (as instructed in several MS articles) the CU version that is installed is now properly displayed.



Exchange Server Version ProductVersion Release Date KB Article Download In Support *
Exchange Server 2016, CU11 15.01.1591.010 4-Oct-2018 KB4134118 ExchangeServer2016-x64-cu11.iso Yes
Exchange Server 2016, CU10 15.01.1531.003 12-Jun-2018 KB4099852 ExchangeServer2016-x64-cu10.iso Yes
Exchange Server 2016, CU9 15.01.1466.003 20-Mar-2018 KB4055222 ExchangeServer2016-x64-cu9.iso No
Exchange Server 2016, CU8 15.01.1415.002 19-Dec-2017 KB4035145 ExchangeServer2016-x64-cu8.iso No
Exchange Server 2016, CU7 15.01.1261.035 16-Sep-2017 KB4018115 ExchangeServer2016-x64-cu7.iso No
Exchange Server 2016, CU6 15.01.1034.026 24-Jun-2017 KB4012108 ExchangeServer2016-x64-cu6.iso No
Exchange Server 2016, CU5 15.01.0845.034 20-Mar-2017 KB4012106 No
Exchange Server 2016, CU4 15.01.0669.032 12-Dec-2016 KB3177106 No
Exchange Server 2016, CU3 15.01.0544.027 14-Sep-2016 KB3152589 No
Exchange Server 2016, CU2 15.01.0466.034 21-Jun-2016 KB3135742 No
Exchange Server 2016, CU1 15.01.0396.030 16-Mar-2016 KB3134844 No
Exchange Server 2016, RTM 15.01.0225.042 1-Oct-2015 Exchange2016-x64.exe No
Exchange Server 2016, Preview 15.01.0225.017 22-Jul-2015     N/A


The Cumulative Update (CU), Rollup, and Service Packs you have running on the on-premises server should also not be overlooked. Under normal circumstances we support you being no more than two updates behind the currently released update for Exchange; however, for hybrid environments, we are stricter and you should not be more than one build behind. If the latest update is Exchange 2013 CU9, then you must have either Exchange 2013 CU9 or CU8 to be considered in a supported state. We are stricter with our hybrid requirements because of how tightly the on-premises and Exchange Online environments will be coupled together. For more information on our available updates please go here.


Additionally, you can run the following two commands from an elevated PowerShell console on an Exchange server to get the current Exchange Product ID that is installed…

([ADSI]"LDAP://CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,$RootDSE").msExchProductID

NOTE: In the command above, the value “CN=First Organization” may vary for your environment.

NOTE: This command will not work for Exchange 2007 or older.


Lastly, this script (Get-ExchangeVersionNumber.ps1) will provide us with the version (or build) number for the Exchange products installed…

$ExServers = Get-ExchangeServer
foreach ($Server in $ExServers)
	$BuildNum = [string]$Server.AdminDisplayVersion.Major+"."+$Server.AdminDisplayVersion.Minor+"."+$Server.AdminDisplayVersion.Build+"."+$Server.AdminDisplayVersion.Revision

	"Name         : " + $Server.Name
	"Role         : " + $Server.ServerRole
	"Edition      : " + $Server.Edition
	"Build Number : " + $BuildNum


Result of running Get-ExchangeVersionNumber.ps1…

[PS] C:\Tools\Scripts>.\Get-ExchangeVersionNumber.ps1
Name         : EX1
Role         : Mailbox, ClientAccess
Edition      : Standard
Build Number : 15.0.1130.7

Name         : EX2
Role         : Mailbox, ClientAccess
Edition      : Standard
Build Number :




Exchange Server Version Schema (Forest): rangeUpper Schema (Forest): objectVersion Active Directory (Domain): objectVersion
Exchange Server 2016, CU7 15332 16213 13236
Exchange Server 2016, CU6 15330 16213 13236
Exchange Server 2016, CU5 15326 16213 13236
Exchange Server 2016, CU4 15326 16213 13236
Exchange Server 2016, CU3 15326 16212 13236
Exchange Server 2016, CU2 15325 16212 13236
Exchange Server 2016, CU1 15323 16211 13236
Exchange Server 2016, RTM 15317 16210 13236
Exchange Server 2016, Preview 15317 16041 13236


Check forest and domain versions by running the following commands in an elevated PowerShell on a domain controller. NOTE: Change “First Organization” to the name of your Exchange organization.

([ADSI]"LDAP://CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,$RootDSE").objectVersion
([ADSI]"LDAP://CN=Microsoft Exchange System Objects,$RootDSE").objectVersion


Related Article(s):




2 thoughts on “Exchange 2016 Product Version Numbers

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s