niiiiiiiiiiiiiiiiiiiice, thanks for this work! Another step forward! I'm going to wait until we have a VMWare solution for Windows 8.1/Server2012R2 and Office 2013 and then I'll host it off of my domain for as long as I can. Thanks again! Edit: God damn, this is excellent documentation....... Edit#2: What would be needed for Server 2012R2 activation? Is the above supplied tokens/mistery/wpa/digitalid only for Windows Client versions? Is that a limitation of the token licenses or a limitation of your method? Edit#3: The KMSv5 activation required only tokens+UUID for vmware Server 2012 host. Are the tokens/mistery/wpa/digitalid components a result of the new added complexity of the KMSv6? Also, I can make a VMWare appliance if I can get the tokens/mistery/wpa/digitalid for the full suite.
It's a limitation of the licenses in the tokens, as available in KMSmicro V5.0. It only contains a Win 8.1 KMS Host key. The activation data I posted (tokens/mistery/wpa/digitalid) is very specifically for a Win 8.1 KMS host installed on Win 7 Pro. Also note that a Win 2012 R2 KMS Host can't be installed on a Windows client version (such as Win 7), so when a Win 2012 R2 KMS Host becomes available in the future, it will be in the form of a Win 2008/2012 computer or VM. As it happens, life would be so much easier if we had a Win 2012 R2 KMS Host in a Win 2012 R2 VM. Transferring full activation state (even without knowing the product key) is so much more easier in Win 2012 than in Win 7, and the method is already known.
Aha, that makes a lot of sense. It's quite weird that the first KMS that we had is on Windows 7 Embedded, but I suppose the original creator chose that for a small KMSMicro instance. Hopefully a brave soul will provide the information for a Server KMS soon. Thanks again!
I assume you mean to combine the Win 8.1 KMS host component of these new tokens with the Office 2010/2013 host components of existing tokens. (There is no sense in combining a Win 8.1 KMS host with a Win 8 KMS host, since a Win 8.1 KMS host activates Win 8 as well). If that is the case, then the answer is unfortunately No. At least, after days of thinking about it, I couldn't come up with a way to do so. There's a challenge
The complexity is not because of KMS v5 vs v6. It is a result of using Windows 7. The activation state is much easier to extract/copy from Windows 2012 than it is from Windows 7.
kelorgo Good to know it works on Enterprise too. I see you did this in Hyper-V, is that correct? Edit: you are the first one to report success following my instructions. You deserve some sort of prize
Hi kelorgo, Great job dude. I'm building my VM now. And I've just noticed the CurrentVersion.reg for QEmu is only 10k, yet for the other three VM's its 1.24mb From your instructions I'm guessing the 10k version would work in all four VM types.
Thanks Kelorgo, another fine piece of work!! The HowTo is great and very clearly written. Enough background information for people where it's needed, and actually a very simple 7-step guide for the actual VM creation. With clear instructions like these, even people like me, who only have about 50% of the IQ needed for something as complicated as creating a KMS VM, can do it. Well, maybe not in one day, but I did finish the first part!! To prove the 50% IQ part: I couldn't even find the Recovery Console, so I tried something else: For replacing the activation files, I booted my Win8PESE iso in the VM (after first adding your reg and cmd files to that ISO). This works great, I could even automate the filecopy process I think, I might do that later. So I'll continue this fun project tomorrow, after checking my notes from last year (still have all the documentation), I'll have to read up again on Charging the host, setting bridged adapters, etc. After the free WMC keys of last year, and the KMSv5 emulator, I must admit I didn't remember everything about the VM's etc... So history repeats itself... THANKS!!!
If you are already running a server as a Hyper-V host, would there not be a way to convert the Qemu ROM into a VHD or VHDX and run it as its own VM under the VM Host? That way, you could authenticate multiple computers on the network even if the network is under the KMS limit imposed by Microsoft. This KMS Server VM could be up and running indefinitely, with its own static IP, against which all the machines in your network could be validated for both Win8/8.1 *and* Office 2013. In fact, this is what I want to do: use valid Win8/8.1 & Office 2013 keys in this form of a KMS Server to validate multiple machines on the network, even though there will be less than 25 Win8/8.1 machines on said network. Edit: Or would I have to install Qemu on the Hyper-V Server and run it alongside Hyper-V just to run the ROM properly? I would prefer a successful conversion to a VHD or VHDX, I just don't know how to do so under a Windows environment.
I've just updated my KMS VM (thanks kelorgo / MDL). Could a MDL member please test it for me with an 8.1 activation request. (I'll drop you a PM with the info, cheers).
Ooops, thanks for pointing that out. It seems I didn't delete the extra fluff in some of the CurrentVersion.reg files I uploaded. I will fix that and reupload.
lunar21 from 1st page. Additional notes The reason why the Office 2010/2013 KMS Hosts are inactive in the resulting VMs is that after transferring activation data from KMSmicro to a different VM, all three KMS Host components are initially inactive (Windows, Office 2010, Office 2013). I was able to reactivate the Windows 8.1 KMS Host, but could not find a way for the Office KMS Hosts. Rather than having unactivated components in grace period, I chose to remove the Office KMS Host product keys.