Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

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.

 
 
Table 58. Exchange Online Connectivity health test counters.
Category
Counter

Basic Network
•
Network Reachable/Unreachable
•
Network Latency (ms)
Shows network latency to Office 365 service. Good is < 50 ms. Warning is >50 ms. Error is >275 ms.
•
Packet Loss (%)
Shows the percentage of packet loss to the Content Delivery Network (CDN) endpoint. Warning is 2%. Error is 5%.
NOTE: If packet loss is 1% or greater, you should investigate.

Advanced Network (round-trip time)

Warning: >50 ms

Error: >275 ms

NOTE: If one of the counters is in error, check your firewall or router settings to ensure the port is not blocked.
•
HTTP - TCP Port 80 (ms)
Affects ability to reach the Microsoft web site.
•
HTTPS - TCP Port 443 (ms)
Affects whether Outlook and mobile devices can connect or synchronize.
•
IMAP - TCP Port 993 (ms)
Affects ability to receive email.
•
POP - TCP Port 995 (ms)
Affects ability to receive email.
•
SMTP - TCP Port 587 (ms)
Affects ability to send email.
 
 
Table 59. Exchange Online connectivity health test targets.
Platform
Target Type

Office 365

Exchange Online

 
Table 60. Exchange Online connectivity health test required software.
Platform
Software Required on the UC Diagnostics computer

Office 365
•
Windows PowerShell 5.0 or later
•
Microsoft Online Service Sign-in Assistant
•
Microsoft Azure Active Directory Module for Windows PowerShell
•
Microsoft Exchange Online PowerShell Module

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 .

 
Table 61. Exchange Online mailbox logon health test counters.
Threshold Name
Condition
Warning Threshold
Error Threshold

Logon status

Equal

N/A

Logon Failed

Logon latency in seconds

Informational

 

 

 
Table 62. Exchange Online mailbox logon health test targets.
Platform
Target Type

Office 365

Exchange Online

 
Table 63. Exchange Online mailbox logon health test required software.
Platform
Software Required on the UC Diagnostics computer

Office 365
•
Windows PowerShell 5.0 or later
•
Microsoft Online Service Sign-in Assistant
•
Microsoft Azure Active Directory Module for Windows PowerShell
•
Microsoft Exchange Online PowerShell Module
 
Table 64. Exchange Online mailbox logon health test credential required permissions.
Platform
Permissions Required for Test Credentials

Office 365
•
Be a valid Office 365 credential that is assigned the Exchange Online service with an active mailbox

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

 
Table 65. Exchange Online mailbox logon health test required API permissions.
Platform
Required API Permissions for OAuth 2.0 authentication

Office 365
•
EWS.AccessAsUser.All
•
full_access_as_app

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.

•
Internal message delivery can be between Exchange on-premise mailboxes and Exchange Online mailboxes, or between mailboxes within Exchange Online. For hybrid environments, you could set either the source or target mailbox to be on-premise or Exchange Online. For native environments, both mailboxes would be Exchange Online.
•
External message delivery detects message delivery between Exchange Online and the internet. You must create an internal mailbox as source mailbox and an external mailbox as the destination mailbox. The source mailbox is an Exchange Online mailbox. The destination mailbox must be configured to send an auto-reply message.

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.

To create an Exchange Online message delivery health test
1
Right-click the organization node and select Detect | Exchange Online Message Delivery Health Test.
2
On the General Test Information page, specify a Test name to identify the test and click Next.
3
On the Test Settings page, review the test schedule, credentials, and notification settings. Make any required changes and click Next.
4
On the Source and Destination page, click Add.
5
Enter the source mailbox email address and the destination email address for the test messages and specify if the message delivery is internal or external.
You must enter the primary SMTP address for the mailboxes.
6
Click OK and click Next.
If you do not want to use the Exchange autodiscover service to connect to the test mailboxes, you can specify the EWS URLs to be used. This setting is optional.
7
On the EWS Authentication page, select either Basic or OAuth 2.0 authentication.
If you select OAuth 2.0, enter the Application ID, Tenant ID, and Client Secret that were assigned when the UC Diagnostics application was registered with the Microsoft Azure portal. For details, see Registering UC Diagnostics with the Microsoft Azure portal .
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.
9
Enter the URL and click OK.
10
Repeat steps 8 and 9 until you have added all the URLs that you want and click Next.
Internal Delivery Settings
a
If you are creating a test for internal message delivery, specify the time the test should wait for delivery in the Timeout (in minutes) box.
b
Review the metrics you want to monitor for the selected target.
c
Review the Condition, Warning Threshold, Error Threshold, and Alarms to Skip Before values and click Next.
External Delivery Settings
a
If you are creating a test for external message delivery, specify the time the test should wait for delivery in the Timeout (in minutes) box.
b
Review the metrics you want to monitor for the selected target.
c
Review the Condition, Warning Threshold, Error Threshold, and Alarms to Skip Before values and click Next.
11
Review the test setting on the Summary page and click Finish.
Exchange Online message delivery health test counters

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

.
Table 66. Exchange Online Internal message delivery health test counters
Category
Counter

Internal Message Delivery
•
Delivery time in seconds
Verifies whether the message can be sent and received successfully internally within the timeout
•
Delivery status (within timeout)

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

 
Table 67. Exchange Online external message delivery health test counters.
Category
Counter

Round-trip Delivery
•
Round trip delivery time in seconds
Verifies whether the message can be sent out and transferred back successfully within the timeout.
•
Round trip delivery status (within timeout)
Exchange Online message delivery health test prerequisites

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

 
Table 68. Exchange Online message delivery health test targets
Platform
Target Type

Exchange Online hybrid

Exchange organization

Exchange Online native

Office 365 tenant

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

 
Table 69. Exchange Online internal message delivery health test configuration.
Platform
Required Configuration

Exchange Online
(native and hybrid)
•
Create user mailboxes or dedicated test mailboxes for source and target mailbox pairs.

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

 
Table 70. Exchange Online external message delivery health test configuration.
Platform
Required Configuration

Exchange Online
(native and hybrid)
•
Create a source test mailbox.
•
Create an external test mailbox.

The following software is required.

 
Table 71. Exchange Online message delivery health test required software.
Platform
Software Required on the UC Diagnostics computer

Office 365
•
Windows PowerShell 5.0 or later
•
Microsoft Online Service Sign-in Assistant
•
Microsoft Azure Active Directory Module for Windows PowerShell
•
Microsoft Exchange Online PowerShell Module

The test credentials must have the following permissions.

 
Table 72. Exchange Online message delivery health test permissions needed by test credentials.
Platform
Permissions required by test credential

Office 365
•
Must be granted impersonation rights on the internal test mailboxes. The test credential is the credential used to connect to Office 365.

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

 
Table 73. Exchange Online message delivery health test required API permissions.
Platform
Required API Permissions for OAuth 2.0 authentication

Office 365
•
EWS.AccessAsUser.All
•
full_access_as_app

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.

About the Office 365 subscription lifecycle

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.

 
Table 74. Office 365 subscription health test counters.
Category
Counter

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.

 
Table 75. Office 365 subscription health test targets.
Platform
Target Type

Office 365

All services

 

The following software is required.

 
Table 76. Office 365 subscription health test required software.
Platform
Software Required on the UC Diagnostics computer

Office 365
•
Windows PowerShell 5.0 or later
•
Microsoft Online Service Sign-in Assistant
•
Microsoft Azure Active Directory Module for Windows PowerShell
•
Microsoft Exchange Online PowerShell Module
 
Table 77. Office 365 subscription health test credential required permissions.
Platform
Permissions Required for Test Credentials

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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation