Plus the tool gives a nice quick view of devices that were mistakenly licensed with MAK keys, and provides a nice easy way to convert them to KMS keys. The biggest bug bear of the older version was that once you'd done a discovery, if you forgot to save the info and closed the tool, you'd have to go through the same process next time. This is now automatically saved with SQL. Plus the tool is not proactive enough to remove devices that have been deleted from the domain, so we use the gui for cleanup, not much fun looking at a list of 25,000 devices when a large number have been removed
this article might be useful
An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012
Once the patch has been installed, install the new 2012 KMS host key from the command line on the KMS server:
cscript %windir%\system32\slmgr.vbs /ipk <KMS host key>
The KMS server will then report that it’s no longer activated and Windows is not ‘Genuine’. Run the following from the command line to reactivate itself with the new key.
cscript %windir%\system32\slmgr.vbs /ato
The install the latest version of VAMT - if you have a test environment I would try this there first
I have never been able to get VAMT 3 to dish out GVLK keys to Win 7 clients.
I ended up just pushing MAK keys out.
Now im getting this...
Unable to connect to the WMI service on the remote machine
firewall at a guess try poking holes for wmi or just turn it off
I'm having issues with VAMT as well, just set it all up and I'm getting :-
DNS records are fine, even with nslookup.Code:
0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
any ideas ?