What actually needs to be done is to uninstall the existing key prior to applying the new one. Contact your system administrato or try a different key.

That key can’t be used to activate Window son this PC-it can only be used to set up a key management service. … I would actually receive the following error: What I’ve noticed in the environment I was working in was that if I attempted to apply the new Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 product key onto the existing Windows Server 2012 R2 KMS server that already has a KMS key via the GUI: … then proceed by ensuring that you have completed the steps outlined in the following KB:Įrror 0xC004F015 when you try to activate Windows 10 Enterprise on a Windows Server 2012 R2 KMS host You can also click on error detail to find the exact error. If you are connected and continue to see the error, contact your system administrator. Please connect to your corporate network. Windows is unable to reach your company’s activation service. If you’re sure that you already have 25 desktops with unique CMIDs activating but activation on the Windows 10 desktop still throws the following error: I’ve recently been involved with deploying a new Windows 10 VMware Horizon View pool to pilot the new operating system with the latest Office 2016 suite and ran into KMS activation issues because the Windows Server 2012 R2 KMS server was not configured properly so I thought it would be a good idea to outline the steps here so I could reference this in the future.īegin by confirming that your Windows 10 desktop is indeed not activating by simply launching the Activation window on the desktop and attempt to activate.

Activate windows 2012