Don't freak out.you now need to re-activate just the KMS host by typing slcmgr.vbs /ato.

The KMS server will then show as 'This copy of Windows is not Genuine' in the desktop and the activation section of the System properties. See here for more details: KB 3086418 Servers can ONLY have a Server license key installed, so you have to use the proper 'Windows Srv 2012R2 DataCtr/Std KMS for Windows 10' license key from the MVLS site. NOTE: If you use the Windows 10 KMS key instead of the one above you will get an error 0xC004F015 during activation. I would recommend taking a screenshot for historical reference.Īctivate the new license on the KMS server by typing slcmgr.vbs /ipk (be patient, it will return a command prompt immediately and then about 10 seconds later show a window pop-up stating the license was installed successfully) On the existing KMS host, run slcmgr.vbs /dlv to get the current detailed KMS license summary.

The correct key is labeled 'Windows Srv 2012R2 DataCtr/Std KMS for Windows 10' in your 'Product Keys' tab of your Relationship Summary page. Retrieve the correct KMS key from the Microsoft VLSC site.On the 2008 R2 KMS host, a hotfix is required: KB 3079821.The rest of the steps should apply to you at that point. NOTE: if you are using a 2012 R2 KMS host, you can skip to step #2. Please be aware these aren't steps to get a KMS host running from scratch, some of those steps are outlined in the TechNet article here: Activate using Key Management Service but be aware that deploying a KMS host server shouldn't be something just thrown into an environment without proper planning. In order to activate Windows 10 clients on a KMS host running Windows Server 2008 R2 you can follow the steps below.

Windows kms key client