Chat now with support
Chat mit 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

Prerequisites for Exchange Delivery Health Tests

The following prerequisites are common to all the Exchange delivery health tests:

Exchange 2007/2010/2013

Exchange 2010 and later

See the individual test descriptions for information about required configuration and permissions needed to run each test:

Exchange Internal Server Delivery Health Test

The Exchange Internal Server Delivery Health test is used to monitor the sending and receipt of messages within an Exchange organization.This test sends a test message from each target server in the test to every other target server.

The Exchange Internal Server Delivery Health test sends a test message from each selected server to every other selected server. For example, if you select your whole organization as the test target and your organization has five mailbox servers, this test sends 20 test messages (5 source servers x 4 destination servers) at each monitoring interval.

This health test is not supported for Exchange 2013 and later. This test is also not useful for Exchange 2010 organizations that have implemented Database Availability Groups (DAGs) since mailboxes in a DAG are not linked to a specific server.

On Exchange 2007 servers, when the test runs, it looks for a test mailbox on each server. The test mailbox can be on any store on that server. You need one test mailbox per server to run this test. If there are multiple test mailboxes on each server, the test uses the first mailbox it finds. By default, the test mailbox creation scripts create one test mailbox per store.

You can configure this test to collect tracking information to trace the test message that flows through the Exchange servers.

For Exchange 2007, you can use the Internal Mailbox Delivery Health test to monitor the sending and receiving of messages between mailboxes. For Exchange 2010 and later, you can use the Exchange Modern Message Delivery Health test.

You must manually create test mailboxes and match the name to the mailbox mask specified in the test configuration. For more information, see Creating test mailboxes for Exchange .

For large organizations, select a subset of the servers to reduce the amount of traffic generated. For example, select one server per geographical region. You can also decrease the monitoring frequency.

For Exchange 2007 servers, create a test mailbox that matches the mailbox mask in at least one store on each server in the organization. However, it is recommended that you create a test mailbox in each store on each server.

For Exchange 2010 servers, create a test mailbox that matches the mailbox mask in at least one mounted mailbox database copy on each server in the organization. However, it is recommended that the test mailbox be created in each mailbox database on each server. When the test runs, it looks for a test mailbox on each server. The test mailbox is in a mailbox database. If there are multiple test mailbox boxes on each server, the test uses the first one it finds. By default, the test mailbox creation scripts create one test mailbox per mailbox database.

While the test is executing, storage groups and stores are enumerated in alphabetical order. If the test takes a long time to complete, you can create a test mailbox in the first storage group in the first store (in alphabetical order) on every server to speed up the query.

For example, you have a server called AMER-MBX-01 with the following stores:

If the mailbox mask specified in the test is the default mask (SOM_<ServerName>_<StorageGroupName>_<StoreName>, then the test looks for the following mailboxes for AMER-MBX-01 until it finds one that is accessible:

For example, you have a server called AMER-MBX-01 containing Database1 and Database2. If the mailbox mask specified in the test is the default mask (SOM_<ServerName>_<DatabaseName>, then the test looks for the following mailboxes for AMER-MBX-01 until it finds one that is accessible:

All test messages sent are automatically deleted from the internal test mailboxes. But other mail, such as NDR messages, is not automatically deleted. You must manually clean out your test mailboxes periodically.

From the All Exchange Servers tab, select the Collect message tracking information check box.

Internal Server Delivery

Creating test mailboxes for Exchange

Creating and configuring health tests

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

Exchange 2007/2010

Mailbox role

The Exchange server must be configured as follows:

Exchange 2007/2010

The test credentials must have the following permissions:

Exchange 2007/2010

Exchange 2007

Exchange 2010

Exchange Internal Mailbox Delivery Health Test

For Exchange 2007 to Exchange 2013, you can use the Exchange Internal Mailbox Delivery Health Test to monitor the sending and receipt of messages between mailboxes in an Exchange organization. This test supports DAGs.

For Exchange 2010 and later, it is recommended that you run the Exchange Modern Message Delivery Health Test instead, especially in scenarios in which the CAS server is behind a load balancer.

Message Delivery

Creating test mailboxes for Exchange

Creating and configuring health tests

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

You can run the test against the following target servers.

Exchange 2007/2010/2013

Mailbox role

The Exchange server must be configured as follows:

All

The test credentials must have the following permissions.

All Exchange versions

Additional for Exchange 2007

Additional for Exchange 2010

Additional for Exchange 2013

Exchange External Message Delivery Health Test

For Exchange 2007 to Exchange 2013, you can use the Exchange External Message Delivery Health test to monitor the health of message delivery to and from an external target.

For Exchange 2010 and later, it is recommended that you run the Exchange Modern Message Delivery Health Test instead, especially in scenarios in which the CAS server is behind a load balancer.

This test tracks the time it takes a test email to leave your organization and the time it takes the message to return to the original server.

For this test, you must enter the names of:

For more information about test prerequisites, see Unified Communications Diagnostics Deployment Guide.

This test targets your entire organization, not individual servers. You must create a test mailbox to run this test.

To monitor round-trip messages, the external mailbox must be configured to automatically bounce the message back to the original mailbox. You would enable the Round-Trip Delivery counter in the test.

All test messages sent are automatically deleted from the internal test mailbox. But any other mail, like NDR messages, are not automatically deleted. You may need to periodically clean out your test mailboxes.

By default, the Organization Exit counters are disabled because they are not fully supported when the source mailbox is hosted on Exchange 2013.The Round-trip Delivery counters are enabled because the external email account needs to be configured to automatically bounce the test message back to the originating mailbox.

Organization Exit

Round-trip Delivery

Creating test mailboxes for Exchange

Creating and configuring health tests

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

You can run the test against the following target servers.

Exchange 2007/2010/2013

Exchange organization

The Exchange server must be configured as follows:

All

The test credentials must have the following permissions.

All Exchange versions

Additional for Exchange 2007

Additional for Exchange 2010

Additional for Exchange 2013

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen