New answers tagged licensing
Was just googling for a similar situation All clients are activating just fine, except for my original KMS client which also happens to be Windows 7 Now I know what I need to do. We are in the process of building out their next 2012r2 server. this should fix for us as well
Please call the Microsoft licensing. 1(866) 230-0560 MSDN license are bind too to the physical site where you are inscripted, thus you better have an official answer
The way we handle it is our PowerShell startup scripts use NirSoft ProduKey to pull that information from the system, and upload the data to a file share. We were already using PowerShell startup scripts to manage a lot of our administrative tasks, so it was easy enough to add another step. Whenever I get questioned on licenses, I just grep the uploaded ...
Generic solution: I think the Microsoft-centric solution to this is to license using volume keys, and then simply use your KMS server to report on license activation status. Windows 7 and above-solution If volume licensing is not an option, and all of your clients are Windows 7 or newer, you could just query the SoftwareLicensingProduct WMI class on each ...
using NirSoft ProduKey: ProduKey.exe /remoteall look for other command line options are in readme.txt
We deployed OCS Inventory. Its free, awesome and provides all the info that you'd need. http://www.ocsinventory-ng.org/fr/
Top 50 recent answers are included