Output of cscript ospp.vbs /act Microsoft (R) Windows Script Host Version 5.8Ĭopyright (C) Microsoft Corporation. Requests with License Status Notification: 0 Requests with License Status Non-genuine grace period: 0 Requests with License Status License expired or Hardware out of tolerance: 0 Requests with License Status Initial grace period: 6 Requests with License Status Unlicensed: 0 Key Management Service cumulative requests received from clients Key Management Service is enabled on this machine I followed the KMS troubleshooting hints and related articles, and currently on Technet there are no advice pieces whether the above is at all possible. Is it indeed the case (i.e., I should use MAK activation instead), or I am still missing something? Judging by what I include below, ospp.vbs hints the above can't be activated via KMS. All the other documented required checks/actions are performed as well prior to activating. Host name is provided correctly (via 'cscript ospp.vbs /sethst:hostname', I tried all the hostnames relevant, starting with that working for activating from workstations). However, the installation on the server itself refuses to use KMS.įirewall is set up correctly. All the workstations activate their MS Office 2013 without a single glitch. There are no entries in KMS event log related to this failure.Įverything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run. Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered). KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc) Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
0 kommentar(er)
