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

Unified Communications Diagnostics 8.6.2 - Deployment Guide

Installing and upgrading Unified Communications Diagnostics Technical Information for UC Diagnostics for Exchange Technical Information for Office 365 Technical Information for UC Diagnostics for BlackBerry Technical Information for UC Diagnostics for OCS Technical Information for UC Diagnostics for Lync/Skype for Business Troubleshooting

Exchange System Health Test

The Exchange System Health Test monitors health sets (groups of monitors) and health information on your Exchange 2013/2016 server, verifying the state of each health set’s monitors. 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 and Exchange 2016 servers.

This test allows you to ensure the health state of health set (whether health or unhealthy).

You can run the system health test against Exchange 2013 and later.

Test prerequisites

See the following tables for the test targets and the required permissions for this test.

You can run the test against the following target servers.

 
Table 37. Exchange system health test targets.
Exchange server version
Target type

Exchange 2013

Client Access Server (CAS) role

Mailbox role

Exchange 2016

Mailbox role

You must meet the following software prerequisites to run the Exchange system health tests:

 
Table 38. Exchange system health test required software.
Exchange server version
Software required on UC Diagnostics computer

Exchange 2013/2016

PowerShell 2.0 or later

The test credentials must have the following permissions.

 
Table 39. Exchange system health test permissions.
Exchange server version
Permissions Required for Test Credentials

All
•
Member of View-only Organization Management

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.

Test prerequisites

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

 
Table 40. 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 41. 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

Historical Reporting Database Usage Estimates

The following table lists the approximate amount of space required for each test each monitoring interval when running Web Reports and when storing test history:

Exchange 2013/2016 space usage
 
Table 42. Space required for web reports and test history - Exchange 2013/2016.
Health Test
Total Space Required per Server per Monitoring Interval (Web Reports)
Total Space Required per Server per Monitoring Interval (Test History)

Server Health

1.2 KB

242 KB

Internal Mailbox Delivery Health

0.1 KB (per source/destination delivery pair)

75 KB (for a test with 50 pairs)

External Message Delivery Health

0.1 KB

37 KB

Storage Health

0.3 KB (per store and per storage group)

52 KB

Queue Health

0.2 KB (per queue)

41 KB (per queue)

Replication Health

0.3 KB (per storage group)

35 KB

Exchange 2007/2010 space usage
 
Table 43. Space required for web reports and test history - Exchange 2007/2010.
Health Test
Total Space Required per Server per Monitoring Interval (Web Reports)
Total Space Required per Server per Monitoring Interval (Test History)

Server Health

1.2 KB

242 KB

Internal Server Delivery Health

0.1 KB (per target server)

36 KB

Internal Mailbox Delivery Health

0.1 KB (per source/destination delivery pair)

75 KB (for a test with 50 pairs)

External Message Delivery Health

0.1 KB

37 KB

Storage Health

0.3 KB (per store and per storage group)

52 KB

Queue Health

0.2 KB (per queue)

41 KB (per queue)

Internal OWA Health

0.1 KB

37 KB

External OWA Health

0.1 KB

37 KB

Replication Health

0.3 KB (per storage group)

35 KB

For example, to run Exchange 2007 Server Health on one server, the maximum space required (with default parameters) would be:

•
Raw data: 1.2 KB x 1 day x 48 bi-hourly values= 58 KB
•
Hourly data: 1.2 KB x 7 days x 24 hourly values = 202 KB
•
Daily data: 1.2 KB x 30 days x 1 daily value = 36 KB

For example, you have a medium-sized environment with the following characteristics:

•
Monitoring 50 Exchange servers
•
Each Exchange server has an average of 5 stores
•
Each Exchange server has an average of 10 queues
•
Running one of each test using the default counters
•
Using default monitoring of 30 minutes for all tests
•
Using default data retention of 7 days for hourly aggregation data
•
Using default data retention of 30 days for daily aggregation data
•
Running Internal Server Delivery Health fully meshed with all servers

The approximate space required for historical data would be:

 
Table 44. Estimated space requirements for specific tests.
Health Test
Total Space Required

Server Health

9.3 MB

Internal Server Delivery Health

15.3 MB

External Message Delivery Health

0.6 MB

Storage Health

6.2 MB

Queue Health

9.3 MB

Internal OWA Health

0.6 MB

External OWA Health

0.6 MB

Replication Health

2.3 MB

Total

41 MB

Exchange Diagnostic Console Technical Information

The Exchange Diagnostic Console provides you with a real-time representation of the messaging system processes and components within Exchange.

You can diagnose and resolve issues using the Exchange Diagnostic Console.

Prerequisite software

The following software must be installed on the UC Diagnostics computer to run the diagnostic console.

 
Table 45. Exchange diagnostic console required software.
Exchange server version
Software required on UC Diagnostics computer

Exchange 2010/2013/2016

PowerShell 2.0 or later

Exchange 2007

Exchange Management Console (EMC) SP 1 or later

Required configuration

The following configuration is required on the Exchange server.

 
Table 46. Exchange diagnostic console configuration.
Exchange server version
Configuration required

All

Enable WMI

Required permissions for Exchange

The following permissions are required on the Exchange servers.

 
Table 47. Exchange diagnostic console permissions.
Exchange server version
Permissions required to access Exchange server

Exchange 2010/2013/2016/2019
•
Member of Local Administrators group to have:
Read access to operating system drive to retrieve disk information
Read access to Service Control Manager
Read access to WMI to retrieve disk information
Read access to Registry to access Performance Counters, DNS settings, and Exchange information
Read access to PowerShell cmdlets for queue and mailbox database information
•
Member of View-Only Exchange Administrator or the View-Only Organization Management group to have:
Read access to PowerShell cmdlets for queue and mailbox database information

Exchange 2007
•
Member of Local Administrators group to have:
Read access to operating system drive to retrieve disk information
Read access to Service Control Manager
Read access to WMI to retrieve disk information
Read access to Registry to access Performance Counters, DNS settings, and Exchange information
Read access to PowerShell cmdlets for queue, storage group, store, and mailbox information
•
Member of View-Only Exchange Administrator to have:
Read access to PowerShell cmdlets for queue, storage group, store, and mailbox information
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택