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

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

Exchange Online Connectivity Health Test

The Exchange Online Connectivity Health test allows you to determine network quality and identify issues that can affect network performance between your client computers and Exchange Online.

You can view the time (in milliseconds) a round trip takes from your computer to Exchange Online (Office 365). You can also view any warnings and errors for the different ports used to access Exchange Online services.

Basic Network

Network Reachable/Unreachable

Advanced Network (round-trip time)

Warning: >50 ms

Error: >275 ms

Office 365

Exchange Online

Office 365

Exchange Online Mailbox Logon Health Test

The Exchange Online Mailbox Logon Health test verifies mailbox accessibility by logging on to Exchange Online. The test uses the Office 365 credential that you specified for either a hybrid Exchange Online connection or for a native Office 365 connection. The credential must have an associated Exchange Online mailbox.

When the logon process succeeds, the test displays Logon Succeeded. Logon latency shows the time that elapsed during the logon process (in seconds).

If you are using OAuth 2.0 to connect to Office 365, you must provide Application ID, Tenant ID, and Client Secret that were assigned when the UC Diagnostics application was registered with the Microsoft Azure portal. For more information, see Registering UC Diagnostics with the Microsoft Azure portal .

Logon status

Equal

N/A

Logon Failed

Logon latency in seconds

Informational

 

 

Office 365

Exchange Online

Office 365

Office 365

If you are using OAuth 2.0 authentication for the test, the required API permissions are:

Office 365

If the password of the Office 365 credential is changed, you must also change the credential password on either the native Office 365 or hybrid Exchange connection properties.

Exchange Online Message Delivery Health Test

The Exchange Online Message Delivery Health test monitors overall message delivery health for both hybrid and native Exchange Online, including test messages sent internally and externally.

The Exchange Online Message Delivery Health test uses Exchange Web Services (EWS) for internal and external message delivery tests.

If you are using OAuth 2.0 to connect to Office 365, you must provide Application ID, Tenant ID, and Client Secret that were assigned when the UC Diagnostics application was registered with the Microsoft Azure portal. For more information, see Registering UC Diagnostics with the Microsoft Azure portal .

The process to create an Exchange Online message delivery health test is as follows.

1
Right-click the organization node and select Detect | Exchange Online Message Delivery Health Test.
6
Click OK and click Next.
7
On the EWS Authentication page, select either Basic or OAuth 2.0 authentication.
8
On the EWS URL Settings (Optional) page, you can select the Use specified EWS URL(s) to find Exchange mailboxes check box and click Add.

The Exchange Online internal message delivery health test contains the following counters:

Internal Message Delivery

The Exchange Online external message delivery health test contains the following counters:

Round-trip Delivery

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

Exchange Online hybrid

Exchange organization

Exchange Online native

Office 365 tenant

For the internal message delivery test, Exchange Online must be configured as follows:

Exchange Online
(native and hybrid)

For the external message delivery test, Exchange Online must be configured as follows:

Exchange Online
(native and hybrid)

The following software is required.

Office 365

The test credentials must have the following permissions.

Office 365

If you are using OAuth 2.0 authentication for the test, the required API permissions are:

Office 365

Office 365 Subscription Health Test

The Office 365 Subscription Health test provides an overview of your Office 365 licensing plans. Licensing plans define the Office 365 services that are available to users. The test shows license activity such as the number of licenses that are currently assigned to users (used) and how many licenses are due for renewal.

During the first 30 days after an Office 365 subscription ends, the Office 365 tenant account is in a period known as the expired state. During the expired period, users can still access data. After 30 days, the tenant account enters the disabled state for 90 days. During this period, users cannot access data. An Office 365 administrator can log in, backup data, or reactivate the subscription.

At the end of the disabled state, 120 days after the subscription has ended, the account enters the deprovisioning state. During the deprovisioning state, the data from user accounts and also email data and documents, is permanently deleted.

Total licenses

Total number of purchased licenses in the licensing plan.

Number of licenses used

Number of licenses that have been assigned to users in the specified licensing plan.

Number of licenses used (%)

Percentage of licenses that have been assigned to users in the specified licensing plan.

Number of licenses that must be renewed

Number of licenses in the licensing plan that have not been renewed and that will expire after the 30-day grace period.

Next lifecycle date

Next date on which a a subscription lifecycle event occurs. Lifecycle events can include states such as active, expired, disabled, or deprovisioned.

Next lifecycle date (days)

Date on which the next subscription lifecycle event will occur that is less than the specified number of days. You can set thresholds for warning and error notifications.

Office 365

All services

The following software is required.

Office 365

Office 365

Valid Office 365 credential that was used to connect to Office 365.

If the password of the Office 365 credential is changed, you must change the password on Office 365 connection properties.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택