![microsoft 2013 professional plus activation kms microsoft 2013 professional plus activation kms](https://office-activator.com/wp-content/uploads/2020/06/office2019.png)
- #Microsoft 2013 professional plus activation kms Activator#
- #Microsoft 2013 professional plus activation kms full#
- #Microsoft 2013 professional plus activation kms software#
- #Microsoft 2013 professional plus activation kms license#
- #Microsoft 2013 professional plus activation kms windows 8#
#Microsoft 2013 professional plus activation kms Activator#
Microsoft Office 2013 Activator 2022 is an excellent activator presented by Microsoft.
#Microsoft 2013 professional plus activation kms full#
I believe there's a separate command-line switch that sets the port, but you don't need to set it explicitly unless you actually attach the KMS service to a TCP port other than the default 1688.1.11 Like this: Microsoft (MS) Office 2013 Professional Activator Full Latest Working The command isn't smart enough to understand that ":1688" is a port number reference and will literally use "hostname:1688" as the hostname, instead of "hostname" as the hostname and 1688 as the port number.
#Microsoft 2013 professional plus activation kms windows 8#
I haven't tested Windows 8 or 8.1 yet.īefore you attempt Office 2013 activation, please make sure that you can DNS look up your KMS host (even if it's the same machine!) with the nslookup command on the host where you're trying to activate Office 2013 (yes, even if it's all on the same machine).įinally, do not specify the port number with cscript ospp.vbs /sethst. Oddly enough the Windows 7 activation script does not exhibit this behaviour. You actually have to use the full ActiveDirectory/DNS name of your KMS server even if it happens to be the same machine. What that means is that you cannot use names like localhost or 127.0.0.1 as your KMS server. That was not the case with earlier KMS-activated versions of Office.
![microsoft 2013 professional plus activation kms microsoft 2013 professional plus activation kms](https://cdn-images-1.medium.com/fit/t/1600/480/0*ft_ZQeCAVueKjcKZ.jpeg)
Office 2013 seems to use DNS lookups exclusively for identifying its KMS server. KMS machine registry override defined: xxxxxx:1688 Not be activated using the Key Management Service (KMS).ĭNS auto-discovery: KMS name not available
#Microsoft 2013 professional plus activation kms software#
Output of cscript ospp.vbs /dstatus Microsoft (R) Windows Script Host Version 5.8ĮRROR DESCRIPTION: The Software Licensing Service reported that the product could To view the activation event history run: cscript ospp.vbs /dhistorykms Please see theĪpplication Event Log for additional information. No Key Management Service (KMS) could be contacted. Last 5 characters of installed product key: xxxxxĮRROR DESCRIPTION: The Software Licensing Service reported that the product could notīe activated.
![microsoft 2013 professional plus activation kms microsoft 2013 professional plus activation kms](https://www.techwaver.com/wp-content/uploads/2020/08/KMS-Activator-Office.jpg)
#Microsoft 2013 professional plus activation kms license#
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx Installed product key detected - attempting to activate the following product: 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.