Ah, if that's right. But having an initial copy of the virtual server KMS, this process can be repeated. That is two VMs = 50 activations .... is not it?
I think installing the Windows 8 client license files on Server Core so that it takes Windows 8 GVLKs (making it a "frankenbuild") could work. If it's only used to bump up the client count on the server it doesn't matter if it's got proper files installed.
How do I activate my W8P, with my KMS server? Which IP address should I target? I have a Windows 7 in VirtualBox Pro, perfectly installed with the key.
Well... you activate like with any other server, except with your KMS server VM's IP. We can't tell you what that is, you'll have to look it up (e.g. by running ipconfig). Although, until the server has received at least 25 activation requests from clients, you can't activate.
The IP of the KMS host of course, think this will not work using NAT but needs a bridged network adapter configured in VirtualBox
I installed two bridge adapters, WiFi and Ethernet, and use the KMS server IPv4 address, but something goes wrong.
Turn off windows firewall on KMS host... or allow traffic on that KMS port... Well geting KMS host up is easy, geting client count to 25 is pain in the butt... im wondering if i would make it public over night... that would be fast solution installing 25x VMs is just boring and you cant even clone VM since every VM gets same hardware id... anyone knows how to regenerate tokens.dat without reinstalling whole system?
Open port in the firewall, either through GUI or with this command Code: netsh advfirewall firewall set rule name="Key Management Service (TCP-In)" new enable=yes