![]() ![]() ![]() ![]() 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.Added basic logging to discovery scripts.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 information outlines initial planning considerations that you need to review for Key Management Services (KMS).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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |