Windows 2008R2部署Win7/2008R2+Office2010/2013/2016+Win8/2012+Win8.1/2012R2及Win10/2016 KMS激活服務器windows
1、部署windows 2008 R2 KMS激活:
服務器
一、安裝Windows2008R2w_sp1系統,加入域,配置好DNS;
網絡
二、以管理員權限運行cmd;app
三、(可省略)查看當前KMS狀態:cscript slmgr.vbs /dlidom
四、安裝KMS Key:cscript slmgr.vbs /ipk <KmsKey>ide
五、激活KMS Host(確保Internet鏈接的狀況下):cscript slmgr.vbs /ato工具
六、發佈KMS服務器到DNS上:cscript slmgr.vbs /sdns測試
七、開啓1688端號,使KMS能夠經過防火牆。打開控制面板,單擊「容許程序經過Windows防火牆」,選中「密鑰管理服務」。ui
八、(可省略)重啓Software Protection服務:net stop sppsvc && net start sppsvcthis
九、(可省略)檢查KMS狀態:cscript slmgr.vbs /dli
十、客戶端激活:slmgr.vbs -skms kms-server-ip
注意:若是此步出錯,運行slmgr -ipk xxx-xx-xx,再運行上一步
slmgr.vbs -ato
十一、在KMS服務器上檢查激活的數量:slmgr.vbs -dlv
Windows2008R2 KMS服務器支持激活Windows 7/2008R2
通常狀況下,每一個kms密鑰直接激活6臺服務器,而且這6臺均可以做爲kms服務器,這6臺機器若是重裝,每臺共能夠激活10次
2、部署Office2010(201三、2016相似)KMS激活:
一、下載office2010 KMS主機許可證包,下載並運行KeyManagementServiceHost.exe
Office2013 KMS許可證包和2010不一樣,下載文件後打開命令行窗口,運行cscript kms_host.vbs
二、出現提示時,輸入您的KMS主機密鑰
三、出現提示時,繼續進行激活(在KMS主機鏈接internet狀況下)
四、客戶端鏈接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
五、查看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
3、部署Windows7 KMS激活方法同Windows2008R2(注意KMS host key系統要求)
一、導入KMS Host密鑰:slmgr /ipk xxx
二、激活KMS Host:slmgr /ato(電話激活:slui.exe 4)
三、重啓服務:net stop sppsvc && net start sppsvc
四、客戶端鏈接激活:
slmgr /skms 10.0.0.1:1688(端口可選)
slmgr /ipk xxx-xx-xx-xx-xxx(可選,導入客戶端密鑰可轉成KMS客戶端版本)
slmgr /ato
4、部署(Windows2008R2 KMS服務器)添加支持Windows 8/2012(+添加支持Windows 8.1/2012R2)的客戶端激活
一、安裝支持Windows 8/2012的KMS補丁(http://support.microsoft.com/kb/2757817/zh-cn),根據提示重啓服務器
若是添加支持支持Windows 8.1/2012R2的激活,請安裝支持Windows 8.1/2012R2的KMS補丁(http://support.microsoft.com/kb/2885698/zh-cn),根據提示重啓服務器
二、安裝用於Windows 8/2012(或8.1/2012R2)激活的新 KMS 主機密鑰,請運行如下命令:
cscript %windir%\system32\slmgr.vbs /ipk <KMS 主機密鑰>
三、激活主計算機上的新 KMS 主機密鑰,在連網狀況下運行:cscript %windir%\system32\slmgr.vbs /ato
Windows 2012(R2)客戶端激活限制的數量包括Windows 2008R2的臺數,即在有5臺Windows2008R2的條件下1臺Windows 2012(R2)同樣能夠激活。
關於使用現有KMS host想激活win8/win2012請參考http://support.microsoft.com/kb/2691586
http://support.microsoft.com/kb/2757817/zh-cn
Win8.1/Win2012R2請參考http://support.microsoft.com/kb/2885698/zh-cn
注意:開通防火牆1688端口(容許key management service經過domain、home),不然會報0xC004F039錯誤。
若是客戶端與服務器時間相差太遠也可能致使激活錯誤,會報0xC004F074錯誤
若是客戶端不足,會報0xC004F038錯誤。Office\Windows 2008R2客戶端激活限制:5臺,Windows7:25臺,如若計數不夠可經過增長計數腳本補充不足計數,腳本見附件(在KMS服務器上執行)。
若是報0xc004f015錯誤說明在2008系統上輸入win7/8的kms host key了,請參考微軟幫助文檔http://support.microsoft.com/kb/2752119
當前Windows 7與Windows Server 2008 R2操做系統的分組以下:
Windows 客戶端分組:Windows 7 Professional、Windows 7 Enterprise;
服務器分組A:Windows Web Server 2008 R二、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>.
===================================================================
5、部署Windows 10 KMS激活
微軟發佈Windows 10後,計劃在公司內把Windows 10客戶端激活服務也添加到KMS Host中。部署方法和上面的相似,只是有一些特殊的限制。具體以下:
一、Windows 10要求Your existing KMS host must be running Windows 8 or later,因此要升級Windows 2008 R2系統至Windows 2012 R2,插入光盤點擊setup,按照默認步驟升級便可(或新安裝一臺);
二、升級完成後,更新系統補丁至最新。打開服務器管理器,安裝「批量激活服務」角色;
三、安裝完打開「批量激活工具」,安裝KMS主機密鑰,以下圖:
四、輸入「Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 」的KMS密鑰(支持Vista/2008至Win10/2012R2的全部系統激活),提交經過網絡或電話激活,關閉完成。也可根據須要修改默認配置;
五、下載Office20十、201三、2016的KMS主機許可證包,運行輸入密鑰激活;
Office2010:KeyManagementServiceHost.exe
http://www.microsoft.com/zh-cn/download/details.aspx?id=25095
Office2013(2016相同):KMS許可證包和2010不一樣,一種是從批量批可中心下載的vbs文件,運行cscript kms_host.vbs;另外一種是從下載中心下載的可執行文件office2013volumelicensepack.exe
http://www.microsoft.com/zh-CN/download/details.aspx?id=35584
六、客戶端激活,同以上的介紹。
注意事項:
官方說明文檔:Windows 10 Activate using Key Management Service
https://technet.microsoft.com/zh-cn/library/mt297923.aspx
若系統未更新到最新,需下載安裝Windows Server 2012 R2 更新程序 (KB3058168)以支持客戶端激活
http://www.microsoft.com/zh-CN/download/details.aspx?id=47622
安裝KB3058168前須要先安裝Windows Server 2012 R2 更新 (KB2919355)
http://www.microsoft.com/zh-CN/download/details.aspx?id=42334
測試過程當中,未查全全部文檔,直接先經過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」
https://support.microsoft.com/en-us/kb/3086418
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的密鑰就能夠了,繞了一圈。
6、部署Windows Server 2016激活
按照上面的部署,在Windows Server 2012 R2系統上部署windows 2016激活,須要完成如下兩個步驟:
一、安裝KB3058168補丁(部署win10時已安裝,此步跳過)
https://support.microsoft.com/kb/3058168
下載地址:https://www.microsoft.com/en-us/download/details.aspx?id=47622
二、安裝KB3172614補丁
https://support.microsoft.com/kb/3172614
下載地址:https://www.microsoft.com/en-us/download/details.aspx?id=53333
安裝完補丁重啓後,便可導入KMS密鑰:
一、打開「批量激活工具」
二、按照提示步驟,在「安裝KMS主機密鑰」處輸入Windows 2016的KMS密鑰
三、下一步,選擇激活產品(以下圖,默認只有一個選項),提交後連網在線激活便可。
客戶端激活:方法同2008,2012。
一、slmgr /skms kms-host-ip
二、slmgr /ato
參考:
https://blogs.technet.microsoft.com/askpfeplat/2016/10/24/kms-activation-for-windows-server-2016
7、附錄:KMS Client Setup Keys
Appendix A: KMS Client Setup Keys
https://technet.microsoft.com/en-us/library/jj612867.aspx
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.
To use the keys listed here (which are GVLKs), you must first have a KMS host running in your deployment. If you haven’t already configured a KMS host, see Deploy KMS Activation for steps to set one up.
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:
|
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」… |
Install this update on the KMS host if it is running Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012. 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. |
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 |
Operating system edition |
KMS Client Setup Key |
---|---|
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 |
Operating system edition |
KMS Client Setup Key |
---|---|
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 |
Operating system edition |
KMS Client Setup Key |
---|---|
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 |
Operating system edition |
KMS Client Setup Key |
---|---|
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 |
Operating system edition |
KMS Client Setup Key |
---|---|
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 |