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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |