Exchange Version and UpdateRollups
Exchange Server 2010
|
Product name |
Build number |
Date |
KB |
|
Microsoft Exchange Server 2010 RTM |
14.0.639.21 |
11/9/2009 |
|
|
Update Rollup 1 for Exchange Server 2010 |
14.0.682.1 |
12/9/2009 |
|
|
Update Rollup 2 for Exchange Server 2010 |
14.0.689.0 |
3/4/2010 |
|
|
Update Rollup 3 for Exchange Server 2010 |
14.0.694.0 |
4/9/2010 |
|
|
Update Rollup 4 for Exchange Server 2010 |
14.0.702.1 |
6/17/2010 |
|
|
Update Rollup 5 for Exchange Server 2010 |
14.0.726.0 |
12/13/2010 |
Exchange Server 2010 Service Pack 1
|
Product name |
Build number |
Date |
KB |
|
Microsoft Exchange Server 2010 SP1 |
14.1.218.15 |
8/24/2010 |
|
|
Update Rollup 1 for Exchange Server 2010 SP1 |
14.1.255.2 |
10/4/2010 |
|
|
Update Rollup 2 for Exchange Server 2010 SP1 |
14.1.270.1 |
12/9/2010 |
|
|
Update Rollup 3 for Exchange Server 2010 SP1 |
14.1.289.3 |
3/7/2011 |
|
|
Update Rollup 3-v3 for Exchange Server 2010 SP1 |
14.1.289.7 |
4/1/2011 |
|
|
Update Rollup 4 for Exchange Server 2010 SP1 |
14.1.323.1 |
6/22/2011 |
|
|
Update Rollup 4-v2 for Exchange Server 2010 SP1 |
14.1.323.6 |
7/27/2011 |
|
|
Update Rollup 5 for Exchange Server 2010 SP1 |
14.1.339.1 |
8/23/2011 |
|
|
Update Rollup 6 for Exchange Server 2010 SP1 |
14.1.355.2 |
10/27/2011 |
|
|
Update Rollup 7 for Exchange Server 2010 SP1 |
14.1.421.0 |
8/13/2012 |
|
|
Update Rollup 7-v2 for Exchange Server 2010 SP1 |
14.1.421.2 |
10/9/2012 |
|
|
Update Rollup 7-v3 for Exchange Server 2010 SP1 |
14.1.421.3 |
11/12/2012 |
|
|
Update Rollup 8 for Exchange Server 2010 SP1 |
14.1.438.0 |
12/10/2012 |
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 |
|
|
Update Rollup 2 for Exchange Server 2010 SP2 |
14.2.298.4 |
4/16/2012 |
|
|
Update Rollup 3 for Exchange Server 2010 SP2 |
14.2.309.2 |
5/29/2012 |
|
|
Update Rollup 4 for Exchange Server 2010 SP2 |
14.2.318.2 |
8/13/2012 |
|
|
Update Rollup 4-v2 for Exchange Server 2010 SP2 |
14.2.318.4 |
10/9/2012 |
|
|
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 |
|
|
Update Rollup 6 for Exchange Server 2010 SP2 |
14.2.342.3 |
2/11/2013 |
|
|
Update Rollup 7 for Exchange Server 2010 SP2 |
14.2.375.0 |
8/13/2013 |
|
|
Update Rollup 8 for Exchange Server 2010 SP2 |
14.2.390.3 |
12/10/2013 |
Exchange Server 2010 Service Pack 3
|
Product name |
Build number |
Date |
KB |
|
Microsoft Exchange Server 2010 SP3 |
14.3.123.4 |
2/12/2013 |
|
|
Update Rollup 1 for Exchange Server 2010 SP3 |
14.3.146.0 |
5/29/2013 |
|
|
Update Rollup 2 for Exchange Server 2010 SP3 |
14.3.158.1 |
8/13/2013 |
|
|
Update Rollup 3 for Exchange Server 2010 SP3 |
14.3.169.1 |
11/25/2013 |
|
|
Update Rollup 4 for Exchange Server 2010 SP3 |
14.3.174.1 |
12/10/2013 |
|
|
Update Rollup 5 for Exchange Server 2010 SP3 |
14.3.181.6 |
2/25/2014 |
|
|
Update Rollup 6 for Exchange Server 2010 SP3 |
14.3.195.1 |
5/23/2014 |
|
|
Update Rollup 7 for Exchange Server 2010 SP3 |
14.3.210.2 |
8/26/2014 |
|
|
Update Rollup 8-v2 for Exchange Server 2010 SP3 |
14.3.224.2 |
12/12/2014 |
|
|
Update Rollup 9 for Exchange Server 2010 SP3 |
14.3.235.1 |
3/17/2015 |
|
|
Update Rollup 10 for Exchange Server 2010 SP3 |
14.3.248.2 |
6/16/2015 |
|
|
Update Rollup 11 for Exchange Server 2010 SP3 |
14.3.266.1 |
9/11/2015 |
|
|
Update Rollup 12 for Exchange Server 2010 SP3 |
14.3.279.2 |
12/10/2015 |
|
|
Update Rollup 13 for Exchange Server 2010 SP3 |
14.3.294.0 |
3/14/2016 |
|
|
Update Rollup 14 for Exchange Server 2010 SP3 |
14.3.301.0 |
6/15/2016 |
|
|
Update Rollup 15 for Exchange Server 2010 SP3 |
14.3.319.2 |
9/13/2016 |
Exchange Server 2013
|
Product name |
Build number |
Date |
KB |
|
Microsoft Exchange Server 2013 RTM |
15.0.516.32 |
12/03/2012 |
|
|
Exchange Server 2013 Cumulative Update 1 (CU1) |
15.0.620.29 |
04/02/2013 |
|
|
Exchange Server 2013 Cumulative Update 2 (CU2) |
15.0.712.24 |
07/09/2013 |
|
|
Exchange Server 2013 Cumulative Update 3 (CU3) |
15.0.775.38 |
11/25/2013 |
|
|
Exchange Server 2013 Service Pack 1 (SP1 aka CU4) |
15.0.847.32 |
02/25/2014 |
|
|
Exchange Server 2013 Cumulative Update 5 (CU5) |
15.0.913.22 |
05/27/2014 |
|
|
Exchange Server 2013 Cumulative Update 6 (CU6) |
15.0.995.29 |
08/26/2014 |
|
|
Exchange Server 2013 Cumulative Update 7 (CU7) |
15.0.1044.25 |
12/09/2014 |
|
|
Exchange Server 2013 Cumulative Update 8 (CU8) |
15.0.1076.9 |
03/17/2015 |
|
|
Exchange Server 2013 Cumulative Update 9 (CU9) |
15.0.1104.5 |
06/16/2015 |
|
|
Exchange Server 2013 Cumulative Update 10 (CU10) |
15.0.1130.7 |
09/14/2015 |
|
|
Exchange Server 2013 Cumulative Update 11 (CU11) |
15.0.1156.6 |
12/10/2015 |
|
|
Exchange Server 2013 Cumulative Update 12 (CU12) |
15.0.1178.4 |
3/14/2016 |
|
|
Exchange Server 2013 Cumulative Update 13 (CU13) |
15.0.1210.3 |
6/20/2016 |
|
|
Exchange Server 2013 Cumulative Update 14 (CU14) |
15.0.1236.3 |
9/20/2016 |
|
|
Exchange Server 2013 Cumulative Update 15 (CU15) |
15.0.1263.5 |
12/13/2016 |
|
|
Exchange Server 2013 Cumulative Update 16 (CU16) |
15.0.1293.2 |
3/21/2017 |
|
|
Exchange Server 2013 Cumulative Update 17 (CU17) |
15.0.1320.4 |
6/27/2017 |
Exchange Server 2016
|
Product name |
Build number |
Date |
KB |
|
Exchange Server 2016 Preview |
15.1.225.16 |
6/22/2015 |
|
|
Exchange Server 2016 RTM |
15.1.225.42 |
10/01/2015 |
|
|
Exchange Server 2016 Cumulative Update 1 (CU1) |
15.1.396.30 |
3/14/2016 |
|
|
Exchange Server 2016 Cumulative Update 2 (CU2) |
15.1.466.34 |
6/20/2016 |
|
|
Exchange Server 2016 Cumulative Update 3 (CU3) |
15.1.544.27 |
9/20/2016 |
|
|
Exchange Server 2016 Cumulative Update 4 (CU4) |
15.1.669.32 |
12/13/2016 |
|
|
Exchange Server 2016 Cumulative Update 5 (CU5) |
15.1.845.34 |
3/21/2017 |
|
|
Exchange Server 2016 Cumulative Update 6 (CU6) |
15.1.1034.26 |
6/27/2017 |
- Build number can be checked using Get-ExchangeServer cmdlet
Get-ExchangeServer | Select Name, AdminDisplayVersion
- Build number can be checked from ExSetup.exe file version information also
Get-Command Exsetup.exe | ForEach{$_.FileVersionInfo}
- The below command will be give detailed information about name, domain, edition, fqdn, server roles installed, site & admin display name.
Get-ExchangeServer | fl name, domain, edition, fqdn, serverrole, site, admindisplayversion
- To check ExSetup.exe file version information on all Exchange servers remotely, use below command.
Get-ExchangeServer | Sort-Object Name | ForEach{ Invoke-Command -ComputerName $_.Name -ScriptBlock { Get-Command ExSetup.exe | ForEach{$_.FileVersionInfo } } } | Format-Table -Auto
- In Exchange 2013 and Exchange 2016 you can also check build numbers in Exchange Admin Center (EAC).
- In EAC click on "servers" category on the left side and then click on "servers" pane.
Exchange Server and Update Rollups Build Numbers
Exchange Server 2013 and 2016 Build Numbers (with Cumulative Updates)
Exchange两种服务器版本：标准版和企业版。
企业版可支持每台服务器处理 100 个数据库；
标准版被限制在每台服务器处理 5 个数据库。
這些都是由【產品金鑰所定義的】授權版本。
當您輸入【有效的授權產品金鑰】時，便會【建立伺服器的支援版本】。
產品金鑰只能【用於相同版本金鑰的交換和升級，不能用於降級】。
您可以使用有效的產品金鑰
- 從 Exchange Server 2010 評估版 (試用版) 升級為 Standard Edition 或 Enterprise Edition。
- 從 Standard Edition 升級為 Enterprise Edition。
- 再授權一次伺服器。不需要重新安裝或重新設定任何項目，即可進行這些動作。在您輸入產品金鑰並重新啟動 Microsoft Exchange Information Store 服務之後，將會反映出對應於該產品金鑰的版本。
- 無法使用產品金鑰從 Enterprise Edition 降級為 Standard Edition，也不能用它們還原成試用版。
要進行這種類型的降級，只能解除安裝 Exchange 2010、重新安裝 Exchange 2010，並輸入正確的產品金鑰。
如需相關資訊
代码参考至：http://www.bhargavs.com/。
#############################################################################
# Get-ExchangeUpdateRollups.ps1
# Gets the Exchange Server 2007, Exchange 2010 and Exchange 2013 Update Rollups
# installed writes output to CSV file in same folder where script is called from
#
# Exchange 2013 CU Build Numbers - http://social.technet.microsoft.com/wiki/contents/articles/15776.exchange-server-2013-and-cumulative-updates-cus-build-numbers.aspx
# Exchange Server Update Rollups and Build Numbers - http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx
#
# This script won't report RUs for Exchange Server 2013 since it uses Cummulative Updates (CU).
# More details on Exchange Team Blog: Servicing Exchange 2013
# http://blogs.technet.com/b/exchange/archive/2013/02/08/servicing-exchange-2013.aspx
#
# Created by
# Bhargav Shukla
# http://www.bhargavs.com
#
# DISCLAIMER
# ==========
# THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE
# RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
############################################################################# # Store header in variable
$headerLine =
@"
Exchange 2013 CU Build Numbers - http://social.technet.microsoft.com/wiki/contents/articles/15776.exchange-server-2013-and-cumulative-updates-cus-build-numbers.aspx
Exchange Server Update Rollups and Build Numbers - http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx Server Name,Rollup Update Description,Installed Date,ExSetup File Version
"@ # Write header to file
$headerLine | Out-File .\results.csv -Encoding ASCII -Append function getRU([string]$Server)
{
# Set server to connect to
$Server = $Server.ToUpper() # Check if server is running Exchange 2007, Exchange 2010 or Exchange 2013 $ExchVer = (Get-ExchangeServer $Server | ForEach {$_.AdminDisplayVersion}) # Set appropriate base path to read Registry
# Exit function if server is not running Exchange 2007, Exchange 2010 or Exchange 2013
if ($ExchVer -match "Version 15")
{
$REG_KEY = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-18\\Products\\AE1D439464EB1B8488741FFA028E291C\\Patches"
$Reg_ExSetup = "SOFTWARE\\Microsoft\\ExchangeServer\\v15\\Setup"
}
elseif ($ExchVer -match "Version 14")
{
$REG_KEY = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-18\\Products\\AE1D439464EB1B8488741FFA028E291C\\Patches"
$Reg_ExSetup = "SOFTWARE\\Microsoft\\ExchangeServer\\v14\\Setup"
}
elseif ($ExchVer -match "Version 8")
{
$REG_KEY = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-18\\Products\\461C2B4266EDEF444B864AD6D9E5B613\\Patches"
$Reg_ExSetup = "SOFTWARE\\Microsoft\\Exchange\\Setup"
}
else
{
return
} # Read Rollup Update information from servers
# Set Registry constants
$VALUE1 = "DisplayName"
$VALUE2 = "Installed"
$VALUE3 = "MsiInstallPath" # Open remote registry
$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $Server) # Set regKey for MsiInstallPath
$regKey= $reg.OpenSubKey($REG_ExSetup) # Get Install Path from Registry and replace : with $
$installPath = ($regkey.getvalue($VALUE3) | foreach {$_ -replace (":","`$")}) # Set ExSetup.exe path
$binFile = "Bin\ExSetup.exe" # Get ExSetup.exe file version
$exSetupVer = ((Get-Command "\\$Server\$installPath$binFile").FileVersionInfo | ForEach {$_.FileVersion}) # Create an array of patch subkeys
$regKey= $reg.OpenSubKey($REG_KEY).GetSubKeyNames() | ForEach {"$Reg_Key\\$_"} # Walk through patch subkeys and store Rollup Update Description and Installed Date in array variables
$dispName = [array] ($regkey | %{$reg.OpenSubKey($_).getvalue($VALUE1)})
$instDate = [array] ($regkey | %{$reg.OpenSubKey($_).getvalue($VALUE2)}) # Loop Through array variables and output to a file
$countmembers = 0 if ($regkey -ne $null)
{
while ($countmembers -lt $dispName.Count)
{
$server+","+$dispName[$countmembers]+","+$instDate[$countmembers].substring(0,4)+"/"+$instDate[$countmembers].substring(4,2)+"/"+$instDate[$countmembers].substring(6,2)+","+$exsetupver | Out-File .\results.csv -Encoding ASCII -Append
$countmembers++
}
}
else
{
$server+",No Rollup Updates are installed,,"+$exsetupver | Out-File .\results.csv -Encoding ASCII -Append
}
} # Get Exchange 2007/2010 servers and write Rollup Updates to results file
$Servers = (Get-ExchangeServer -Identity WENDY* | Where-Object {($_.AdminDisplayVersion -match "Version 8" -OR $_.AdminDisplayVersion -match "Version 14" -OR $_.AdminDisplayVersion -match "Version 15") -AND $_.ServerRole -ne "ProvisionedServer" -and $_.ServerRole -ne "Edge"} | ForEach {$_.Name})
$Servers | ForEach {getRU $_}
Write-Output "Results are stored in $(Get-Location)\results.csv"
Exchange Version and UpdateRollups的更多相关文章
- .net 下发送calendar
前段时间公司系统中有一块需要发送邮件calendar outlook可以接受查看calendar 发送outlook主要是有rrule脚本的边界 网上找过一些资料,主要有两种实现方式 1.一种是已ic ...
- [No0000108]Git1/9-Git简介与入门
Git是什么? Git是目前世界上最先进的分布式版本控制系统(没有之一). Git有什么特点?简单来说就是:高端大气上档次! 那什么是版本控制系统? 如果你用Microsoft Word写过长篇大论, ...
- The Best Hacking Tools
The Best Hacking Tools Hacking Tools : List of security tools specifically aimed toward security pro ...
- 中国版Office 365混合部署功能
中国版Office 365混合部署功能已经正式上线了(原计划6月份推出),虽然支持的类型不如国际版的Office 365全面,但这也标志了该功能与之前相比,已经迈出了重要一步.目前中国版Office ...
- What is an ISAPI Extension?
https://www.codeproject.com/Articles/1432/What-is-an-ISAPI-Extension Introduction Unless you have be ...
- 滥用exchage远程调用域管理员API接口
0x00 前言 在大多数的Active Directory和Exchange中,Exchange服务器具有很高的权限,即Exchange服务器上的管理员可以很容易地将权限提升到域管理员权限,我在zdi ...
- IPSec无法建立？注意第一阶段hash sha !
该篇注意记录一下,有些情况下,我们配置了IPSec ,但是就是无法建立,发现连第一阶段都无法建立起来. 1.检查配置无问题 2.开启debug crypto isakmp发现有IKE的重传 3.sho ...
- 密钥交换协议之IKEv2
1. IKEv2 1.1 IKEv2简介 IKEv2(Internet Key Exchange Version 2,互联网密钥交换协议第 2 版)是第 1 版本的 IKE 协议(本文简称 IKEv1 ...
- JDK HttpClient 单次请求的生命周期
HttpClient 单次请求的生命周期 目录 HttpClient 单次请求的生命周期 1. 简述 2. uml图 3. Http连接的建立.复用和降级 3.1 调用流程及连接的建立和复用 3.2 ...
随机推荐
- Xgboost 模型保存和载入（）
https://blog.csdn.net/u012884015/article/details/78653178 xgb_model.get_booster().save_model('xgb.mo ...
- Python zip Python zip函数
zip([iterable, ...])zip()是Python的一个内建函数,它接受一系列可迭代的对象作为参数,将对象中对应的元素打包成一个个tuple(元组),然后返回由这些tuples组成的li ...
- springboot+springAOP实现数据库读写分离及数据库同步(MySQL)----最新可用2019-2-14
原文:https://blog.csdn.net/wsbgmofo/article/details/79260896 1,数据源配置文件,如下 datasource.readSize=1spring. ...
- WEEX快速入门
WEEX快速入门 WEEX 是阿里推送的一款基于Node.js,轻量级的移动端跨平台动态性技术解决方案,用于构建原生的速度的跨平台APP. 1. 搭建WEEX环境 1.1 首先下载安装Node.js, ...
- java之Thread Dump分析
什么是Thread Dump Thread Dump是非常有用的诊断Java应用问题的工具.每一个Java虚拟机都有及时生成所有线程在某一点状态的thread-dump的能力,虽然各个 Java虚拟机 ...
- spring-pool.xml
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.sp ...
- SAML2.0 协议初识（二）---Service Provider(SP)
上一节,我们初步认识了 SAML 协议的概念和工作流程,这一节将介绍 SP 端的一些细节. 通常情况下,SP 端是请求发起端,即当用户访问 SP 端的受保护资源时,由 SP 端向认证中心(IDP 端) ...
- spring的数据源
Spring提供了两个这样的数据源(都位于org.springframework.jdbc.datasource程序包里): DriverManagerDataSource:在每个连接请 ...
- php服务器端与android客户端通信问题
http://www.oschina.net/question/616446_90760
- C++基础细节2
1.关于引用和指针 概念上,引用(&)并不是对象,而是一个已经存在的对象的别名:引用不可以重新绑定到另外一个对象,因此引用必须初始化.(类比const,一经定义就不能修改,所以必须初始化,是同 ...