Daz's bits and bobs …bytes bits
Getting the KMS count up over the initial threshold is a pain when you only have one server or one workstation to start with. Typically you need at least 5 servers or 25 client machine requesting activation before it will work.
This guy here as created a nice .exe that will trick KMS into thinking it has received all the required requests…
If DNS is failing you…. You can run the following powercil script to list all IP’s to virtual machines within vmware….
$IPaddresses = @()
foreach($vm in Get-VM){
$vm.Guest.VmName | %{
$IPaddresses += $_
}
$vm.Guest.IPAddress | %{
$IPaddresses += $_
}
}
$IPaddresses
Run this elevated command to find out;
powercfg /requests
There are some good windows web proxies about. The only problem with them is they sometimes dont natively act as a transparent proxy. i.e. typically you’ll need to set your client machines to a specific IP and port.
I’ve used squid historically when setting up transparent proxies (mainly since it actually has a transparent mode) and this has worked well. Recently i thought i’d have a go at some of the windows solutions to see how they pan out.
netsh is going to be the tool to assist in this case. Here is a typical use for netsh;
netsh
>add v4tov4 listenport=80 connectaddress=127.0.0.1 connectport=8080
This should grab all traffic that hits your machine bound for port 80 and redirect to port 8080.
You’ll also need to make sure that routing is enabled, so your machine can act as a gateway between the requests and the real outbound gateway (typically your dsl modem)
Some really good info at this site : http://kennethvanditmarsch.wordpress.com/2009/11/04/understanding-hp-flex-10-mappings-with-vmware/
A bit more around his finding during some tests : http://kennethvanditmarsch.wordpress.com/2009/12/04/testing-scenarios-vmware-hp-c-class-infrastructure/