지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Editing Individual server thresholds while creating a health test

In the Edit Server Thresholds dialog, if no Server is shown, click the Browse button. In the Select Servers dialog, check the boxes for one or more servers, or group. Click OK to return.

Specify Error and/or Warning threshold values for the selected Server. If only one threshold is specified, the other threshold assumes the value shown in the Default counter thresholds, if present.

These values override the default threshold values for this server only, and only in this health test.You cannot leave this dialog with invalid threshold values specified.

In the health test creation wizard, up to 5 servers that have a server specific threshold defined are listed in the Overrides column for that counter. To view all servers with override values, right-click on the counter and select Edit Server Thresholds.

Editing counter thresholds in the test results pane

You can edit counter thresholds in the Test Results section without opening an associated health test wizard.

You can edit default error and warning thresholds that apply to all servers. You can also specify server-specific error and warning thresholds. These override the default values.

Counters with the same name may be defined on the same page of the Exchange Server Health test wizard. Both counters are required to define test conditions. Do not change the thresholds for either one of these counters in the Test Results area because both counters are changed which significantly alters test conditions and test results.

To edit the threshold of a counter
1
In the Test Results tab, select a test result.
2
In the lower panel, double-click a counter with highlighted thresholds. Alternatively, right-click on a highlighted threshold and select Edit Thresholds.
The Edit Counter Thresholds dialog contains the following sections:
 
Table 3. Counter thresholds for test results.
Section Name
Description

Counter thresholds at the time of test execution

indicates the default or server-specific counter threshold values set at the time the test was executed. These values cannot be changed.

Current default counter thresholds

indicates the threshold values for servers that do not have server-specific thresholds set

Current server-specific counter thresholds

indicates the threshold values for the current server, if applicable for the specific test type.

3
Enter new warning and/or error thresholds for the current default counter thresholds, or for a specific server.
To remove a server-specific threshold, delete any current value in the threshold box and leave the field empty.
4
Click OK.
The new threshold values are in effect on the next test execution.

Some counters are configured to use wildcards. If you edit the threshold of a particular counter (in Test Results) using one of the instances reported in test results, then the new threshold value is applied to all instances of the counter.

For example, if you create an Exchange Server Health Test, there is a performance counter called Network Interface\Packets Outbound Errors (<All instances>). When you view the test results, you will notice that there are two instances of Network Interface\Packets Outbound Errors that were monitored.

If you edit the threshold of one instance of this counter in the test results pane, then the threshold of the other instance of this counter is also changed.

This applies to performance counters only.

Setting data collection options

Data collection options can affect the server health test results that are returned for volumes, network availability, and services:

This section describes some of the configuration options that can be used to affect the Server Health tests:

•
Volumes - Allowing API fallback if WMI fails
•
Network Availability - Disabling reverse DNS lookup alarm
•
Services - Ignoring warnings for some services

For the Exchange System Health test, there is a data collection configuration option used to ignore warnings for target servers on which health sets are not installed. For information about health sets and the Exchange System Health test, see Exchange System Health Test .

•
Health Sets - Ignoring warnings if health sets not installed
Volumes - Allowing API fallback if WMI fails

WMI is used to retrieve accurate disk space information when using mount points. If you do not use mount points, you can configure your tests to use Windows API if WMI fails.

When you make this change in one server type, all other server types are changed for the test.

To allow Windows API fallback
1
In the Server Health Test, select a server type.
2
Click Data collection options.
3
Cick the Volumes tab and select Allow API fallback if WMI fails.
Do not use Allow Windows API fallback if WMI fails if the volume is mounted on a network-attached storage device because the metrics returned may not be accurate.
4
Click OK.
Network Availability - Disabling reverse DNS lookup alarm

The Server Health test always performs a reverse DNS lookup to validate that DNS server has a record that maps the IP address of the target server to the host name. By default, the reverse DNS lookup alarm is enabled. If you do not want the test to alarm if the names returned by a DNS lookup do not match the FQDN of the target server, you can disable this option.

When you make this change in one server type, all other server types are changed.

To disable alarm on reverse DNS lookup
1
In the Server Health Test, select a server.
2
Click Data collection options.
3
Click the Network Availability tab and clear the Alarm on reverse DNS lookup check box.
4
Click OK.
Services - Ignoring warnings for some services

The Server Health test normally reports all warnings and errors that exceed their thresholds. However, you can ignore warnings for services that are not installed in the target server or warnings for services that are not configured to start automatically.

To ignore warnings for certain services
1
From the Server Health Test, select a server.
2
Click Data collection options.
3
Click the Services tab.
4
To ignore warnings from uninstalled services, select Ignore services not installed.
5
To ignore warnings from services that are not started up automatically, check Ignore services with non-automatic startup type.
Health Sets - Ignoring warnings if health sets not installed

The Exchange System Health test monitors the health state for different groups of monitors, called health sets. 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.

If health sets are not installed on the target server, the counters would be shown with a status of “Not Complete”. You can use the following option to ignore warnings for health sets that are not installed in the target server.

To ignore warnings for certain health sets
1
From the System Health Test, select a server.
2
Click Data collection options.
3
Click the Health Sets tab.
4
To ignore warnings for health sets that are not installed on the selected server, select Ignore health sets not installed.

If, at a later date, health sets are installed on the Exchange target server, you can clear the check box.

Managing health tests

After you create health tests, you can modify the test settings (schedule, notifications, credentials), disable or enable a test, or delete a test.

To edit a test
1
Expand the Tests node in the Management Console treeview, right-click the test you want to edit, and select Edit.
2
Edit the existing settings you want to change in the Execution Schedule, Notification Settings, and Alternate Credentials Settings dialog boxes and click Next.
3
Edit the metrics you want to change in the test-specific pages and click Finish.
The edited test is displayed under the Tests node.
To enable/disable a test
•
Expand the Tests node in the Management Console treeview, right-click the test you want to edit, and select Enable or Disable.
To delete a test
•
Expand the Tests node in the Management Console treeview, right-click the test you want to delete, and select Delete.

Raw historical data is deleted; aggregated data is kept and is purged as scheduled.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택