Converse agora com nosso suporte
Chat com o suporte

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

Introducing health tests

You can use health tests to monitor the health and performance of individual servers or for the entire organization or environment. Health tests detect problems by collecting and analyzing data or simulating user interaction with the server at regular intervals. Because UC Diagnostics is a monitoring tool, its functions only discover the servers in your organization and run health tests against the servers.

Each health test can run against individual servers or against groups of servers. Some tests, such as the Active Directory Account Lockout Health Test, cannot be run against individual servers and are run at the Exchange organization or Skype for Business/Lync environment level.

When you create a test from the Home Page, the entire organization is targeted by default. In a clustered environment, health tests run against the active node only. Health tests read information from nodes as a whole through a virtual server name.

By default, health tests are executed using the Diagnostic Services account. The Remote Registry Service is required for some health tests. Ensure this is running on your client. Only health tests that are relevant to available servers are shown when you right-click a server and select Detect. You can configure any test against a group.

All health tests use global settings such as notifications and alternate credentials. It is recommended you configure your global settings before you configure your health tests. For more information on configuring global settings, see Specifying the test configuration .

Types of health tests

The Management Console includes the following health tests:

 
Table 1. Available health tests.
Organization/Environment
Health Tests

Exchange
•
Exchange Server Health 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 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

Office 365 (Exchange Online)
•
Exchange Online Connectivity Health Test
•
Exchange Online Mailbox Logon Health Test
•
Exchange Online Message Delivery Health Test
•
Office 365 Subscription Health Test

BlackBerry
•
BlackBerry Server Health Test
•
BlackBerry Message Delivery Health Test

Lync/Skype for Business
•
Lync/Skype Server Health Test
•
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
•
Active Directory Account Lockout Health Test

Office 365 (Skype for Business Online)
•
Skype for Business Online DNS Connectivity Health Test
•
Office 365 Subscription Health Test

Office Communications Server (OCS
•
OCS Server Health Test

By default, it is recommended that these tests be run every 30 minutes except for the server health tests. For more information about server health tests, see About server health tests

Creating and configuring health tests

You can perform the following functions with health tests:

•
Creating a health test
•
Specifying the test configuration
•
Customizing counters
•
Setting data collection options
•
Managing health tests
•
Cloning a health test
•
Viewing test results

Creating a health test

If you select a container for a health test, the test runs against all servers in the group at the time of execution. Typically, the test would be configured for all servers. If you add a new server, the test automatically runs against that server (without needing to be updated). You can configure a test to run only once or at regular intervals during a specified time period.

When creating a test, you can set the conditions, error thresholds, and warning thresholds. You can also specify the number of alarms to be skipped before notifications are sent. You might want to ignore notifications for occasional spikes, and only be notified if there are consecutive alarms.

For example, if your tests are configured to alert on errors only, you might decide to ignore notifications until a counter exceeds the error threshold four times consecutively. You would enter 3 in the Alarms to skip before sending notifications box. In this case, you are notified after the error threshold is exceeded four times in a row.

To create a health test
1
Right-click the Exchange organization node or the Lync/Skype environment node and select Detect | <test name>.
- OR -
2
Right-click a selected server and select Detect | <test name>.
3
On the General Test Information dialog box, specify the Test Name and Test Targets and click Next.
4
Review the test execution schedule, test credentials and notification settings in the Test Settings dialog box. Make any required changes to the selections and click Next.
For more information on configuring Test Settings, see Specifying the test configuration .
5
Select the server type in the left pane of the New <platform type> Server Health Test dialog box to indicate the type of server whose metrics you want to specify.
This dialog is displayed for selected tests and environments. Skip this step if the dialog is not displayed.
6
Review the metrics you want to monitor for the selected target by configuring and selecting the Network, Volumes, Services, Performance Counters and Event Log metrics.
7
Review the Condition, Warning Threshold and Error Threshold values and click Next.
8
Use the Summary page to review and confirm the general, test and notification settings you have made then click Finish to accept the settings.

Once the test is created, it runs immediately.

The Server Health test is preconfigured with general defaults. Some tests have counters preconfigured to skip an alarm the first time it occurs before sending a notification. For a list of these counters, see Counters with Non-Zero Alarm Values .

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação