apache.org
Subject: RE: Windows Product Activation and KMS Server
You could write a script that runs once on boot, say after sysprep has
completed, that registers the Windows instance with a public facing KMS server
that is only accessible in your environment, for example, the public IP ranges
s
t: RE: Windows Product Activation and KMS Server
You could write a script that runs once on boot, say after sysprep has
completed, that registers the Windows instance with a public facing KMS server
that is only accessible in your environment, for example, the public IP ranges
supplied in Cloud
Hi Len,
You could create a NAT rule and pass that through to your KMS server. I
would set some ACLs on your firewall to only accept traffic from your
public ip range (which is assigned to your tenant VMs/Virtual Routers).
Sysprep can be used to point to the FQDN for that KMS server.
KMS agents ac
You could write a script that runs once on boot, say after sysprep has
completed, that registers the Windows instance with a public facing KMS server
that is only accessible in your environment, for example, the public IP ranges
supplied in Cloudstack that your instances use as a source NAT to a
Hi, I do not know kms server so I used sysprep.
Regards
2013/4/5 Len Bellemore
> Hi Guys,
>
> Anyone have a solution for activating Windows instances using a KMS server?
>
> Given that the KMS server needs to be publicly available to Cloud users,
> but not to general internet traffic, we need t
