The primary method of discovery is to search for a registry value “KeyManagementServiceListeningPort” in the following registry key: “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform” If your KMS is not getting discovered – you can add that registry value.Note: This MP will still create config churn as I did not change the design where the MP classes discover properties that will change often.The next window will let give you some information about the automation of the license activation for MS products and how KMS works. Continue to the next window and add the required Features. Install-WindowsFeature -Name VolumeActivation. Added basic logging to discovery scripts. Launch powershell in Admin mode and run the following CMDLET.Added number of samples (matchcount) to Service Monitor.
Changed discoveries and monitoring to more reasonable frequencies.Renamed and reduced views to make it more useable.Changed class design so source and path on alerts will contain the FQDN of the computer.Removed all manual reset monitors and switched to rules.Added discovery support out of the box for KMS on WS20 servers.This MP supports KMS on Windows Server 2012 and laterĬhanges from the original Microsoft KMS MP:
This management pack will discover and monitor your KMS servers. Many customers still use KMS activation for on-prem deployments.
0 kommentar(er)
