my setup process server 2008 ent which has AD, DHCP and DNS clients windows 7 sysprep by altiris with generalization for windows 7 prof ran the command on host cscript c:\windows\system32\slmgr.vbs /ipk server 2008 R2 Std/Ent KMS B product key then cscript c:\windows\system32\slmgr.vbs /ato it activated and put the _VLMCS record under the _tcp which is under my domain.local with the srv information the server has a record in the forward and reverse lookup zones I can manually set client to host with command of slmgr.vbs -skms server01.instfo.local:1688 then command slmgr.vbs /ato which sends a request to the host these work as of right now and i have 25 requests to the host but the clients are not activating yet. The only error in the event under application is the publishing the kms to dns domain failed I will look at the tech tips for fix right now

forgot this info host command slmgr.vbs /dlv shows 103 failed reqeusts

when i run the command net stop sppsvc && net start sppsvc i get the system error 1060 has occurred the specified servcie does not exist as an installed servcie

when i run the command net stop sppsvc && net start sppsvc i get the system error 1060 has occurred the specified servcie does not exist as an installed servcie Go to folder C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft Right click SoftwareProtectionPlatform folder, in the security tab, add user NT Service\sppsvc (if it doesn't exist) and provide full control. See if it helps. Please note, AppData is a hidden folder !Vote As Helpful, if you find my information useful ! This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

i get all the way to microsoft folder but do not see the SoftwareProtectionPlatform folder. have internet explorer, softwarelicensing, systemcertificates and windows

Make sure following folder permissions are set. Post which, you should be able to view SoftwareProtectionPlatform folder in C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft Vote As Helpful, if you find my information useful ! This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

yes that is correct but i show in my server 2008 Softwarelicensing not SoftwareProtectionPlatform

yes that is correct but i show in my server 2008 Softwarelicensing not SoftwareProtectionPlatform Ah Yes, for 2008 that would be Softwarelicensing folder. Well, try this.. Right click SoftwareLicensing folder, in the security add user NT Service\slsvc (if it doesn't exist) and provide full control. Vote As Helpful, if you find my information useful ! This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

OK It is done, ran the net stop sppsvc && net start sppsvc same problem: system error 1060 has occurred "the specified servcie does not exist as an installed service" should there be a software install for this? should this show up in services? Is this related to my event error in application stating publishing the KMS to DNS domain failed?

In case of 2008, you should run net stop slsvc && net start slsvc ~ Knowledge Seeker

As suggested by K Seeker, try net stop slsvc && net start slsvcVote As Helpful, if you find my information useful ! This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

ok that worked now clients are requesting but failing. firewall is off on domain host and domain client so i don't think i need to worry about host to client communication Have 25 clients connecting to the host but are failing activation. Is this related to my event error in application stating publishing the KMS to DNS domain failed? Should i remove my dns record and re add it?

Please see if following thread helps... Event ID 12293 - Windows 2008 http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/c00cf870-47bb-4d2a-aea9-2b92d694f4f9/Vote As Helpful, if you find my information useful ! This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

kms host has event error in application publishing the KMS to DNS domain failed. clients do not automaticly resolve dns and activate license i can run the command slmgr.vbs -skms server01.instfo.local:1688 and it connects the client and host manually but don't want to do that for hundreds of windows 7 computers

can you run cscript slmgr.vbs /dli on your host and one client and post the output here? (to confirm the KMS has correctly accepted and activated its own KMS prodkey) also, 12293 events should show additional info: http://technet.microsoft.com/en-us/library/ff793440.aspx Don

Hi, if your KMShost server doesn't have permissions to create/update the DNS records in the _vlmcs._tcp zone, you will get this error. You can either grant the KMShost server permissions to update its own records, or manage the records yourself? http://technet.microsoft.com/en-us/library/ff793434.aspx#EIF http://technet.microsoft.com/en-us/library/ff793409.aspx#E1B Don

Hello, I’d suggest setup KMS again following this deploy instruction Check this: Deploying KMS Activation http://technet.microsoft.com/en-us/library/ff793409.aspx Thanks ZHANG

This is on a test network before implementing on live network. So what i did was back on the 31st of January I put it on my test network which i had a server01 which had the AD, DHCP, DNS and then i put on the KMS role because i've been told it is so easy and it is automatic for clients to activate. It didn't not work how it was suppose to so I blamed it on my test network. I got a HOST server put on it a Hyper V server windows 2008r2 ent server with the roles of AD, DNS and DHCP. Made sure that all was well with the system as far as DNS, DHCP and AD were concerned with. I then created another server just for kms and it is a windows 2008r2 ent virtual server Since the 2 tries act the same way i am getting to a loss of why. The following information from microsoft sight Code 0x8007232b says if i run this command it must be a srv record issue. I actually used the VMAT 2.0 tool and activated the first 25 machines. First run the following commands: cscript \windows\system32\slmgr.vbs -skms <KMS_FQDN>:<port> cscript \windows\system32\slmgr.vbs ato If these two commands resolve the issue, the issue is a SRV record issue and requires you to troubleshoot the SRV record. The next 5 windows 7 clients i have actually ran the slmgr.vbs -ato command but still get the error 0x8007232b say DNS error. The HOST doesn't see these 5 machines request at all in the KMS server Event log. I thought any client would request automatic? The Client in the application event log i show a License Activation Scheduler (sppuinotify.dll) was not able to automatically activate. Error code: 0x8007232b Event ID 8196

I have same problem Started over from scratch Windows 2008 Ent R2 Server with Active Directory, DNS and DHCP Server New from scratch. Windows 2008 Ent R2 Server KMS 30 Clients with Windows 7 Professional 32bit Used VMAT 2.0 to update computer status and on 25 of them I clicked activate then KMS Activate then i used the specific kms host and put in the FQDN for the KMS Server which activated the 25 computers. The auto discovery of the computers for activation did not happen I also ran the nslookup for the kms info and it came back with all the correct information. I also ran a netstat command and found the port 1688 is listening The next picture i submit will be 3 commands run on the 26th computer and it isn't activating the kms key. I am running out of ideas

nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt ran this command on the client in the cmd prompt this is what it says ***server01.instfo.local can't find _vlmcs._tcp: Non-existent domain server01 is my AD server serverkms is my kms server the txt file output has this information in it Server: server01.instfo.local Address: 192.168.0.9

I ran this from the client side and it returned correctly for communicating witht the kms server portqry.exe -n serverkms.instfo.local -p tcp -e 1688 The command will return "TCP port 1688 (unknown service): LISTENING" if the computer is able to communicate with the KMS server.

nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt ran this command on the client in the cmd prompt this is what it says ***server01.instfo.local can't find _vlmcs._tcp: Non-existent domain server01 is my AD server serverkms is my kms server the txt file output has this information in it Server: server01.instfo.local Address: 192.168.0.9 ok, you have a DNS issue. ( the client activates ok if you hard-code the kmshost using slmgr.vbs -skms ) your client is failing to resolve the kmshost by service/protocol. (the kmsclient service issues a name query "is there a kms here?" and it's getting a response from your dns "Nope" ) check for existence / create if missing, the needed dns records: http://technet.microsoft.com/en-us/library/ff793405.aspxDon

your KMShost looks setup fine (the KMS aspect), and your KMSclient looks fine (again KMS aspect). it sure seems like a DNS name resolution issue to me. is your KMShost logging success or fail, when it tries to publish to DNS? is the KMShost showing clients hitting it and failing to activate, or, not showing clients hitting it? is the client logging that it is attempting, and to what? is the client hitting the correct DNS suffix/zone? (I note you mentioned your "domain.local" but you show your KMShost is server01.instfo.local) on the client, do this: nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt is the correct RR returned? this is a good article on troubleshooting KMS activation, using event logs: http://technet.microsoft.com/en-us/library/ee939272.aspx Don

I ran the nslookup on the following and got the above results Active Directory Server 2008r2 Ent KMS Server 2008r2 Ent Altiris Deployment Server 2003 Windows XP client computer

So I am thinking it isn't DNS because the nslookup for kms record seems to work for servers and xp client It has to be something to do with the Windows 7 Clients.

Get this Took the Windows 7 Professional CD and wiped and reinstalled the OS with NO updates just installed the NIC Driver and disabled the IPV6. Joined it to the domain and group policy turned off the firewall. ran the command slmgr.vbs /ato It activated immediately!!!!! So something in our original image which we pushed out thru our altiris server causing the problem. We are currently creating a base image of OS no updates with ip v6 disabled then use the altiris create image then deploy to couple computers. And we are using the altiris sys prep on the image.