Graeme Bray here with a quick article around KMS and Server 2016. KMS and Server 2016 you say? Shouldn’t I be using Active Directory Based Activation? Yes, you should, but in case you are not, let’s go over the pre-requisites to activate Windows Server 2016 via KMS.

You can use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys..

********* UPDATE (5/5/17)***************** The requirements have been updated below to remove and add a required update. There was a supersedence change that makes 3058168 superseded by the July 2016 Update Rollup. Additionally, there is often an error saying that the update is not applicable to your machine.

To fix this issue, you need to install the latest Servicing Stack Update (SSU) for 2012 or 2012 R2. Their KB’s and links are below: Windows Server 2012 R2 / KB3173424 Windows Server 2012 / KB3173426 ******************************************* First, lets review the pre-requisite updates that must be installed.

Hi Christopher. Thanks for the question!

While you are correct that you must have Volume Activation Tools installed to add the activation object for AD Based Activation, you do not need to leave the role installed on your server. You could utilize a Windows Server 2012 R2 machine in each forest, enable AD Based Activation, then remove the Volume Activation Tools role from the system. Rinse and repeat. In regards to your other question, you can use the same KMS key to activate systems in your own network. This includes multiple forests/domains. From the Volume License Service Center (VLSC): “The Key Management Service (KMS) is an activation service that allows organizations to activate systems within their own network, eliminating the need for individual computers to connect to Microsoft for product activation.” I hope that is helpful.

It may be more work up front, but there are no dependencies in ADBA on the _VLMCS entry in DNS, nor specific port requirements (1688). Hi Graeme, A bit offtopic but I am really struggling with KMS using to activate Windows 10 clients. At the moment, we use a Windows Server 2008R2 KMS host to activate Windows and Office editions in our VDI environment (floating desktops) However, we would like to upgrade our VDI environment to the latest Windows 10 edition so the KMS host should activate those instances.

I have downloaded and installed the update to allow Windows Server 2008R2 to activate Windows 10 KMS clients. Bakugan Battle Brawlers Defenders Of The Core Wii Iso Download. However, I keep getting error message: 0xC004F074 The edition I try to activate is Windows 10 Enterprise 2016 LTSB.

I have added the following KMS keys to our Windows Server 2008R2 KMS host; Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 Win Srv 2008 R2 Data Ctr/Itan KMS C Where the 2008 R2 always have been used for the Windows 7 clients. I have installed the key both via VAMT 3.1 and via SLMGR.VBS but no avail. Any idea what I am doing wrong or should we upgrade the KMS host to Windows Server 2012R2?

Erik – I would recommend that you enable AD Based Activation for your Windows 10 clients. You would then be able to leave your KMS host as is to service Windows 7, Windows Server 2008 R2, and Office 2010.

This is your KB in regards to your 0xC003F073 – This error means that there is a missing license key, or update. As far as the update for 2008 R2, you can install this: to allow Win10 to be activated by Server 2008 R2.

I strongly recommend using ADBA for your VDI infrastructure to simplify activations. I realized I didn’t read your post closely enough.

You are correct that Windows 10 Enterprise LTSB 2016 will not activate against a Windows Server 2008 R2 KMS host. You will either need to be on Windows Server 2012+ KMS host or utilize AD Based Activation. From this link (July 21, 2016 Update – KB3172614), it specifically calls out Windows Server 2016 and Windows 10 Enterprise LTSB 2016. “This update extends support of the Key Management Service (KMS) for Windows 8 and Windows Server 2012, in order to enable the activation of clients running Windows 10 Anniversary Update-based long-term servicing branch (LTSB) and Windows Server 2016 clients, when they become available.”. Graeme This is the same error I receive when I attempt to install a Windows Server 2016 key. I have found that to activate 2016 with KMS the KMS host needs to be on at least Windows Server 2012.

I suspect it is the same with Windows 10 2016 LTSB. Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid While this link show Windows Server 2008 R2 is not supported as a KMS Host for Windows Server 2016 or Windows 10 Enterprise 2016 LTSB edition My existing KMS host server running on Windows server 2008 R2 and existing environment clients are Windows7,8, 10, Windows server 2008R2, 2012R2, Office 2010, 2013. Please guide me so that I can able to execute in production environment. Can you please confirm? Hi Ravi, Please see my post reply to Marc above.

You are not able to activate Windows 10 2016 LTSB or Windows Server 2016 via 2008 R2. You should look to implement Active Directory Based Activation for your latest Operating Systems (see links in the main blog post).

This would be our recommendation moving forward. You can use ADBA for Office 2013+, Windows 8+, and Windows Server 2012+. If you are not able to do this, you will need to build a Windows Server 2012 R2 host to install the KMS key for Windows 10 2016 LTSB or Windows Server 2016.

Hi MorgenS, I have Windows Server 2012 R2 domain and forest level. 3 Domain controllers with Windows Server 2012 R2 on the board, with full updated (except.NET 4.6.) Two activation services: 1. VAT with ADBA on third DC in domain users/PC network. Installed KMS host keys (from corp.A EA) by date/time range: a) Windows Srv 2016 DataCtr/Std KMS for Windows 10 b) Windows 10 Enterprise 2016 LTSB KMS c) Windows 10 Enterprise 2016 KMS d) Office 2016 Suites and Apps KMS e) Windows Srv 2012R2 DataCtr/Std KMS key 2. VAT with KMS Host on second DC in standalone/non_domain users/PC network (filial) a) Windows Srv 2016 DataCtr/Std KMS for Windows 10 b) Windows 10 Enterprise 2016 LTSB KMS d) Office 2016 Suites and Apps KMS e) Windows Srv 2012R2 DataCtr/Std KMS key After install Windows Srv 2012R2 DataCtr/Std KMS key, kms clients changed errors from Error: 0xc004F074 (can’t find license) TO Error: 0xc004F038 (not enough counter). I don’t know what Microsoft doing with KEY algorithms, but for Windows 10 Enterprise 2016 LTSB used Windows Srv 2016 DataCtr/Std KMS key ONLY, in domain VAT ADBA & non_domain VAT KMS HOST. Office 2016 activated without problems.

KMS host is running Windows Server 2012 R2, full patched including all optional updates. KMS host is already succefully activating our Windows 10 clients. According to the updates mentioned in this thread: KB2969339 Not Applicable KB2975061 Not Applicable KB3012199 Not Applicable KB3021910 Installed 2015-05-31 KB3058168 Not Applicable When I try to add a key for Windows Server 2016 in VAMT (10.1.10586.0) I get the error “The specified product key is invalid, or is unsupported by this version of VAMT. An update to support additional products may be available online.”. Thanks for the great article.

I was just setting up an activation for Server 2016 and Windows 10 on our Server 2012 R2 KMS host. I’ve followed up on installing all prerequisites and added the GVLK keys on the clients, while installing the Windows Srv 2016 DataCtr/Std Windows 10 KMS host CSVLK key on the KMS host. However my activations were failing because of a key mismatch error 0xC004F042. Acapela Infovox 3 Crack.

I knew this was not true, because I had the Server 2016/Windows 10 keys installed on the KMS host in the VAMT. I also saw errors 0xC004F074 – No Key Management Service (KMS) could be contacted. – I knew this was not true, because I added older product keys, such as Windows 7, Server 2008 and Server 2012 to up the count and to check that the server was accessible. I found one comment on a forum that suggested to install the 2016 key on the 2012 server. (not only in the VAMT, but on the actual OS) by running the following: On the KMS Server 2012 R2 server: slmgr /ipk “add your Server 2016/Windows 10 CSLVK (KMS) key here” slmgr /ato I tried that and the Server 2016/Windows 10 clients started connecting and activating immediately. So essentially, you are installing a 2016 key on a 2012 server, which is why i assume this information is not that widely available.

I hope this helps anyone who is having similar issues. There is a caveat for ADBA; *all* computers in *all* domains in a forest must be able to communicate with the domain controllers for the forest root domain in order to be activated – other domain controllers do *not* activate clients on their own. If you have any domains separated from the forest root domain by firewalls, you must open the ‘standard’ IP ports for AD communications between that domain’s clients and the forest root DCs.

If you cannot do this for any reason, you have no choice but to implement KMS for those separated domains or use MAK keys. As we learned to our dismay.

I'm using KMSAuto Net 2016 v1.4.9 by Ratiborus. I have Microsoft Office Home and Student. = Products Status: Office 2010, Office 2013/2016 == Office 16, Office16HomeStudentR_Grace edition Product Description: Office 16, RETAIL(Grace) channel Partial Product Key: DJ3QD License Status: Out-of-Box (OOB) Grace Reason: 0x4004f00c When I try to activate it says, 'Forced GVLK Installation' 'Default key does not exist. You can try to enter the your own key' What key do I enter? P.S The Microsoft Office had come pre-installed with a licensed Windows 10 • • • • •.