サポートと今すぐチャット
サポートとのチャット

Unified Communications Diagnostics 8.6.2 - 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 Registering UC Diagnostics with the Microsoft Azure portal
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

Introducing the OCS Diagnostic Console

Introducing the OCS Diagnostic Console

The Diagnostic Console provides you with a real-time representation of the messaging system processes and components within OCS (Office Communications Server). The Diagnostic Console can perform real-time monitoring on Front-End and Conferencing servers only.

The Diagnostic Console retrieves a large amount of data from a server frequently, which can place excessive stress on a server, affecting the server's performance. Also, using the Diagnostic Console for an extended period of time can consume critical system resources, affecting the stability of UC Diagnostics. It is recommended that the Diagnostic Console view a maximum of 10 servers at any one time.

The Diagnostic Console contains the following:

•
Home pages that highlight targeted areas of the OCS server activity.
•
Graphical flows that illustrate the rate at which data is moving between server components. Colorful buttons, gauges, queues, spinners, and containers display the value of key statistics and metrics.
•
Visual warnings if the performance metrics exceed acceptable thresholds, which you can adjust. The buttons, gauges, queues, and other visual objects, collectively referred to as components, change color to show you the source of the problem.
•
Warning messages that are displayed well before the traffic levels of a server become critical.
•
A range of reports and graphs that provide you with detailed information about a server. You can view this information on the screen or you can print it.

If you are using the Diagnostic Console as a monitoring tool, you must disconnect from, then reconnect to the Diagnostic Console daily. Though the Management Console can run tests when it is closed, the Diagnostic Console cannot perform any actions when it is closed.

For information about software prerequisites and the permissions required to run the diagnostic console on OCS, see the Unified Communications Diagnostics Deployment Guide.

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
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択