Tuesday, May 25, 2010 1:31 PM
Out institution was running windows 2008 DC that was acting as a KMS host for windows 7. Due to the office 10 KMS not being able to run on 2008 we created a new DC that is acting as the windows 7 KMS host server now and also an office 2010 kms host. The windows 7 KMS seems to be working fine however the office 2010 kms is having an issue i believe. when (on a client machine running office 10) i run a "cscript ospp.vbs /dhistorykms" i get the KMs activation events, the first few events list the OLD DC that had the windows kms running on it and states "the software licensing service determined that the specified KMS cannot be used. I then did a "cscript ospp.vbs /remhst" and a "cscript ospp.vbs /sethst:NewKmsServer" i then re-ran "cscript ospp.vbs /dhistorykms" and the new events pop up "error/host: 0x00000000, 0x00000000, MyServer.Domain.Name Error Description: N/A" Now, i do not currently have 5 office 10's activated aginst the new DC/KMS so that may be throwing the error?
Tuesday, May 25, 2010 6:59 PM
When you've added your new KMS host with ospp.vbs /sethst, then did you try ospp.vbs /act?
If the current count is not high enough (e.g. you need more than 5 clients before activation), you will get a different error message.
Are you using DNS autodiscovery to find your KMS host for all your clients, or are you hard-coding the KMS host name in all the clients? You will need to run /sethst on all your client machines if you're not using DNS.
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
- Marked As Answer by Jennifer Zhan Monday, May 31, 2010 8:42 AM