Communication Monitoring Server 2007 R2 cannot support more than 100 instances of Mediation Server or of A/V Conferencing Server

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:

• 967837  (http://support.microsoft.com/kb/967837/ ) Description of the update package for Office Communications Server 2007 R2, Monitoring Server: April 2009

If you have a scenario in which more than 100 instances of Mediation Server or A/V Conferencing Server are deployed, and you apply this update, you can monitor up to 500 instances of Mediation Server or of A/V Conferencing Server.

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:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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:

How to increase the threshold

To update the agent restart threshold, follow these steps:

1. In the authoring section of the console, find the Monitoring Host Private Bytes Threshold Rule in the Performance category for the Agent class.
2. Override the value for a specific object, and then select the target agent. You can also override the value for all instances of agents.
3. Set the threshold to 418430400 (400MB). Note that you should not store the override in the Default Management Pack.
4. Follow these steps for the Health Service Private Bytes Threshold Monitor.
   
   Note To prevent the agent from being disabled, follow these steps for the Agent class.