CTX219672
Article | Licensing | {{likeCount}} found this helpful | Created: {{articleFormattedCreatedDate}} | Modified: {{articleFormattedModifiedDate}}
Information
Sometimes after properly following the preparation steps, on start up the Operating System shows only 3 days remaining to be activated, or Office prompts users to activate now, or similar. This doesn’t necessarily indicate an issue with PVS image preparation, or with the streamed image. It’s up to the KMS client (OS or Office) to start the activation process, which can be triggered at any time from KMS client product start up. To expedite this process, the following commands can be utilised:
- Operating Systems:slmgr /ato
- Office installations: launch the Office application and runcscript ospp.vbs /act
The KMS clients come with a key pre-installed, called the Generic Volume License Key (GVLK) or KMS Client Setup Key.The presence of the GVLK is what makes a system a KMS client.The KMS clients find the KMS host via a DNS SRV record (_vlmcs._tcp) and then automatically attempt to discover and use this service to activate themselves.When in the 30 dayOut of Boxgrace period, they will try to activate every 2 hours. Once activated, the KMS clients will attempt a renewal every 7days.
To identify if a KMS activation has been triggered by the client, we can look for theevents in the event log of the KMS client machine.Below you will see a snippet from Application event log from my machine.A successful activation/reactivation on the client will have two events, 12288 and 12289.If you only see the 12288 event (without a corresponding 12289) it means that the KMS client was not able to reach the KMS host or it did not respond/response was lost. In this case, confirm that the KMS host is discoverable and reachable by the KMS client systems.
In the 12288 event entry, the most relevant piece of information is data in the Info section.For example, the FQDN and TCP port used by the client to attempt activation is shown, along with the current state of the client.The FQDN can also help to troubleshoot cases where the count on a KMS host is not increasing. For example, if there are too many KMS hosts available to the clients (either legitimate or rogue systems) then the count may be distributed over all of them.
An unsuccessful activation will not always mean that the client has 12288 and not 12289. A failed activation/reactivation may also have both events.This is where you need to examine the second event to confirm the reason for the failed attempt.
In the 12289 event entry, the Info section is also where you will look to find what you need:
-
Activation Flag
-
This will be a 1 (successful) or 0 (failure) on the attempt.
-
-
Current Count on the KMS Host
- The client will log the count received by the KMS host. If activation fails, it may be because the count is not sufficient for this client OS or that there are not enough systems in the environment to build the count.
You can also look for the above information by running the slmgr /dlv command. Below is a snippet of the output of the command.
It’s important to understand that PVS has no control over when the activation will take place. If the/atocommand is successful, Windows will show as ‘activated’ shortly. If it does not, this should be troubleshot as a KMS client activation issue outside of PVS.Remember PVS involvement is only to ensure unique CMID generation.
Additional Resources
KMS with PVS: https://www.citrix.com/blogs/2014/05/01/demystifying-kms-and-provisioning-services/
How to troubleshoot the Key Management Service (KMS): https://technet.microsoft.com/en-us/library/ee939272.aspx
Volume Activation Troubleshooting:https://technet.microsoft.com/en-us/library/ff793439.aspx
KMS Activation Timing and Discovery for Volume Activation:https://technet.microsoft.com/en-us/library/dn502530(v=ws.11).aspx
Disclaimer
Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsem*nt by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.
As an expert in systems and activation processes, I have extensive knowledge and experience in the realm of Key Management Service (KMS) activation for operating systems and Office installations. I've delved into the intricacies of KMS client activation, troubleshooting, and the underlying mechanisms that govern the activation process. My expertise is grounded in practical applications and a deep understanding of the technology involved.
Now, let's dissect the provided article, specifically focusing on the concepts and commands used:
-
CTX219672 Article Overview:
- The article addresses a common issue where, despite following proper preparation steps, the Operating System shows a limited activation period.
- It emphasizes that this issue might not be related to PVS image preparation but rather to the KMS client's activation process.
-
Activation Commands:
- The article provides commands to expedite the activation process for different scenarios:
- For Operating Systems:
slmgr /ato - For Office installations: Launch the Office application and run
cscript ospp.vbs /act
- For Operating Systems:
- The article provides commands to expedite the activation process for different scenarios:
-
Generic Volume License Key (GVLK) or KMS Client Setup Key:
- KMS clients come with a pre-installed key called the Generic Volume License Key (GVLK) or KMS Client Setup Key.
- The presence of the GVLK is what designates a system as a KMS client.
-
KMS Activation Process:
- KMS clients find the KMS host via a DNS SRV record (_vlmcs._tcp) and automatically attempt to discover and use this service for activation.
- During the 30-day grace period, KMS clients try to activate every 2 hours. After activation, they attempt a renewal every 7 days.
-
Event Log Monitoring:
- The article recommends checking the event log on the KMS client machine for activation events.
- A successful activation/reactivation will have two events, 12288 and 12289. The absence of 12289 indicates a failure.
-
Troubleshooting Unsuccessful Activation:
- If activation fails, examining the second event (12289) is crucial to determine the reason for the failure.
- Information in the Info section of the events includes Activation Flag (1 for success, 0 for failure) and Current Count on the KMS Host.
-
Additional Resources:
- The article provides links to additional resources for further understanding and troubleshooting:
- KMS with PVS:
- How to troubleshoot the Key Management Service (KMS):
- Volume Activation Troubleshooting:
- KMS Activation Timing and Discovery for Volume Activation:
- The article provides links to additional resources for further understanding and troubleshooting:
-
Disclaimer:
- Citrix issues a disclaimer, stating that it is not responsible for the contents of third-party websites linked in the article.
In conclusion, the article provides comprehensive information on troubleshooting KMS activation issues, covering commands, key concepts, event log analysis, and additional resources for further exploration.
