SKU-specific cached KMS host (This is the cached identity of the host used in the last successful KMS activation.)ĭNS auto-discovery ( weight and priority honored) Global value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\KeyManagementServiceName REG_SZ registry value SKU-specific value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\AppID\SKUID\KeyManagementServiceName REG_SZ registry valueĪppID-specific value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\AppID\KeyManagementServiceName REG_SZ registry value When KMS auto-discovery is enabled (default) and KMS host caching is not disabled, KMS clients will use the following order to determine which KMS to use (they will try each step until an activated KMS host with the correct key responds): After 15 minutes, the system stops monitoring for qualifying events but still attempts every Activation Interval minutes. If it fails, the system will watch for network changes or other qualifying events to trigger another attempt. If it succeeds, the 180-day period is reset. The client is activated for 180 days but still attempts reactivation every Renewal Interval minutes-by default, 7 days. Activation renewal operates as a sliding window, similar to a Dynamic Host Configuration Protocol (DHCP) lease. When KMS activation succeeds, the client receives and stores the KMS host’s Renewal Interval, and Windows activates for 180 days. By default, this happens every two hours.
In operation, the KMS client attempts to contact a KMS host on startup and again every Activation Interval minutes upon failure. This value can be set on the client but will be overridden by the value that the KMS host provides. The default value is 10,080 minutes (7 days). This value can be set using slmgr /sri interval. The KMS Renewal Interval determines how often the KMS client attempts reactivation with KMS, once it has been activated. Once a system contacts a KMS host, the KMS host setting will override the local client setting. See the sections “Slmgr.vbs Options” and “Registry Settings” for more information. This value is set on the client by running slmgr.vbs /sai. The KMS Activation Interval determines how often the KMS client attempts activation before it is activated. KMS activation timing is controlled by two settings: the Activation and Renewal timers:
Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2 On this page
0 kommentar(er)
