To view the activation event history run: cscript OSPP.VBS /dhistorykms NOTICE: A KB article has been detected for activation failure: 0xC004F074 FOR MORE INFORMATION PLEASE VISIT: When I ran the suggested command 'cscript ospp.vbs /dhistorykms' I got a laundry list of errors with many dates. Please see the Application Event Log for additional information. No Key Management Se rvice (KMS) could be contacted. Also check the event logs on both KMSclient and KMShost, you should be seeing the KMSclient issue an activation request (logged at client), followed by receipt of that same request at KMShost (logged at host), followed by response from KMShost (logged at host) and receipt of that response at KMSclient (logged at client). ![]() VL pkey has to be 5 or greater, else KMSclients will simply not be able to activate to this KMShost. Next step is to examine the (redacted) CurrentCount information for this specific VL pkey. ![]() You should see the counters incrementing on KMShost (shown in the slmgr output when you use the /dli or /dlv parameters) Don doesn't work for MSFT, and they're probably glad about that. If the request/response is not logged, check firewall at KMShost is allowing TCP:1688 inbound to KMShost.
0 Comments
Leave a Reply. |