Assure the Performance of Your Microsoft OCS Environment

With NetIQ® AppManager® for Microsoft® Office Communications Server (OCS), you can monitor the operation and performance of your Microsoft Unified Communications environment. This module raises events in your NetIQ AppManager console when problems arise and collects information you can use for trend analysis and reporting. Flexible monitoring policies allow you to meet the unique needs of different users and environments, while the out-of-the-box Knowledge Scripts get you started quickly.

Microsoft AppMgr.gif
 

This module is part of our comprehensive solution that monitors the experience of the Microsoft OCS user, intelligently profiles the performance of the server, and delivers event correlation and automation.

Features and Benefits

Call server health monitoring. Gives you proactive health monitoring, detecting potential problems before they impact your Microsoft OCS users.

Automated event response. Allows you to set up event-driven actions easily-such as sending an e-mail or a pager alert, generating an SNMP trap to a network manager or running a corrective fix program-to execute automatically when a specific event occurs.

Comprehensive reporting. Monitors server resource usage down to the end-user level, while providing you with prepackaged performance, traffic, and service-level agreement reports. Also stores performance data to enable trend analysis.

Reduced support costs. Eliminates wasted effort during troubleshooting by providing you with centralized visibility and detailed reporting of the distributed communications environment.

Rapid time to value. Implement monitoring quickly with prepackaged Knowledge Scripts, which includes industry best practices for monitoring your Microsoft OCS environment

What’s Monitored
NetIQ AppManager for Microsoft OCS monitors the following components of Microsoft Unified Communications:

    • Archived VoIP Call Activity. Monitors the various VoIP call metrics contained in the CDR database.
    • Conference Call Activity. Monitors the number of active conferences and how many users are in those conferences.
    • CW AIM Failures. Monitors the current IM session failures on the Communicator Web Access (CWA) server.
    • CW AIM Session Activity. Monitors the current IM sessions on the CWA server.
    • CWA Server Status. Monitors the CWA server status for throttling states.
    • CWA User Session Activity. Monitors the current user sessions on the CWA server.
    • CWA User Session Failures. Monitors the current session failures on the CWA server.
    • Edge Server Call Activity. Monitors current call activity metrics for the Edge server.
    • Edge Server Call Failures. Monitors current call failure metrics for the Edge server.
    • Health Check. Monitors the running status of primary services of the OCS server.
    • IIS Server CPU Utilization. Monitors the CPU utilization of the IIS server running the CWA site.
    • IIS Server Health Check. Monitors service availability of the IIS server running the CWA site.
    • IIS Server CPU Process. Monitors the CPU utilization of IIS processes: dllhost, MTX, aspnet_wp, and w3wp and kills the process if it exceeds the specified threshold.
    • IIS Server Memory High. Monitors the memory pool of the IIS server running the CWA site.
    • IIS Server Restart. Restarts the IIS server running the CWA site.
    • IIS Server. Service Up Time Monitors time since last reboot for the IIS server running the CWA site.
    • MCU Status. Monitors the status of various services installed on the OCS server.
    • Mediation Server Call Activity. Monitors inbound and outbound call activities on the Mediation server.
    • Mediation Server Call Failures. Monitors the MediaRelay engine components of the Mediation server.
    • Mediation Server Health. Monitors server health metrics for the Mediation server.
    • Mediation Server Usage. Monitors server resource usage for the Mediation server.
    • Session Call Activity. Monitors data about the number of current sessions.
    • Session Call Failures. Queries the Call Detail Record server to find any known session failures.
    • System Uptime. Monitors the length of time a system has been up and running since a reboot.
    • System Usage. Monitors the total CPU usage of the server using OCS.
    • Discovery OCS. Discovers servers with OCS installed, including Mediation and Edge servers.