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

Specifying the test configuration

When scheduling health tests, you must provide details about the following settings:

Configuring the execution schedule

Use the Execution schedule panel to set up the frequency and the time frames during which you want the tests to run. The following options are available in the Execution Schedule panel:

Run once

Select this to run the test immediately, and on demand.

Run every (minutes)

Select this to enter the time interval in minutes after which the next test starts.

Use execution window

Select this check box to only run within a specific time window. You must specify a Start time and End time for the Test Execution Schedule.

Run every day at

Select this to schedule the test to run once daily at this specific time.

For information on setting notifications and credentials, Configuring notification settings and Configuring alternate credentials respectively.

You can use the Run Now option on scheduled or unscheduled tests.

Configuring notification settings

Use the Notification Settings panel to select the group that is notified when the server counter values exceed the configured threshold. You can configure notification settings to alert users about errors only or about both errors and warnings. To save time, configure the global settings before you configure individual tests.

You can create notification groups to allow specified groups to receive messages about alarms, warnings, or errors on a per counter basis. You can send notifications only to groups, not to individual users. Use the Add Recipients dialog box to specify the members of each group. You can include the same recipients across notification groups.

You can specify the following notification parameters:

1
If you are in the process of creating a test, click Manage Notifications in the Test Settings page.
8

You can send a test message to see if the SMTP server is working by clicking the Send Test button. This ensures that UC Diagnostics can deliver a message to the specified email address.

Adding notification groups

After you have added recipients, you can create notification groups that include the recipients.

7

The following list shows the tokens that are supported for the external application command line. The tokens are replaced with corresponding real time results, when the external application is run.

The tokens dictate how many times the external application is called. The Notifications tokens are general tokens. With the Counter tokens, the external application is called once per test per each server per counter. With the Server tokens, the external application is called once per test per each server. With the Test tokens, the external application is called once per test.

You can configure notification groups to:

The following best practices are recommended when you set notifications:

You can receive a notification when an error occurs for a specified number of times. If the error still occurs after the specified number of times, you do not receive further notifications. In this cas you can receive a notification when the alarm is cleared. To do this:

1
Deselect the Send unlimited notifications for an alarm check box.
2
In the Maximum number of notifications to send per alarm box, enter a number for the maximum number of times you would like to receive a notification.
3
Select the Send alarm cleared notification when alarm ends check box.

You can receive unlimited error or warning notifications, but choose not receive cleared notifications. This assumes that once you stop receiving error or warning notifications, the alarm has been cleared. To do this:

1
Select the Send unlimited notifications for an alarm check box.
2
Deselect the Send alarm cleared notification when alarm ends check box.

A cleared alarm is an alarm that recipients need not manage - either the problem has been resolved or has become less severe. For example, if you are receiving notifications on errors only, and the status changes from error to warning, the alarm is considered cleared. If you are receiving notifications on both errors and warnings, and the status changes to success, the alarm is considered cleared.

2
Select the Send alarm cleared notification when alarm ends check box.
3

If a specific event is found in the event log while you run a Server Health Test (such as an Exchange Server Health Test), an event notification is sent to the notification recipients with the corresponding severity. The next time that the Server Health Test runs, the test scans only the event logs from beyond the time of the previous test run.

If no identical event is found during the second run, the notification engine does not issue the cleared notification for the event. If the event is not found during the second test run, the problem is not necessarily resolved. It only means there are no new events logged for the exact same problem.

This feature allows you to receive unlimited notifications about alarms on counters.

2
Select the Send unlimited notifications for an alarm check box.
3

Selecting this option overrides the maximum number of notification messages you may have set.

This feature can help you limit the number of notification emails you receive if you encounter problems with the same counter.

2
Enter a number in the Maximum notifications to send per alarm box.
3
Also, you can have your notifications set to receive errors only if your performance counters on your Front-End server exceeds its error threshold, and you have selected the Send alarm cleared notification when problem ends check box. You receive a notification the first time the error occurs, and two more times if the error occurs on that performance counter again. If the fourth time, the error threshold is no longer exceeded, you receive a cleared notification.

You can pass alerts to external applications using Simple Network Management Protocol (SNMP).

For example, you can enter:
"C:\Program Files\Quest\UC Diagnostics\ManagementConsole \Binaries\iwsnmptrap.exe" 10.4.60.95 public 6 0 "CounterOutcome$ on $ServerName$ - $CounterName$ = $CounterValue$”
3

If you want to pass errors only using SNMP, you can create a batch file that contains the tokens you want to use in your notifications.

1
Create a batch file, and enter:
If %1 == error "C:\Program Files\Quest\UC Diagnostics\ManagementConsole\Binaries\iwsnmptrap.exe" 10.4.60.95 public 6 0 "%1 on %2 - %3 = %4".
4
In the External application command line, enter:
"<directory of snmp.bat file>\snmp.bat" "$CounterOutcome$" "$ServerName$" "$CounterName$" "$CounterValue$", and save the notification group.

You can configure UC Diagnostics for Short Message Service (SMS) notifications.

Related Documents