Microsoft Exchange Server Version number is often displayed in a numeric format, e.g Version 8.1 (Build 278.2). It may not look very meaningful at first but it’s easy enough to decode these numbers.
Find Exchange version
You can find out your Exchange 2007 and 2010 version either using following methods:
Exchange Management Shell
- Run: GCM exsetup |%{$_.Fileversioninfo}
Check ExSetup.exe version
Navigate to your exchange installation Bin directory (e.g. C:\Program Files\Microsoft\Exchange Server\Bin) and check ExSetup.exe file properties. Version will be listed in Version or Details tab.
Exchange management Console
- Open EMC > Help > About Exchange Server
Following two methods are also often used, but can be quite unreliable. Although they display major versions correctly, Update Rollup can be inaccurate. I would recommend using one of the above methods
Exchange Management Shell
- Run: Get-ExchangeServer | fl name, edition, admindisplayversion
Exchange management Console
- Open Server Configuration and check Version column
Version Number
Let’s take our first example: Version 8.1 (Build 278.2)
- First number represents Exchange version: Version 8 is Exchange 2007, Version 14 is Exchange 2010
- Number after a dot represents Service Pack: 1 for SP1, 2 for SP2, etc
- Build number changes after installing Update Rollups (more info below)
So Version 8.1 (Build 278.2) is Exchange 2007 Service Pack 1 Update Rollup 2
Update Rollups
To decode Update Rollup version for Exchange 2007 and 2010 check this Microsoft TechNet article.
In case MS article gets moved or deleted, here is a copy:
Exchange Server Release dates
Product name | Build number | Date |
Microsoft Exchange Server 2003 | 6.5.6944 | 30/6/2003 |
Microsoft Exchange Server 2003 SP1 | 6.5.7226 | 25/5/2004 |
Microsoft Exchange Server 2003 SP2 | 6.5.7638 | 19/10/2005 |
Microsoft Exchange Server 2007 | 8.0.685.24 | 9/12/2006 |
Microsoft Exchange Server 2007 | 8.0.685.25 | 9/12/2006 |
Microsoft Exchange Server 2007 SP1 | 8.1.240.6 | 29/11/2007 |
Microsoft Exchange Server 2007 SP2 | 8.2.176.2 | 24/8/2009 |
Microsoft Exchange Server 2007 SP3 | 8.3.083.6 | 20/6/2010 |
Microsoft Exchange Server 2010 | 14.0.639.21 | 9/11/2009 |
Microsoft Exchange Server 2010 SP1 | 14.1.218.15 | 24/8/2010 |
Microsoft Exchange Server 2010 SP2 | 14.2.247.5 | 4/12/2010 |
Microsoft Exchange Server 2010 SP3 | 14.3.123.4 | 2/12/2013 |
Microsoft Exchange Server 2013 | 15.0.516.32 | 10/11/2012 |
Exchange Server 2007 Service Pack 1
Exchange Server 2007 Service Pack 2
Exchange Server 2007 Service Pack 3
Exchange Server 2010
Exchange Server 2010 Service Pack 1
Exchange Server 2010 Service Pack 2
Product name | Build number | Date | KB |
Microsoft Exchange Server 2010 SP2 | 14.2.247.5 | 12/4/2011 | |
Update Rollup 1 for Exchange Server 2010 SP2 | 14.2.283.3 | 2/13/2012 | KB2645995 |
Update Rollup 2 for Exchange Server 2010 SP2 | 14.2.298.4 | 4/16/2012 | KB2661854 |
Update Rollup 3 for Exchange Server 2010 SP2 | 14.2.309.2 | 5/29/2012 | KB2685289 |
Update Rollup 4 for Exchange Server 2010 SP2 | 14.2.318.2 | 8/13/2012 | KB2706690 |
Update Rollup 4-v2 for Exchange Server 2010 SP2 | 14.2.318.4 | 10/9/2012 | KB2756485 |
Update Rollup 5 for Exchange Server 2010 SP2 | 14.2.328.5 | 11/13/2012 | KB2719800 |
Update Rollup 5-v2 for Exchange Server 2010 SP2 | 14.2.328.10 | 12/10/2012 | KB2785908 |
Update Rollup 6 for Exchange Server 2010 SP2 | 14.2.342.3 | 2/11/2013 | KB2746164 |
Update Rollup 7 for Exchange Server 2010 SP2 | 14.2.375.0 | 8/13/2013 | KB2874216 |
Update Rollup 8 for Exchange Server 2010 SP2 | 14.2.390.3 | 12/10/2013 | KB2903903 |
Exchange Server 2010 Service Pack 3
Product name | Build number | Date | KB |
Microsoft Exchange Server 2010 SP3 | 14.3.123.4 | 2/12/2013 | KB2808208 |
Update Rollup 1 for Exchange Server 2010 SP3 | 14.3.146.0 | 5/29/2013 | KB2803727 |
Update Rollup 2 for Exchange Server 2010 SP3 | 14.3.158.1 |
8/13/2013 | KB2866475 |
Update Rollup 3 for Exchange Server 2010 SP3 | 14.3.169.1 | 11/25/2013 | KB2891587 |
Update Rollup 4 for Exchange Server 2010 SP3 | 14.3.174.1 | 12/10/2013 | KB2905616 |
2014.02
Leave a Reply