Having a problem with our KMS server as follows: I installed a KMS server without realizing that a former colleague had also installed a KMS server but on a different server. I uninstalled the original KMS server however the DNS record for that original server keeps recreating itself. I do in and delete the record from the _TCP folder and then done an AD replicate from that server, then by the next day it has recreated itself. I have tried running the uninstall command again on the server but this has done nothing. The new server has a DNS record but each time the old one is recreated it seems to take precedence over the new one so when i try to license a server it doesnt work until i delete the old DNS record. Will be going to Windows 7 soon and don't want any problems with licensing. What im i missing? Is this the old KMS server that is the problem or is it something to do with DNS? Thanks

This link seem to have everything documented http://www.networksteve.com/forum/topic.php/Remove_KMS_Host/?TopicId=10515&Posts=0 slmgr -upk Delete the record from the DNS: Open DNS console: Expand _tcp node under the domain.com. There will be a record _VLMCS. Delete this record. when you done then run following command nslookup -type=all _vlmcs._tcp

Hi, KMS is DNS resolve based, so configuring DNS for KMS host is vital. The procedures to configure DNS, there is a link for your reference: Title: Configuring DNS URL: http://technet.microsoft.com/en-us/library/ff793405.aspx After adding the SRV record, you need to make sure that the Office and Windows could be discoverd: Title: How to discover Office and Windows KMS hosts via DNS and remove unauthorized instances URL: http://blogs.technet.com/b/odsupport/archive/2011/11/14/how-to-discover-kms-hosts-via-a-dns-query-and-remove-them-if-need-be.aspx Regards, JamesJames Xiong TechNet Community Support

Thanks for the replies. I have done what you suggest as following: slmgr -upk Delete the record from the DNS: Open DNS console: Expand _tcp node under the domain.com. There will be a record _VLMCS. Delete this record. when you done then run following command nslookup -type=all _vlmcs._tcp And the above command comes back with the new server. However if i leave it for a few days and go back into DNS Console the _VLMCS record for the old server is recreated again. If i go to the old server and run the command: slmgr.vbs /dli It says it is a client of the new server so why is the DNS record recreating itself?

on the "old" server, check the event logs, there should be events showing the DNS publishing occurring. you said you did slmgr -upk did you then do slmgr -ipk AAAAA-BBBBB-CCCCC-DDDDD-EEEEE (the KMSclient pkey)? and then slmgr /ato ?Don (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

on the old server in the event log i can see event ID 12294 which is running everyday at the same time. It ran today at 13:40 and the DNS record was recreated. I have ran the commands in the order you have stated and deleted the DNS record. Will check the event log again tomorrow to see it that has fixed it. Thanks

Hello, Have you rebooted the machine? Since we have some of the activation in a cache, the machine may need to be rebooted after the product key is changed. You should not ever need to use slmgr /UPK, this is not a good thing to do, your machine is now totally unlicensed and in an unknown state. Bad things can happen.Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Right so i rebooted the old KMS server and it has published the record back in DNS again. If i check the Event log there is the 12294 evenet ID just after the server is rebooted. Why is it still doing this and how can i stop it.

on the old KMS server, when you executed slmgr.vbs -ipk <generic KMS client pkey here> did it return a success result/message? You can check the current status by executing slmgr.vbs /dli The relevant list of GVLK's (KMSclient pkeys) are here: http://technet.microsoft.com/en-us/library/jj612867 Choose the matching GVLK for the OS of the old KMS install the GVLK using the command slmgr.vbs -ipk activate it to your new KMS using the command slmgr.vbs /ato check the result using slmgr.vbs /dli tell us what happensDon (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

on the old KMS server, when you executed slmgr.vbs -ipk <generic KMS client pkey here> did it return a success result/message? You can check the current status by executing slmgr.vbs /dli The relevant list of GVLK's (KMSclient pkeys) are here: http://technet.microsoft.com/en-us/library/jj612867 Choose the matching GVLK for the OS of the old KMS install the GVLK using the command slmgr.vbs -ipk activate it to your new KMS using the command slmgr.vbs /ato check the result using slmgr.vbs /dli tell us what happensDon (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Ok thats what i have done. The slmgr.vbs -ipk <generic KMS client pkey here> taken from the web site does return a success message This is the result of the slmgr.vbs /dli DNS i have blanked out is going to the new KMS server  So it looks like it is now just a clinet of the new KMS server but it seems like it is still publishing the DNS record for some reason.

that's looking fine. reboot this old guy (or if R2 just execute: net stop sppsvc && net start sppsvc) zap that DNS record for this old guy reboot this old guy again (or if R2 just execute: net stop sppsvc && net start sppsvc) check the DNS record - it should *not* come back, there should not be event 12294 in this old guy's log Don (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Hi Don, I have followed what you said to the letter. After second reboot the server puts the DNS record back and there is the event 12284 in the log?

arg. what a tricky bugger. 12294 = successfully published into DNS... i can't imagine this *should* work on a KMSclient, but give it a try (force do-not-publish-into-DNS=true) slmgr.vbs /cdns http://technet.microsoft.com/en-us/library/ff793409.aspx http://technet.microsoft.com/en-us/library/cc303695.aspxDon (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

arg. what a tricky bugger. 12294 = successfully published into DNS... i can't imagine this *should* work on a KMSclient, but give it a try (force do-not-publish-into-DNS=true) slmgr.vbs /cdns http://technet.microsoft.com/en-us/library/ff793409.aspx http://technet.microsoft.com/en-us/library/cc303695.aspxDon (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

I think that has fixed it. I have rebooted it and it has created the DNS record. Will check it again tomorrow to make sure, and let you know if it is fixed.

I think that has fixed it. I have rebooted it and it has created the DNS record. Will check it again tomorrow to make sure, and let you know if it is fixed. *not* created the DNS record?? (said with a hopeful/pleading tone of voice :)Don (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Yes sorry not

Ok i have checked again this afternoon and no more DNS record and nothing in the vent log on that old server. Looks like that has solved the problem. Thanks for the help.