Problem : Event ID 12293: Publishing the Key Management Service (KMS) to DNS in the ‘domain_name’ domain failed.
I am receiving the above-mentioned error in the event log of my new Exchange 2007 server. I have reviewed several documents on the internet in regards to the message, but not sure if it is even necessary for my Exchange Server to have this service trying to publish to DNS. I am not very familiar with KMS, but does this mean that my Exchange server is acting as a KMS Host, and if so, is that something I would want it to do? I’ve contemplated turning this service off, but am a bit concerned about possible ramifications.
Solution : Event ID 12293: Publishing the Key Management Service (KMS) to DNS in the ‘domain_name’ domain failed.
KMS doesn’t have to be a DC. If you’re on Windows 7 or Windows Server 2008 R2 you should be able to go to the command prompt (run as admin) and type slmgr -cdns to stop them from publishing in DNS. Not sure, but the latest KMS update might enable that in 2008 R1 and below too.. check slmgr /? from the command prompt and see which options you get. It’s good that you only have one showing as _VLMCS as your KMS clients should auto-discover it when trying to activate machines.
If you don’t have the option to stop publishing in DNS check this article:
http://social.technet.micr
You have to manually go into the registry and disable it and luckily (since you only have the correct one publishing) you wont have to go manually clean out the VLMCS entries.
As far as switching over the Exchange Server (and other Servers) to be KMS clients opposed to hosts you have two options:
1. Download the Windows 7 AIK and use the VAMT 1.2 Tool and set the servers to be KMS Clients. It’s got a real nice GUI interface and makes it realllly easy to manage your KMS and MAK machines or
2. Manually install the KMS ‘Client Setup Keys’ on each server and activate them against your KMS Host.
The WAIK is a huge download but probably the best method, imo.
Basically, and you probably already know this, but cant hurt to pass it on, you get a KMS Host key from Microsoft (usually KMS A, B or C) and then there are ‘dummy’ keys (Client Setup Keys) that you use on the clients. I’ve found with R2 and W7 that you don’t even need to use these keys. Just going to the command prompt after an install and typing slmgr -ato (or just use VAMT 1.2) should automatically activate the machines… Assuming you’ve met the thresholds (5 Windows Servers or 25 Windows Vista/7). If you already have a bunch of Vista or 7 machines using MAK keys it’s super easy to use that VAMT tool to convert them to KMS to meet the threshold quick. You basically install the setup keys on 25 machines, let them all fail and when you hit 26 go back and activate all of them and you’re good to go with your KMS.
