Active Directory agents using WinRM connection to Windows 2012/2012 R2 Domain Controllers cause CPU utilization to spike to 100% on monitored servers.
This issue does not happen if DCOM is used instead of WinRM
Workaround:
(Recommended) Create a Domain Local Group in an OU in the AD domain as per MSDN discussion thread.
-OR-
Increase MaxEnvelope size setting of WinRM by running below command on monitored DC, as documented under Troubleshooting section of Active Directory cartridge Release Notes:
winrm set winrm/config @{MaxEnvelopeSizekb="1000"}
Then restart Widows Remote Management service
-OR-
Modify REG key permissions on monitored DCs as documented under System Requirements section of Active Directory cartridge Release Notes and then configure Active Directory agent to use DCOM instead of WinRM.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center