Windows

通過在同一台伺服器上執行的 KMS 啟動 MS Office 2013 Standard

  • May 23, 2015

給定:Microsoft Windows Server 2008 R2 Enterprise 64 位,應用了所有最新的安全更新。

KMS 服務設置並執行,應用了所有推薦的更新(以處理 Windows 8 等可能的啟動問題)

Microsoft Office 2013 Standard 部署在上述伺服器和 Intranet 上的工作站上,批量許可生效(已輸入用於啟動 Microsoft Office 2013 的正確 KMS 密鑰)。

問題:我無法啟動在執行 KMS 服務的同一台伺服器上執行的 MS Office 2013 安裝。

KMS 事件日誌中沒有與此故障相關的條目。

一切都已重新啟動、重新安裝等多次(包括安裝 32 位和 64 位版本的 Office)。

請注意,KMS 服務工作正常。所有工作站都毫無故障地啟動了他們的 MS Office 2013。但是,伺服器本身的安裝拒絕使用 KMS。

防火牆設置正確。正確提供了主機名(通過’cscript ospp.vbs /sethst:hostname’,我嘗試了所有相關的主機名,從用於從工作站啟動的主機名開始)。所有其他記錄在案的所需檢查/操作也在啟動之前執行。

從我下麵包含的內容來看,ospp.vbs 提示上述內容無法通過 KMS 啟動。確實如此(即,我應該使用 MAK 啟動),還是我仍然遺漏了什麼?

我遵循了KMS 故障排除提示和相關文章,目前在 Technet 上沒有關於上述是否可行的建議。

slmgr.vbs / dlv 2E28138A-847F-42BC-9752-61B03FFF33CD 的輸出

---------------------------
Windows Script Host
---------------------------
Software licensing service version: 6.1.7601.17946

Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2013 10:00:12 AM

Key Management Service is enabled on this machine
   Current count: 5
   Listening on Port: 1688
   DNS publishing disabled
   KMS priority: Normal

Key Management Service cumulative requests received from clients
   Total requests received: 6
   Failed requests received: 0
   Requests with License Status Unlicensed: 0
   Requests with License Status Licensed: 0
   Requests with License Status Initial grace period: 6
   Requests with License Status License expired or Hardware out of tolerance: 0
   Requests with License Status Non-genuine grace period: 0
   Requests with License Status Notification: 0

---------------------------
OK   
---------------------------

cscript ospp.vbs /act的輸出

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: xxxxx
ERROR CODE: 0xC004F074
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not
be activated. No Key Management Service (KMS) could be contacted. Please see the
Application Event Log for additional information.
To view the activation event history run: cscript ospp.vbs /dhistorykms
---------------------------------------
---------------------------------------
---Exiting-----------------------------

cscript ospp.vbs /dstatus的輸出

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---NOTIFICATIONS---
ERROR CODE: 0xC004F056
ERROR DESCRIPTION: The Software Licensing Service reported that the product could
not be activated using the Key Management Service (KMS).
Last 5 characters of installed product key: xxxxx
       DNS auto-discovery: KMS name not available
       KMS machine registry override defined: xxxxxx:1688
       Activation Interval: 120 minutes
       Renewal Interval: 10080 minutes
       KMS host caching: Enabled
---------------------------------------
---------------------------------------
---Exiting-----------------------------

http://blogs.technet.com/b/odsupport/archive/2013/10/17/unable-to-kms-activate-office-running-on-windows-8-1-or-windows-server-2012-r2.aspx

從KB2885698安裝修補程序對我有用。一定要試一試。

Office 2013 似乎專門使用 DNS 查找來辨識其 KMS 伺服器。早期的 KMS 啟動版本的 Office 並非如此。這意味著您不能使用 localhost 或 127.0.0.1 之類的名稱作為 KMS 伺服器。您實際上必須使用 KMS 伺服器的完整 ActiveDirectory/DNS 名稱,即使它恰好是同一台機器。奇怪的是,Windows 7 啟動腳本沒有表現出這種行為……我還沒有測試過 Windows 8 或 8.1。

在您嘗試啟動 Office 2013 之前,請確保您可以在嘗試啟動 Office 2013 的主機上使用 nslookup 命令 DNS 查找您的 KMS 主機(即使它是同一台機器!)(是的,即使它是都在同一台機器上)。

最後,不要使用cscript ospp.vbs /sethst指定埠號。該命令不夠聰明,無法理解“:1688”是一個埠號引用,並且將使用“hostname:1688”作為主機名,而不是“hostname”作為主機名,1688 作為埠號。我相信有一個單獨的命令行開關可以設置埠,但您不需要明確設置它,除非您實際將 KMS 服務附加到預設 1688 以外的 TCP 埠。

引用自:https://serverfault.com/questions/475462