지금 지원 담당자와 채팅
지원 담당자와 채팅

Unified Communications Diagnostics 8.6.3 - 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

BlackBerry Diagnostic Console Recommendations

The BlackBerry Diagnostic Console provides a real-time representation of the messaging system processes and components within your BlackBerry server. The Diagnostic Console retrieves a large amount of data from a server frequently, which can place excessive stress on a server, actually 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 as a whole.

Quest recommends the following:

For information about the required configuration on the BlackBerry Enterprise server and the permissions that are required by the diagnostic console credentials, see the Unified Communications Diagnostics Deployment Guide.

BlackBerry Panels

The BlackBerry Server Home Page displays a high-level operational summary of the BlackBerry server and is comprised of the following panels:

BlackBerry Service Health Panel

The Service Health panel displays the CPU and memory usage status of the BlackBerry services described in the following table:

BlackBerry Attachment Service

Converts supported attachments into a format that users can view on their BlackBerry handheld devices.

BlackBerry Dispatcher Service

Compresses and encrypts all BlackBerry data and routes the data through the BlackBerry router to and from the wireless network.

BlackBerry Messaging Agents Service

Connects to BlackBerry to provide wireless enterprise activation, and delivers messages to and from the user’s mailboxes on the BlackBerry server.

BlackBerry Policy Service

Performs administrative services over the wireless network, such as sending IT policies and IT commands.

BlackBerry Router Service

Connects to the wireless network to route data to and from BlackBerry handheld devices.

BlackBerry Synchronization Service

Synchronizes organizer data between BlackBerry handheld devices and the messaging server over the wireless network.

BlackBerry SRP Panel

This panel indicates whether or not the BlackBerry server is connected to the Server Relay Protocol. This point-to-point protocol runs on top of TCP/IP, and defines transactions between the BlackBerry services and the Relay Server.

Reconnections

Indicates the number of times the BlackBerry Dispatcher Service has successfully reconnected to SRP since it was started.

Failed Connections

Indicates the number of times the BlackBerry Dispatcher Service has tried, but failed to connect to SRP since it was started.

SRP Time Not Connected (sec)

Indicates the total time, (in seconds), that the BlackBerry Dispatcher Service has not been connected to SRP since startup.

SRP Last Connect

Indicates the following:

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택