サポートと今すぐチャット
サポートとのチャット

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

Lync/Skype Address Book Service Health Test

This test allows you to monitor the ability to connect to an Address Book Download Web Service from a pool.

 
Table 11. Counters for address book service health test counters.
Category
Counter

Address Book Service Transaction
•
Transaction latency in seconds
•
Transaction status
•
Transaction details

Lync/Skype Persistent Chat Message Health Test

This test verifies whether two users can exchange messages using the Persistent Chat service. The test logs two users on to Lync Server 2013 or to Skype for Business 2015, connects the users to a persistent chat room, exchanges a pair of messages, exits the chat room and logs off the two users.

This test will fail if you have not created a chat room or if the two test users have not been assigned a Persistent Chat policy that provides access to the Persistent Chat service.

The test is not available for Lync 2010.

 
Table 12. Persistent chat message health test required configuration.
Lync/Skype server version
Required Configuration

All

The test uses the PowerShell Test-CsPersistentChatMessage –TargetPoolFqdn <target fqdn> cmdlet. Before the cmdlet can work, you must use Setup parameter to enable it.

•
Run the Test-CsPersistentChatMessage cmdlet with the Setup parameter from a computer that has access to the Lync/Skype server topology.
NOTE: When you use the Setup parameter, you must also use the TestUser1SipAddress and the TestUser2SipAddress parameters.

For example, suppose you are running the Test-CsPersistentChatMessage cmdlet with the Setup parameter for a pool named LyncEnt-pool.smov2.qc.kan.ca.qsft. First you must create two test users in the pool. If you are running the test against more than one Lync 2013 registrar pool, you must create same test users for each pool.

For more information about creating Lync/Skype test users, see Creating a test user for the Lync/Skype Environment .

The following example shows the syntax for the cmdlet:

Test-CsPersistentChatMessage -TargetFqdn LyncEnt-pool.smov2.qc.kan.ca.qsft -Setup $true -TestUser1SipAddress “sip:testuser1@smov2.qc.kan.ca.qsft”
-TestUser2SipAddress “sip:testuser2@smov2.qc.kan.ca.qsft”
 
Table 13. Counters for persistent chat message health test counters.
Category
Counter

Persistent Chat Message Transaction
•
Transaction latency in seconds
•
Transaction status
•
Transaction details

Skype for Business Online DNS Connectivity Health Test

The Skype for Business Online DNS Connectivity Health test helps you verify the correctness of your DNS configuration and identify any issues. Skype for Business Online requires four DNS records. The domain name is the name of the Session Initiation Protocol (SIP) of your organization.

In China, Skype for Business Online is operated by 21Vianet and the required DNS configuration has different destination domain names. When you configure the health test, you must select the appropriate service:

•
Office 365
•
Office 365 operated by 21Vianet
 
Table 14. Skype for Business Online DNS connectivity health test counters
DNS Record Type
Service
Domain Name
Protocol
Port
Purpose

SRV (Service)

_sip

sipdir.online.lync.com

_tls

443

Used by Skype for Business to coordinate the flow of information between Lync clients.

SRV (Service)

_sipfederation

sipfed.online.lync.com

_tcp

5061

Allows your Office 365 domain to share instant messaging (IM) features with external clients by enabling SIP federation.

CNAME (Alias)

sip

sipdir.online.lync.com

 

 

Used by the Lync client to help find the Skype for Business Online service and sign in.

CNAME (Alias)

lyncdiscover

webdir.online.lync.com

 

 

Used by the Lync mobile client to help find the Skype for Business Online service and sign in.

 
 
Table 15. Skype for Business Online operated by 21 Vianet DNS connectivity health test counters
DNS Record Type
Service
Domain Name
Protocol
Port
Purpose

SRV (Service)

_sip

sipdir.online.partner.lync.cn

_tls

443

Used by Skype for Business to coordinate the flow of information between Lync clients.

SRV (Service)

_sipfederation

sipfed.online.partner.lync.cn

_tcp

5061

Allows your Office 365 domain to share instant messaging (IM) features with external clients by enabling SIP federation.

CNAME (Alias)

sip

sipdir.online.partner.lync.cn

 

 

Used by the Lync client to help find the Skype for Business Online service and sign in.

CNAME (Alias)

lyncdiscover

webdir.online.partner.lync.cn

 

 

Used by the Lync mobile client to help find the Skype for Business Online service and sign in.

 
Table 16. Skype for Business Online DNS connectivity health test targets.
Platform
Target Type

Office 365

Skype for Business Online

 
Table 17. Skype for Business Online DNS 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

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 18. 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 19. Office 365 Subscription health test targets.
Platform
Target Type

Office 365

All services

The following software is required.

 
Table 20. 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 21. 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.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択