Found out there was a VLMSC DNS record for another DC that is not a KMS server. The pc had a record of this under the HKEY_User S-1-5-20 Software Microsoft Windows NT CurrentVersion SoftwareProtectionPlatform. Changed that to the actual KMS server and windows activated.
Hi This error code is a very generic output to a KMS client having problems activating. To view your output, run slmgr.vbs –ato When troubleshooting this problem, we checked the following details – if any were a problem, they would generate this error code:. DNS record not published at VLMCS.tcp.client.domain.
This must be an SRV record, which the KMS server will automatically register. If you have disabled this, you will need to use a GPO on the clients to point them to the correct KMS server to use. No network connectivity from the KMS client to the MS server on the KMS port (tcp/1688 by default). Install telnet on the client and run telnet KMS.Server.Name 1688 and make sure the screen goes blank. Not more than 4 hours time difference between KMS server and client. Check that your time zones are correct.
If using server core, run timedate.cpl. No major hardware changes to the KMS server. If the KMS server is a VM and you have added a number of new devices, CPUs, memory etc, or P2Ved you will need to reactivate your KMS license. The KMS service must have the keys to issue for the KMS client requesting a license. For example, if the KMS server is Windows Server 2008 and you are trying to activate Windows 7, you will need an update installed on the KMS server AND the correct KMS key for Windows 7. And the last one was the problem we hit: Our KMS server was Windows Server 2008 R2, just as the KMS clients.
We’d crossed the threshold of 5 servers. But they still would not activate. The problem was that there are different license “channels” for Windows Server.
They are described here: Our servers which were having problems activating were all Windows Server 2008 R2 Datacenter Edition, and we had a “B Channel” KMS license installed on the KMS server. We followed these steps on the KMS server to install the correct channel license:. slmgr -upk. slmgr -cpky. slmgr -ipk. slmgr -ato After doing the above, we ran slmgr -ato on the Windows Server 2008 R2 Datacenter Edition servers. Note that “Channel C” is able to active all lower level channels.
@Tatenda: Windows 8 Pro can be installed in one of 2 ways: Retail or Volume License. Retail means OEM or via a box you buy from a shop.
This is not compatible with KMS. You need to install Windows 8 Pro using Volume Licensing ISO file you download from your Volume Licensing website subscription. This will come with a well-know key in to instructing it to look for a KMS server.
You can see these keys here: You can also use your MAK keys from your VL website subscription to active these. The only supported way to go from a Retail version to a VL version is to reinstall Windows. @Stilfari – Blog comments aren’t the forum for troubleshooting production issues.
You should contact your TAM or SDM representing your Premier Support contract for assistance, or log a request for support here: To get you started however, I think the commands in the blog should re-activate your KMS key. If you tried them without success, then just build a new KMS computer and activate that. A single KMS key should be able to be activated not more than 5 times. KMS servers don’t retain any permanent 'state' for activations.
We use Windows 7 exclusively for our end users and some time ago I updated our Server 2008 R2 to support Windows 8 and Windows 8.1 with the patches to support KMS activation from a request from our software developers. I ran into this error and double-checked everything and still a “no go” with this error. After some pain and suffering I installed KMS on our new Server 2012 R2 system that is going to replace the Server 2008 R2 system and everything just works.
I sure wish the developers at Microsoft would share more insights into EVERY error code KMS throws as it is nearly impossible to troubleshoot and error where the client says it cannot contact the KMS server, but the KMS server shows it is receiving a request and not activating.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |