Exchange 2013 Product Version Numbers

Updated on 3 November 2017

IMPORTANT: Beginning with CU16 for Exchange 2013, .NET Framework 4.6.2 is now a requirement.  If you are upgrading from a CU version prior to CU16, you must upgrade Exchange 2013 to CU15 first, then upgrade to .NET Framework 4.6.2, and finally upgrade Exchange 2013 to one of the newer, supported CUs.

NOTE: .NET Framework is not currently supported with Exchange 2013.

To get the product version number of the currently installed version of Exchange Server 2013, open the Exchange Management Shell and run this command…

Get-Command ExSetup.exe | % {$_.FileVersionInfo}

 

The output provided will look similar to this…

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

 

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

  • “15” in the first number group refers to the Exchange version. Version “15” is Exchange Server 2013.
  • “00” in the second number group refers to the service pack that is installed. “00” is Exchange Server 2013 RTM and Service Pack (SP) 1.
  • “0995” in the third number group refers to the update rollup that is installed. “0995” is Exchange Server 2013 Cumulative Update (CU) 6.
  • “029” in the fourth number group refers to an Exchange team internal revision number. “029” refers to a version of a specific CU (i.e. CU2-v2). There might be multiple versions of the same CU.

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

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 2013

Exchange Server Version ProductVersion Release Date KB Article Download In Support *
Exchange Server 2013, CU19 ??? Dec-2017  
Exchange Server 2013, CU18 15.00.1347.002 16-Sep-2017 KB4022631 Exchange2013-x64-cu18.exe Yes
Exchange Server 2013, CU17 15.00.1320.004 24-Jun-2017 KB4012114 Exchange2013-x64-cu17.exe Yes
Exchange Server 2013, CU16 15.00.1293.002 20-Mar-2017 KB4012112 Exchange2013-x64-cu16.exe No
Exchange Server 2013, CU15 15.00.1263.005 12-Dec-2016 KB3197044 Exchange2013-x64-cu15.exe No
Exchange Server 2013, CU14 15.00.1236.003 20-Sep-2016 KB3177670   No
Exchange Server 2013, CU13 15.00.1210.003 21-Jun-2016 KB3135743   No
Exchange Server 2013, CU12 15.00.1178.004 15-Mar-2016 KB3108023 No
Exchange Server 2013, CU11 15.00.1156.006 15-Dec-2015 KB3099522 No
Exchange Server 2013, CU10 15.00.1130.007 14-Sep-2015 KB3078678 No
Exchange Server 2013, CU9 15.00.1104.005 17-Jun-2015 KB3049849 No
Exchange Server 2013, CU8 15.00.1076.009 17-Jun-2015 KB3030080 No
Exchange Server 2013, CU7 with KB3040856 15.00.1044.029 10-Mar-2015 KB3040856 No
Exchange Server 2013, CU7 15.00.1044.025 9-Dec-2014 KB2986485 No
Exchange Server 2013, CU6 15.00.0995.029 26-Aug-2014 KB2961810 No
Exchange Server 2013, CU5 15.00.0913.022 27-May-2014 KB2936880 No
Exchange Server 2013, CU4 (aka Service Pack 1) 15.00.0847.032 24-Feb-2014 KB2926248   No
Exchange Server 2013, CU3 15.00.0775.038 25-Nov-2013 KB2892464 No
Exchange Server 2013, CU2-v2 15.00.0712.024 29-Jul-2013 KB2859928 No
Exchange Server 2013, CU2 15.00.0712.022 9-Jul-2013 N/A No
Exchange Server 2013, Cumulative Update 1 (CU1) 15.00.0620.029 2-Apr-2013 KB2816900 No
Exchange Server 2013, Release to Manufacturing (RTM) 15.00.0516.032 3-Dec-2012 RTM No
Exchange Server 2013, Beta 15.00.0466.013 16-Jul-2012 N/A 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…

$RootDSE=([ADSI]"").distinguishedName
([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.

 

Related Article(s):

 

Reference(s):

 

Advertisements

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s