Managing License States
The display license information (/dli) command-line option of Slmgr.vbs displays the current license state of computers running Windows 7 or Windows Server 2008 R2. The output of this parameter also includes general information about the current license, time remaining before expiration, and time remaining in the grace period, if applicable.
The following code is an example of the information displayed when Slmgr.vbs /dli runs on a KMS client:
Name: Windows(R) 7, Enterprise edition Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel Partial Product Key: DVQ7P License Status: Licensed Volume activation expiration: 243720 minute(s) (169 day(s)) Key Management Service client information Client Machine ID (CMID): 2ffcfc30-6a6a-49ec-92b8-f6150c7df211 KMS machine name from DNS: emeronb10-rc3.sppvltest.net:1688 KMS machine extended PID: 55041-00140-015-871562-03-1033-7078.0000-0992009 Activation interval: 15 minutes Renewal interval: 25 minutes KMS host caching is enabled
The following code is an example of the information displayed when Slmgr.vbs /dli runs on a KMS host:
Name: Windows Server(R), ServerEnterprise edition Description: Windows Operating System - Windows Server(R), VOLUME_KMS_C channel Partial Product Key: PYWKV License Status: Licensed
Key Management Service is enabled on this machine Current count: 2 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal
Key Management Service cumulative requests received from clients Total requests received: 826 Failed requests received: 0 Requests with License Status Unlicensed: 0 Requests with License Status Licensed: 826 Requests with License Status Initial grace period: 0 Requests with License Status License expired or Hardware out of tolerance: 0 Requests with License Status Non-genuine grace period: 0 Requests with License Status Notification: 0
More detailed licensing information is available using the /dlv parameter. The following code is an example of the information displayed when Slmgr.vbs /dlv runs on a KMS host:
Name: Windows Server(R), ServerEnterprise edition Description: Windows Operating System - Windows Server(R), VOLUME_KMS_C channel Activation ID: fed62577-3bef-4309-90e8-671abdc076d8 Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 55041-00140-015-871562-03-1033-7078.0000-0992009 Installation ID: 007770007653131654256624425615586710406244931761974006 Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343 Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345 Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344 Partial Product Key: PYWKV License Status: Licensed Evaluation End Date: 6/1/2010 4:59:59 PM Remaining Windows rearm count: 3 Trusted time: 4/28/2009 2:32:10 PM
Key Management Service is enabled on this machine Current count: 2 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal Key Management Service cumulative requests received from clients Total requests received: 826 Failed requests received: 0 Requests with License Status Unlicensed: 0 Requests with License Status Licensed: 826 Requests with License Status Initial grace period: 0 Requests with License Status License expired or Hardware out of tolerance: 0 Requests with License Status Non-genuine grace period: 0 Requests with License Status Notification: 0
Note Both the /dli and /dlv commands work when run on retail and original equipment manufacturer (OEM)–activated computers. For more information about available activation methods and possible license states, see the Volume Activation Deployment Guide.
Recovering from a Non-Genuine State
If a KMS (CSVLK) or MAK key is lost or misused, the product key can be marked non-genuine and invalid for activation. In this case, the product key checked during online validation is considered invalid, and the system fails validation. In addition, the computer will be placed in a 30-day non-genuine state grace period, which allows for the time needed to obtain a new product key. The desktop wallpaper is changed to a solid black background, and periodic notification balloons appear in the system tray to remind the user to validate the license status of the system.
When evidence of system tampering is detected, the system goes into a non-genuine or tampered state depending on the type of tampering. If the computer has altered system files, the best way to recover is to reinstall the operating system, and then reactivate the computer. If a KMS host or KMS client is marked non-genuine because of a compromised product key, replace the KMS key on all KMS hosts configured with that key. Then, force an immediate reactivation of the KMS clients by running Slmgr.vbs /ato, or allow the clients to reactivate themselves according to the activation renewal schedule. If the original key is compromised on a MAK-activated computer, install a new MAK and reactivate.
Before a computer can recover from a validation failure, IT must first determine why the computer failed validation; then, appropriate recovery steps can be taken. Begin by examining the Application event log for event ID 8209. The reason for the validation failure is listed in this event.
After a computer is reactivated, connect to the Genuine Microsoft Software Web site at http://go.microsoft.com/fwlink/?LinkId=64187for a validation to change the non-genuine state to genuine.
Activation of Windows OEM Computers
Windows 7 and Windows Server 2008 R2 have different usage rights based on the channel used to purchase them. Generally, the product usage rights for OEM-licensed products prohibit conversion of an OEM installation of an operating system to a Volume License installation. However, there are exceptions. If one of the exceptions applies, an OEM version of Window 7 or Windows Server 2008 R2 can be changed to a Volume License version.
One exception that allows changing an OEM installation to a Volume License installation is if Software Assurance is purchased within 90 days of purchasing the OEM product. This exception applies only to Windows 7 or Windows Server 2008 R2. Another exception is if the OEM product is the same product for which a Volume License agreement already exists. Volume License customers have reimaging rights and may be eligible to upgrade an OEM installation using Volume License media. For more information about imaging rights, see the Microsoft Volume Licensing brief, “Reimaging Licensed Microsoft Software by Using Volume Licensing Media,” at http://download.microsoft.com/download/1/7/7/17745e4a-5d31-4de4-a416-07c646336d94/reimaging.doc and “Customizing Windows Vista Business Edition” at http://go.microsoft.com/fwlink/?LinkID=137292.
Computers obtained through OEM channels that have an ACPI_SLIC table in the system basic input/output system (BIOS) are required to have a valid Windows marker in the same ACPI_SLIC table. The appearance of the Windows marker is important for Volume Licensing customers who are planning to use Windows 7 Volume License media to re-image or upgrade an OEM system through the re-imaging rights they have in their Volume Licensing agreement. Computers that have an ACPI_SLIC table without a valid Windows marker generate an error when a volume edition of Windows 7 is installed. For more information, see “You receive an error message when you try to activate Windows Vista on a computer that was obtained from an OEM” at http://support.microsoft.com/default.aspx?scid=kb;EN-US;942962.
These systems cannot be activated with KMS, but they can be activated using a MAK or a retail key.