Chatee ahora con Soporte
Chat con el soporte

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

OCS Server Health Test

The OCS Server Health Test allows you to monitor the basic health of all your OCS 2007 and OCS 2007 R2 servers. This test allows you to monitor the following types of information:

OCS Server Health Test Prerequisites

The following tables show the test target servers, required configuration to run the test, and the permissions required by the test credentials.


All servers

The OCS Server Health test does not monitor federated partners.



For SQL server prerequisites, see the Unified Communications Diagnostics Deployment Guide.

You can become a member of RTCUniversalServerAdmin to update the Back-End databases to provide the db_datareader user role for the rtc, rtcconfig, and rtcdyn tables.

As an alternative, you can:

Creating a test user for the Lync/Skype Environment

Several of the Lync/Skype synthetic transaction health tests require test users. You must create test users for each registrar pool against which you want to run health tests.

These test users are created using a Microsoft PowerShell cmdlet called New-CsHealthMonitoringConfiguration. You execute the PowerShell cmdlet in the Lync Server Management Shell on the Lync server or the Skype for Business Server Management Shell on the Skype server. For more information about this cmdlet, go to

The script has the following syntax:



Identifies the location in the Active Directory where the created user is associated with a mailbox.

If this parameter is not specified, you are prompted to enter the name of an Organizational Unit.

FirstTestUserSipUri or SecondTestUserSipUri

Identifies the mailbox names that the script generates.

FirstTestSamAccountName or SecondTestSamAccountName

Identifies an account name to be associated with the test mailboxes.

This parameter is optional.


Selects whether to prompt for confirmation before executing the command.


Selects whether to suppress the display of any non-fatal error message that may occur when executing the command.


Creates an object reference without actually committing the object as a permanent change.

If you assign the output of this cmdlet (called with this parameter) to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet’s matching Set- cmdlet.


Describes what would happen if you executed the command, without actually executing the command.

An example use of the cmdlet follows:

Test users are required to run the following Lync/Skype synthetic transaction health tests:


Resolving Problems with Native Tools

Unified Communications Diagnostics allows you access to native management tools to help you troubleshoot and resolve problems with your Exchange, Skype for Business, Office 365, OCS, Lync, and BlackBerry environments.

Several tools are available that can be used for most environments.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación