Article ID: 968940 - View products that this article applies to.
Microsoft Office Communication Server 2007 R2 SCOM Pack QoE Monitoring provides media quality monitoring for Mediation Server, for A/V Conferencing Server, and for Location. However, if you have more than 100 instances for each category (Mediation Server, A/V Conferencing Server, or Location), some of instances do not appear in the SCOM console.
SCOM QoE Monitoring uses performance counters that are published by the Office Communication Server Monitoring Server. This issue occurs because the maximum number of instances that can be published for Mediation Servers and for A/V Conferencing Servers by the Office Communication Server Monitoring Server is 100.
To resolve this issue, apply the following update:
However, this hotfix does not affect the maximum number of performance counter instances that are published for network location monitoring. If you have more than 100 subnets that you want to monitor, we recommend you use imported location instead of subnet monitoring. For more information, visit the following Microsoft Web site:
The SCOM agent has memory usage thresholds. By default, the limitation on memory in both Health Service and Monitoring Host is 100 MB private bytes. This means that Health Service or Monitoring Host can use 100 MB at most.
We recommend that you increase the threshold if you want to monitor more than 250 instances (including Mediation Server, A/V Conferencing Server, and Location) or if you notice that the following event is logged:
Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6024
Time: 10:29:16 AM
Description: RestartHealthService.js : Restarting Health Service. Health Service exceeded Process\Private Bytes threshold.
How to increase the thresholdTo update the agent restart threshold, follow these steps: