Microsoft 2 - Manuals

Volume Activation 2.0 Operations Guide 6 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 firew...

Volume Activation 2.0 Operations Guide 7 Issue Resolution client. 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 edition-specific. Remember to delete any unnecessary SRV res...

Volume Activation 2.0 Operations Guide 8 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...

Volume Activation 2.0 Operations Guide 9 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 ...

Volume Activation 2.0 Operations Guide 10 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 dep...

Volume Activation 2.0 Operations Guide 11 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,...

Volume Activation 2.0 Operations Guide 12 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.0000- 1752006 Activation interval: 120 ...

Volume Activation 2.0 Operations Guide 13 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 . Recovery from an Unlicense...

Volume Activation 2.0 Operations Guide 14 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 ...

Volume Activation 2.0 Operations Guide 15 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 o...

Volume Activation 2.0 Operations Guide 16 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/fwli...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 18 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 Typ...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 21 Class Name Type Description Scope Examples Slmgr SoftwareLicensingService RequiredClientCount uint32 The minimum number of clients required to connect to a Key Management Service computer to enable volume licensing. KMS client 25 S...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 22 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 (*) afte...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 24 KMS Registry Keys / Values Registry path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL Registry path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL Value Type Description Scope DisableDnsPublishing REG_DWORD Set this...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 26 Registry path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL Value Type Description Scope KeyManagementServiceRegisteredPortNumber REG_SZ Cached port number when KMS is enabled. This is mainly used when KMS computer name is ...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 29 Event ID Logg ed By Description Message Parameters Fields included in comma- delimited string Examples 12292 KMS Renewal timer initialization failure Key Management Service (KMS) failed to initialize renewal timer.%nInfo:%n%1 HRESU...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 30 Name Type Size [bytes] Description LicenseStatus DWORD 4 Licensing status 0 - Unlicensed 1 - Licensed (Activated) 2 - OOB grace 3 - OOT grace 4 - NonGenuineGrace BindingExpiration DWORD 4 Interval until expiration (minutes) AppID U...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 32 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 Activation Type Possible Ca...

Volume Activation 2.0 Operations Guide Microsoft Corporation Page 33 Error Code Error Message Activation Type Possible Cause Troubleshooting Steps hardware ID binding is beyond level of tolerance. host the drivers were updated on the system. activation. 1 KMS – Reboot or run slmgr.vbs /ato 2 0xC004F...