windows server 2008 r2 activation 0xc004f074

So then I refer back to the application event log, hoping against hope that the “additional information” wasn’t some weird circular reference. Double-check that MS KB2885698 is installed to add support for newer operating systems on a Windows 2008 R2 KMS hostĪt first blush, everything appeared to be fine.Ensure that the proper KMS key and channel (VOLUME_KMS_2012-R2 channel) shows up in the KMS server’s licensing (slmgr /dlv all).Ensure the Software Protection Service (sppsvc) is in fact running on the KMS server.Ensure the domain _VLMCS DNS records are correct.Then, I started to dive into the rabbit-hole that is KMS troubleshooting: The first thing I do, naturally, was just to make sure my KMS server was in fact reachable from this machine. Please see the Application Event Log for additional information. No Key Management Service (KMS) could be contacted. The Software Protection Service reported that the computer could not be activated. I logged into one of the machines that was reporting activation errors and ran the trusty activation command: slmgr /ato Their two most recently deployed servers were reporting activation errors. In December, he reported that his newest servers weren’t activating properly. Because no one complained in June, I had assumed that someone had activated the proper key on the KMS server to support the new version. The KMS server had previously been patched to support Server 20 R2 KMS clients. In June of last year, they started deploying Windows Server 2012 R2 servers. One of our clients has an environment running KMS on Windows Server 2008 R2. Given that we still manage some Windows 2003 servers (if we must), I think it’s fair to assume we’ll still be using KMS well into the next decade. It is of course on the way out, to be replaced by Active Directory-based Activation in Server 2012, but KMS will stick around until all of our Server 2008 R2 machines are out of production.

Windows server 2008 r2 activation 0xc004f074