Windows 10 Enterprise LTSB 2016 KMS nightmare!

[mulderite]

Apologies if I'm posting this in the wrong forum, but I'm at my wits end and figured the Windows 10 forum would get the most hits...

 

Here are our current KMS keys available to us as part of our Licence Agreement:

 

 

We are currently using the yellow highlighted key on our KMS host since the Summer and it has been successfully activating hundreds of Windows 7 workstations and the few Windows Enterprise LTSB 2015 test workstations we've configured so far. Last week I thought I'd download and start testing with the Windows 10 Enterprise LTSB 2016 version instead, and saw that it wasn't activating with our current KMS key. A quick search and I discovered that 2016 requires a new KMS key.

 

No problem, I'll call Microsoft support and request a new key. Well, after what seems like numerous calls which have either been disconnected at their end, disconnected at MY end (after slamming the phone down because I ended up speaking with someone who, to put it nicely, must speak English as a second language AND trying to understand them over an incredibly poor line) I finally managed to get across the fact that I required a new KMS key for activating LTSB 2016.

 

This morning I logged into the VLSC to review our KMS keys and saw we now have a new KMS key listed for 2016 (circled in red).

 

My issue is I'm not sure how to proceed. My limited understanding of KMS is that I can only have one key active at a time, so how am I supposed to use the newly acquired KMS key they have provided me? Surely they should be updating our Windows Srv2012R2 DataCtr/Std KMS for Windows 10 key?

 

I don't think I can bear another call to Microsoft support - only to have them forward me to their website and be immediately prompted to enter my credit card details.

 

Can someone point me in the right direction?

 

Warm thanks in advance..

[FN-GM]

I have found the people at this address are very helpful - [email protected]

 

The KMS key for Server 2016 will activate both LTSB 2015 & 2016 so could that be an option?

 

Thanks

[mulderite]

We have a Server 2012 R2 server acting as our KMS host, and as our Server 2016 key (as shown in the screenshot) doesn't specifically state it includes Windows 10 like the other KMS key does, I wasn't sure if I could/should be using that one?

 

Is that all I need to do then is just register the Server 2016 key on our host, thus replacing the old one?

[localzuk]

The recommended way for Windows 10 activation to be completed now is "Active Directory activation" - https://technet.microsoft.com/en-gb/itpro/windows/deploy/activate-using-active-directory-based-activation-client

[mulderite]

Unfortunately we also use the Windows 10 LTSB installation on staff laptops (which are configured to be in a workgroup) so I prefer not to use that method.

[localzuk]

Configured in a Workgroup?! Why?!

[mulderite]

The laptops are not configured to be part of the domain but are configured to use KMS, that's just the way its set up here.

[SHimmer45]

I have a server 2012R2 & Windows 10 KMS key installed on my 2008 KMS server and it activates for our domain laptops& computers ok.

 

for workgroup stuff you might need to manually set the KMS host and port using SLMGR.VBS on the laptop if it doesnt pick up the service location from DNS.

[mulderite]

Hi Shimmer45

 

Just to clarify, so you are actually activating TWO separate keys on your host?

[SHimmer45]

No i have one KMS host key installed which at the time is / was Server2012R2&windows 10.

this is a class B key iirc which means it will activate 2012R2 Windows 10 and versions of windows below that to a point.

 

the Windows 10 LTSB KMS key will only activate Windows 10 clients (possibly only LTSB without looking at the specifics of that key) and ones below it like 8.1 8 7

which is how KMS always used to work and in my experience is still the case

MS published a document which explains what the different KMS key types activate (at the time THIS was what i referred to )

[mulderite]

Hi SHimmer54,

 

To clarify, we already have workstations/laptops activating correctly (both on domain and in workgroups). My issue is I'm unable to activate Windows 10 LTSB 2016 with my current KMS setup. I have asked Microsoft for an updated key to allow me to do this but I've only been given a specific Windows 10 LTSB 2016 key, when I was expecting them to give me an updated Server2012R2&Win10 key..

[SHimmer45]

i would have assumed the 2012r2 for windows 10 would have done the trick regardless of LTSB version date unless they are mucking about with it, apologies if i came across as telling you to suck eggs

[ttorment]

Were you ever able to get this resolved? We've been back & forth with Microsoft on this for days now, and my understanding is that the only way to activate Windows 10 Enterprise LTSB 2016 is with a Server 2016 KMS host key. Allegedly the Server 2016 KMS host key will still work/install properly on a Server 2012 R2 KMS host, but we're not licensed for Server 2016, so we're likely going to have to purchase Server 2016 just to get the stupid KMS host key.

 

Absolutely ridiculous from Microsoft, why they couldn't just update again to allow the Windows Srv 2012 Std for Windows 10 KMS host key to work, I've no idea. Here's the blog post that (mostly) confirms it, although I've yet to find anyone directly employed by Microsoft who will flat out say that you *must* have Server 2016 to activate Windows 10 Enterprise LTSB 2016.

 

https://blogs.technet.microsoft.com/askcore/2016/10/19/windows-server-2016-volume-activation-tips/

[whartomt01]

Did anyone get any further with LTSB KMS activation from Windows Server 2012R2

 

How has anyone done it? With a Windows 10 VM on a server. Or new server on 2016.

 

Or any other suggestions.

[JRowley]

I've never done it but, this guide should do the trick - https://www.windowsmanagementexperts.com/windows-10-2016-ltsb-server-2016-kms-activation/windows-10-2016-ltsb-server-2016-kms-activation.htm

 

You'll also need the 'Windows Srv 2012R2 DataCtr/Std KMS for Windows 10' KMS key from VLSC.

Edited February 8, 2017 by JRowley

[ttorment]

So apparently the only ways to activate Windows 10 Enterprise LTSB 2016 is to use a Server 2016 KMS host key, or to use Active Directory activation (not KMS). After weeks of whining and complaining, we finally got Microsoft to give us a Server 2016 KMS host key so that we could activate ours, since AD activation wasn't an option, and we don't (currently) have Server 2016 available due to our SA being expired at the moment.

[AlexB]

Thanks for all this. I ran into the same issue. VOLUME_KMS_2012-R2_WIN10 working for Windows 10, but not Windows 10 LTSB 2016. I'm covered for Server 2016 and tried adding the Server 2016 DC KMS key (VOLUME_KMS_WS16) to my Server 2012 R2 Standard (something I didn't know you could do) and it has worked great.

[KK20]

The "windows 10 2016 LTSB KMS key" is for "active directory" activation only. If you want to activate using KMS server classic then you will need "Server 2016" activation key. I know because I went through these hoops. You can run active directory and classic on the same server at the same time.

 

Server 2012R2 key for Windows 10 is only good for 2015 LTSB.

 

I emailed the VL team with my agreement and simply asked for a server 2016 KM adding to our agreement. It was done within 1 hour. When I needed the office 2016 KMS key I telephoned and got one added to the agreement there and then on the phone. It was painless.

 

Classic KMS activates using the "highest key possible" and will activate ALL other versions underneath it. The actual licensing count in this scenario is a paperwork exercise (afterall, you could have a couple of 2012R2 on KMS, server 2008R2, Windows 10 LTSB and Windows 10 1607 all running KMS client - the server 2016 host key activates them all)

Edited December 1, 2017 by KK20