Microsoft/KMS/Notes
Recent Changes to Volume Activation
- "With Volume Licensing for products such as Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, and Microsoft Office 2010, you must use a new type of product activation called Volume Activation (VA). To activate these operating systems with VA, you can use either a Multiple Activation Key (MAK) or Key Management Service (KMS), requiring a KMS key.
- Volume Activation is a product activation technology used to activate Windows Vista, Windows Server 2008, 2008 R2, Windows 7 and Office 2010. It is designed to allow Volume Licensing customers to automate the activation process in a way that is transparent to end users. Volume Activation applies to systems that are covered under a Volume Licensing program and is used strictly as a tool for activation and is in no way tied to license invoicing or billing.
Volume Activation provides two different models for completing volume activations. The first model is Key Management Service (KMS) and the second is Multiple Activation Key (MAK). KMS allows organizations to activate systems within their own network, while MAK activates systems on a one-time basis, using Microsoft’s hosted activation services. Customers can use either or both activation methods in their environment. The type of key entered in the product determines the activation method.
If you plan to deploy Windows 7 and/or Office 2010 using Key Management Service (KMS) as the activation method, please note:
- Windows Server 2008 is not supported as a KMS host to activate Windows 7 and Office 2010.
- A patch is available to allow activation of Windows 7 client machines. (A Windows Server 2008 R2 KMS key is required.)
- A patch is not available to allow activation of Office 2010 clients.
- If you are using Windows Server 2008 as a KMS host, here are your alternatives:
- Upgrade the KMS host machine to Windows Server 2008 R2.
- Downgrade the machine to Windows Server 2003.
- Run the KMS host on a Windows 7 volume edition machine.
- Run a Windows Server 2003 virtual machine on the Windows Server 2008 machine.
If your organization has fewer than 50 PCs, the best option is to use Multiple Activation Keys (MAK) with Volume Activation Management Tool (VAMT).
While Microsoft makes every effort to cover all of its previous platforms for compatibility, new technologies may make it necessary to decide which previous versions will continue to be supported. Therefore, Windows Server 2008 is not covered as a platform as an Office 2010 KMS host.
Volume License Keys (VLK), including MAK and KMS, are issued to you under a specific license agreement and enable your organization to use the software that you have licensed.
VLKs can be used only with Volume Licensing products; they cannot be used with retail software or software that is preinstalled on a new computer (original equipment manufacturer, or OEM, products).
Volume Activation
Multiple Activation Key:
- The Multiple Activation Key (MAK) activates either individual computers or a group of computers by connecting directly to Microsoft servers over the Internet or by telephone. The keys can be used a limited number of times. This activation limit can be increased by calling your Microsoft Activation Center.
Key Management Service:
- Your organization can host the Key Management Service (KMS) internally to automatically activate computers running Windows Vista. To use the KMS, you must have a minimum of 25 computers running Windows Vista that are connected together. Computers that have been activated through KMS will be required to reactivate by connecting to your organization's network at least every six months.
- Currently the KMS software runs on a local computer running Windows Vista or the Microsoft Windows Server Code Name "Longhorn" operating system. In the future, it will run on the Microsoft Windows Server 2003 operating system.
KMS Activation: Background Information
Vista Activation:
_vlmcs._tcp.<default-domain-name> TCP port 1688
When a Vista machine is attached to a network, it will attempt to activate automatically by looking for a KMS server at _vlmcs._tcp.<default-domain-name> on TCP port 1688. The <default-domain-name> usually can be found by running the ipconfig program on the Vista machine and looking at the Connection-specific DNS Suffix. If the KMS is found, the Vista machine will request a six-month activation. At no point in this process does the Vista client machine communicate with Microsoft regarding activation. After two weeks, the Vista machine will automatically try to obtain a new six-month activation from the KMS server. So long as the KMS server is available, the Vista machine will always remain activated. If the Vista machine is unable to reach the KMS prior to the expiration of the six-month activation, it will enter a 30-day grace period, following which it will enter a reduced-functionality mode. Summary
- Vista operates normally for 30 days following installation without entering a license key.
- Vista activates automatically if _vlmcs._tcp.<default-domain-name> points to the KMS server and TCP port 1688 is not blocked.
- Activations obtained via KMS are good for six months and Vista will attempt to renew them every two weeks.
- If an activation obtained via KMS expires, there is an additional 30 day grace period before the machine goes to reduced functionality mode.
- The KMS server is only available to computers physically on an OSU network or via VPN to an OSU network.
- Machines located off-campus that do not return to campus physically or connect to campus via a VPN at least once every 210 days should not rely on KMS activation.
slmgr
slmgr options:
C:\>cscript c:\windows\system32\slmgr.vbs /?
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.
Unrecognized option: /?
Windows Software Licensing Management Tool
Usage: slmgr.vbs [MachineName [User Password]] [<Option>]
MachineName: Name of remote machine (default is local machine)
User: Account with required privilege on remote machine
Password: password for the previous account
Global Options:
-ipk <Product Key>
Install product key (replaces existing key)
-ato
Activate Windows
-dli [Activation ID | All]
Display license information (default: current license)
-dlv [Activation ID | All]
Display detailed license information (default: current license)
-xpr
Expiration date for current license state
Advanced Options:
-cpky
Clear product key from the registry (prevents disclosure attacks)
-ilc <License file>
Install license
-rilc
Re-install system license files
-rearm
Reset the licensing status of the machine
-upk
Uninstall product key
Volume Licensing: Key Management Service (KMS) Client Options:
-skms <Name[:Port] | :Port>
Set the name and/or the port for the KMS computer this machine will use
-ckms
Clear name of KMS computer used (sets the port to the default)
Volume Licensing: Token-based Activation Options:
-lil
List installed Token-based Activation Issuance Licenses
-ril <ILID> <ILvID>
Remove installed Token-based Activation Issuance License
-ctao
Clear Token-based Activation Only flag (default)
-stao
Set Token-based Activation Only flag
-ltc
List Token-based Activation Certificates
-fta <Certificate Thumbprint> [<PIN>]
Force Token-based Activation
From: W2K8x86 server
How can I setup a KMS server - www.windows-noob.com
What is a KMS server
- KMS activates operating systems on your local network, eliminating the need for individual computers to connect to Microsoft. To do this, KMS uses a client/server method of implementation. KMS clients connect to a KMS server, called the KMS host, for activation. The KMS host resides on your local network.
Supported platforms
- A KMS server can run on either windows 2008, Windows vista or Windows Server 2003 with SP1 and later, however installing it on Windows 2003 requires you to download the appropriate installation files for KMS v1.1.
Number of PC's required
- To activate Windows Vista, you must have at least 25 computers running Windows Vista or Windows Server 2008 that are connected together; for Windows Server 2008, the minimum is 5 computers. Computers that are activated through KMS must be reactivated every six months by connecting to your organization's network.
KMS Setup
Note: Do all the commands below via a command prompt which has been opened with Administrative privileges.
Installing KMS Server:
Open C:\Windows\system32 and execute the following command
cscript c:\Windows\System32\slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Obvioulsy replace xxxxx with your key.
You should see the following:
Microsoft ® Windows Script Host Version 5.7 Copyright © Microsoft Corporation. All rights reserved. Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.
How can I activate via Telephone (offline activation)
If activation for the KMS server is necessary then call Microsoft and follow the instructions.
Open C:\Windows\system32 and execute the following command
slui.exe 4
Then
- Show me other ways to activate
- use the automated phone system
And then call Microsoft and follow the instructions. After successful activation, click on close.
Then do as follows:
net stop slsvc && net start slsvc
You should see the following:
The Software Licensing service is stopping. The Software Licensing service was stopped successfully.
The Software Licensing service is starting. The Software Licensing service was started successfully.
Open the Firewall for KMS traffic
In Windows Firewall, click on Exceptions and allow the now listed Key Management Services, failure to do this step will mean that your KMS hosts can not talk to the KMS service and therefore will not activate.
KMS listens on port 1688, to change the port you must do as follows:
SLMgr.vbs /SPrt xxxx
where xxxx = the new port number
After you have entered this command you must restart the SLMgr service using:
net stop slsvc && net start slsvc
Test the KMS server configuration
The KMS server should publish its SRV records in your domain DNS, you should verify that these records exist.
Open C:\Windows\system32 and execute the following command
nslookup -type=srv _vlmcs._tcp
You should see output similar to the following:
DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.3.1 _vlmcs._tcp.windows-noob.local SRV service location: priority = 0 weight = 0 port = 1688 svr hostname = sccm2007.windows-noob.local sccm2007.windows-noob.local internet address = 192.168.3.1
To manually activate a client over the Internet
Any client will automatically try to activate itself every 120 minutes by default, so there is no need to run the acivation command manually. However if you want to test or speed up the process then do as follows.
Open C:\Windows\system32 and execute the following command
cscript C:\windows\system32\slmgr.vbs /ato
To change the 120 minutes setting, you must do as follows:
SLMgr.vbs /sai x
where x = the new interval in minutes
After you have entered this command you must restart the SLMgr service using:
net stop slsvc && net start slsvc
Query KMS server
To query the KMS server and see its status open a command prompt and execute the following command.
cscript slmgr.vbs /dli
You should see output similar to below:
Microsoft ® Windows Script Host Version 5.7 Copyright © Microsoft Corporation. All rights reserved. Name: Windows Server®, ServerStandard edition Description: Windows Operating System - Windows Server®, VOLUME_KMS_B channel Partial Product Key: xxxxx 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: 5 Failed requests received: 0 Requests with License Status Unlicensed: 0 Requests with License Status Licensed: 0 Requests with License Status Initial grace period: 5 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
Microsoft Video showing KMS in action
License States
A computer can be in one of 5 license states
Initial grace Period
- This occurs after the computer is installed and can only last for up to 30 days, this can be reset twice.
Non-Genuine grace Period
- This occurs after a computer is found to have a non-genuine or counterfeit Windows operating system installed. This state can last up to 30 days to give you time to reactivate using a genuine copy and License key.
Out-of-tolerance grace period
- This can occur when either several hardware changes are made to the computer or when the KMS key has not contacted Microsoft for updates in 180 days. This state can last up to 30 days.
Licensed
- This state occurs when everything is ok and the system is activated.
Unlicensed
- This state occurs when the activation period has expired and nothing was done about it. The computer will stay in a limited access state until it has been activated.
Windows 7 Specific KMS info
For Windows 7 and Windows Server 2008 R2 KMS info refer to this post.
Which Key do I use, KMS, MAK, VLK
IF you are unsure about which key to use for activation then take a look at this post on Technet
KMS Version
Server 2003 EE x86 slmgr -dlv 6.0.6001.16550
???
Windows 7 Licensing Server:
6.1.7600.16385
Windows Vista Activation
Install one of the following versions: (business versions)
- Windows Vista Business with Service Pack 2 (x86/x64) - DVD (English)
- Windows Vista Enterprise with Service Pack 2 (x86/x64) - DVD (English)
Windows 7 Activation
- "Corporations with volume licensing agreement which had been setting up and using Windows Server 2003 has KMS (Key Management Service) server to provide volume activation to computers running Windows Vista and Windows Server 2008, can download an updated patch, KMS version 1.2, to extend support for Key Management Service (KMS) to provide volume activation for Windows 7 and Windows Server 2008 R2, in the event of OS upgrade or acquire of new PC with new operating systems."
KMS 1.2 provides support for the following KMS client installations:
- Windows Server 2008 R2
- Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
- Windows 7
- Windows Vista and Windows Vista Service Pack 2 (SP2)
Win 7 KMS Activation
FOR KMS ACTIVATION USE ENTERPRISE OR PROFESSIONAL (VL) VERSIONS
Install one of the following versions:
- Windows 7 Professional, VL Build (x86/x64) - DVD (English)
- en_windows_7_professional_vl_build_x64_dvd_x15-71037.iso
- en_windows_7_professional_vl_build_x86_dvd_x15-71033.iso
- Windows 7 Enterprise (x86/x64) - DVD (English)
- en_windows_7_enterprise_x64_dvd_x15-70749.iso
- en_windows_7_enterprise_x86_dvd_x15-70745.iso
Note: Win 7 Ultimate does not use KMS activation:
- Windows 7 Ultimate (x86/x64) - DVD (English)
- en_windows_7_ultimate_x64_dvd_x15-65922.iso
- en_windows_7_ultimate_x86_dvd_x15-65921.iso
Windows Server 2008 Activation
It appears that any Enterprise version of 2008 will activate against the KMS server.
Windows Server 2008
Install one of the following versions:
- ?? Windows Server 2008 Datacenter, Enterprise, and Standard with Service Pack 2 (x86) - DVD (English) ??
- ?? Windows Server 2008 Datacenter, Enterprise, and Standard with Service Pack 2 (x64) - DVD (English) ??
- en_windows_server_2008_datacenter_enterprise_standard_sp2_x64_dvd_342336.iso
Windows Server 2008 R2
Install one of the following versions:
- Windows Server 2008 R2 Standard, Enterprise, Datacenter, and Web, VL Build (x64) - DVD (English)
- en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso
- Windows Server 2008 R2 Standard, Enterprise, Datacenter, and Web with Service Pack 1, VL Build (x64) - DVD (English)
- en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_vl_build_x64_dvd_617403.iso
KMS Server Status Output
C:\>cscript //H:CScript
The default script host is now set to "cscript.exe".
C:\>slmgr /dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Software licensing service version: 6.0.6001.16550
Name: Windows(TM) Server 2003 KMS, W7R2-Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_C channel
Activation ID: 8fe15d04-fc66-40e6-bf34-942481e06fd8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00168-305-016440-03-1033-3790.0000-1242010
Installation ID: 020260205766562811258860556503726773202030100311046296
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938
Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939
Partial Product Key: 8D9MK
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 18
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Note: you can watch the event viewer log "Key Management Service" for activation requests.
Successful Activation
Server 2008 R2
C:\>systeminfo
Host Name: TESTHOST
OS Name: Microsoft Windows Server 2008 R2 Standard
OS Version: 6.1.7600 N/A Build 7600
Product ID: 00477-001-0000421-84502
C:\>cscript //H:CScript
The default script host is now set to "cscript.exe".
C:\>slmgr /ato
Activating Windows Server(R), ServerStandard edition (68531fb9-5511-4989-97be-d1
1a0f55633f) ...
Product activated successfully.
C:\>slmgr /dlv
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Software licensing service version: 6.1.7600.16385
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT chan
nel
Activation ID: 68531fb9-5511-4989-97be-d11a0f55633f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00477-00168-001-000042-03-1033-7600.0000-0952011
Installation ID: 007055161536981512867076264581634115711955267974097191
Partial Product Key: R7VHC
License Status: Licensed
Volume activation expiration: 259200 minute(s) (180 day(s))
Remaining Windows rearm count: 1
Trusted time: 6/30/2011 11:08:45 AM
Key Management Service client information
Client Machine ID (CMID): 04a6cf07-00c0-4f3c-a366-2a460e032bc9
KMS machine name from DNS: kms.oeey.com:1688
KMS machine extended PID: 55041-00168-305-016440-03-1033-3790.0000-1242010
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabled
C:\>systeminfo
Host Name: DBSQLSERVER
OS Name: Microsoft Windows Server 2008 R2 Standard
OS Version: 6.1.7601 Service Pack 1 Build 7601
Product ID: 00477-001-0000421-84675
C:\>cscript //H:CScript
The default script host is now set to "cscript.exe".
C:\>slmgr /dlv
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Software licensing service version: 6.1.7601.17514
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT chan
nel
Activation ID: 68531fb9-5511-4989-97be-d11a0f55633f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00477-00168-001-000042-03-1033-7601.0000-0622011
Installation ID: 021764577625688334810014798556725600475360826362171746
Partial Product Key: R7VHC
License Status: Licensed
Volume activation expiration: 249360 minute(s) (173 day(s))
Remaining Windows rearm count: 1
Trusted time: 6/30/2011 12:28:20 PM
Key Management Service client information
Client Machine ID (CMID): b0ae93b0-8884-451c-a146-21b621ed80b4
KMS machine name from DNS: kms.oeey.com:1688
KMS machine extended PID: 55041-00168-305-016440-03-1033-3790.0000-1242010
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabled
Failed Activation
C:\>systeminfo Host Name: SAP1 OS Name: Microsoft Windows Server 2008 R2 Standard OS Version: 6.1.7601 Service Pack 1 Build 7601 Product ID: 00477-001-0000421-84387 C:\>cscript //H:CScript The default script host is now set to "cscript.exe". C:\>slmgr /ato Activating Windows Server(R), ServerStandard edition (68531fb9-5511-4989-97be-d1 1a0f55633f) ... Error: 0xC004F074 The Software Licensing Service reported that the computer coul d not be activated. The Key Management Service (KMS) is unavailable C:\>slmgr /dlv Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Software licensing service version: 6.1.7601.17514 Name: Windows Server(R), ServerStandard edition Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT chan nel Activation ID: 68531fb9-5511-4989-97be-d11a0f55633f Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 00477-00168-001-000042-03-1033-7601.0000-1322011 Installation ID: 015733974065277735273315935353378694129401299151585250 Partial Product Key: R7VHC License Status: Initial grace period Time remaining: 43140 minute(s) (29 day(s)) Remaining Windows rearm count: 2 Trusted time: 7/1/2011 2:44:02 PM Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
Cause: the server's time was out of sync
Microsoft - Top 5 Product Key Activation Challenges IT Pros Encountered and Solved (DOC)
The Computer Could Not Be Activated. The Returned Count from Your Key Management Service is Insufficient.
0xC004F038 - The Software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
What causes this issue?
For systems to activate using KMS, the KMS host must be contacted by a minimum number of physical systems (referred to as KMS activation threshold). The minimal physical count required is 25 Windows Vista or 5 Windows Server 2008 machines to perform successful deployment. It is referenced as KMS Activation Threshold in the Planning Guide for Volume Activation 2.0.
KMS clients activate only after this threshold is met. To ensure that the activation threshold is met, a KMS host counts the number of physical computers requesting activation on the network. The count of activation requests is a combination of both Windows Vista and Windows Server 2008 computers. However, each of these operating systems begins activating after a different threshold is met. Virtual computers do not contribute to the activation count, but virtual computers are activated by KMS after the physical computer threshold is met. Read more about it in the Volume Activation 2.0 planning guide.
The two scenarios that cause this error include: using multiple KMS host, or activating against various hosts and having the same client machine IDs CMIDs on your machines due to prior re-imaging.
How to solve it?
You can use a number of methods to resolve this issue to continue successful activation of your systems. Check all your clients, depending on your situation and knowledge of the methods described by:
- Using Volume Activation Management Tool (VAMT) that checks the status of your machines on the network. From the VAMT help file, you can see whether the machine identifies as a KMS host, KMS client, or a MAK key and whether those machines are activated or not.
- Using the Operations Manager KMS Management Pack tool or SCOM (if you already have those tools) to show against which KMS hosts your KMS clients are communicating with. The Operations Manager KMS Management Pack provides you with a number of reports, including activation count, virtual machine, KMS activity, licensing status summaries, machine expiration chart and details.
- Solving it manually, and going to elevated command prompt and run SLMGR /dlv (this is located on the following output line - KMS machine name from DNS) and you will see the KMS machine name from DNS which is your KMS host machine.
- Rerunning your machines with a sysprep/ generalize switch, if the CMIDs are the same on those machines. The CMIDs will change, the count might increase after those machines contact the KMS host machine. This is a requirement when deploying images. If you are installing by running setup.exe or installing by booting from the DVD, the CMIDs should all be different. When you deploy images of the OS, using sysprep with the generalize switch resets the CMIDS as well as other requirements that are needed to work properly. Step-by-step reference can be found in the knowledge base (KB929829) article.
NOTE: Virtual computers do not contribute to the activation count, but virtual computers are activated by KMS after the physical computer threshold is met.
Issues
The Computer Could Not Be Activated. The Returned Count from Your Key Management Service is Insufficient.
0xC004F038 - The Software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
Request Timestamp is Invalid
0xC004F06C - The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid.
Your date and time are not synced with the KMS server. Fix the date and time and try again.
Action Requires Elevated Privileges
0xC004F025 - Access denied: the requested action requires elevated privileges.
Error:
Activating Windows(R) 7, Professional edition Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable
Cause:
- "You will get the error with a mismatch between the KMS host machines and unsupported clients" [1]
Solution:
- Check time sync - Your client machine time must be in sync with activation server. *** TRY THIS FIRST *** [2]
Solution:
- Check the KMS version on both client and server ("slmgr /dlv") - 6.0.x vs 6.1.x
- KMS version 1.2 is required and a new 'VOLUME_KMS_R2_C channel' host key is required to activate Windows 7 and Server 2008 R2 systems.
- KMS 1.2 - An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003
Alternate Solution: [3]
- Uninstall KMS license Key on host - slmgr.vbs /upk
- Install Windows Server 2008 R2 KMS license key - slmgr.vbs /ipk <Your Key>
- Activate KMS server online: slmgr.vbs /ato
- Server 2008 (R1) KMS server to activate Win7 - http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/936e7dbf-2ed5-4369-9504-b8d0393f205c
Error 0xC004C003 - key is in use
Error 0xC004C003
slui.exe 0x2a 0xC004C003 Description: The activation server determined the specified product key is in use.
Solution: use a different product key
Error code 0xC004F051 - licensing service - product key blocked
Symptom
When you try to use KMS or a MAK to activate one or more computers, you may receive the following error message:
0xC004F051 The software Licensing Service reported that the product key is blocked.
Cause
This issue may occur if the product key on the activation server is blocked by Microsoft.
Workaround
Obtain a new MAK or a new KMS key, install the new key on the system, and then activate the computers.
Error Code 0xC004C003 - activation server - product key is blocked
Error:
Activating Windows Server(R), ServerEnterprise edition (b297426d-464d-4af1-abb2-3474aeecb878) ... Error: 0xC004C003 The activation server determined the specified product key is blocked
This found on a server 2008 r2 system.
Solution:
- Use the "Default KMS" key and try again.
Default Key:
- Windows Server 2008 R2 Enterprise - 489J6-VHDMP-X63PK-3K798-CPX3Y
Notes
Microsoft Volume Licensing - Product Activation:
- "Microsoft includes product activation technology in some products sold through the Volume Licensing channel. A product key is required to activate these products.
- Recent Changes to Volume Activation
- With Volume Licensing for products such as Windows 7, Windows Server 2008 and Windows Vista, you must use a new type of product activation called Volume Activation (VA). To activate these operating systems with VA, you can use either a Multiple Activation Key (MAK) or Key Management Service (KMS), requiring a KMS key."
Microsoft Volume Licensing - Volume License Keys for Windows Vista and Windows Server 2008 FAQ:
- "How do I deploy Windows Vista and Windows Server 2008 by using Multiple Activation Keys (MAK) and Key Management Service (KMS) keys?
- To deploy Windows Vista and Windows Server 2008, follow the guidelines available from Microsoft TechNet. The documentation is available for download to use when you plan and manage deployment."
- "Volume Activation (VA) 2.0 is designed to automate and manage the activation process while addressing the piracy and product key management problems associated with Volume License Keys (VLKs) issued for Windows XP and Windows Server 2003. Volume Activation 2.0 eliminates the use of product keys at installation and enables better protection and management of customer-specific product keys through some new and enhanced activation management tools. All installations of Windows Vista and Windows Server 2008 must be activated."
Download details: Volume Activation 2.0 Technical Guidance:
- "Technical documentation for planning, deployment, and operations of Volume Activation 2.0 for Windows Vista and Windows Server 2008. Includes the Volume Activation 2.0 Overview Guide, Planning Guide, Deployment Guide, Operations Guide, Resources, FAQ and Technical Attributes."
- Volume Activation 2.0 Overview Guide, Planning Guide, Deployment Guide, Operations Guide - Provides planning, deployment and operational guidance for activating volume editions of Windows Vista and Windows Server 2008.
- Volume Activation 2.0 Resources - Provides a list of resources for Volume Activation 2.0.
- Volume Activation 2.0 FAQ - Answers to frequently asked questions about Volume Activation 2.0.
- Volume Activation 2.0 Technical Attributes - Spreadsheet detailing Volume Activation 2.0 technical attributes.
cscript c:\Windows\System32\slmgr.vbs:
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Windows Software Licensing Management Tool
Usage: slmgr.vbs [MachineName [User Password]] [<Option>]
MachineName: Name of remote machine (default is local machine)
User: Account with required privilege on remote machine
Password: password for the previous account
Global Options:
-ipk <Product Key>
Install product key (replaces existing key)
-upk [Activation ID]
Uninstall product key
-ato [Activation ID]
Activate Windows
-dli [Activation ID | All]
Display license information (default: current license)
-dlv [Activation ID | All]
Display detailed license information (default: current license)
-xpr [Activation ID]
Expiration date for current license state
Advanced Options:
-cpky
Clear product key from the registry (prevents disclosure attacks)
-ilc <License file>
Install license
-rilc
Re-install system license files
-dti [Activation ID]
Display Installation ID for offline activation
-atp <Confirmation ID> [Activation ID]
Activate product with user-provided Confirmation ID
Volume Licensing: Key Management Service (KMS) Options:
-sprt <Port>
Set TCP port KMS will use to communicate with clients
-sai <Activation Interval>
Set interval (minutes) for unactivated clients to attempt KMS connection. The
activation interval must be between 15 minutes (min) and 30 days (max) although
the default (2 hours) is recommended.
-sri <Renewal Interval>
Set renewal interval (minutes) for activated clients to attempt KMS connection.
The renewal interval must be between 15 minutes (min) and 30 days (max) although
the default (7 days) is recommended.
-sdns
Enable DNS publishing by KMS (default)
-cdns
Disable DNS publishing by KMS
-spri
Set KMS priority to normal (default)
-cpri
Set KMS priority to low
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /ipk GBX49-K6VXX-CGHH6-GFMX7-Q2BBK Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Installed product key XXX-XXX-XXX successfully. --- C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dli Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Name: Windows(TM) Server 2003 KMS, KmsW2k3Prs edition Description: Windows(TM) Server 2003 KMS, VOLUME_KMS channel Partial Product Key: Q2BBK License Status: Unlicensed
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /ipk C9XHY-RC84R-J7WRG-P64TB-YFJR4 Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Installed product key XXX-XXX-XXX successfully. --- C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dli Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Name: Windows(TM) Server 2003 KMS, Kms3 edition Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel Partial Product Key: YFJR4 License Status: Unlicensed --- C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -dlv Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Software licensing service version: 6.0.6001.16501 Name: Windows(TM) Server 2003 KMS, Kms3 edition Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_B channel Activation ID: 56df4151-1f9f-41bf-acaa-2941c071872b Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 55041-00152-339-012961-03-1033-3790.0000-1212010 Installation ID: 002600700540253920909015959011435862047723782650125981 Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938 Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940 Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939 Partial Product Key: YFJR4 License Status: Unlicensed
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /ipk XXX-XXX-XXX
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Installed product key XXX-XXX-XXX successfully.
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dli
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
Partial Product Key: WR8JM
License Status: Unlicensed
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Software licensing service version: 6.0.6001.16501
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
Activation ID: c90d1b4e-8aa8-439e-8b9e-b6d6b6a6d975
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00152-381-010445-03-1033-3790.0000-1212010
Installation ID: 007996643452703992130493651890964074775304439261506956
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938
Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939
Partial Product Key: WR8JM
License Status: Unlicensed
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -xpr
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Windows is unlicensed
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -ato
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
This operation connects over the Internet to send the appropriate computer infor
mation, such as the types of hardware you are using and the product ID, to the M
icrosoft activation server. By using this Software, you consent to the transmiss
ion of this information. Microsoft does not use the information to identify or c
ontact you. Learn more online at http://go.microsoft.com/fwlink/?LinkID=106348
Do you want to continue [y/n]?
y
Activating Windows(TM) Server 2003 KMS, Kms4 edition (c90d1b4e-8aa8-439e-8b9e-b6
d6b6a6d975) ...
Product activated successfully.
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dli
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
Partial Product Key: WR8JM
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Software licensing service version: 6.0.6001.16501
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
Activation ID: c90d1b4e-8aa8-439e-8b9e-b6d6b6a6d975
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00152-381-010445-03-1033-3790.0000-1212010
Installation ID: 007996643452703992130493651890964074775304439261506956
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938
Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939
Partial Product Key: WR8JM
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
C:\Windows\System32>cscript c:\windows\System32\slmgr.vbs /ipk ff3cq-kdb72-9xtk9-kjjcp-y7w8r Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Run 'slui.exe 0x2a 0xC004F015' to display the error text. Error: 0xC004F015 C:\Windows\System32>slui.exe 0x2a 0xC004F015 Description: The Software Licensing Service reported that the license is not installed.
I suggest referring to the following article first:
Volume Activation 2.0 Deployment Guide http://technet.microsoft.com/en-us/library/cc303280.aspx
C:\Users\Administrator>cscript c:\windows\System32\slmgr.vbs /ipk 489J6-VHDMP-X63PK-3K798-CPX3Y Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Run 'slui.exe 0x2a 0xC004F050' to display the error text. Error: 0xC004F050 C:\Users\Administrator>slui.exe 0x2a 0xC004F050 Description: The Software Licensing Service reported that the product key is invalid.
Forum FAQ: You cannot use a KMS key to activate more than 6 computers.
Use KMS client keys to activate your KMS clients. KMS client keys are public released: Windows Server 2008 R2 Enterprise 489J6-VHDMP-X63PK-3K798-CPX3Y Windows Server 2008 Enterprise YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Virtualization
Both KMS server/host and KMS client will support running inside virtual machines. The KMS server/host can now run on a Windows Vista-based virtual machine or a Windows Server 2008-based virtual machine. So you can start considering to put the KMS server/host on a virtual machine. The KMS clients (read: all Windows Vista clients and Windows Server 2008 installations) running in virtual machines can now also be activated through the KMS server/host. However, only physical computers are added to the KMS count.
Server 2008 R2 - OEM or VOL (have KMS-key!):
My iso ie.cfg also says OEM, but, just after install, if I run slmgr -dlv, it says: Software licensing service version: 6.1.7600.16385 Name: Windows Server(R), ServerEnterprise edition Description: Windows Operating System - Windows Server(R), RETAIL channel Partial Product Key: D7P97
slmgr -dlv
Why won't my Windows 7 KMS key work on my Server 2008 KMS server? - Server Fault:
As it turns out, the version of the KMS software included with Server 2008 is version 1.1. In order to use Windows 7 and Server 2008 R2 KMS keys, you need to be running KMS 1.2. KMS 1.2 is included as part of Windows 7 and Server 2008 R2, but requires a separate download to run on Server 2008 (non-R2) or Server 2003.
I found the answer and more info on Microsoft's site: FAQ About Volume License Keys
KB article 968915 is now available and contains links to download KMS 1.2 for Windows 2003 Server. Here are direct links for x86 and x64.
KB article 968912 is now available and contains links to download KMS 1.2 for Windows Vista and Server 2008. Here are some direct links for Server 2008 (x86, x64, ia64) and Vista (x86 and x64).
Getting KMS to activate Windows Vista and Windows Server 2008 | microsoftNOW:
- "Starting with Windows Vista, Volume License Keys (VLKs) have been replaced by the Key Management Service (KMS). A KMS Server is deployed in the organization, which will respond to activation requests from client machines. Hosts activated via a KMS have to report back to that KMS key server once every 180 days.
At the place where I work, a Key Management Server was already in place and it was used for activating Windows Vista. With release of Windows Server 2008 earlier this year, we started deploying/migrating some of the workloads to the new server OS.
Windows Server 2008 also uses the KMS activation system. However, the KMS server refused to activate Windows Server 2008 computers, while Vista was OK. Upon closer examination and long discussions with Microsoft, it was discovered that the KMS key installed on our KMS server was only for Windows Vista. Microsoft calls this a "Class A" key.
In order for the KMS server to be able to activate BOTH Windows Server 2008 AND Windows Vista, we should remove the "Class A" key, replace it with a "Class B" key and then activate the KMS server. Here, the "Class B" key is nothing but the Windows Server 2008 Std/Ent – KMS key on the MVLS website. This key can not only activate WS08, it can also activate Vista!
This is how its done (from the Command Prompt):
uninstalls our "Class A" KMS key:
slmgr -upk
installs the "Class B" KMS key:
slmgr -ipk <insert Windows 2008 KMS key here>
activates the KMS server:
slmgr -ato
While using slmgr, it is important to wait 5-10 seconds after each command to get the confirmation popup box, even though command prompt will return as though nothing happened.
Once the server has successfully activated, type the following command to verify that you have a "Class B" KMS key.
slmgr -dlv
Notice that it says KMS_B channel, indicating a "Class B" KMS key that will activate both Windows Server 2008 and Windows Vista.
Remove or KILL KMS server? - Page 2 - Vista Forums:
One one machine they get Error: 0xC004f015 Run 'slui.exe 0x2a 0xC004f015' to display the error text" when they run cscript \windows\system32\slmgr.vbs /ipk YFKBB-PQJJV-G996G-VWGXY-2V3X8
Hello,
Let's try uninstalling the KMS host key first./
run slmgr -upk first
Then run slmgr /ipk YFKBB-PQJJV-G996G-VWGXY-2V3X8
the run
Thanks,
Darrell Gorter[MSFT]
Error message when you try to activate Windows Vista: "An error has occurred"
- "When you try to activate Windows Vista, you may receive an error message that is accompanied by an error code and its description.
- This article will guide you through step-by-step methods to help you resolve your problem. First, we'll take a look at your symptom, and then, based on your answer, we'll determine which of these methods we should have you try."
Ask the Core Team : Update to KB968912:
One additional caveat with this update is that if you try to install your KMS host key you may receive this error message
0xc004f015: The Software Licensing Service reported that the license is not installed.
SL_E_PRODUCT_SKU_NOT_INSTALLED
This can occur if you are trying to install a KMS host key on the incorrect KMS Host SKU. For example
* Installing a Client KMS host key on Windows Server 2008 * Installing a Group B KMS host key on Windows Server 2008 Datacenter KMS host * Installing a Group A KMS host key on Windows Server 2008 Standard, Enterprise, or Datacenter KMS host
This is by design. The following lists the type of KMS host key and the operating systems it can be installed on to setup a KMS host.
Group Definitions:
Client: Windows Vista/Windows 7 VL Editions (Business, Enterprise, Professional)
Group A: Windows Server 2008 Web, Windows Server 2008 Web, Windows Server HPC 2008, Windows Server HPC 2008 R2
Group B: Windows Server 2008/2008R2 Enterprise, Windows Server 2008/2008R2 Standard
Group C: Windows Server 2008/2008R2 Datacenter, Windows Server 2008/2008R2 for Itanium Editions
Microsoft - Top 5 Product Key Activation Challenges IT Pros Encountered and Solved (DOC)
- "Windows Vista® and Windows Server® 2008 include some significant changes relating to product activation over Windows® XP and Windows Server 2003. These changes, while simple, often caused concerns and operational challenges for IT Pros in deploying Windows. Microsoft® product support services identified the following to be the most common product activation related issues encountered by various customers who are evaluating and or deploying Windows Vista (or Windows Server 2008). Understanding these issues will help you and your team to manage the activation changes more effectively and optimize your deployment experience."
Fixing Win 7 / Server 2008 R2 issue
- Activating Windows(R) 7, Professional edition
- Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable
- Corporations with volume licensing agreement which had been setting up and using Windows Server 2003 has KMS (Key Management Service) server to provide volume activation to computers running Windows Vista and Windows Server 2008, can download an updated patch, KMS version 1.2, to extend support for Key Management Service (KMS) to provide volume activation for Windows 7 and Windows Server 2008 R2, in the event of OS upgrade or acquire of new PC with new operating systems.
- The KB968915 update installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 1 (SP1) or later versions of Windows Server 2003, and will be replacing KMS 1.1 for Windows Server 2003 (KB948003). KMS 1.2 provides support for the following KMS client installations:
- Windows Server 2008 R2
- Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
- Windows 7
- Windows Vista and Windows Vista Service Pack 2 (SP2)
- After installing KMS v1.2 with KB968915 update package, new KMS Host Key will need to be installed on the existing KMS host for Windows 7 or Windows Server 2008 R2 client to activate. Once activated, the KMS host will be able to activate all products (depending on the KMS key that is used).
- This update installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003. KMS 1.2 provides support for the following KMS client installations:
- Windows Server 2008 R2
- Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
- Windows 7
- Windows Vista and Windows Vista Service Pack 2 (SP2)
How to troubleshoot the Key Management Service (KMS):
- The Server Product Group C key, for Windows Server 2008 R2 key means that all KMS clients are supported (Windows Vista/Windows Server 2008 RTM and later).
How to Choose the Right Volume License Key for Windows:
- "With Windows, the keys are organized in product groupings. There are four product groupings that cover all of the Windows client and Windows Server operating systems. One grouping is for the client editions; the other three cover the server editions. In the figure (below) you can see the four groupings for Windows 7 and Windows Server 2008 R2, and the specific OS editions that fall into each group."
.png)
NOTE: A NEW 'VOLUME_KMS_R2_C channel' IS REQUIRED ('VOLUME_KMS_C channel')
The Software Licensing Service is version 6.0.6001.16550 after installing the KMS 1.2 update.
--- Updating License Service to KMS 1.2 ---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Software licensing service version: 6.0.6001.16550
Name: Windows(TM) Server 2003 KMS, Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_C channel
Activation ID: c90d1b4e-8aa8-439e-8b9e-b6d6b6a6d975
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00152-381-010445-03-1033-3790.0000-1242010
Installation ID: 007996643452703992130493651890964074775304439261506956
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938
Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939
Partial Product Key: WR8JM
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 33
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
--- Installing new VOLUME_KMS_R2_C channel license for Win7 and Server 2008 R2 ---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /ipk RGJY7-D2X2Y-7VK4X-DXK2M-8D9MK
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Installed product key RGJY7-D2X2Y-7VK4X-DXK2M-8D9MK successfully.
--- Activating new host key ---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs -ato
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
This operation connects over the Internet to send the appropriate computer infor
mation, such as the types of hardware you are using and the product ID, to the M
icrosoft activation server. By using this Software, you consent to the transmiss
ion of this information. Microsoft does not use the information to identify or c
ontact you. Learn more online at http://go.microsoft.com/fwlink/?LinkID=106348
Do you want to continue [y/n]?
y
Activating Windows(TM) Server 2003 KMS, W7R2-Kms4 edition (8fe15d04-fc66-40e6-bf
34-942481e06fd8) ...
Product activated successfully.
--- License details after new host key ---
C:\Documents and Settings\Administrator>cscript c:\Windows\System32\slmgr.vbs /dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Software licensing service version: 6.0.6001.16550
Name: Windows(TM) Server 2003 KMS, W7R2-Kms4 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_C channel
Activation ID: 8fe15d04-fc66-40e6-bf34-942481e06fd8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00168-305-016440-03-1033-3790.0000-1242010
Installation ID: 020260205766562811258860556503726773202030100311046296
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938
Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939
Partial Product Key: 8D9MK
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 33
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
--- Activating a Windows 7 System after new host key ---
C:\Windows\system32>cscript slmgr.vbs /ato
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Activating Windows(R) 7, Professional edition (b92e9980-b9d5-4821-9c94-140f632f6
312) ...
Product activated successfully.