Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

External Outlook Web Access (OWA) Availability Health Test

The External OWA Availability Health test monitors the availability of OWA functionality in your organization through an external URL. This test verifies that the users associated with the alternate credentials can logon to their mailboxes through an external OWA URL. This test uses an external or internal URL. If an external URL is specified, ensure that the DNS server can resolve this URL.

This test is applicable only to organizations with at least one Exchange 2007/ 2010 server. This test does not run on Exchange 2013 or later because the Microsoft Exchange Management Shell does not support OWA Connectivity testing for Exchange 2013 or later. For Exchange 2013 or Exchange 2016, you can use the Exchange System Health test to monitor OWA health.

This test uses mailboxes associated with alternate credentials. You must explicitly choose the alternate credentials on the Test Settings page when you create this test. You cannot configure the test if you have selected the Use Diagnostic Services Credentials option.

•
For an Exchange 2010 mailbox, a PowerShell 2.0 cmdlet is run on each Exchange 2010 CAS server in the organization until the mailbox logon attempt is successful.
•
For an Exchange 2007 mailbox, logons to the mailbox are attempted using a local Exchange 2007 Management Shell cmdlet.

If you would like to test External OWA functionality using both types of mailboxes, you must configure two tests - one using credentials of the user who has 2007 mailbox, and the second using credentials of the user with 2010 mailbox.

This test allows you to ensure the following:

•
Mailbox is accessible
•
Mailbox logon latency is within expected threshold.

Creating test mailboxes for Exchange

Creating and configuring health tests

External OWA availability 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.

 
Table 38. External OWA availability health test targets.
Exchange Server Version
Target Type

All

Exchange organization

 
Table 39. External OWA availability health test software.
Exchange Mailbox Version
Software required on UC Diagnostics computer

Exchange 2010

PowerShell 2.0 or later

Exchange 2007

Exchange 2007 Management Console (EMC) Service Pack 1 Rollup 1 or later

 
Table 40. External OWA availability health test configuration.
Exchange Mailbox Version
Required configuration

Exchange 2010

Account specified in the alternative credentials for the test must have mailbox on the Exchange 2010 server. The alternate credentials must have Exchange View-Only Organization Management privileges.

Exchange 2007

Account specified in the alternative credentials for the test must have mailbox on the Exchange 2007 server. The alternate credentials must have Exchange View-Only Administrator privileges.

 
Table 41. External OWA availability health test credential required permissions.
Exchange version
Permissions required for test credentials

Exchange 2007/2010
•
Account specified in alternate credentials must have an Exchange 2007/2010 mailbox, and sufficient rights to browse the Exchange container in Active Directory.

Exchange 2007
•
Diagnostic services account must have sufficient rights to execute Exchange 2007 Management Shell Service Pack 1.0 cmdlets on the server where UC Diagnostics is installed.

Exchange 2010
•
Diagnostic services account must have sufficient rights to execute Exchange cmdlets using PowerShell 2.0 on the Exchange 2010 CAS server in the Exchange organization.

Exchange Replication Health Test

The Exchange Replication Health test monitors the health of transaction log replication on your Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 mailbox servers. This test detects whether replication is configured and what type of replication is configured.

For Exchange 2010 and later, there is also information provided about lagged database copies if you have configured the Exchange lagged database copy function.

The Exchange Replication Health test contains the following counters for Exchange 2007:

 
Table 42. Exchange 2007 replication health test counters.
Category
Counter

Cluster Continuous Replication
•
Copy status
•
Copy queue length
•
Replay queue length
•
Hours since last log inspection
•
Target transaction log path

Local Continuous Replication
•
Copy status
•
Copy queue length
•
Replay queue length
•
Hours since last log inspection
•
Target transaction log path

Standby Continuous Replication
•
Copy status
•
Copy queue length
•
Replay queue length
•
Hours since last log inspection
•
Target transaction log path

The Exchange Replication Health test contains the following counters for Exchange 2010:

 
Table 43. Exchange 2010 replication health test counters.
Category
Counter

Passive Mailbox Database Copy
•
Master
•
Mounted on server
•
Copy status
•
Copy queue length
•
Replay queue length
•
Hours since last log inspection
•
Activation preference
•
Active on preferred servers
•
Replay lag status
•
Configured lag time

The Exchange Replication Health test contains the following counters for Exchange 2013 and Exchange 2016:

 
Table 44. Exchange 2013 and Exchange 2016 replication health test counters.
Category
Counter

Passive Mailbox Database Copy
•
Master
•
Mounted on server
•
Copy status
•
Copy queue length
•
Replay queue length
•
Hours since last log inspection
•
Activation preference
•
Active on preferred servers
•
Replay lag status
•
Configured lag time
•
Actual lag time
•
Lag percentage
•
Lag play down reason

Transaction log replication is handled by Database Availability Groups (DAGs) for Exchange 2010, Exchange 2013, and Exchange 2016. For more information, see Viewing Database Availability Groups (DAG) .

Creating test mailboxes for Exchange

Creating and configuring health tests

Exchange replication health test prerequisites

The following tables show the test target servers, required software, and the permissions needed by the test credentials.

 
Table 45. Exchange replication health test targets.
Exchange Server Version
Target Type

Exchange 2007/2010/2013/2016

Mailbox role

 
Table 46. Exchange replication health test software.
Exchange Server Version
Software Required on the UC Diagnostics computer

Exchange 2010/2013/2016

PowerShell 2.0 or later

Exchange 2007

Exchange Management Console (EMC) Service Pack 1 Rollup 1 or later

 
Table 47. Exchange replication health test credential required permissions.
Exchange version
Permissions required for test credentials

Exchange 2007
•
Member of View-only Exchange Administrators group to enumerate storage groups and replication configurations in Active Directory

Exchange 2010, 2013, and 2016
•
Member of View-only Organization Management group to enumerate storage groups and replication configurations in Active Directory using PowerShell

Exchange System Health Test

The Exchange System Health test monitors the health state for different groups of monitors, called health sets. Monitors that are similar or are related to a component’s architecture are grouped to form a health set. Health sets provide the health information for applications and services such as Outlook Web App, Exchange ActiveSync, the Information Store service, content indexing, and transport services on your Exchange 2013 Client Access Servers (CAS) and mailbox servers and on your Exchange 2016 mailbox servers.

If all a health set’s monitors are healthy, the health set is in a healthy state. If any monitor is not in a healthy state, the health set state is determined by its least healthy monitor.

This test is available only for Exchange 2013 and later.

The health sets are organized into four main health groups:

•
Customer Touch Points
•
Service Components
•
Server Components
•
Dependency Availability
Customer Touch Points health group

The Customer Touch Points health group is comprised of monitors for components that affect real-time user interactions such as protocols or the Information Store. The test shows the condition of healthy or unhealthy for each of the following health set counters:

 
Table 48. Counters for the Customer Touch Points health group.
Server roles
Health set counter

Exchange 2013 CAS

Exchange 2016 Mailbox
•
Autodiscover
•
Compliance
•
EWS (Exchange Web Services)
•
IMAP (IMAP4 proxy infrastructure)
•
Outlook
•
OWA (Outlook Web App)
•
POP (POP3 service and POP3 client connectivity)
•
UM (Unified Messaging)

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox
•
ActiveSync
•
ECP (Exchange Administration Center (EAC) and of the Outlook Web App user setting service)
•
RPS (Remote PowerShell service)

Exchange 2013 and 2016 Mailbox
•
Public Folders
•
Site Mailbox
Service Components health group

The Service Components health group is comprised of monitors for components without direct, real-time user interactions such as the Microsoft Exchange Mailbox Replication service or the offline address book generation process (OABGen). The test shows the condition of healthy or unhealthy for each of the following health set counters:

 
Table 49. Counters for the Service Components health group.
Server roles
Health set counter

Exchange 2013 CAS

Exchange 2016 Mailbox
•
ActiveSync.Proxy
•
Autodiscover.Proxy
•
ClientAccess.Proxy
•
ECP.Proxy (Exchange Administration Center proxy infrastructure)
•
EWS.Proxy (Exchange Web Services proxy)
•
FfoUMC (Forefront administration website)
•
FfoWebService (Forefront web service)
•
IMAP.Proxy
•
MailFlow
•
OAB.Proxy
•
Outlook.Proxy
•
OWA.Proxy
•
POP.Proxy
•
Transport

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox
•
Data Protection (redundancy of databases in a database availability group (DAG))
•
EDS (Exchange Diagnostic Service thresholds)
•
FIPS (Federal Information Processing Standards)
•
FrontendTransport
•
HubTransport
•
Monitoring
•
PowershellDataProvider (Exchange Management Shell)
•
RemoteMonitoring
•
RPS.Proxy (Remote PowerShell service)
•
Search
•
SMTP
•
UM.CallRouter
•
UserThrottling

Exchange 2013 and 2016 Mailbox
•
ActiveSync.Protocol
•
Antimalware
•
Antispam
•
Autodiscover.Protocol
•
Classification (Data Loss Prevention (DLP) feature)
•
Ediscovery.Procotol
•
Event Assistants
•
EWS.Protocol
•
FfoQuarantine (Forefront message quarantine)
•
FfoTransport (Forefront transport components)
•
FreeBusy
•
IMAP.Protocol
•
MailboxMigration
•
MailboxTransport
•
MessageTracing
•
MRS (Mailbox Replication Service)
•
MSExchangeCertificateDeployment
•
OAB (Offline Address Book)
•
Outlook.Procotol (MAPI protocol)
•
OWA.Protocol (Outlook Web App protocol)
•
POP.Protocol (POP3 protocol)
•
PushNotifications.Protocol
•
RPS.Protocol (Remote PowerShell protocol)
•
Store
•
UM.Protocol (Unified Messaging protocol)
Server Components health group

The Server Components health group is comprised of monitors for the server physical resources such as disk space, memory, and networking. The test shows the condition of healthy or unhealthy for each of the following health set counters:

 
Table 50. Counters for the Server Components health group.
Server Roles
Counter

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox
•
DiskSpace
•
Memory

Exchange 2013 and 2016 Mailbox
•
Clustering (Windows cluster services)
•
MailboxSpace
Dependency Availability health group

The Dependency Availability health group monitors the server’s ability to access necessary dependencies, such as Active Directory, DNS, and instant messaging. The test shows the condition of healthy or unhealthy for each of the following health set counters:

 
Table 51. Counters for the Dependency Availability health group.
Server Roles
Counter

Exchange 2013 CAS

Exchange 2013 and 2016 Mailbox
•
AD (Active Directory)
•
Network (in Domain Name System (DNS))

Exchange 2013 and 2016 Mailbox
•
OWA.Protocol.Dep (instant messaging services in Outlook Web App between Exchange and Skype for Business/Lync)
Exchange system health test prerequisites

The following tables show the test target servers, required software, and the permissions required by the test credentials.

 
Table 52. Exchange system health test targets.
Exchange Server Version
Target Type

Exchange 2013

Client Access Server (CAS) role

Mailbox role

Exchange 2016

Mailbox role

 
Table 53. Exchange system health test software.
Exchange Server Version
Software Required on the UC Diagnostics computer

Exchange 2013/2016

PowerShell 2.0 or later

 
Table 54. Exchange system health test credential required permissions.
Exchange Server Version
Permissions Required for Test Credentials

All

Be a member of the following groups:

•
Member of View-only Organization Management

Creating and configuring health tests

Active Directory Account Lockout Health Test

The Active Directory Account Lockout Health test provides information about how many and which Active Directory accounts are currently locked out. The test shows accounts that are locked out due to invalid passwords being submitted and accounts that are locked because the password has expired. The test detects the domain accounts that are currently locked out and provides information about the lockout event.

You run the test against a domain to which an Exchange organization or a Lync/Skype for Business environment belongs. You cannot run the test against the individual servers.

* 
NOTE: Information about locked-out accounts is available only for the first 1000 accounts.

The Active Directory Account Lockout Health test contains the following counters:

 
Table 55. Active Directory Account Lockout health test counters.
Category
Counter

General
•
Total accounts locked out

Lockout information
•
User status
•
Last time bad password was submitted
•
Number of login attempts with bad password
•
Date and time account was locked out
•
Last time password was changed
•
Next expiry date for password
Active Directory account lockout health test prerequisites

The following tables show the test targets for the test and the permissions required by the test credentials.

 
Table 56. Active Directory Account Lockout Health test targets.
Platform Versions
Target Type

Exchange 2007/2010/2013/2016

Organization

Lync 2010/2013 and Skype for Business 2015

Environment

The test credentials must have read permission on User objects in Active Directory.

 
Table 57. Active Directory Account Lockout Health test credential required permissions.
Platform
Permissions Required for Test Credentials

Exchange

•
Member of View-Only Exchange Administrators group or View-Only Organization Management group.

Lync/Skype for Business

•
Member of CSHelpDesk, CSServerAdministrator, or CSViewOnlyAdministrator group
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation