/build/static/layout/Breadcrumb_cap_w.png

KMS Licensing - super easy question

So MAK keys Im fine with, but with KMS…??

KMS Servers with the clients getting activations.

The key that client uses, is it a unique key to the company? Or can you use a GVLK key for the software?

I know the KMS host server needs a MS provided VLK key, it the client software key I’m interest in.


See link below for example, I would refer to technet, but they don’t have a nice list of GVLK keys.
http://www.win7vista.com/index.php/topic/9013-gvlk-keys-windows-782008r22012-and-office-20102013/ 

 

Anyway when you deploy Windows 7, Office or whatever, do you package it up with a unique KMS key for that site, or do you use a GVLK and the KMS server does the rest?

I’ve only dealt with MAK keys, never had work with a KMS server yet.

 

Cheers for your thoughts.

 


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: SMal.tmcc 11 years ago
Red Belt
2

there is a server key you get from MS and a general client key you put in the ans file to look for the KMS server.

see for a list of keys to use in your ans files

http://www.itninja.com/link/kms-kms-keys-for-windows-8-1-windows-server-2012-r2-windows-8-windows-server-2012-windows-7-windows-server-2008-r2-windows-vista-and-windows-server-2008


Comments:
  • Cheers, I thought that was correct but google was unable to confirm (: - rileyz 11 years ago
    • It is allusive to find the KMS key list URL, that is why I posted it on ITNinja - SMal.tmcc 11 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ