Chat now with support
Chat with Support

Unified Communications Diagnostics 8.5 - User Guide

About Unified Communications Diagnostics Getting Started Using the Management Console Introducing Management Console health tests Health tests available from the Exchange organization node
About the Exchange-based health tests Exchange Server Health Test Prerequisites for Exchange Delivery Health Tests Exchange Internal Server Delivery Health Test Exchange Internal Mailbox Delivery Health Test Exchange External Message Delivery Health Test Exchange Modern Message Delivery Health Test Exchange Storage Health Test Exchange Queue Health Test Internal Outlook Web Access (OWA) Availability Health Test External Outlook Web Access (OWA) Availability Health Test Exchange Replication Health Test Exchange System Health Test Active Directory Account Lockout Health Test Exchange Online Connectivity Health Test Exchange Online Mailbox Logon Health Test Exchange Online Message Delivery Health Test Office 365 Subscription Health Test BlackBerry Server Health Test BlackBerry Message Delivery Health Test Creating test mailboxes for Exchange Adding health sets for Exchange System health tests Configuring Exchange impersonation for the Modern Message Delivery health test
Health tests available from the Lync/Skype for Business Environment Resolving Problems with Native Tools Launching the Diagnostic Console from the Management Console Launching UC Analytics from the Management Console Diagnosing Problems using the Diagnostic Console UC Diagnostics: Exchange 2007 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2010 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2013 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2016 Diagnostic Console (Plug In) UC Diagnostics: BlackBerry Diagnostic Console (Plug In) UC Diagnostics: OCS Diagnostic Console (Plug In) UC Diagnostics: Lync 2013 or Skype for Business 2015 Diagnostic Console (Plug In) Reporting Using Web Reports Counters with Non-Zero Alarm Values

When Connecting to OCS

You may see your service account in the security log of the OCS environment that is being monitored. If you are using the OCS Diagnostic Console, you connect to the OCS server using the user credentials of the user who is currently logged in. Kerberos logs events in the event log during authentication.

Before you launch and connect to the OCS Diagnostic Console, read OCS related information on Active Directory. You need read access to the following:

•
Perfmon on the target server
•
Event Logs on the target server
•
Back-End database tables (rtc and rtcdyn) for the pool where the target server is located
•
Back-End database stored procedures (rtc and rtcconfig) for the pool where the target server is located
To get read access on OCS
1
Create a new domain security group named "OCS Diagnostic Users".
2
Connect to the OCS Back-End server using SQL client tools.
3
Assign to the "OCS Diagnostic Users" group the database roles of "db_datareader" and "public", for the rtc, rtcconfig, and rtcdyn databases.
4
Add the "OCS Diagnostic Users" group to the TRCUniversalReadOnlyAdmins domain security group.
This provides read access to the OCS data in Active Directory.
5
Add the "OCS Diagnostic Users" group to the Power Users and Performance Monitor Users local security groups on each OCS server.

Understanding the OCS Diagnostic Console

When you connect to the Diagnostic Console, the home page displays a high level summary of your OCS server.

The home page contains the various panels, message flows, and drilldowns to help you perform an extensive analysis of the major components on your OCS server.

To view detailed information on your specific components, right-click a component, message flow, and drilldown, and select What’s This, Metrics, or Properties.

Panels
OCS Message Flows
OCS Drilldowns
Metrics

Panels

The Diagnostic Console contains the following panels:

•
Server Information Panel
•
Clients/Network Panel
•
Server Load Panel
•
Server Roles Panel
•
OS/Subsystem Panel

Server Information Panel

The Server Information panel, located below the toolbar, displays information about the OCS environment you are currently viewing. This information includes:.

 
Table 1. OCS server information panel.
Component
Description

OCS Version

Indicates the OCS version to which you are connected - either OCS 2007 or OCS 2007 R2.

Server FQDN

Indicates the Fully Qualified Domain Name of the server being monitored.

Operating System

Indicates the operating system running on the server being monitored.

OCS Pool

Indicates the name of the pool to which the server being monitored belongs.

Back-End Database

Indicates the server (and possible instance) hosting the Back-End database for the pool.

Server Certificate (CRT) Status Ball

Validates the identification of the remote server.

AS Status Ball

Indicates if the Application Sharing (AS) server is present and registered in the environment. Use the drilldown to monitor the performance and requests of the AS Server.

The AS Status Ball is active only if you are connected to an OCS 2007 R2 server.

QMS Status Ball

Indicates that there is a Quality of Monitoring Experience (QMS) server configured in the environment. Use the drilldown to see what server(s) is (are) hosting the role.

CDR Status Ball

Indicates there is a Call Details Report (CDR) Server Role configured in the environment. Use the drilldown to see what server(s) is (are) hosting the role.

CWA Status Ball

Indicates there is a Communicator Web Access (CWA) Server Role configured in the environment. Use the drilldown to see what server(s) is (are) hosting the role

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating