1st October ... Where's LTSB2016??

[Arthur]

I will want to activate server 2016 at some point so I've got the server 2016 key installed which activates the LTSB 2016 also.

I was sent the same "Windows Srv 2016 DataCtr/Std KMS" key from MS. Does it also activate all Windows client OSs inc. 7, 8.x and 10 (non-LTSB editions)?

 

When I installed the new key it deactivated the combined 2012 R2 + W10 key so I guess it might?

[AndiMarv]

I was sent the same "Windows Srv 2016 DataCtr/Std KMS" key from MS. Does it also activate all Windows client OSs inc. 7, 8.x and 10 (non-LTSB editions)?

 

When I installed the new key it deactivated the combined 2012 R2 + W10 key so I guess it might?

 

Yes, that has been my experience. My previous 2012 R2 with windows 10 key was replaced with this one and my Win 7/8/10 clients are all licensed with that.

[timbo343]

Am i right in thinking i have the wrong Windows 10 LTSB2016 KMS keys here (attached)

[Arthur]

Am I right in thinking I have the wrong Windows 10 LTSB 2016 KMS keys here

You would only need to install and activate the WS2016 key you highlighted since this will also activate LTSB 2016.

[timbo343]

You would only need to install and activate the WS2016 key you highlighted since this will also activate LTSB 2016.

 

I didnt know if i was missing a Windows Server 2016 Data Center / Standard for Windows 10 like i have a Windows Server 2012R2 Data Center / Standard for Windows 10

[Arthur]

I didnt know if I was missing a Windows Server 2016 Data Center / Standard for Windows 10

I assumed the key would be called that too, but it appears not.

[CHiLL]

I already have two Windows 10 2015 LTSB (1511) clients installed and activated using VAMT 3.1 and Active Directory-based Activation, though it appears the same keys do not work for Windows 10 2016 LTSB (1607).

 

Am i right in thinking i have the wrong Windows 10 LTSB2016 KMS keys here (attached)

I have those two keys installed using VAMT 3.1, to AD activation using the newly added Windows 10 2016 LTSB KMS Host key, I receive the following error:

VAMT encountered an unknown error:
System.Runtime.InteropServices.COMException (0xC004F050)
at
Microsoft.Licensing.VolumeActivation.ActiveDirectoryWorker.RunWorkerSync()
at
Microsoft.Licensing.VolumeActivation.Presentation.ADForestsFormView.OnlineActivateForestThreadProc(Object job)

Researching that error states that the product key is invalid, despite the VLSC support team telling me it is the correct key on numerous occasions. I also receive the exact same error whilst attempting to activate the Server 2016 KMS Host key using ADirectory Activation. The keys are copied, pasted and triple checked from our VLSC agreement.

 

The last time I encountered this issue, I think was when trying to install the key for Office 2016, where I needed to install the Office 2016 Volume License Pack, though it appears nothing like that exists for Windows 10/Server 2016.

 

I'm kind of stuck at the moment.

Edited October 12, 2016 by CHiLL

[CHiLL]

I've managed to get Windows 10 2016 LTSB and Server 2016 KMS Host keys activated using Active Directory-based Authentication within VAMT 3.1. Now my Windows 10 2016 LTSB has successfully activated!

 

After some research, I stumbled across this Technet thread: https://social.technet.microsoft.com/Forums/en-US/6b05ee31-e6b5-4658-86d1-3015d4ecf79e/mastering-windows-10-enterprise-2016-ltsb-workgroup-kms-activation-issue?forum=win10itprosetup

 

The important item that I found from that article was the fact that KB3172614 was required on the Server 2012 R2 KMS server. It can be downloaded here: https://support.microsoft.com/en-gb/kb/3172614. Once I installed that (requires a server reboot), I was then able to successfully add my Windows 10 2016 LTSB and Server 2016 KMS Host keys into Active Directory-based Authentication.

 

The KMS Host Keys I installed (obtained from our VLSC) are named:

• Windows 10 Enterprise 2016 LTSB KMS
  
• Windows Srv 2016 DataCtr/Std KMS
  

 

The following KMS Host key is required also, though most will already have it installed for previous Windows 10 KMS activations:

• Windows Srv 2012R2 DataCtr/Std KMS for Windows 10
  

Edited October 12, 2016 by CHiLL

[Simcfc73]

I'm getting invalid keys error - please update VAMT

 

I'll add it to the list of stuff wrong with my W10 install decision

[CHiLL]

I'm getting invalid keys error - please update VAMT

 

I'll add it to the list of stuff wrong with my W10 install decision

What version of VAMT are you using?

[Simcfc73]

Volume Activation Management Tool

Microsoft Corporation

Version: 10.0.10240.0

[CHiLL]

Volume Activation Management Tool

Microsoft Corporation

Version: 10.0.10240.0

I'm using VAMT 3.1, which has this version number:

 

Volume Activation Management Tool

Microsoft Corporation

10.1.14393.0

 

I would suggest that you do indeed need to upgrade to the latest version of VAMT.

Edited October 12, 2016 by CHiLL

[Simcfc73]

Brilliant, W10 Aniversary works fine but LTSB needs me to update.... I'll just check the microsoft update site as it must be straightforward... oh wait.

[Simcfc73]

Anyone noticed this on their network.

 

When I installed W10 Edu the network icon was fine when I started the PC up. When I startup LTSB its got a cross on it saying no internet access. Port 80 is blocked so LTSB is chatting to the internet when it boots up whereas Edu doesnt have to. if I open 80 its ok. They boot up and work fine.. just a bit weird.

[timbo343]

Anyone noticed this on their network.

 

When I installed W10 Edu the network icon was fine when I started the PC up. When I startup LTSB its got a cross on it saying no internet access. Port 80 is blocked so LTSB is chatting to the internet when it boots up whereas Edu doesnt have to. if I open 80 its ok. They boot up and work fine.. just a bit weird.

 

Our LTSB2015 has the little yellow warning triangle over it at the CTRL ALT DEL screen but we dont push out the default gateway via DHCP, we only use Proxy so there's no need for the default gateway.

 

Once the machine logs onto the network, the yellow warning triangle disappears.