Chat now with support
Chat with Support

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

External Outlook Web Access (OWA) Availability Health Test

The External OWA Availability Health test monitors the availability of OWA functionality in your organization through an external URL. This test verifies that the users associated with the alternate credentials can logon to their mailboxes through an external OWA URL. This test uses an external or internal URL. If an external URL is specified, ensure that the DNS server can resolve this URL.

This test is applicable only to organizations with at least one Exchange 2007/ 2010 server. This test does not run on Exchange 2013 or later because the Microsoft Exchange Management Shell does not support OWA Connectivity testing for Exchange 2013 or later. For Exchange 2013 or Exchange 2016, you can use the Exchange System Health test to monitor OWA health.

This test uses mailboxes associated with alternate credentials. You must explicitly choose the alternate credentials on the Test Settings page when you create this test. You cannot configure the test if you have selected the Use Diagnostic Services Credentials option.

If you would like to test External OWA functionality using both types of mailboxes, you must configure two tests - one using credentials of the user who has 2007 mailbox, and the second using credentials of the user with 2010 mailbox.

This test allows you to ensure the following:

Creating test mailboxes for Exchange

Creating and configuring health tests

The following tables show the test target servers, required configuration to run the test, and the permissions required by the test credentials.

All

Exchange organization

Exchange 2010

PowerShell 2.0 or later

Exchange 2007

Exchange 2007 Management Console (EMC) Service Pack 1 Rollup 1 or later

Exchange 2010

Account specified in the alternative credentials for the test must have mailbox on the Exchange 2010 server. The alternate credentials must have Exchange View-Only Organization Management privileges.

Exchange 2007

Account specified in the alternative credentials for the test must have mailbox on the Exchange 2007 server. The alternate credentials must have Exchange View-Only Administrator privileges.

Exchange 2007/2010

Exchange 2007

Exchange 2010

Exchange Replication Health Test

The Exchange Replication Health test monitors the health of transaction log replication on your Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 mailbox servers. This test detects whether replication is configured and what type of replication is configured.

For Exchange 2010 and later, there is also information provided about lagged database copies if you have configured the Exchange lagged database copy function.

The Exchange Replication Health test contains the following counters for Exchange 2007:

Cluster Continuous Replication

Local Continuous Replication

Standby Continuous Replication

The Exchange Replication Health test contains the following counters for Exchange 2010:

Passive Mailbox Database Copy

The Exchange Replication Health test contains the following counters for Exchange 2013 and Exchange 2016:

Passive Mailbox Database Copy

Transaction log replication is handled by Database Availability Groups (DAGs) for Exchange 2010, Exchange 2013, and Exchange 2016. For more information, see Viewing Database Availability Groups (DAG) .

Creating test mailboxes for Exchange

Creating and configuring health tests

The following tables show the test target servers, required software, and the permissions needed by the test credentials.

Exchange 2007/2010/2013/2016

Mailbox role

Exchange 2010/2013/2016

PowerShell 2.0 or later

Exchange 2007

Exchange Management Console (EMC) Service Pack 1 Rollup 1 or later

Exchange 2007

Exchange 2010, 2013, and 2016

Exchange System Health Test

The Exchange System Health test monitors the health state for different groups of monitors, called health sets. Monitors that are similar or are related to a component’s architecture are grouped to form a health set. Health sets provide the health information for applications and services such as Outlook Web App, Exchange ActiveSync, the Information Store service, content indexing, and transport services on your Exchange 2013 Client Access Servers (CAS) and mailbox servers and on your Exchange 2016 mailbox servers.

If all a health set’s monitors are healthy, the health set is in a healthy state. If any monitor is not in a healthy state, the health set state is determined by its least healthy monitor.

This test is available only for Exchange 2013 and later.

The health sets are organized into four main health groups:

The Customer Touch Points health group is comprised of monitors for components that affect real-time user interactions such as protocols or the Information Store. The test shows the condition of healthy or unhealthy for each of the following health set counters:

Exchange 2013 CAS

Exchange 2016 Mailbox

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox

Exchange 2013 and 2016 Mailbox

The Service Components health group is comprised of monitors for components without direct, real-time user interactions such as the Microsoft Exchange Mailbox Replication service or the offline address book generation process (OABGen). The test shows the condition of healthy or unhealthy for each of the following health set counters:

Exchange 2013 CAS

Exchange 2016 Mailbox

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox

Exchange 2013 and 2016 Mailbox

The Server Components health group is comprised of monitors for the server physical resources such as disk space, memory, and networking. The test shows the condition of healthy or unhealthy for each of the following health set counters:

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox

Exchange 2013 and 2016 Mailbox

The Dependency Availability health group monitors the server’s ability to access necessary dependencies, such as Active Directory, DNS, and instant messaging. The test shows the condition of healthy or unhealthy for each of the following health set counters:

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox

Exchange 2013 and 2016 Mailbox

The following tables show the test target servers, required software, and the permissions required by the test credentials.

Exchange 2013

Client Access Server (CAS) role

Mailbox role

Exchange 2016

Mailbox role

Exchange 2013/2016

PowerShell 2.0 or later

All

Be a member of the following groups:

Creating and configuring health tests

Active Directory Account Lockout Health Test

The Active Directory Account Lockout Health test provides information about how many and which Active Directory accounts are currently locked out. The test shows accounts that are locked out due to invalid passwords being submitted and accounts that are locked because the password has expired. The test detects the domain accounts that are currently locked out and provides information about the lockout event.

You run the test against a domain to which an Exchange organization or a Lync/Skype for Business environment belongs. You cannot run the test against the individual servers.

The Active Directory Account Lockout Health test contains the following counters:

General

Lockout information

The following tables show the test targets for the test and the permissions required by the test credentials.

Exchange 2007/2010/2013/2016

Organization

Lync 2010/2013 and Skype for Business 2015

Environment

The test credentials must have read permission on User objects in Active Directory.

Exchange

Lync/Skype for Business

Related Documents