Chat now with support
Chat with Support

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

Clearing the health test results

To clear the test results
•
Expand the Tests node in the Management Console treeview, right-click the test whose results you want to clear, and select Clear Test Results.

The test results are cleared only in the Management Console. The next time you open the Management Console, the test results appear.

You can run the test again to bring back the results by right-clicking the test and selecting Run Now.

About server health tests

Use the server health tests to monitor the overall health and performance of your Exchange, BlackBerry, OCS or Lync/Skype servers. The test verifies various performance counters, services, event logs, disk space, and network availability. You can schedule the Server Health test to proactively check the status of your servers before problems occur, or you can schedule tests to run after you fix an issue to ensure the server problem is resolved.

It is recommended that you configure two server health tests - one without monitoring event logs with an interval of 30 minutes and the second for monitoring event logs that run only once a day.

The following server health tests are available for the various platforms:

•
Exchange Server Health Test
•
BlackBerry Server Health Test
•
Lync/Skype Server Health Test
•
OCS Server Health Test

For more information on test settings, see Specifying the test configuration .

For information on creating and configuring a server health test, see Creating and configuring health tests .

It is recommended that you configure two server health tests - one test without monitoring event logs with an interval of 30 minutes and the second test for monitoring event logs that run only once a day. For more information on test settings, see Creating and configuring health tests .

Health tests available for multiple platforms

Most health tests are specific to a certain platform such as Exchange or Skype for Business. However, some tests can be run for more than one platform.

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.

* 
NOTE: Information about locked-out accounts is available only for the first 1000 accounts.

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

 
Table 5. Active Directory Account Lockout health test counters.
Category
Counter

General
•
Total accounts locked out

Lockout information
•
User status
•
Last time bad password was submitted
•
Number of login attempts with bad password
•
Date and time account was locked out
•
Last time password was changed
•
Next expiry date for password
Active Directory Account Lockout Health test prerequisites

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

 
Table 6. Active Directory Account Lockout Health test targets.
Platform Versions
Target Type

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.

 
Table 7. Active Directory Account Lockout Health test credential required permissions.
Platform
Permissions Required for Test Credentials

Exchange

•
Member of View-Only Exchange Administrators group or View-Only Organization Management group.

Lync/Skype for Business

•
Member of CSHelpDesk, CSServerAdministrator, or CSViewOnlyAdministrator group
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating