0

We have a very small virtual environment with only two Server 2012 VMs. We just purchased a license (local government entity) for Windows Server 2016 in order to add another VM to our stack. I'm having trouble activating the new VM. We are not using a KMS because that seems like a lot of extra work for such a small group. But when I attempt to activate the new 2016 server with the MAK key provided from microsoft.com/licensing, it says the system must connect to a local licensing service. Then it fails with 0xc004e028 error: "We can't activate Windows on this device right now. You can try activating again later or go to the store to buy genuine Windows."

What is the correct procedure to activate Windows Server 2016 using a MAK key and Microsoft's activation servers (not local), avoiding the need for local KMS infrastructure?

Thanks

  • Make sure your DNS is set correctly. Try rebooting a few times. That error message just means it can't connect to the activation servers in general. Also, are you certain the key is legit? – IAmTheSquidward Nov 29 '18 at 17:17
  • Yes the key is legit: direct from our account on www.microsoft.com/licensing. The DNS is set up correctly also, but I have a feeling it's still trying to access a local KMS instead of reaching out to MS's public activation servers... anything I can do about that? – Ryan Griggs Nov 29 '18 at 17:50
  • The MAK key just uses the KMS at MS. See my answer below. – IAmTheSquidward Nov 29 '18 at 17:52
  • Just as note: KMS setup took me 15 minutes, so "a lot of work" is REALLY relative. Also you should run DataCenter edition and use pass through activation to avoid all the trouble - if you can set up KMS; you have the proper keys. And those should be stored in active directory. – TomTom Nov 29 '18 at 18:04
2

Error 0xc004e028 is, according to Microsoft:

You might see this error if you try to activate a device that is already in the process of activation. Your device should be activated after the first request is completed.

Sounds to me like your server is just pending activation. I'd give it an hour or so, reboot, and if it's not activated, try again.

  • You're right - it worked after I rebooted and re-ran SLUI 3, then entered the MAK key. – Ryan Griggs Nov 29 '18 at 18:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.