VMware

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
0 Replies Last post: Nov 6, 2009 1:50 PM by jawerjksdpgfj…  

Non-functioning KMS (Server 2003) after P2V conversion posted: Nov 6, 2009 1:50 PM

Click to view jawerjksdpgfjlmascouawf's profile Lurker 2 posts since
Jan 7, 2009

I did a local-based conversion from on an old Dell 2450 to ESXi yesterday. Since the change in visible hardware is obviously significant enough and caused the KMS to spit out "KMS license expired or hardware out of tolerance" as a message whenever I do "slmgr.vbs -dlv," this required re-activation of the KMS via "slmgr.vbs -ato." However, now whenever I do "slmgr.vbs -dlv" it tells me that the status is "licensed" but there's no current client activation count. When I have Vista clients try to connect to the server, the clients get a message that KMS can't be reached. A packet trace clearly reveals that connection to TCP 1688 is made and that RPC transactions are taking place. There's apparently something wrong with the KMS.

Has anyone else had this issue? I really don't want to have to go through a KMS license key reinstall since I can't seem to locate ours.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities