The most prevalent version is 9. ![]() It was initially added to our database on. I.e., for Office, the KMShost is not automatically activated for Office usage - you must configure the machine as KMSclient and meet the KMSclient requirements, i.e. The latest version of KMSpico (Beta) is 9.2.2.RC, released on. ![]() Output of cscript ospp.vbs /dstatus LICENSE NAME: Office 15, OfficeStandardVLKMSClient edition LICENSE DESCRIPTION: Office 15, VOLUMEKMSCLIENT channel LICENSE STATUS: -OOBGRACE- ERROR CODE: 0x4004f00c ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c Last 5 characters of installed product key: GVGXT DNS auto-discovery: KMS name not available Your Office KMShost server, is also an Office KMSclient, but, the Office KMSclient configuration on this machine is incorrect? In general, for Windows KMShost purposes, the same machine is not a KMSclient+KMShost. Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run. KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc) 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). ![]() Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |