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.
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...