Hello everyone, We are experiencing major problems with our Operations Manager 2007 R2 environment. On multiple servers running Windows Server 2008 SP2 we currently have the issue of CPU usage going to a 100% whenever the SCOM agent is running, if we stop the healthservice the cpu usage goes down. So far we tried all kinds of solutions. Usually a simple reboot or deleting the health service state en recreate it by starting the healthservice helps for a few days and then the cpu usage is back again. It seems to be that the Wmiprsve.exe is causing the trouble. Whenever we stop the healtservice the CPU usage seem to be significant lower but Wmiprsve.exe is still using about 25% CPU, so it seems that the problem is in wmiprsve.exe more then in the SCOM agent but that the agent triggers the problem to a critical rate. We already installed a hotfix that we could find searching this problem: http://support.microsoft.com/kb/974051 and we tried to install http://support.microsoft.com/kb/970067 but it says it's not for our system. Now we currently had to disable the agent leaving a couple of our servers unmonitored. Because the problem keeps returning we can't enable the agent because it occurs on both terminal servers as SQL servers. I think that this problem occurs in Windows server 2008 SP2 because our Windows server 2008 SP1 servers don't have this problem untill now. I hope someone can help me with this problem. Regards, Dave

Try these: http://support.microsoft.com/kb/2505348/en-us http://support.microsoft.com/kb/981314/en-us Regards, Marc Klaver http://jama00.wordpress.com/

Hello, Thanks for your reply! I tried both hotfixes but since my system is Windows server 2008 SP2 and the hotfixes are for Server 2008 R2 the updates won't install. Also to add some extra information the cpu usage of Wmiprsve.exe is also very high whenever we open Task Manager or Services.exe Regards, Dave

Hi, Try also going through this article of hotfixes http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx Are you experiencing this only on servers that are virtualized? I have seen one vcpu machines could be similarly affected as there is only one core to do the job even though it wouldn't take 50% of cpu time when using 2 vcpu's. -TeroMCT | MCSE | MCITP | MCTS SCOM, SCCM, SCVMM, SCDPM | Open CITS

Try these: http://support.microsoft.com/kb/2505348/en-us http://support.microsoft.com/kb/981314/en-us Regards, Marc Klaver http://jama00.wordpress.com/

Hello, The servers i mentioned in this example are indeed virtualized. 2 of the servers use Xenserver 5.5 with 2 vpcu and 1 uses Xenserver 5 with 4 vcpu. I will have a look into the hotfix list you provided. Regards, Dave

Hello, I looked into the list of hotfixes/tips. There aren't really any hotfixes that are either not installed or for our system. As for the vcpu issue is there anything we could do about that so maybe it would solve our problem? Regards, Dave

Hi, Well I would recommend having always minimum of 2 vcpu's. That is "modern" to have more than one core in windows. That's how you can ensure that OS works optimally so that one bad executable can't jam/crash the OS totally. This seems to help in the cases that I have seen issues on virtual machines that had problems. There was also a case where I saw that agents started to use a lot of CPU when agents were SP1 level but the infrastructure was updated to R2. If these things don't help, then you need to start debugging what the SCOM agent is actually running when it hits 100%. -Tero MCT | MCSE | MCITP | MCTS SCOM, SCCM, SCVMM, SCDPM | Open CITS

See also this link: there is a problem in the networking monitoring

Hello, When doing some research on the servers i found out the problems are not only caused by the Operations manager agent only that the SCOM agent makes it worse. After having the agent disabled for a few days the 100% CPU problems were gone but whenever i start Event viewer, services, explorer or task manager i see the CPU usage go up caused by the wmiprsve.exe only the CPU isn't going to 100% like when we enable the SCOM agent but it does cause performance problems. Could there be any general problems with wmiprsve.exe which are made worse by the SCOM agent? Regards, Dave

This is a well known issue with MOM/SCOM agents and often not easy to put a finger on the exact cause of why an agent is suddenly using a lot of CPU on sertain servers, while other servers are unaffected. WMI can be one of the culprits in this. Through my years (from MOM 2005 to SCOM 2007 R2) I have encountered this problem time and again on various sites. - Are there an exceptional amount of events being generated on the affected server? - Other applications/services already using a fair amount of available resources? - WMI (Windows Management Instrumentation) whoes? If none of the above. The quickest and easiest workaround is to create a scheduled task that stops and starts the MOM/SCOM Agent once or twice a week on the affected server(s). Most of the time this will resolve the High CPU issue with MOM/SCOM Agents. In other cases, when WMI is playing up, then unfortunately the problems might run much deeper. If you are lucky, restarting the WMI service (with IPHelper service as dependency) might resolve the issue. If you are unlucky, you are dealing with a corrupt repository. And while there are plenty of articles on the net with how to rebuild the repository. I would seriously spare me the trouble and seriously consider to just reinstall the affected server/VM instead.

This is a well known issue with MOM/SCOM agents and often not easy to put a finger on the exact cause of why an agent is suddenly using a lot of CPU on sertain servers, while other servers are unaffected. WMI can be one of the culprits in this. Through my years (from MOM 2005 to SCOM 2007 R2) I have encountered this problem time and again on various sites. - Are there an exceptional amount of events being generated on the affected server? - Other applications/services already using a fair amount of available resources? - WMI (Windows Management Instrumentation) whoes? If none of the above. The quickest and easiest workaround is to create a scheduled task that stops and starts the MOM/SCOM Agent once or twice a week on the affected server(s). Most of the time this will resolve the High CPU issue with MOM/SCOM Agents. In other cases, when WMI is playing up, then unfortunately the problems might run much deeper. If you are lucky, restarting the WMI service (with IPHelper service as dependency) might resolve the issue. If you are unlucky, you are dealing with a corrupt repository. And while there are plenty of articles on the net with how to rebuild the repository. I would spare me the trouble and seriously consider to just reinstall the affected server/VM instead.