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

Creating a test mailbox for External Message Delivery Health Test

The External Message Delivery Health tests do not have any restrictions on the name of the mailbox.

The Exchange External Message Delivery Health Test allows you to monitor the ability to send a message to an external target, and to measure delivery and round trip time.

For this test, you must enter the names of:

•
The source mailbox to send a message to an SMTP address and receive replies from that address.
•
The destination email address where test messages is sent.

The destination mailbox can be in another Exchange organization or in any free web-based email service.

To test round-trip delivery, the destination mailbox must be configured to automatically forward the message back to the originating mailbox, thus enabling the Round-Trip Delivery counter in the test. For the test to recognize the returning message, the original subject line must be inserted in the subject or body of the returning message.

For External Message Delivery Health tests, if the test source mailbox is hosted on an Exchange 2010/2013 mailbox database, the Exchange organization must have at least one available Exchange CAS server that exists on the same site as the active mailbox database copy.

To create test mailboxes for Exchange 2010/2013, see Creating Exchange 2010 or Exchange 2013 test mailboxes .

To create test mailboxes for Exchange 2007, see Creating Exchange 2007 test mailboxes .

Creating a test mailbox for the Internal Mailbox Delivery Health Test

You can create user mailboxes or dedicated test mailboxes for source and target mailbox pairs to allow both DAG and non-DAG database mailboxes. You can create one or more test mailboxes on each mailbox database.

For information about creating test mailboxes for Exchange 2010 or 2013, see Creating Exchange 2010 or Exchange 2013 test mailboxes . For information about creating test mailboxes for Exchange 2007, see Creating Exchange 2007 test mailboxes .

Creating test mailboxes for the OWA Availability Health Test

The OWA Availability Health uses a Microsoft PowerShell cmdlet called test-OwaConnectivity to test OWA availability. For this cmdlet to run, you must create at least one test mailbox using the Microsoft PowerShell cmdlet called new-TestCasConnectivityUser. For more information about this cmdlet, go to www.microsoft.com.

You must create one or more test mailboxes on a Mailbox server to perform this test. It is recommended that you set the accounts created for test mailboxes to have “password never expires”. This setting prevents logon failures due to a password expiring.

Creating Exchange 2007 test mailboxes for OWA Availability

UC Diagnostics uses a PowerShell script to simplify creating test mailboxes for Exchange 2007 servers. You must create mailboxes for the Exchange 2007 OWA Availability Health test using the PowerShell cmdlet called new-CASConnectivityMailbox.

To create test mailboxes for the Internal OWA Availability test
1
Login to one of your Exchange 2007 Mailbox servers as a Domain Administrator.
2
Open the Exchange Management PowerShell Console.
3
Change the directory to the Exchange Server Scripts folder (for example, C:\Program Files\Microsoft\Exchange Server\Scripts)
4
Execute the following command:
get-mailboxServer|.\new-TestCasConnectivityUser.ps1
5
When prompted for the Organizational Unit (OU), enter the Distinguished Name (DN).
The OU is specified as a DN since multiple OUs of the same name can exist in your organization. For example:
OU=Users,DC=mscs,DC=qc,DC=kan,DC=ca,DC=qsft
Creating Exchange 2010 Test Mailboxes for OWA Availability

UC Diagnostics uses a PowerShell script to simplify creating test mailboxes for Exchange 2010 servers.Mailboxes for the Exchange 2010 OWA Availability Health test must be created using the PowerShell cmdlet called new-CASConnectivityMailbox.

Ensure all database copies of the mailbox database are in the same site as your CAS server. The PowerShell cmdlet used in the test requires a test mailbox for each site. This guarantees you always have a test mailbox in the site, even when databases fail over/switch over among member servers of the Database Availability Group (DAG).

To create test mailboxes for the Internal OWA Availability test
1
Login to one of your Exchange 2010 Mailbox servers as a Domain Administrator.
2
Open the Exchange Management PowerShell Console.
3
Change the directory to the Exchange Server Scripts folder (for example, C:\Program Files\Microsoft\Exchange Server\Scripts)
4
Execute the following command:
get-mailboxServer|.\new-TestCasConnectivityUser.ps1
To specify the OU in which the test mailboxes are created, include the “-ou” parameter in the above command. This avoids a potential error message returned by the script if the “Users” OU exists anywhere in your Active Directory. For example, enter:
get-mailboxServer|.\new-TestCasConnectivityUser.ps1 -ou "OU=Users,DC=mscs,DC=qc,DC=kan,DC=ca,DC=qsft"

Creating a test mailbox for the External OWA Availability Health Test

This test verifies that users associated with the alternate credentials can logon to their mailboxes through an external OWA URL.

Since 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.

Account Prerequisites

The account associated with alternate credentials must have a mailbox on Exchange 2007 or 2010. The alternate credentials must have View-Only Organization Management privileges for Exchange 2010.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating