07-19-2007 03:16 AM - edited 03-14-2019 10:39 PM
Hi all,
Have anyone got problem with winmgmt.exe process in Call Manager ?
Currently I'm using CCM 4.1(3)SR4D. I know that the cause of winmgmt spiking is the monitoring software Cisco Unified Operations Manager 2.0. Currently I disable the WMI service in Call Manager, but as a result my monitoring service doesn't work. Any solution so Call Manager and monitoring software can both work without disturbing each other ? This is quite a dilemma.
Great thanks all.
Wiyandi
07-23-2007 12:43 AM
There is a known bug, fixed in new versions of the OS 2000.4.X. If you have the latest version and the problem still occurs open a TAC case.
07-24-2007 12:34 AM
Hi,
I have checked my servers, and the logging level is already set at "Errors only", but the problem still occurs. I'm using OS 2000.2.7.
Thanks.
Wiyandi
10-25-2007 11:05 PM
Hi,
Have you already resolve this issue because im also having same problem but for me I installed Operation manager 2.0.1.
I appreciate if you help me.
Thanks
10-26-2007 05:00 AM
We have had problems with winmgmt.exe spikes caused by CUOM, and I think we are finally over them. There are at least two bugs that could be leading to your problems...
CCM OS - as referenced above you need to upgrade your OS (via the Cisco provided upgrades, and patches) to cover for the Microsoft bug. I am now on 2000.4.4aSR10
CUOM interoperability - the bug CSCsh75491 (in new Bug Tool) specifically references CUOM causing the CPU spike. I did the work-around, and have since upgraded from 2.0.0 to 2.0.1 on CUOM to get the bug fix.
Here is a link to the CUOM bug...
I hope this helps,
--Joe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide