What are you trying to activate with what key? To activate via KMS you´ll obviously need a gVLK, aka Volume License Key .
Hi ppl. I have a problem and need help. I manage to activate Win 8.1 pro through phone and after that had a trouble with office 2013. I tried same phone method but fail with wrong keys. I tried KMS nano v 11 just in case and counting that will not make mess, but I was wrong. After that somehow I managed to activate Office with phone but now ,when I check office status I se two notices. First one that office is activated and second one that need to be activated(change key). When I check in cmd I noticed that I have retail key and office is activated, and other one is KMS key who showing error. So my question is ,how to remove second KMS key or how to disable KMS server or uninstall KMS ? Sry for my bad english and ty in advance edit> my log after check activation Active code page: 866 Result KMSnano: Windows Status: Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Name: Windows(R), Professional edition Description: Windows(R) Operating System, RETAIL channel Partial Product Key: 8G33RI License Status: Licensed Office 2013 Status: Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing-------------------------- --------------------------------------- SKU ID: xxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxxxxx LICENSE NAME: Office 15, OfficeProPlusMSDNR_Retail edition LICENSE DESCRIPTION: Office 15, RETAIL channel BETA EXPIRATION: 1.1.1601. LICENSE STATUS: ---LICENSED--- Last 5 characters of installed product key: 234T31 --------------------------------------- SKU ID: xxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxxxxx LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel BETA EXPIRATION: 1.1.1601. LICENSE STATUS: ---OOB_GRACE--- ERROR CODE: 0x4004F00C ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period. REMAINING GRACE: 29 days (42390 minute(s) before expiring) Last 5 characters of installed product key: GVGXT Activation Type Configuration: ALL DNS auto-discovery: KMS name not available KMS machine registry override defined: 127.0.0.3:1688 Activation Interval: 43200 minutes Renewal Interval: 43200 minutes KMS host caching: Enabled Edit I found solution. I used MT 2.4.9, and removed that KMS serial from office.
If you all are worried about using your KMS RTM keys to make a reference KMS server, don't worry, M$ just made the ISOs available on MSDN and VLKS. So much for Oct 18th. I'm going to set up reference KMS server to debug/capture. If anyone here needs activate tokens for themself only please PM me, should have them soon.
Host, and only to the ppl here that I know are actually doing some work on this. Not going to have the world get activations from my REAL keys...
This month's edition of patch tuesday has a rather interesting update: KB2871389 Code: (...) Additionally, this update fixes several issues in Windows 8 Enterprise, Windows Server 2012, and volume licensed installations of Windows 8. (...) I haven't installed it yet, but I am curious what kind of fixes they placed there, although I don't see anyone complaining about it... It shouldn't be KMS v6, because of the need of changes on the KMS hosts, but then...
I just reactivated my main W8 machine against my local v5 host and it still works after that update. Its all good at the moment but I don't know what that update is all about.
Noticed the same thing when I wanted to update yesterday so I checked out the KB article but didn't elaborate on any of the specifics so I thought I'd go to my next best resource... MDL but quickly noticed the site was DOWN without any real explanation!!! After recalling some of the progress nosferati87 et. al. made on KMS v6 in the past couple days, the lack of info on KB2871389 and MDL being totally down for the first time that I can remember, paranoia set in as I thought it was a major crackdown by M$, ICE and Co. so I completely disconnected my laptop from the grid and checked this site's status from my phone Fortunately, the site came back online before my imagination ran totally wild and I realized after this experience that I probably need to curtail reading all those sci-fi conspiracy books... I mean the one I've recently been perusing through talks about a government spying on its citizen's by surreptitiously monitoring their conversations and online activities... talk about FICTION! PS. Great to see MDL up and running again and looking forward to the developments ahead Update: I updated all the patches listed on WU and all seems to be running fine with MTK activated sys.
Damn, I just did a re-install thinking I'd have no problem re-activating. Every server I tried is dead. Are they down for good ? I've been trying all night, I'll try again tomorrow. Maybe someone has a working one for me (win8) ? Thanks.
Well I finally got around to setting up KMS host, and it looks like you can't copy the tokens, and BIOS info from A VM liike you could do in the past. Anyone got any ideas about what's changed?
I installed the first VM from DVD, and used VAMT to activate a KMS host key on it, so I could cache the response just in case. Activated just fine. On a different hyper-v host, I installed a fresh server 2012R2 just like the first, edited the XML file on the second hyper-v host to have the same BIOS ID/GUID just like we did in the 2012(non-r2) days, cleared the key (-cpky), stoped sppsvc, robocopied (/b) the tokens from the activated KMS host, to the new one, and then started sppsvc. It's the same procedure everyone did back when the activated tokens from 2012 were released.
I might be remembering this incorrectly, but I don't recall having to replace tokens files during 2012/Win8 RTM. There was an entire virtual machine setup in Server 2012 Core and made available for download. The VM that I downloaded was already activated. All I had to do was change the BIOS ID/GUID in a file (xml)? for the VM prior to booting it for the first time. Once I did that, I was able to boot the (already activated) VM and it was ready to roll. I think that is what CODY was suggesting, moving the entire VM to another workstation and simply modify the BIOS ID/GUID files on that new machine.
On Hyper-V the BIOS Serialnumber and Guid are in an XML configuraiton file. Replacing the token's is easier and smaller then keeping a copy of the whole VM, and for me, my only optoin since my cable uplink is less then 64k on a good day. I can try just for kicks here, an export of the VM and import it on another server, but as far as getting it off my own net, the tokens are my only option.
200MB on my cable uplink? Good luck, whenever I make a new setup package for a software product of mine, and upload it to my download site, and it's just about 30mb, it takes like an hour. Even w/ QoS on my router, I can't do s**t while it's going on, including e-mail and phone, so my clients wouldn't be to happy about that.