Confirmed by MS Premier Support. This rule does not do anything else than to log the event. The monitors using the event are disabled by default. It is totally safe to disable, and as long as you have *any* other event collected by SCOM you have confirmation of event collection work
Is it possible to get an official comment on this? I could disable the following rule http://systemcenter.wiki/?GetElement=Microsoft.SystemCenter.AgentManagement.LogEndToEndEvent&Type=Rule&ManagementPack=Microsoft.SystemCenter.2007&Version=7.3.13142.0
But i'm not sure that's good, but how often is event log collection on an agent broken?
Hi Kevin, yes, we noticed the cpu impact on our hosts. Managed to track it down to that particular script using perf.mon etc. over a few hours. Not a problem for a single VM but for a host you will see CPU wait time etc caused by this as all VM's want to run at the exact same time.
Added a few screen shots. one for a VM and one for the host who struggle the most
6 votes0 comments · General Operations Manager Feedback » Azure Management Pack · Flag idea as inappropriate… · Admin →
It could be improved but there's a cmdlet for creating maintenance schedules
Please leave your email id in comments if you would like to test this fix.
Yep, i havent tought about it earlier, but I was investigating with a colleague from our data center department and we pin pointed it to cscrcript which let me think of scom.
We dont use this data, so it's disabled now.