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...70 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
I'm using a Mac and open the web console of SCOM 1807 in Chrome or Safari. Clicking on a result in Results pane, I get only a couple of lines in the Details pane. Although I can drag and drop the grey line between the Results and Details pane, it constantly reverts to it's former position.12 votes
Planned for SCOM 2019 UR1
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.119 votes
Please leave your email id in comments if you would like to test this fix.
When using the Edge browser to view the web console, you are unable to resize any of the sections. When you click on a border, you will get a error icon (red circle with red line).4 votes
Release planned for SCOM 2019 UR1
Do any of you have a requirement to use gMSA accounts in your SCOM environment? If you do, please upvote this suggestion and kindly add the scenario you hope to use it for and how it would help you.290 votes
- Don't see your idea?