Chat now with support
Chat with Support

Unified Communications Diagnostics 8.4.1 - 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
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 Exchange 2007 test mailboxes

UC Diagnostics ships with a PowerShell script called new-Exchange2007TestMailboxes to simplify creating test mailboxes for Exchange 2007 servers. This script will create one test mailbox per store per server. The list of Exchange servers must be piped into the script.

The script must be run inside the Exchange 2007 Management Shell from a computer in the same forest as the Exchange servers. The script has the following syntax:

where:

Organizational Unit

Indicates the location in the Active Directory where the created user is associated with a mailbox.

If this parameter is not specified, you are prompted to enter the name of an Organizational Unit.

Mailbox Name Mask

Indicates the pattern of mailbox names that the script generates.

This parameter is optional. If it is not specified, the default mask is SOM_<ServerName>_<StorageGroupName>_<StoreName>.

Authorized User

Indicates the user account that will be granted access to the created mailboxes. This should be the account specified for the Diagnostic Services component during install unless alternate credentials are specified for the test.

If this parameter is not specified, you are prompted to enter the user account name.

No Prompt

Allows you to suppress confirmation to create each test mailbox.

This parameter is optional. If it is not specified, confirmation is required before creating each test mailbox.

To run scripts, the account must have the following permissions:

Exchange 2007

For example, to create test mailboxes on all servers with the default mailbox mask, use:

Or, to create test mailboxes on the server AMER-MBX-01 with a non-default mailbox mask:

Creating Exchange 2010 or Exchange 2013 test mailboxes

To simplify creating test mailboxes for Exchange 2010 or Exchange 2013 servers, UC Diagnostics ships with a PowerShell script called new-Exchange2010and2013TestMailboxes. This script creates one test mailbox per database per server, or one test mailbox per server, depending on the mask setting. The list of Exchange servers must be piped into the script.

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 server that hosts the active mailbox database copy. Mailboxes must be named according to the server and database where they are located.

If you are creating a test mailbox for the Exchange 2010 OWA Health test, ensure all database copies for the mailbox database are in the same site as your CAS server. Because 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).

You must run the script inside the Exchange 2010 or Exchange 2013 Management Shell from a computer in the same forest as the Exchange servers. The script has the following syntax:

 

Organizational Unit

Indicates the location in the Active Directory where the created user is associated with a mailbox. If this parameter is not specified, you are prompted to enter the name of an Organizational Unit.

Mailbox Name Mask

Indicates the pattern of mailbox names that the script generates. This must match the setting in the Internal Server Delivery Health test.

This parameter is optional. If it is not specified, the default mask is SOM_<ServerName>_<DatabaseName>.

<DatabaseName> is optional.

Authorized User

Indicates the user account that is granted access to the created mailboxes. This must be the account specified for the Diagnostic Services component during install unless alternate credentials are specified for the test.

No Prompt

Allows you to suppress confirmation to create each test mailbox.

This parameter is optional. If it is not specified, confirmation is required before creating each test mailbox.

To run this script, the account must have the following permissions:

The list of Exchange servers must be piped into the script.

For example, to create one test mailbox for every mailbox server in the Exchange organization, use the following script:

Or, to create one test mailbox on every mailbox database on the server AMER-MBX-01, use the following script:

About test mailboxes for Internal Server Delivery Health Test

This test involves the exchange of messages between each pair of servers in your network. You must create at least one test mailbox on each server that is included in the test.

By creating one mailbox per storage group/store (Exchange 2007) or per database (Exchange 2010), you can ensure that the complete test runs even if there is a problem with one of the stores or databases.

Mailboxes for the Internal Server Delivery Health test on Exchange 2007 servers must be named according to the server, storage group, and store where they are located. Mailboxes for the Internal Server Delivery Health test on Exchange 2010 servers must be named according to the server and database where they are located. For more information, see Exchange Internal Server Delivery Health Test .

If the test source mailbox is hosted on an Exchange 2010 mailbox database for the BlackBerry Message Delivery Health test or for the Exchange Internal and External Message Delivery Health tests, the Exchange organization must have at least, one available Exchange 2010 CAS server on the same site as the active mailbox database copy.

The Internal Server Delivery health test is not supported for Exchange 2013. Use the Internal Mailbox Delivery health test to monitor the sending and receiving of messages between mailboxes of all Exchange versions.

About test mailboxes for the External Message Delivery Health Test

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 destination mailbox can be in another Exchange organization or it can be in any of the free web-based email services.

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.

If the test source mailbox is hosted on an Exchange 2010/2013 mailbox database, the Exchange organization must have at least one available Exchange 2010/2013 CAS server that exists on the same site as the server that hosts the active mailbox database copy.

Related Documents