KMS Confusion

[Planehazza]

**Sorry, wrong forum!**

 

 

My manager and I are being tormented by our KMS setup not dishing out license.

We're running 2012R2 as KMS Host (same server as DC) with windows 10 LTSB 2016 clients.

 

When building the image, we have entered the client setup key, which according to here, is DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ. This is in and accepted. The KMS server is online and set up and we have keys installed. The host is registered and activated withthe "2012R2 Server/DataCenter CSVLK for Win10" key. We have all the updates in that we have read about.

When we try to activate a client, we get a message that the KMS server cannot be contacted. We can ping the IP, telnet via the 1688 port, and connection otherwise is fine. In VAMT, the devices show up when we discover them. Because they have the client setup key installed, they show up as GLVK with non genuine and status as 'notification'. If I try to activate the client from here, I just get the same error.

Upon looking in event viewer ID 12288 on the client, it appears we get a license mismatch error. Great, perhaps we don't have the KMS client key installed? Is this the right way to think of it? There should be a host KMS key, client setup key, and client key. Correct?

 

In which case, from where on the VLSC do we get the KMS keys that will activate Windows10 2016LTSB? We have three keys: two are 500 license MAK, and one for KMS. What is confusing me is that the product key title says Windows 10 LTSB 2016 KMS, with type KMS. Is this a client key, or when you use Windows 10 LTSB as the KMS host?!

 

Any ideas? We've been going at this for days and short of creating a new 2016 KMS server we're stuck for ideas.

 

Thanks!

Edited August 1, 2017 by Planehazza

[Steve21]

First would strongly advise you to remove that key if it's your own as you're just given it away to the public

 

Secondly did you patch your kms server? There's a specific patch to allow 2012r2 to activate win10

 

Steve

[Planehazza]

First would strongly advise you to remove that key if it's your own as you're just given it away to the public

 

Secondly did you patch your kms server? There's a specific patch to allow 2012r2 to activate win10

 

Steve

Woops, you're right. Removed the host key.

 

yes, it has had a load of updates and the update for 2012R2 to activate win10. Do you happen to have the KB number so I can double check?

[Steve21]

https://support.microsoft.com/en-us/help/3058168

 

Think thats the one we used, not sure if it's been updated since as it was just while testing.

 

Few other things to check, did you activate more than 5 yet? Else it wouldn't kick the kms server into action, also did you open the firewall ports on your 10 image for the kms server?

 

Steve

[Arthur]

it has had a load of updates and the update for 2012R2 to activate win10. Do you happen to have the KB number so I can double check?

To activate LTSB 2016 clients you need to install the KMS host key named 'Windows Srv 2016 DataCtr/Std KMS' from VLSC (on your server). If it's not there, request it from Microsoft.

 

As long as your Windows Server 2012 R2 server has the July 2016 Rollup Update (or newer) you will be able to activate the LTSB 2016 key.

Edited August 1, 2017 by Arthur

[Arthur]

not sure if it's been updated since as it was just while testing.

That update has been superseded many times already.

 

The latest rollup update for 2012 R2 is KB4025336.

[Planehazza]

https://support.microsoft.com/en-us/help/3058168

 

Think thats the one we used, not sure if it's been updated since as it was just while testing.

 

Few other things to check, did you activate more than 5 yet? Else it wouldn't kick the kms server into action, also did you open the firewall ports on your 10 image for the kms server?

 

Steve

 

Hi Steve,

 

Looks like my boss just cracked it. We'd tried everything, or so we thought. After registering it as 2012R2 for Win10, we tried registering it as 2016. Now, all of a sudden, all of the 30+ PCs are activating!

 

https://www.linkedin.com/pulse/windows-10-enterprise-2016-ltsb-activation-issues-ahmed-ateeq

 

 

EDIT: Ninja'd by Arthur. Yup, exactly as he said!

[Arcolite]

Just to add here, but we ditched KMS for our Win10 rollout and instead use Active Directory-based Activation.

The KMS key is stored in AD and machines activate as soon as they are joined to the domain.

 

Far far simpler.

 

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

Edited August 1, 2017 by Arcolite