Environment
Cisco Call Manager 3.x
Cisco Call Manager 4.x
Situation
Resolution
To resolve the problem you must exclude the temporary folder defined as the %TEMP% under evironmental variable under My Computer|Properties|Advanced|Environmental Varibles for the user account the netiqmc service is running under.
Cause
The follow knowledge scripts create a temporary file under the TEMP folder specified by the environmental variable %TEMP%:
NT_CpuLoaded
NT_DNSConnectivity
NT_DynamicLogicalDiskSpace
NT_FindFiles
NT_FolderFileCount
NT_FolderSize
NT_LogicalDiskSpace
NT_MemByProcess
NT_NetSession
NT_PrinterQueue
NT_ProcessUp
NT_ServiceDown
NT_SharedFiles
NT_TopCpuProcs
NT_TopMemoryProcs
If this folder is not excluded from real time virus scanning the netiqmc.exe process may spike the processor utilization or the processor utilization may stay
at over 90% for an extended period of time. The latter has proven to be problematic at times and cause critical Call Manager services to crash.