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

Configuring alternate credentials

Configuring alternate credentials

By default, user credentials are specified when you install the Diagnostic Services used for test execution. You can override the initial credentials for a specific test by specifying and configuring alternate credentials. Alternate credentials are used to run tests under different credentials than those specified in the Diagnostic Test Engine (DTE). The credentials are stored encrypted in the database.

If you are using alternate credentials on Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016, you must disable UAC on the client from the Registry Editor. Restart your computer for the changes to take effect.

You cannot run PowerShell cmdlets across domains with alternate credentials.

 
* 
TIP: To save time, configure the global settings before configuring your tests.
To manage alternate credentials
•
If you are in the process of creating a test, click Manage Credentials in the Test Settings page.
Otherwise, expand the Global Settings node in the Management Console treeview and select Alternate Credentials.

Managing database settings

Database Settings identify the server on which your database is installed, the size of your database, and how much free space you have within your database.

Database retention controls the length of time that the health test result data is kept in the database before being purged. You can set the database settings for weekly or hourly retention rates. The test result data is aggregated into hourly and daily historical data. This data is used for the Web Reports.

You can also use Database Settings to set Test Results History and purge test results from the database after the specified number of days. Test results are purged upon the next test execution after midnight (UTC).

If you want to purge the data from the daily Web Reports and Test Results before the specified execution time, click the Purge Now button next to the Web Reports daily data retention (days) or the Test Results data retentions days boxes.

Due to the amount of space that test history requires in the database, you can increase the value for Test History retention (days). For more information, see the section titled Historical Reporting Database Usage Estimates in the Unified Communications Diagnostics Deployment Guide.

Customizing counters

You can perform several customizing functions on counters, depending on the type of health test and the nature of the counter. These functions are divided into ones that can performed in the Server Health test only, and those available in other health tests.

Customizing Counters in the Server Health Test

Adding services
Adding performance counters
Adding event log entries
Deleting services, performance counters, and event log entries

Editing Counter Thresholds

Editing counters while creating a health test
Editing Individual server thresholds while creating a health test
Editing counter thresholds in the test results pane

Adding services

You can include additional services that you want to monitor for the specific server health test that you want to run.

To add services
1
Click <Add Services> located under the Services sections in the listview of the server health test that you select.
2
Enter a name to query a list of current services you want to monitor and the services you want to add in the Select Services dialog box and click OK.
3
Configure the thresholds you want to monitor for the new service you have added.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating