Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Understanding the Exchange 2010 Diagnostic Console

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

To view detailed information on specific components, right-click a component, message flow, or 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, 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.

You can diagnose and resolve issues using the Exchange Diagnostic Console.

Quest recommends the following:

•
Allow the Diagnostic Console view a maximum number of 10 servers at any one time.
•
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.
•
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.

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 2010 Diagnostic Console contains the following panels:

•
AD/DNS Panel
•
Server Role Status Panel
•
Transport-In Panel
•
Transport Panel
•
Transport-Out Panel
•
Clientsl Pane
•
Information Store Panel
•
OS/Subsystem Panel

AD/DNS Panel

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

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

AD

Shows the status of the Active Directory (AD) servers used by this Exchange 2010 server

DNS

Shows the status about the Domain Name System (DNS) servers in use by this Exchange 2010 server

Server Role Status Panel

This panel shows the Exchange 2010 roles that are installed. This information includes:

 
Table 2. Exchange 2010 server role status panel.
Component
Description

MBX

Shows whether the Mailbox role is installed on this Exchange 2010 server. The Mailbox role is responsible for hosting mailbox and public folder data. It also provides MAPI access for Outlook clients.

UM

Shows whether the Unified Messaging role is installed on this Exchange 2010 server. The Unified Messaging role enables you to access their mailbox, address book, and calendar using telephone and voice.

The IP-PBX or VoIP gateway must be installed to use the functionality of the Unified Messaging role.

CAS

Shows whether the Client Access role is installed on this Exchange 2010 server. The Client Access role provides mailbox server protocol access apart from MAPI. It allows you access to the mailboxes using Outlook Web Access (OWA), POP3/IMAP4, and ActiveSync.

EDG

Shows whether the Edge Transport role is installed on this Exchange 2010 server. The Edge Transport role provides mail quarantine and SMTP services to enhance security. It is the first hop of incoming mail and the last hop of outgoing mail. Note that it does not require AD access so that it can function with limited access to the corporate network (for added security).

HUB

Shows whether the Hub Transport role is installed on this Exchange 2010 server. The Hub Transport role handles mail flow by routing messages to either another Hub Transport server, an Edge server, or a Mailbox server. This role uses AD site info to determine the mail flow.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation