We have observed multiple cases of the application of the stock system monitors on Windows 2008 R2 endpoints resulting in unacceptably poor performance on the endpoint. I was unable to identify any specific processes or services as the culprit, but non-service CPU utilization was persistently at 80+%.
In the absence of an substantial response from Kaseya support, I was able to resolve the issue by manually stopping and removing the Kaseya-created performance monitor objects and rebooting (and by removing all Kaseya monitors from the affected endpoints). On one hand, this leaves us unable to use Kaseya to monitor performance on the affected endpoint. On the other hand, the ONLY performance issues we've experienced on this endpoint were caused by Kaseya monitoring.
Has anyone experienced anything similar or does anyone have any thoughts?
thanks,
Lee
