TL;DR: is it possible to install some kind of local kms activation proxy, so the clients could only talk to the proxy, and the proxy will forward the activation request to a kms server which can not be reached by the clients themselves?

At our university, we provide two client pools for our students: a hardware pool with 50 Win7 clients, and a virtual VMWare View pool with Win8.1 clients. VMWare View does not support MAK activation, so we have to use kms - we want to use kms activation in the hardware pool as well. These pools are using an ip address pool that can not access the outside, only ports 80 and 443 through a web proxy.

Due to a cooperation between the universities in our state there is one university who is registrated with Microsoft, and all other universities are using there licences. This university has a kms server which we could use, and they do not want us to set up our own kms server - they say microsoft does not like to have too much kms servers in the same licensed organisation.

So what we want to do: our clients in a private subnet and blocked from the outside world with the exceptions http/https want to communicate with the kms server of another institution - since they provide the kms server for different institutions, i don't think they would accept changeing their kms ports...

What i can do ist to put kind of a gateway server in the middle - one foot in the internet, one foot in the private client net, and this "proxy" could then take the activation requests from the clients and pass them to the external kms server.

Is this somehow possible? The only thing i read about proxies in combination of win licensing is a proxy activation for mak keys... But this does not help.

  • 1
    Add allow rule for port 1688 to talk to that KMS server ?, else kb.vmware.com/selfservice/microsites/… – yagmoth555 Aug 11 '15 at 14:07
  • That was what i asked our network admin - he does not want to do that. he won't allow anything else then 80 and 443 for this subnet. – Tobias Aug 11 '15 at 14:10
  • 6
    Well, tell the network admin it's required, and if necessary, involve the higher ups to make it possible. Your university pays a lot of money for this contract and to use it, you need to access this service. – Sven Aug 11 '15 at 14:18
  • 1
    It seems not only to be an adminsitrative but also a techinal problem: according to the net admin, non of our networking devices is capable of NAT. NOw i read that i could use a Win Server as router and let him NAT the addresses... Can it be that this is the only solution? – Tobias Aug 12 '15 at 8:26
  • @Tobias You mean the network the PC stand-in is isolated and not routed ? Just there it's a design error. – yagmoth555 Aug 12 '15 at 12:26

I finaly created my own virtual KMS proxy appliance: simple debian, one NIC in the internal net, one to the outside world. Configured iptables to forward to the external KMS server, enabled NAT.

Now i only have to publish a new route to the external KMS server through this proxy, and activation is working fine.

I am still looking forward to our new network infrastructure...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.