Chat now with support
Chat mit Support

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 Exchange 2016 Diagnostic Console

The Exchange 2016 Diagnostic Console provides a real-time representation of the messaging system processes and components within specific connected Exchange 2016 servers. You can diagnose and resolve issues using the Exchange 2016 Diagnostic Console.

The Exchange 2016 Diagnostic Console contains the following:

•
Home pages that highlight targeted areas of the Exchange 2016 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.

Understanding the Exchange 2016 Diagnostic Console

When you connect to the Exchange 2016 Diagnostic Console, the home page displays a high level summary of your Exchange 2016 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 Exchange 2016 server.

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

Exchange Diagnostic Console Recommendations

The Exchange Diagnostic Console provides you with a real-time representation of the messaging system processes and components within Exchange.

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:

•
Allow the Diagnostic Console view a maximum number of 10 servers at any one time.
•
If you are using the Diagnostic Console as a monitoring tool, you must disconnect from and reconnect to the Diagnostic Console daily. Though the Management Console can run tests when closed, the Diagnostic Console cannot perform any actions when it is closed.
•
If you install the Diagnostic Console on a computer that contains Spotlight products and you want to launch the Diagnostic Console from the UC Diagnostics Management Console, the Diagnostic Console and the Spotlight products must be installed on the C: drive. Otherwise, the Diagnostic Console fails to launch from the Management Console. As a workaround, create a shortcut on your desktop to C:\Program Files\Quest\Spotlight\Console\Spotlight.exe to manually open connections.

For information about the Exchange software prerequisites, Exchange required configuration, and the permissions needed by the credentials to access Exchange, see the Unified Communications Diagnostics Deployment Guide.

Panels

The Exchange 2016 Diagnostic Console contains the following panels:

•
AD/DNS Panel
•
Server Roles Panel
•
Clients Panel
•
Client Access Services Panel
•
Transport Panel
•
Information Store Panel
•
OS/ Subsystem Panel

AD/DNS Panel

The components of the Directory Services panel indicate how Exchange 2016 interacts with directory services. This information includes:

 
Table 1. Exchange 2016 AD/DNS panel.
Component
Description

AD

Shows the status of the Active Directory (AD) servers used by this Exchange 2016 server and checks the following conditions (non-edge Exchange servers only):

•
If the domain controller is local to this Exchange 2016 server’s AD site.
•
If the domain controller is synchronized with the rest of the forest.
•
The average LDAP Search Time (in msec) for all queries made against that domain controller.
•
The number of LDAP Search Timeouts for all queries made against that domain controller.
•
The ping time between the client (UC Diagnostics) and the domain controller.
•
If the domain controller is available on the network (from this client computer).

DNS

Shows the status about the Domain Name System (DNS) servers in use by this Exchange 2016 server and checks the following conditions:

•
The ping time between the client (the Diagnostic Console) and the DNS server
•
If the DNS server can be reached on the network from this client
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen