Monitoring Server Component

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

Topic Last Modified: 2013-06-26

Microsoft Office Communications Server 2007 R2 Monitoring Server is an optional server role for both Office Communications Server Standard Edition and Office Communications Server Enterprise Edition. This component collects two types of data:

• Quality of Experience (QoE) data: numerical data that indicates the quality of your network media, and information about participants, device names, drivers, IP addresses, and endpoint types involved in calls and sessions.

• Call Detail Records (CDR): usage information related to Voice over IP (VoIP) calls, instant messaging (IM) messages, audio/video (A/V) conversations, meetings, file transfers, application sharing, remote assistance, and file transfers. CDR data does not include the content of IM messages.

Monitoring Server consists of the CDR and QoE services and their associated databases, which are always installed together in a single SQL Server instance and are known collectively as the Monitoring database.

If you deploy Monitoring Server, you can choose one of the following configurations.

For Standard Edition

• Collocate the Monitoring service with the Monitoring database on a computer that is separate from the computer running Standard Edition.

• Collocate the Monitoring service with the Monitoring database on the computer running Standard Edition.

  Note

  This configuration is appropriate for very small deployments only.
  If the Monitoring database is collocated with a Standard Edition server, you still need to install a full edition of SQL Server on the server. For details about supported versions, see Internal Office Communications Server Component Requirements.

For Enterprise Edition

• Install the Monitoring service and the Monitoring database on separate computers.

• Collocate the Monitoring service with the Monitoring database on a single computer.

• Install the Monitoring service on a separate computer and collocate the Monitoring database with the Back-End Database in the same SQL Server instance.

• Connect two Enterprise pools to the same Monitoring Server.

• Connect multiple Monitoring services running on separate computers with a single Monitoring database running on a different computer.

  Important

  The purge time for the Monitoring services must be specially configured to support this topology. A SQL Server lock condition can occur if multiple Monitoring services attempt to purge data at the same time. For details about configuring the purge time, see Configuring Retention of QoE and CDR Data.

• Install the Monitoring service on a separate computer and collocate the Monitoring database with other third-party SQL Server applications on a shared server, but in separate SQL Server instances.

The Monitoring database can be a single SQL Server computer, or alternatively, a virtual SQL Server instance running in a cluster. A SQL Server cluster improves availability by providing failover capabilities.