Volume Activation 2.0 Operations Guide Volume Activation 2.0 Operations Guide for Windows Vista® and Windows Server® 2008 Microsoft Corporation Published: March, 2008 Abstract Volume Activation 2.0 is designed to automate and manage the activation process for volume licensing customers. This document provides operational guidance for Microsoft Volume Licensing customers who have deployed Volume Activation 2.0 in their organization’s environment.
Volume Activation 2.0 Operations Guide This document and any document referenced herein is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user.
Volume Activation 2.0 Operations Guide Volume Activation 2.0 Operations Guide Introduction ........................................................................................................................ 4 Management Tools for Volume Activation ................................................................................ 4 Volume Activation Management Tool (VAMT) ........................................................ 4 Systems Management Server (SMS) 2003 SP3 .................................
Volume Activation 2.0 Operations Guide Introduction This guide contains information to assist you in managing the activations of volume editions of Windows Vista® and Windows Server® 2008 in your environment. Topics covered include available management tools, troubleshooting, recovery from unlicensed states, and resolving Non-Genuine issues, as well as specific information on managing each method of volume activation.
Volume Activation 2.0 Operations Guide Group Policy Support There are no specific settings for volume activation in Group Policy. However, all configuration and property data for VA 2.0 is accessible though WMI and the Windows registry, and can therefore be managed with Group Policy. Volume Activation Troubleshooting All activation events are logged. The event provider name for all activation events is Microsoft-Windows-Security-Licensing-SLC.
Volume Activation 2.0 Operations Guide Issue Resolution 12289. Check this event for the following: • Is the result code 0? Anything else is an error. • Is the KMS host name in the event correct? • Is the KMS port correct? • Is the KMS host accessible? • If the client is running a third-party firewall, do you need to configure the outbound port? On the KMS host, look in the KMS event log for event 12290.
Volume Activation 2.0 Operations Guide Issue client. Resolution The Volume Activation 2.0 Deployment Guide contains a table of setup keys that you can use to revert the computer back to a KMS client. These keys are publicly known and are editionspecific. Remember to delete any unnecessary SRV resource records from DNS and restart the computers.
Volume Activation 2.0 Operations Guide KMS initialization failures, DNS SRV publishing issues, when KMS counts drop below activation thresholds, and when no KMS activity occurs for more than 8 hours. To download the KMS Management Pack, go to the System Center Operations Manager product catalog at http://go.microsoft.com/fwlink/?LinkID=110332. This download includes a Management Pack guide that covers installation, configuration, and included rules.
Volume Activation 2.0 Operations Guide Working with 64-Bit Windows Vista KMS Hosts The OpsMgr 2005 agent is available only as a 32-bit application. As a result, 64-bit versions of Windows Vista RTM are not automatically added to the KMS computer group defined by the KMS Management Pack. KMS hosts running Windows Vista SP1 or Windows Server 2008 are not affected by this issue. Computers that are not a member of this group do not send data to Operations data warehouse.
Volume Activation 2.0 Operations Guide Programs menu. This link and the program are only in Windows Vista Business editions available through volume-licensed and retail channels. System administrators can choose to disable WAU for users by adding a registry value to the reference image before deploying Windows. When WAU is disabled and the user clicks the WAU link, the error message, shown in Figure 1, appears. This prevents the user from obtaining an upgrade license using Control Panel.
Volume Activation 2.0 Operations Guide To disable the WAU link 5. In the tree pane, click the WAU key. Right-click in the details pane, point to New, and then click DWORD (32 bit) Value. 6. Type Disabled as the name of the new value, and then press Enter. 7. Right-click the new Disabled value, and then click Modify. 8. In the Value data box, type 1 and then click OK. 9. Exit the registry editor. 10. Complete the reference image and deploy it using standard techniques.
Volume Activation 2.0 Operations Guide Key Management Service client information Client Machine ID (CMID): 45d450a8-2bef-4f04-9271-6104516a1b60 DNS auto-discovery: KMS name not available from DNS KMS machine extended PID: 11111-00140-008-805425-03-1033-5384.00001752006 Activation interval: 120 minute(s) Renewal interval: 10080 minute(s) The following is an example of the information displayed when Slmgr.vbs /dli runs on a KMS host.
Volume Activation 2.0 Operations Guide Note Both the /dli and /dlv commands work when run on retail and OEM activated computers as well. For more information about available activation methods and possible license states, see the Volume Activation 2.0 Deployment Guide.
Volume Activation 2.0 Operations Guide Figure 2: RFM Dialog box (applicable only to Windows Vista RTM) The option the user selects depends on the activation method desired. • • • • Clicking Activate Windows online now results in the system attempting to connect to either a KMS host or Microsoft hosted activation services, depending on whether the system is configured as a KMS client or has a MAK installed. Users who need to purchase a product key should click Buy a new product key online.
Volume Activation 2.0 Operations Guide In Windows Vista SP1 and Windows Server 2008, RFM is removed from the product and replaced with a notifications-based experience. You can return a client to its initial activation state for the current license by using the Slmgr.vbs script with the /rearm option. This option resets the computer’s activation timer and reinitializes some activation parameters, including a KMS client’s client computer ID (CMID).
Volume Activation 2.0 Operations Guide should first 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, it must visit the Genuine Microsoft Software Web site at http://go.microsoft.com/fwlink/?LinkId=64187 for a validation to change the Non-Genuine state to Genuine.
Volume Activation 2.0 Operations Guide that contains a valid Windows marker in the ACPI_SLIC table or purchase new computers that have an operating system and a valid BIOS installed.
Volume Activation 2.0 Operations Guide Appendix 1: WMI Software Licensing Classes and Properties VA 2.0 uses Slmgr.vbs to make configuration changes. Slmgr.vbs uses WMI to access WMI classes and properties. WMI Properties Required Privilege: Standard User Class Name Type Description Scope Examples SoftwareLicensing Product SoftwareLicensing Product ApplicationID string All Description string The ID of current product's Application.
Volume Activation 2.0 Operations Guide Class Name Type Description Scope Examples Slmgr SoftwareLicensing Product LicenseStatus uint32 All 1 dli SoftwareLicensing Product MachineURL string License status of this product's application. 0=Unlicensed, 1=Licensed, 2=OOBGrace, 3=OOTGrace, 4=NonGenuineGrace. Software licensing server URL for the binding certificate. http://go.microsoft.
Volume Activation 2.0 Operations Guide Class Name Type Description Scope Examples Slmgr SoftwareLicensing Service KeyManagement ServiceCurrentC ount uint32 KMS 50 dli SoftwareLicensing Service KeyManagement ServiceFailedRe quests KeyManagement ServiceLicensed Requests KeyManagement ServiceMachine uint32 The count of currently active volume clients. -1 indicates the computer is not enabled as a Key Management Service or has not received any client licensing requests.
Volume Activation 2.0 Operations Guide Class Name Type Description Scope Examples Slmgr SoftwareLicensing Service RequiredClientC ount uint32 KMS client 25 SoftwareLicensing Service SoftwareLicensing Service Version string All 6.0.5378.0 dlv VLActivationInte rval uint32 KMS, KMS client 120 dli SoftwareLicensing Service VLRenewalInter val uint32 The minimum number of clients required to connect to a Key Management Service computer to enable volume licensing.
Volume Activation 2.0 Operations Guide Required Privilege: Administrator Note: This is enforced by the Software Licensing Service and registry ACLs. A registry override in Windows Vista allows a standard user to call specific methods. These are designated with (*) after the method's name.
Volume Activation 2.
Volume Activation 2.
Volume Activation 2.0 Operations Guide Registry path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL Value KeyManagementServiceVersion Type REG_SZ UserOperations REG_DWOR D Description Set this for MOM automatic discovery of the Key Management Service (current default is to use the WMI SoftwareLicensingService Version property). Delete this value if the KMS is no longer functional on the computer. Create and set to 1 to enable standard users to install product keys, activate, and rearm computers.
Volume Activation 2.0 Operations Guide Registry path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL Value KeyManagementServiceRegisteredPortN umber Type REG_SZ DiscoveredKeyManagementServiceName REG_SZ DiscoveredKeyManagementServicePort REG_SZ CustomerPID REG_SZ Description Cached port number when KMS is enabled. This is mainly used when KMS computer name is changed so it republishes DNS RR. No default. This is KMS side registry setting.
Volume Activation 2.0 Operations Guide Event ID Logg ed By Description Message Parameters Fields included in commadelimited string Server:Port Name:port CMID Client Machine ID Client Time VM Info Licensing Status Time to Expiration ActID N-Policy 12289 Client After KMS response validation (client) The client has processed an activation response from the key management service computer.
Volume Activation 2.0 Operations Guide Event ID Logg ed By Description 12290 KMS KMS server side log for each request Message An activation request has been processed.
Volume Activation 2.0 Operations Guide Event ID 12292 Logg ed By KMS 12293 KMS 12294 KMS Description Renewal timer initialization failure DNS RR publishing failure DNS RR publishing success Message Key Management Service (KMS) failed to initialize renewal timer.%nInfo:%n%1 Publishing the Key Management Service (KMS) to DNS in the '%2' domain failed.%nInfo:%n%1 Publishing the Key Management Service (KMS) to DNS in the '%1' domain is successful.
Volume Activation 2.
Volume Activation 2.
Volume Activation 2.0 Operations Guide Appendix 2: Troubleshooting by Error Code The following table provides troubleshooting help when using volume editions of Windows Vista and Windows Server 2008 operating systems. Error Code Error Message Activatio n Type Possible Cause Troubleshooting Steps 0xC004C001 The activation server determined the specified product key is invalid MAK Invalid MAK entered. Verify the key is the MAK provided by Microsoft.
Volume Activation 2.0 Operations Guide Error Code Error Message Activatio n Type Possible Cause Troubleshooting Steps hardware ID binding is beyond level of tolerance. host the drivers were updated on the system. activation.1 0xC004F014 The Software Licensing Service reported that the product key is not available MAK/KMS client No product keys are installed on the system. Install MAK product key or install KMS Setup key found in \sources\pid.txt on the installation media.
Volume Activation 2.0 Operations Guide Error Code Error Message Activatio n Type computer could not be activated. The Key Management Service (KMS) is not enabled. Possible Cause Troubleshooting Steps KMS request is not answered. (default) is not blocked by a firewall or otherwise filtered. 0xC004F041 The software Licensing Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated. KMS client KMS host is not activated.
Volume Activation 2.0 Operations Guide Error Code Error Message Activatio n Type the valid non-genuine period. 0xC004F066 Possible Cause Troubleshooting Steps determined the system is not Genuine. The system will continue to run during the NonGenuine grace period. the end of the grace period. The Software Licensing Service reported that the product SKU is not found. MAK/KMS client Volume media has been used with a nonVolume key. Match the product key to the OS edition.
Volume Activation 2.0 Operations Guide Error Code Error Message Activatio n Type Possible Cause Troubleshooting Steps 0x800706BA The RPC server is unavailable. KMS client Firewall settings are not configured on the KMS host or DNS SRV records are stale. Ensure the KMS port is allowed access through the firewall on the KMS host or ensure SRV records point to a valid KMS host. The KMS client cannot find KMS SRV resource records in DNS. Troubleshoot network connections and DNS.
