Create Windows 8.1 KMS Host on Windows 7 Professional in a VM

I updated the zip attachment. The only change is that I trimmed the CurrentVersion.reg files which included extra unnecessary stuff.

 

You can try, but there may be issues. The x64 versions of Windows have additional registry keys and file locations, which I have not copied or studied.

 

If it was that simple, I would not have had to go to all this trouble. Unfortunately, you can't just take a hard disk image from one VM type and convert it to another, at least not in this case, as we are messing with activation states.

On the plus side, what I provide is setting up your own VM under Hyper-V from scratch, so you get more flexibility as to what you do with that VM.

That's the idea. With the things I provided, you can at least already do this for a Win 8.1 KMS Host. Just set up your own KMS host in a VM under Hyper-V and configure it how you like.

I think lots of people are aiming for this. Sadly no technique exists yet for setting up a Win 8.1 + Office KMS Host in an arbitrary VM. What you can do already though is run two VMs:
1) One VM would run an Office 2010/2013 KMS Host (this is already possible)
2) Other VM would run a Win 8.1 KMS Host
Just configure both VMs to listen on two different ports.

You could do that, yes. A single VM running in QEmu on your Server can be set up to activate your entire network.

 

As I note in my post, you should actually be able to update an existing WES7 VM Host with the activation data I provide. Use a similar technique as in the HowTo, you need to transfer the mistery/tokens/digitialid/wpa data into the WES7 VM corresponding to your VM type. This should work because Win 7 Pro and WES7 share the same activation method for KMS Hosts. The downside is that this will only enable Win 8.1 activation, and will kill Office 2010/2013 activation.

 

Noone has a KMS Host yet in QEmu that can activate a server.

 

Nice to hear. Which set of activation data did you use for this, the VMWare ones? I'm surprised it works, because I thought that ESXi virtualized a slightly different set of hardware than Workstation/Player.

 

That depends a bit on how you set up your VMs. What you write is true only if the VMs are directly exposed to the network. If they are hidden on the host (for example using NAT), their IP is not directly visible on the network, and all connections would go to the host's IP. In this case there'd be port forwarding involved.