When monitoring the Windows 2016 Failover Cluster disks, the script (Microsoft.Windows.Server.MonitorClusterDisks.vbs) times out and also causes the clussvc.exe to use excessive amount of CPU usage (on average 25% with peaks to 100%) if the cluster has a higher amount of physical disks (100). The systems are physical servers, with Xeon CPUs (8 physical cores + HT). The script does eventually finish if ran manually, but it needs 25 minutes...67 votes
We have a bug tracking this issue.
We generally check the catalog regularly for updated Management Packs in SCOM 2012 R2. The catalog is currently showing what appear to be incorrect versions of the MPs for the customers still on 2012 R2:
It might be a good idea to correct this, since these versions will break UNIX/Linux monitoring in SCOM 2012 R2, at the very least agent deployment will be broken.1 vote
We have fixed this, please verify and comment
The SCOMpercentageCPUTimeCounter (vbs or ps1) used by Agent processor utilization rule and monitor runs on each agent every 5 minutes (321 sec) and with a sync time set to 00:00.
This causes CPU spike on virtualization hosts.110 votes
Please leave your email id in comments if you would like to test this fix.
- Don't see your idea?