Microsoft Office 2013 RTM KMS Activation

with the files of english vl iso ?

 

Ok, it's for Office 2010, I opened 2010, waited for it to repair itself and rebooted, and that key has returned

 

Especially for Office this seems possible, only because the E-Z Activator was used to activate Office 2010 VL so what is the difference between versions and activation methods? Seems like the same process to me....

 

Where to get this files?
Regards

 

"proplus.ww" is language-independent (ww == worldwide), so it's the same on the VL release of any language. The VL-specific files are in "proplus.ww" and "admin". Copy these directories from a VL ISO to a retail one (any language), delete "proplusr.ww", and you've got a VL release.

 

What about KMS server?
Still not working?

 

The Connection is intermitten i have tryed a dozen time and have managed to activate 3 times

 

Code:

cscript ospp.vbs /sethst:91.149.135.83:80

correct?

Code:

---Processing--------------------------
---------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: b322da9c-a2e2-4058-9e4e-f59a6970bd69
LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: GVGXT
ERROR CODE: 0xC004F074
ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
d not be activated. No Key Management Service (KMS) could be contacted. Please s
ee the Application Event Log for additional information.
To view the activation event history run: cscript ospp.vbs /dhistorykms
---------------------------------------
---------------------------------------
---Exiting-----------------------------

Try again?

 

How to do this without having proper files?

 

take off the :80

 

Code:

---Processing-----------------------------------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: b322da9c-a2e2-4058-9e4e-f59a6970bd69
LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: GVGXT
ERROR CODE: 0x8007000D
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x8007000D
---------------------------------------
---------------------------------------
---Exiting-----------------------------

 

Mine doesn't even say that

Code:

C:\Program Files (x86)\Microsoft Office 2013\Office15>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: b322da9c-a2e2-4058-9e4e-f59a6970bd69
LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: GVGXT
ERROR CODE: 0x8007000D
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x8007000D

 

What yours says is better. The error 0x8007000D at least implies that you are getting through to the server, just not able to activate. The reason the user above you is getting the service not found message is because this server is not listening on port 80 for KMS activations.

This is a total shot in the dark, but I am wondering if there are problems because of the extra encryption added in KMS activation on Win8/Office 2013. I am able to activate my Office 2010 VL against this server without problems. However, as soon as I attempt to activate any Office 2013 VL (running on Windows 8), I receive the 0x8007000D message immediately.

 

Yea I noticed if I added a port to the end of the KMS IP, it would add it like this xxx:xxx:xxx:xxx:80:1688 and end up with 2 x ports


I have somehow broken my 2010 license, no matter what I do it keeps telling me to repair the install, this is a genuine Technet install too, so gonna have to uninstall it I think

Why does 2013 not have Office Picture Manager? That`s really all I miss from 2010

 

That is because you cannot specify a port via /sethst. To set port, use /setprtORT# so that it would look like:

cscript ospp.vbs /setprt:1688

 

Ah ok, anyway KMS is generally :1688 though right ?

 

Yes, standard Key Management Service listens on 1688. Admin of the server would have to change that port number - only then would you need to specify another port.

 

You need to login to view this posts content.

 

I think I'm going to uninstall it for now until something easier and more permanent arrives to activate it, it's not playing nice with 2010 and I use picture manager all the time

 

I Have succsesfuly activate 6 copys so far.