Windows 8 KMS Activation

I've installed the new server essential version on one of my machines in my local network. Question: can I use the key, which is for the VM provided in the magnet also with this physical machine as KMS host or is the key only for VM?

 

Client only, you can't install a client host key on server OS

 

OK so I use any client in this network e.g. a simple machine with W7 on it and use this as KMS host?

 

If you want to use the pkeyconfig and tokens.dat from the dl to activate, you must install Win7 professional in VM with default settings (it's all in the pdf file).

 

Thank you, I read this but my question was, if I can do the same on a physical machine in my network with W7 Ultimate (thats the only version I have) as well not using VM

 

By using another setup, you wont be able to activate the host. Better to make a VM. Works like a charm.

 

The activation state is tied to the machine's hardware, and restoring it to a physical machine will cause the OS to de-activate because it no longer matches the previous (VM) hardware.

 

I guess you know what I wanted to do. I didn't understand first, that this method is tied to the VM only. Now I got it and will wait for a version that fits my physical way if ever issued.

 

Awesome some interesting progress in the last 10 pages

In summary at this point in time we can,

- Create a local offline KMS Host (using magnet link)
- The KMS host has to be Windows 7 or Windows 8 (NO SERVER)
- You must have 25 clients requesting KMS activation EVERY 30 days

Some questions:

- Does the KMS host activate clients (Windows 7 & 8) and servers (Windows 2008 & 2012)?
- Do the 25 clients have to be a mix of client and server OSs or can they be one or the other?
- Any chance of making a KMS host on Windows 2012 Core to reduce footprint?

 

Why not just use VMware Player and create a Windows 8 VM and make it into a KMS host. Turn it on and off when needed.

 

KMS host must be a Windows 7 Professional Virtual Machine.

 

This is simply why I like the physical way with all separate on different units. I don't like VM and I never had the need for as I always had many machines around doing individual jobs. I'm doing this since many years to eliminate the risk of total collapse of my only PC containing all my data.

 

- no, 7/8 only
- clients only
- no, not with this KMS host key

 

This is why I thought KMS host could be Win 7 or 8.

 

Ah that changes my excitement

 

The activation state and VM UUID for Win 8 are not provided yet. We should be grateful to have the Win 7 ones...

 

Right I know that and I didn't say I wasn't! I was simply summarising what I thought to be the current situation.

 

You will get tokens and pkey with virtualbox uuid as soon as i get home... there will be also client count to 25 if it saves in tokens...

 

That KMS host key is a "client-type" key and only activates client OSs, i.e. all KMS-capable editions of Vista, 7, and 8.

I don't think restoring the Windows 7 activation state would work on Windows 8/2012. However, I've been able to restore the activation state to a 2008 R2 Core VM (making it a "frankenbuild" by installing the license files from Windows 7), to keep the footprint small. Similarly, a Server 2008 Core VM with a Vista Business client key works as a KMS client to increase the count on the server.

 

Thanks for explaining. I hope someone shares a KMS host "server-type" key or figures out some way other way of creating a local KMS host.