VAMT - not working with windows 10 education

[tj2419]

I am using vamt to licence a few windows 10 education machines.

 

I have added the KMS key but when i try add the licence key to the machines they come up with an error stating "Product Key not Available"

 

I go to install product key, select "automatically select a KMS client Key, GVLK" and it shows the product key not available message. In the product keys section of vamt it lists education next to edition so not sure why it says it is not there.

 

Any ideas?

[r0cketbev]

Hi tj,

 

Try adding the MAK key and see if that will work for you.

 

RB

[tj2419]

Hi tj,

 

Try adding the MAK key and see if that will work for you.

 

RB

 

The MAK key works but I have 250 of them left and 400 workstations to activate

[DJ-1701]

You don't add the KMS key to the computer itself, you just add it to the VAMT. After a certain number of machine communicate with the KMS server they should activate.

 

Although I prefer to use Active Directory Based Activation.

 

https://docs.microsoft.com/en-us/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client

[r0cketbev]

email this address [email protected] with the following info

 

- Company name

- Agreement and/or license number and licensing program in this request.

-The last 5 characters of each key you wish to increase.

- Requestor name, phone and e-mail address

- Product (Windows 10 EDU MAK version)

- Number of activations requested

- Reason for request

- Required date

in about 5 - 7 days you will get your increase.

[ricki]

Try injecting windows 10 and office 365 Kms key into as Richard

[BKGarry]

What server version are you using, and what client version of Win 10 Education.

 

I did a test with the original version a while back and it was all ok, but after the Anniversary update, it required a different KMS key from MS Licensing. Once I got that, it all started working, but you do need to specify the server version (2012 r2 in my case) and then client version, like 1703 or whatever it is, I only think this occurred once, but it was a bit fun trying to get it working

[nicholab]

Have you need the key into AD? Also for me VAMT did not like re-imaged workstation with the same name I had to delete and rediscover.