I’m no closer to solving the CPU dramas that we’re having with our test installation of Systems Center Operations Manager 2007.

So far, I’ve removed the agents from the environment and removed most of the management packs from the SCOM server. The Operations Manager Health Service on the SCOM server still goes nuts periodically, and it’s only monitoring itself. Restarting the Health Service results in 100% CPU for 10 - 15 minutes.

I’ve run Process Explorer to investigate what is causing the CPU usage - it appears to be some routines within HealthServiceRuntime.dll, launched by MonitoringHost.exe. While that might be useful to a SCOM developer, unfortunately, it doesn’t help me get any closer to the solution.

Is anyone else experiencing this problem? Unfortunately, I won’t have much time to look at it over the next few weeks.