Unified Communications Diagnostics 8.6.2

About Unified Communications Diagnostics

Getting Started Using the Management Console

About the Management Console Connecting to Diagnostic Services Connecting to a Platform Importing and Exporting Topology Layout Viewing an OCS Environment

Discovering Federated Partners in OCS Viewing Pool Properties in OCS Viewing OCS Server Properties

Viewing Link Types Viewing a Lync/Skype Environment

Viewing Lync/Skype Pool Properties Viewing Lync/Skype Server Properties

Managing Custom Groups

Creating a Static Custom Group Creating a Dynamic Custom Group Editing a Custom Group Deleting a Custom Group Grouping Servers by Type

Managing Global Filters Putting Servers in Maintenance Mode Managing Missing Objects Viewing Database Availability Groups (DAG)

Prerequisites

Introducing Management Console health tests

Introducing health tests Types of health tests Creating and configuring health tests

Creating a health test Specifying the test configuration

Configuring the execution schedule Configuring notification settings Adding notification groups Configuring alternate credentials Managing database settings

Customizing counters

Adding services Adding performance counters Adding event log entries Deleting services, performance counters, and event log entries Editing counters while creating a health test Editing Individual server thresholds while creating a health test Editing counter thresholds in the test results pane

Setting data collection options Managing health tests Cloning a health test Viewing test results

Viewing details on test results Browsing test result history Clearing the health test results

About server health tests Health tests available for multiple platforms

Active Directory Account Lockout Health Test Office 365 Subscription Health Test

Health tests available from the Exchange organization node

BlackBerry Server Health Test Prerequisites

BlackBerry Message Delivery Health Test Creating test mailboxes for Exchange

Creating Exchange 2007 test mailboxes Creating Exchange 2010 or Exchange 2013 test mailboxes About test mailboxes for Internal Server Delivery Health Test About test mailboxes for the External Message Delivery Health Test Creating a test mailbox for External Message Delivery Health Test Creating a test mailbox for the Internal Mailbox Delivery Health Test Creating test mailboxes for the OWA Availability Health Test Creating a test mailbox for the External OWA Availability Health Test

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

About the Lync/Skype for Business health tests Lync/Skype Server Health Test

Lync or Skype Server Health Test Prerequisites

Lync/Skype Synthetic Transaction Health Tests

Lync/Skype Synthetic Transaction Health Test Prerequisites

Lync/Skype Instant Messaging Health Test Lync/Skype Instant Messaging Conference Health Test Lync/Skype Peer-to-Peer Audio/Video Call Health Test Lync/Skype Audio/Video Conferencing Health Test Lync/Skype Presence Status Health Test Lync/Skype Logon Registration Health Test Lync/Skype Address Book Service Health Test Lync/Skype Persistent Chat Message Health Test

Skype for Business Online DNS Connectivity Health Test Office 365 Subscription Health Test OCS Server Health Test

OCS Server Health Test Prerequisites

Creating a test user for the Lync/Skype Environment

Resolving Problems with Native Tools

Native tools for most servers Native tools for Exchange Native tools for Lync/Skype for Business Native tools for Office 365 Native tools for OCS Native tools for BlackBerry

Launching the Diagnostic Console from the Management Console Launching UC Analytics from the Management Console Diagnosing Problems using the Diagnostic Console

Introducing the Diagnostic Console

Launching the Diagnostic Console from the Management Console

UC Diagnostics: Exchange 2007 Diagnostic Console (Plug In)

Introducing the Exchange 2007 Diagnostic Console Understanding the Exchange 2007 Diagnostic Console Panels

AD/DNS Panel Server Role Status Panel Transport-In Panel Transport Panel Transport-Out Panel Clients Panel Information Store Panel OS/ Subsystem Panel

Message Flows Drilldowns Metrics

UC Diagnostics: Exchange 2010 Diagnostic Console (Plug In)

Introducing the Exchange 2010 Diagnostic Console Understanding the Exchange 2010 Diagnostic Console Panels

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

Message Flows Drilldowns Metrics

UC Diagnostics: Exchange 2013 Diagnostic Console (Plug In)

Introducing the Exchange 2013 Diagnostic Console Understanding the Exchange 2013 Diagnostic Console Panels

AD/DNS Panel Server Roles Panel Clients Panel Client Access Server (CAS) Mailbox Server (MBX) Transport Panel Mailbox Server (MBX) Information Store Panel OS/ Subsystem Panel

Message Flows Drilldowns Metrics

UC Diagnostics: Exchange 2016 Diagnostic Console (Plug In)

Introducing the Exchange 2016 Diagnostic Console Understanding the Exchange 2016 Diagnostic Console Panels

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

Message Flows Drilldowns Metrics

UC Diagnostics: BlackBerry Diagnostic Console (Plug In)

Introducing the BlackBerry Diagnostic Console Understanding the Diagnostic Console

BlackBerry Diagnostic Console Recommendations

BlackBerry Panels

BlackBerry Service Health Panel BlackBerry SRP Panel BlackBerry System Panel BlackBerry Server Panel BlackBerry Users Panel BlackBerry OS/ Subsystem Panel

BlackBerry Message Flows BlackBerry Drilldowns Metrics

UC Diagnostics: OCS Diagnostic Console (Plug In)

Introducing the OCS Diagnostic Console

When Connecting to OCS

Understanding the OCS Diagnostic Console Panels

Server Information Panel Clients/Network Panel Server Load Panel Server Roles Panel OS/Subsystem Panel

OCS Message Flows OCS Drilldowns Metrics

UC Diagnostics: Lync 2013 or Skype for Business 2015 Diagnostic Console (Plug In)

Introducing the Lync/Skype Diagnostic Console

When Connecting to Lync/Skype

Understanding the Lync/Skype Diagnostic Console Panels

General Information Panel AD/DNS Panel Roles Panel Connections Panel Web Components SIP Stack Lync/Skype Server Health Panel OS/Subsystem Panel

Lync/Skype Message Flows Lync/Skype Drilldowns Metrics

Reporting Using Web Reports

Understanding Web Reports

Types of Reports

Counters with Non-Zero Alarm Values

Prerequisites for Exchange Delivery Health Tests

The following prerequisites are common to all the Exchange delivery health tests:

Table 2. Software required for the Exchange delivery health tests.

Exchange Version

Required Software

Exchange 2007/2010/2013

•

For Exchange 2007, 2010, or 2013, install MAPI & CDO (version 8.3.0.8353.000 or later). You can download MAPI & CDO here::

•

https://www.microsoft.com/download/details.aspx?id=42040

Exchange 2010 and later

•

PowerShell 2.0 or later

See the individual test descriptions for information about required configuration and permissions needed to run each test:

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 Internal Server Delivery Health Test

The Exchange Internal Server Delivery Health test is used to monitor the sending and receipt of messages within an Exchange organization.This test sends a test message from each target server in the test to every other target server.

The Exchange Internal Server Delivery Health test sends a test message from each selected server to every other selected server. For example, if you select your whole organization as the test target and your organization has five mailbox servers, this test sends 20 test messages (5 source servers x 4 destination servers) at each monitoring interval.

This health test is not supported for Exchange 2013 and later. This test is also not useful for Exchange 2010 organizations that have implemented Database Availability Groups (DAGs) since mailboxes in a DAG are not linked to a specific server.

On Exchange 2007 servers, when the test runs, it looks for a test mailbox on each server. The test mailbox can be on any store on that server. You need one test mailbox per server to run this test. If there are multiple test mailboxes on each server, the test uses the first mailbox it finds. By default, the test mailbox creation scripts create one test mailbox per store.

You can configure this test to collect tracking information to trace the test message that flows through the Exchange servers.

For Exchange 2007, you can use the Internal Mailbox Delivery Health test to monitor the sending and receiving of messages between mailboxes. For Exchange 2010 and later, you can use the Exchange Modern Message Delivery Health test.

Figure 1. A test message is sent from each server to every other server.

You must manually create test mailboxes and match the name to the mailbox mask specified in the test configuration. For more information, see Creating test mailboxes for Exchange .

Recommendations for Performance Optimization

For large organizations, select a subset of the servers to reduce the amount of traffic generated. For example, select one server per geographical region. You can also decrease the monitoring frequency.

For Exchange 2007 servers, create a test mailbox that matches the mailbox mask in at least one store on each server in the organization. However, it is recommended that you create a test mailbox in each store on each server.

For Exchange 2010 servers, create a test mailbox that matches the mailbox mask in at least one mounted mailbox database copy on each server in the organization. However, it is recommended that the test mailbox be created in each mailbox database on each server. When the test runs, it looks for a test mailbox on each server. The test mailbox is in a mailbox database. If there are multiple test mailbox boxes on each server, the test uses the first one it finds. By default, the test mailbox creation scripts create one test mailbox per mailbox database.

While the test is executing, storage groups and stores are enumerated in alphabetical order. If the test takes a long time to complete, you can create a test mailbox in the first storage group in the first store (in alphabetical order) on every server to speed up the query.

For example, you have a server called AMER-MBX-01 with the following stores:

•

First-Mailbox-Store (in storage group First-Storage-Group)

•

Second-Mailbox-Store (in storage group First-Storage-Group)

•

Third-Mailbox-Store (in storage group Second-Storage-Group)

If the mailbox mask specified in the test is the default mask (SOM_<ServerName>_<StorageGroupName>_<StoreName>, then the test looks for the following mailboxes for AMER-MBX-01 until it finds one that is accessible:

•

SOM_AMER-MBX-01_First-Storage-Group_First-Mailbox-Store

•

SOM_AMER-MBX-01_First-Storage-Group_Second-Mailbox-Store

•

SOM_AMER-MBX-01_Second-Storage-Group_Third-Mailbox-Store

For example, you have a server called AMER-MBX-01 containing Database1 and Database2. If the mailbox mask specified in the test is the default mask (SOM_<ServerName>_<DatabaseName>, then the test looks for the following mailboxes for AMER-MBX-01 until it finds one that is accessible:

•

SOM_AMER-MBX-01_Database1

•

SOM_AMER-MBX-01_Database2

<DatabaseName> token is optional.

All test messages sent are automatically deleted from the internal test mailboxes. But other mail, such as NDR messages, is not automatically deleted. You must manually clean out your test mailboxes periodically.

To enable this test to collect tracking information

•

From the All Exchange Servers tab, select the Collect message tracking information check box.

The tracking information is located in the Delivery details counter.

Table 3. Exchange Internal Server Delivery Health Test counters

Table 4. Internal server delivery health test targets
Exchange Server Version	Target Type
Exchange 2007/2010	Mailbox role

Exchange Internal Mailbox Delivery Health Test

For Exchange 2007 to Exchange 2013, you can use the Exchange Internal Mailbox Delivery Health Test to monitor the sending and receipt of messages between mailboxes in an Exchange organization. This test supports DAGs.

For Exchange 2010 and later, it is recommended that you run the Exchange Modern Message Delivery Health Test instead, especially in scenarios in which the CAS server is behind a load balancer.

Table 7. Exchange Internal Mailbox Delivery Health Test counters

Table 8. Exchange internal mailbox delivery health test targets.
Exchange Server Version	Target Type
Exchange 2007/2010/2013	Mailbox role

	TIP: For Exchange 2010 and later, it is recommended that you run the Exchange Modern Message Delivery Health Test instead.

Exchange External Message Delivery Health Test

For Exchange 2007 to Exchange 2013, you can use the Exchange External Message Delivery Health test to monitor the health of message delivery to and from an external target.

For Exchange 2010 and later, it is recommended that you run the Exchange Modern Message Delivery Health Test instead, especially in scenarios in which the CAS server is behind a load balancer.

This test tracks the time it takes a test email to leave your organization and the time it takes the message to return to the original server.

For this test, you must enter the names of:

•

Source mailbox to send a message to an SMTP address and receive replies from that address

•

Destination email address to indicate where test messages are sent

For more information about test prerequisites, see Unified Communications Diagnostics Deployment Guide.

About the test

This test targets your entire organization, not individual servers. You must create a test mailbox to run this test.

To monitor round-trip messages, the external mailbox must be configured to automatically bounce the message back to the original mailbox. You would enable the Round-Trip Delivery counter in the test.

All test messages sent are automatically deleted from the internal test mailbox. But any other mail, like NDR messages, are not automatically deleted. You may need to periodically clean out your test mailboxes.

By default, the Organization Exit counters are disabled because they are not fully supported when the source mailbox is hosted on Exchange 2013.The Round-trip Delivery counters are enabled because the external email account needs to be configured to automatically bounce the test message back to the originating mailbox.

Table 11. External message delivery health test counters.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Unified Communications Diagnostics 8.6.2 - User Guide

Prerequisites for Exchange Delivery Health Tests

Exchange Internal Server Delivery Health Test

Exchange Internal Mailbox Delivery Health Test

Exchange External Message Delivery Health Test