一、部署windows 2008 R2 KMS激活:
1、安裝Windows2008R2w_sp1系統,加入域,配置好DNS;
2、以管理者權限運作cmd;
3、(可省略)檢視目前KMS狀态:cscript slmgr.vbs /dli
4、安裝KMS Key:cscript slmgr.vbs /ipk <KmsKey>
5、激活KMS Host(確定Internet連接配接的情況下):cscript slmgr.vbs /ato
6、釋出KMS伺服器到DNS上:cscript slmgr.vbs /sdns
7、開啟1688端号,使KMS可以通過防火牆。打開控制台,單擊“允許程式通過Windows防火牆”,選中“密鑰管理服務”。
8、(可省略)重新開機Software Protection服務:net stop sppsvc && net start sppsvc
9、(可省略)檢查KMS狀态:cscript slmgr.vbs /dli
10、用戶端激活:slmgr.vbs -skms kms-server-ip
注意:如果此步出錯,運作slmgr -ipk xxx-xx-xx,再運作上一步
slmgr.vbs -ato
11、在KMS伺服器上檢查激活的數量:slmgr.vbs -dlv
Windows2008R2 KMS伺服器支援激活Windows 7/2008R2
一般情況下,每個kms密鑰直接激活6台伺服器,并且這6台都可以作為kms伺服器,這6台機器如果重裝,每台共可以激活10次
二、部署Office2010(2013、2016類似)KMS激活:
1、下載下傳office2010 KMS主機許可證包,下載下傳并運作KeyManagementServiceHost.exe
Office2013 KMS許可證包和2010不同,下載下傳檔案後打開指令行視窗,運作cscript kms_host.vbs
<a href="http://blog.51cto.com/attachment/201310/151411530.jpg" target="_blank"></a>
2、出現提示時,輸入您的KMS主機密鑰
3、出現提示時,繼續進行激活(在KMS主機連接配接internet情況下)
4、用戶端連接配接KMS伺服器激活:
cscript ospp.vbs /sethst:<KMS 主機名>
cscript ospp.vbs /act //激活
cscript ospp.vbs /dhistorykms //檢視激活曆史,确認是否已經和激活主機連接配接上了
注意:ospp.vbs 在 Office 安裝目錄,如 Office2010安裝目錄:C:\Program Files (x86)\Microsoft Office\Office14
Office2013安裝目錄:C:\Program Files (x86)\Microsoft Office\Office15
<a href="http://blog.51cto.com/attachment/201310/151523988.jpg" target="_blank"></a>
5、檢視KMS伺服器office激活的數量:slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864
Office 2013 Activation ID:2E28138A-847F-42BC-9752-61B03FFF33CD
Office 2010 Activation ID:bfe7a195-4f8f-4f0b-a622-cf13c7d16864
手動導入用戶端密鑰:cscript ospp.vbs /inpkey:xxx-xx-xx-xx-xxx
三、部署Windows7 KMS激活方法同Windows2008R2(注意KMS host key系統要求)
1、導入KMS Host密鑰:slmgr /ipk xxx
2、激活KMS Host:slmgr /ato(電話激活:slui.exe 4)
3、重新開機服務:net stop sppsvc && net start sppsvc
4、用戶端連接配接激活:
slmgr /skms 10.0.0.1:1688(端口可選)
slmgr /ipk xxx-xx-xx-xx-xxx(可選,導入用戶端密鑰可轉成KMS用戶端版本)
slmgr /ato
四、部署(Windows2008R2 KMS伺服器)添加支援Windows 8/2012(+添加支援Windows 8.1/2012R2)的用戶端激活
2、安裝用于Windows 8/2012(或8.1/2012R2)激活的新 KMS 主機密鑰,請運作以下指令:
cscript %windir%\system32\slmgr.vbs /ipk <KMS 主機密鑰>
3、激活主計算機上的新 KMS 主機密鑰,在連網情況下運作:cscript %windir%\system32\slmgr.vbs /ato
<a href="http://blog.51cto.com/attachment/201310/152101776.jpg" target="_blank"></a>
Windows 2012(R2)用戶端激活限制的數量包括Windows 2008R2的台數,即在有5台Windows2008R2的條件下1台Windows 2012(R2)一樣可以激活。
<a href="http://support.microsoft.com/kb/2757817/zh-cn" target="_blank">http://support.microsoft.com/kb/2757817/zh-cn</a>
注意:開通防火牆1688端口(允許key management service通過domain、home),否則會報0xC004F039錯誤。
如果用戶端與伺服器時間相差太遠也可能導緻激活錯誤,會報0xC004F074錯誤
如果用戶端不足,會報0xC004F038錯誤。Office\Windows 2008R2用戶端激活限制:5台,Windows7:25台,如若計數不夠可通過增加計數腳本補充不足計數,腳本見附件(在KMS伺服器上執行)。
目前Windows 7與Windows Server 2008 R2作業系統的分組如下:
Windows 用戶端分組:Windows 7 Professional、Windows 7 Enterprise;
伺服器分組A:Windows Web Server 2008 R2、Windows Server 2008 R2 HPC Edition、Windows HPC Server 2008 R2;
伺服器分組B:Windows Server 2008 R2 Standard、Windows Server 2008 R2 Enterprise;
伺服器分組C:Windows Server 2008 R2 Datacenter、Windows Server 2008 R2 Itanium-based System。
server C>server B>server A>client VL
用進階别的密鑰組成的KMS伺服器可以激活低級别的系統。
KMS的密鑰類型旨在激活指定主機系統的服務,在本質上是按等級劃分的。
(1)KMS 密鑰可釋出至特定的産品分組,并與它們互相關聯。
(2)每種 KMS 密鑰可以激活産品組内以及該層次結構中級别更低的産品組中的産品。
将KMS主機、MAK或零售版的Windows轉換成KMS用戶端方法:
slmgr /ipk <setup key>.
===================================================================
五、部署Windows 10 KMS激活
微軟釋出Windows 10後,計劃在公司内把Windows 10用戶端激活服務也添加到KMS Host中。部署方法和上面的類似,隻是有一些特殊的限制。具體如下:
1、Windows 10要求Your existing KMS host must be running Windows 8 or later,是以要更新Windows 2008 R2系統至Windows 2012 R2,插入CD光牒點選setup,按照預設步驟更新即可(或新安裝一台);
2、更新完成後,更新系統更新檔至最新。打開伺服器管理器,安裝“批量激活服務”角色;
3、安裝完打開“批量激活工具”,安裝KMS主機密鑰,如下圖:
<a href="http://s3.51cto.com/wyfs02/M00/71/57/wKioL1XMFDWTPOLDAAFM-wDad0Q945.jpg" target="_blank"></a>
4、輸入“Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 ”的KMS密鑰(支援Vista/2008至Win10/2012R2的所有系統激活),送出通過網絡或電話激活,關閉完成。也可根據需要修改預設配置;
5、下載下傳Office2010、2013、2016的KMS主機許可證包,運作輸入密鑰激活;
Office2010:KeyManagementServiceHost.exe
<a href="http://www.microsoft.com/zh-cn/download/details.aspx?id=25095" target="_blank">http://www.microsoft.com/zh-cn/download/details.aspx?id=25095</a>
Office2013(2016相同):KMS許可證包和2010不同,一種是從批量批可中心下載下傳的vbs檔案,運作cscript kms_host.vbs;另一種是從下載下傳中心下載下傳的可執行檔案office2013volumelicensepack.exe
<a href="http://www.microsoft.com/zh-CN/download/details.aspx?id=35584" target="_blank">http://www.microsoft.com/zh-CN/download/details.aspx?id=35584</a>
6、用戶端激活,同以上的介紹。
注意事項:
官方說明文檔:Windows 10 Activate using Key Management Service
<a href="https://technet.microsoft.com/zh-cn/library/mt297923.aspx" target="_blank">https://technet.microsoft.com/zh-cn/library/mt297923.aspx</a>
若系統未更新到最新,需下載下傳安裝Windows Server 2012 R2 更新程式 (KB3058168)以支援用戶端激活
<a href="http://www.microsoft.com/zh-CN/download/details.aspx?id=47622" target="_blank">http://www.microsoft.com/zh-CN/download/details.aspx?id=47622</a>
安裝KB3058168前需要先安裝Windows Server 2012 R2 更新 (KB2919355)
<a href="http://www.microsoft.com/zh-CN/download/details.aspx?id=42334" target="_blank">http://www.microsoft.com/zh-CN/download/details.aspx?id=42334</a>
測試過程中,未查全所有文檔,直接先通過Windows Server 2012 R2 Standard - Windows Server 2012 R2 (Std and DataCtr)的KMS密鑰激活2012R2,然後再輸入Windows 10的KMS密鑰時,提示“軟體授權服務報告許可證未安裝”、系統日志“安裝購買證明失敗。0xC004F015”的錯誤。
在Win10用戶端激活時報“0xC004F074 軟體授權服務報告無法激活計算機,無法聯系任何密鑰管理服務”、系統日志報事件ID12288的“0xC004F042”的錯誤
在網上搜尋官方文檔有以下說明:“Error 0xC004F015 when you try to activate Windows 10 Enterprise on a Windows Server 2012 R2 KMS host”
<a href="https://support.microsoft.com/en-us/kb/3086418" target="_blank">https://support.microsoft.com/en-us/kb/3086418</a>
To resolve this problem, follow these steps:
Log on to the Volume Licensing Service Center (VLSC).
Click License.
Click Relationship Summary.
Click License ID of their current Active License.
After the page loads, click Product Keys.
In the list of keys, locate Windows Srv 2012R2 DataCtr/Std KMS for Windows 10.
Install this key on the KMS host.
輸入Windows Srv 2012R2 DataCtr/Std KMS for Windows 10的密鑰就可以了,繞了一圈。
六、部署Windows Server 2016激活
按照上面的部署,在Windows Server 2012 R2系統上部署windows 2016激活,需要完成以下兩個步驟:
1、安裝KB3058168更新檔(部署win10時已安裝,此步跳過)
<a href="https://support.microsoft.com/kb/3058168" target="_blank">https://support.microsoft.com/kb/3058168</a>
2、安裝KB3172614更新檔
<a href="https://support.microsoft.com/kb/3172614" target="_blank">https://support.microsoft.com/kb/3172614</a>
安裝完更新檔重新開機後,即可導入KMS密鑰:
1、打開“批量激活工具”
2、按照提示步驟,在“安裝KMS主機密鑰”處輸入Windows 2016的KMS密鑰
3、下一步,選擇激活産品(如下圖,預設隻有一個選項),送出後連網線上激活即可。
<a href="https://s3.51cto.com/wyfs02/M01/8D/D6/wKiom1ir_d_Bb7rDAACfMOQQYQc896.jpg" target="_blank"></a>
用戶端激活:方法同2008,2012。
1、slmgr /skms kms-host-ip
2、slmgr /ato
參考:
<a href="https://blogs.technet.microsoft.com/askpfeplat/2016/10/24/kms-activation-for-windows-server-2016" target="_blank">https://blogs.technet.microsoft.com/askpfeplat/2016/10/24/kms-activation-for-windows-server-2016</a>
七、附錄:KMS Client Setup Keys
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx" target="_blank">https://technet.microsoft.com/en-us/library/jj612867.aspx</a>
Updated: August 2, 2016
Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2
Computers that are running volume licensing editions of Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008 are, by default, KMS clients with no additional configuration needed.
If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from the following tables. To install a client setup key, open an administrative command prompt on the client, type slmgr /ipk <setup key> and then press Enter.
If you want to…
…use these resources
Activate Windows outside of a volume-activation scenario (that is, you’re trying to activate a retail version of Windows), these keys will not work.
Use these links for retail versions of Windows:
<a href="http://windows.microsoft.com/windows/get-windows-product-key" target="_blank">Get a new Windows product key</a>
<a href="http://windows.microsoft.com/windows/help/genuine" target="_blank">Genuine Windows Help & How-to</a>
<a href="http://answers.microsoft.com/windows/forum/windows8_1-windows_install-winactivate?tab=Threads" target="_blank">Microsoft Community forum on installation and activation</a>
Fix this error that you get when you try to activate a Windows 8.1, Windows Server 2012 R2 or newer system: “Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid”…
If you are running Windows Server 2008 R2 or Windows 7, be on the lookout for an update to support using those as KMS hosts for Windows 10 clients.
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_0" target="_blank"></a>
Operating system edition
KMS Client Setup Key
Windows Server 2016 Datacenter
CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Standard
WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Essentials
JCKRF-N37P4-C2D82-9YXRT-4M63B
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_1" target="_blank"></a>
Windows 10 Professional
W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Professional N
MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Enterprise
NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N
DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Education
NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N
2WH4N-8QGBV-H22JP-CT43Q-MDWWJ
Windows 10 Enterprise 2015 LTSB
WNMTR-4C88C-JK8YV-HQ7T2-76DF9
Windows 10 Enterprise 2015 LTSB N
2F77B-TNFGY-69QQF-B8YKP-D69TJ
Windows 10 Enterprise 2016 LTSB
DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ
Windows 10 Enterprise 2016 LTSB N
QFFDN-GRT3P-VKWWX-X7T3R-8B639
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_2" target="_blank"></a>
Windows 8.1 Professional
GCRJD-8NW9H-F2CDX-CCM8D-9D6T9
Windows 8.1 Professional N
HMCNV-VVBFX-7HMBH-CTY9B-B4FXY
Windows 8.1 Enterprise
MHF9N-XY6XB-WVXMC-BTDCT-MKKG7
Windows 8.1 Enterprise N
TT4HM-HN7YT-62K67-RGRQJ-JFFXW
Windows Server 2012 R2 Server Standard
D2N9P-3P6X9-2R39C-7RTCD-MDVJX
Windows Server 2012 R2 Datacenter
W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9
Windows Server 2012 R2 Essentials
KNC87-3J2TX-XB4WP-VCPJV-M4FWM
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_3" target="_blank"></a>
Windows 8 Professional
NG4HW-VH26C-733KW-K6F98-J8CK4
Windows 8 Professional N
XCVCF-2NXM9-723PB-MHCB7-2RYQQ
Windows 8 Enterprise
32JNW-9KQ84-P47T8-D8GGY-CWCK7
Windows 8 Enterprise N
JMNMF-RHW7P-DMY6X-RF3DR-X2BQT
Windows Server 2012
BN3D2-R7TKB-3YPBD-8DRP2-27GG4
Windows Server 2012 N
8N2M2-HWPGY-7PGT9-HGDD8-GVGGY
Windows Server 2012 Single Language
2WN2H-YGCQR-KFX6K-CD6TF-84YXQ
Windows Server 2012 Country Specific
4K36P-JN4VD-GDC6V-KDT89-DYFKP
Windows Server 2012 Server Standard
XC9B7-NBPP2-83J2H-RHMBY-92BT4
Windows Server 2012 MultiPoint Standard
HM7DN-YVMH3-46JC3-XYTG7-CYQJJ
Windows Server 2012 MultiPoint Premium
XNH6W-2V9GX-RGJ4K-Y8X6F-QGJ2G
Windows Server 2012 Datacenter
48HP8-DN98B-MYWDG-T2DCC-8W83P
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_4" target="_blank"></a>
Windows 7 Professional
FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Windows 7 Professional N
MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Windows 7 Professional E
W82YF-2Q76Y-63HXB-FGJG9-GF7QX
Windows 7 Enterprise
33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows 7 Enterprise N
YDRBP-3D83W-TY26F-D46B2-XCKRJ
Windows 7 Enterprise E
C29WB-22CC8-VJ326-GHFJW-H9DH4
Windows Server 2008 R2 Web
6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Windows Server 2008 R2 HPC edition
TT8MH-CG224-D3D7Q-498W2-9QCTX
Windows Server 2008 R2 Standard
YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise
489J6-VHDMP-X63PK-3K798-CPX3Y
Windows Server 2008 R2 Datacenter
74YFP-3QFB3-KQT8W-PMXWJ-7M648
Windows Server 2008 R2 for Itanium-based Systems
GT63C-RJFQ3-4GMB6-BRFB9-CB83V
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_5" target="_blank"></a>
Windows Vista Business
YFKBB-PQJJV-G996G-VWGXY-2V3X8
Windows Vista Business N
HMBQG-8H2RH-C77VX-27R82-VMQBT
Windows Vista Enterprise
VKK3X-68KWM-X2YGT-QR4M6-4BWMV
Windows Vista Enterprise N
VTC42-BM838-43QHV-84HX6-XJXKV
Windows Web Server 2008
WYR28-R7TFJ-3X2YQ-YCY4H-M249D
Windows Server 2008 Standard
TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Standard without Hyper-V
W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
Windows Server 2008 Enterprise
YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 Enterprise without Hyper-V
39BXF-X8Q23-P2WWT-38T2F-G3FPG
Windows Server 2008 HPC
RCTX3-KWVHP-BR6TB-RB6DM-6X7HP
Windows Server 2008 Datacenter
7M67G-PC374-GR742-YH8V4-TCBY3
Windows Server 2008 Datacenter without Hyper-V
22XQ2-VRXRG-P8D42-K34TD-G3QQC
Windows Server 2008 for Itanium-Based Systems
4DWFP-JF3DJ-B7DTH-78FJB-PDRHK
<a href="https://technet.microsoft.com/en-us/library/jj612867.aspx#Anchor_6" target="_blank"></a>
<a href="https://technet.microsoft.com/en-us/library/jj134042.aspx" target="_blank">Plan for Volume Activation</a>
本文轉自 lorysun 51CTO部落格,原文連結:http://blog.51cto.com/lorysun/1261192