Thanks Michael that is exactly what we were after and answers my question.

We can also see the Windows Server 2016 KMS key so will look to update our KMS 
with that key!

Cheers
Damon

From: [email protected] [mailto:[email protected]] On 
Behalf Of Michael Niehaus
Sent: Thursday, 6 October 2016 11:59 AM
To: [email protected]
Subject: [mssms] RE: Windows 10 2016 LTSB KMS Key Query OT

The new Windows Server 2016 KMS key, which can be installed on Windows Server 
2012 and above as long as they have the right hotfixes, will activate Windows 
Server 2016, Windows 10 Enterprise LTSB 2016, and all older operating systems.

If you grabbed a Windows Server 2012 R2 key, then that won't work to activate 
Windows Server 2016 or Windows 10 Enterprise LTSB 2016, but will activate 
earlier versions.

To add support for Windows Server 2016 and Windows 10 Enterprise LTSB 2016 to 
Windows Server 2012 or Windows Server 2012 R2 KMS servers:


*         First install KB 3058168 (Activate Windows 10 from WS 2012/2012 R2 
KMS Hosts).

*         For Windows Server 2012, then install KB 3172615.  For Windows Server 
2012 R2, then install KB 3172614.

Note that there will be no hotfix available for Windows Server 2008 R2 - that 
release is in extended support, so no new functionality is being added (e.g. 
activation of new OSes).

Thanks,
-Michael

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Johns, Damon (DoJ)
Sent: Wednesday, October 5, 2016 4:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Re: Windows 10 2016 LTSB KMS Key Query OT

Hi Everyone, apologies this is a little off topic.

I'm having some problems finding clarification around KMS activation of Windows 
10 2016 LTSB.

We would like to deploy a mixture of Windows 10 Enterprise CB / CBB and Windows 
10 LTSB for our business critical PC's.

At the moment we have a 2012 R2 Server which is using a Windows Srv 2012R2 
DataCtr/Std KMS for Windows 10 key (I updated this to latest one available in 
VLSC yesterday). This is activating Windows 10 1607 and down as well as all of 
our server OS and Windows 7 PC's. It is not however activating our Windows 10 
2016 LTSB test PC's.

We have installed KB3172614 on our KMS server.

The advice to date that I have indicates that we need to use a new KMS key to 
active Windows 10 2016 LTSB. I can see that we have a KMS key for that in VLSC.

My Question.

Do we need to stand up a new additional KMS server with that specific Windows 
10 2016 LTSB KMS key to activate that edition or should we update the KMS on 
the existing server to use the new LTSB one? If we do this, will it stop 
activating Windows 10 1607, 1511, Windows 7, Server OS's etc?

I've found it difficult to find anything beyond "You need to add a new KMS key 
to activate Windows 10 2016 LTSB" statements.

Cheers
Damon

________________________________

CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.



________________________________

CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.



Reply via email to