Spotlight on Messaging User Guide

7.4.17.4.17.4.17.4.1Spotlight on MessagingSpotlight on MessagingSpotlight on MessagingSpotlight on Messaging

User Guide

© 2010 Quest Software, Inc. ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software World HeadquartersLEGAL Dept5 Polaris WayAliso Viejo, CA 92656 USAwww.quest.comemail: [email protected]

Refer to our Web site for regional and international office information.

TRADEMARKS

Quest, Quest Software, the Quest Software logo, and Spotlight are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners.

Third Party Contributions

Spotlight on Messaging 7.4.1 contains some third party components (listed below). Copies of their licenses may be found on our website at http://www.quest.com/legal/third-party-licenses.aspx.

Quest Spotlight on Messaging User GuideUpdated - January 2010Software Version - 7.4.1

COMPONENT LICENSE OR ACKNOWLEDGEMENT

Zlib zlib 1.2.3

http://www.quest.com/

mailto:[email protected]

http://www.quest.com/legal/third-party-licenses.aspx

CONTENTS

CHAPTER 1INTRODUCING QUEST SPOTLIGHT ON MESSAGING . . . . . . . . . . . . . 7

ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ABOUT SPOTLIGHT ON MESSAGING . . . . . . . . . . . . . . . . . . . . 8

ABOUT THE DIAGNOSTIC PACKS . . . . . . . . . . . . . . . . . . . 9

CHAPTER 2GETTING STARTED USING THE MANAGEMENT CONSOLE . . . . . . . . 11

ABOUT THE MANAGEMENT CONSOLE . . . . . . . . . . . . . . . . . . . .12

CONNECTING TO A PLATFORM. . . . . . . . . . . . . . . . . . . . . . . .13

CONNECTING TO DIAGNOSTIC SERVICES . . . . . . . . . . . . . . . . .16

IMPORTING AND EXPORTING TOPOLOGY LAYOUT . . . . . . . . . . . .17

UNDERSTANDING FEDERATED PARTNERS IN OCS . . . . . . . . . . . .18

UNDERSTANDING SERVER PROPERTIES . . . . . . . . . . . . . . . . . .18

UNDERSTANDING POOL PROPERTIES IN OCS . . . . . . . . . . .20

UNDERSTANDING LINKS . . . . . . . . . . . . . . . . . . . . . . . .20

MANAGING CUSTOM GROUPS . . . . . . . . . . . . . . . . . . . . . . . .21

CREATING A STATIC CUSTOM GROUP . . . . . . . . . . . . . . . .21

CREATING A DYNAMIC CUSTOM GROUP . . . . . . . . . . . . . . .22

EDITING A CUSTOM GROUP . . . . . . . . . . . . . . . . . . . . . .22

DELETING A CUSTOM GROUP . . . . . . . . . . . . . . . . . . . . .22

GROUPING SERVERS BY TYPE . . . . . . . . . . . . . . . . . . . . . . . .23

MANAGING GLOBAL FILTERS . . . . . . . . . . . . . . . . . . . . . . . .23

PUTTING SERVERS IN MAINTENANCE MODE . . . . . . . . . . . . . . .24

MANAGING MISSING OBJECTS . . . . . . . . . . . . . . . . . . . . . . .25

VIEWING DATABASE AVAILABILITY GROUPS (DAG) . . . . . . . . . .25

CHAPTER 3DETECTING PROBLEMS USING THE MANAGEMENT CONSOLE . . . . . 27

INTRODUCING HEALTH TESTS. . . . . . . . . . . . . . . . . . . . . . . .28

TYPES OF HEALTH TESTS . . . . . . . . . . . . . . . . . . . . . . . . . .28

SERVER HEALTH TEST . . . . . . . . . . . . . . . . . . . . . . . . .30

BLACKBERRY MESSAGE DELIVERY HEALTH TEST . . . . . . . . .30

Quest Spotlight on Messaging

iv

EXCHANGE INTERNAL MESSAGE DELIVERY HEALTH TEST . . . .31

EXCHANGE EXTERNAL MESSAGE DELIVERY HEALTH TEST . . . .32

EXCHANGE STORAGE HEALTH TEST . . . . . . . . . . . . . . . . .33

EXCHANGE QUEUE HEALTH TEST. . . . . . . . . . . . . . . . . . .36

EXCHANGE OUTLOOK WEB ACCESS AVAILABILITY

HEALTH TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

EXCHANGE REPLICATION HEALTH TEST . . . . . . . . . . . . . . .39

MANAGING TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

CREATING A HEALTH TEST . . . . . . . . . . . . . . . . . . . . . .41

CONFIGURING TEST SETTINGS . . . . . . . . . . . . . . . . . . . .42

EDITING A HEALTH TEST . . . . . . . . . . . . . . . . . . . . . . .54

ENABLING/DISABLING A HEALTH TEST . . . . . . . . . . . . . . .55

RUNNING A HEALTH TEST NOW . . . . . . . . . . . . . . . . . . .55

DELETING A HEALTH TEST . . . . . . . . . . . . . . . . . . . . . .55

CLONING A HEALTH TEST . . . . . . . . . . . . . . . . . . . . . . .55

VIEWING TEST RESULTS . . . . . . . . . . . . . . . . . . . . . . . .56

CHAPTER 4RESOLVING PROBLEMS USING THE MANAGEMENT CONSOLE . . . . . 59

LAUNCHING NATIVE TOOLS . . . . . . . . . . . . . . . . . . . . . . . . .60

CHAPTER 5DIAGNOSING PROBLEMS USING THE MANAGEMENT CONSOLE . . . . 63

LAUNCHING THE DIAGNOSTIC CONSOLE FROM THE MANAGEMENT CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . .64

CHAPTER 6DIAGNOSING PROBLEMS USING THE DIAGNOSTIC CONSOLE . . . . . 65

INTRODUCING THE DIAGNOSTIC CONSOLE . . . . . . . . . . . . . . . .66

LAUNCHING AND CONNECTING TO THE DIAGNOSTIC CONSOLE .67

UNDERSTANDING THE DIAGNOSTIC CONSOLE . . . . . . . . . . . . . .68

UNDERSTANDING THE BLACKBERRY DIAGNOSTIC CONSOLE . . .69

UNDERSTANDING THE EXCHANGE 2000/2003

DIAGNOSTIC CONSOLE. . . . . . . . . . . . . . . . . . . . . . . . .78

UNDERSTANDING THE EXCHANGE 2007

DIAGNOSTIC CONSOLE. . . . . . . . . . . . . . . . . . . . . . . .103

UNDERSTANDING THE EXCHANGE 2010

v

DIAGNOSTIC CONSOLE. . . . . . . . . . . . . . . . . . . . . . . .118

UNDERSTANDING THE OCS DIAGNOSTIC CONSOLE. . . . . . .134

CHAPTER 7REPORTING USING WEB REPORTS . . . . . . . . . . . . . . . . . . . . . 143

UNDERSTANDING WEB REPORTS . . . . . . . . . . . . . . . . . . . . .144

TYPES OF REPORTS . . . . . . . . . . . . . . . . . . . . . . . . . .146

APPENDIX ACOUNTERS WITH NON-ZERO ALARM VALUES . . . . . . . . . . . . . . 151

GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

CONTACTING QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . .173

CONTACTING QUEST SUPPORT . . . . . . . . . . . . . . . . . . . . . .173


vi

Introducing Quest Spotlight on Messaging

• About This Guide

• About Spotlight on Messaging

• About the Diagnostic Packs

1


8

About This Guide

This document has been prepared to assist you in becoming familiar with the

Quest Spotlight on Messaging Diagnostic Packs for Blackberry, Exchange, and

Office Communications Server (OCS). The User Guide contains the information

required to launch and use the Spotlight on Messaging Diagnostic Packs. It is

intended for network administrators, consultants, analysts, and any other IT

professionals using the product.

About Spotlight on Messaging

Spotlight on Messaging helps administrators detect problems in their messaging

environment, accurately locate the root cause, and resolve the problems from a

single, easy-to-use interface. It provides a robust and informed troubleshooting

solution for Exchange, BlackBerry, and Office Communications Server (OCS).

Spotlight on Messaging contain the following components and features:.

COMPONENT DESCRIPTION

Management Console The Management Console gives the overall picture of your

servers. It helps you visualize and monitor the health of all

your servers. It contains the following features:

• Automatic discovery process — initially discovers and

displays all your servers in the Management Console.

Discovery runs automatically once a day to detect

changes to your environment.

• Monitoring and detection — allows you to monitor the

health of your environment and detect any problems

before they happen

• Detailed web reports — provide historical reporting and

trending and analysis over time

Note: For more information on the Management Console,

see “About the Management Console” on page 12.

About Spotlight on Messaging

9

About the Diagnostic Packs

The Diagnostic Packs include:

Diagnostic Console The Diagnostic Console allows you to view one server at a

time. It contains the following features:

• Real-time diagnostics — provides visual representation of

process flows within a server so you can observe actual

server activity in real time

• Auto calibration — determines the normal range of values

for your server and sets the visual indicators accordingly

• Rapid resolutions — displays the details of problem areas

including user connections, clients, and server resources

for rapid problem resolutions

• Effective warnings — provides visual warnings to alert

you when performance metrics exceed acceptable

thresholds

• Detailed drilldown tables and graphs — provide detailed

information allowing you to identify the source of each

problem

Note: For more information on the Diagnostic Console, see

“Diagnosing Problems using the Diagnostic Console” on page

65.

Web Reports Web Reports allow you to view trending and historical data

using preconfigured and custom reports, graphs, and tables.

Note: For more information on Web Reports, see “Reporting

Using Web Reports” on page 143.

Each Diagnostic Pack comes with a 30-day trial license. If you do not want to

purchase a full license before your 30-day trial expires, right-click the

Diagnostic Pack you are not using, and select Deactivate Plug-In. Else, your

trial will expire and you will lose all Diagnostic Pack functionality.

DIAGNOSTIC PACK DESCRIPTION

BlackBerry The BlackBerry Enterprise Server (BES) is a Windows-based

server product that manages data transfer and

synchronization between handheld devices and a messaging

and collaboration server such as Exchange.



10

Home Page

Each Diagnostic Pack provides a Home Page to help you become familiar with

the functionality and product features of each Diagnostic Pack in an

easy-to-navigate format.

This page contains various hyperlinks from which you can get you started on

detecting, diagnosing, and resolving problems with the Spotlight on Messaging .

The Home Page provides access to the following functional features from which

you can choose:

• Connecting to a server. For more information, see “Connecting to a

Platform” on page 13.

• Configuring Global Setting (Notification Settings, Alternate Credential

Settings, and Default Test Settings). For more information on

configuring global settings, see see “Configuring Test Settings” on

page 69.

• Creating Health Tests. For more information on health tests, see

“Detecting Problems Using the Management Console” on page 27.

Exchange The Exchange Diagnostic Pack helps diagnose and resolve

problems for your entire Microsoft® Exchange server

organization.

OCS Microsoft® Office Communications Server (OCS) 2007

combines enterprise-ready instant messaging (IM), presence,

conferencing, and Voice over IP (VoIP) telephony in a fully

integrated unified communications solution.a

a.Microsoft Office Communications Server 2007 Technical Overview

DIAGNOSTIC PACK DESCRIPTION

Getting Started Using the Management Console

• About the Management Console

• Connecting to a Platform

• Connecting to Diagnostic Services

• Understanding Federated Partners in OCS

• Understanding Pool Properties in OCS

• Understanding Server Properties

• Managing Custom Groups

• Grouping Servers by Type

• Managing Global Filters

• Putting Servers in Maintenance Mode

• Managing Missing Objects

• Viewing Database Availability Groups (DAG)

2


12

About the Management Console

The Management Console, based on the Microsoft Management Console (MMC),

hosts administrative tools that you can use to administer networks, computers,

services, and other system components. When you add the Diagnostic Packs,

you get a complete overview of your organization and servers.

To open the Management Console

• Click Start | Program Files | Quest Software | Spotlight |

Spotlight on Messaging.

The Management Console is divided into the following:

Your BlackBerry servers are located under your Exchange organization in the

treeview.

MANAGEMENT CONSOLE

SECTIONDESCRIPTION

Menu Contains the standard menu items, plus others:

• File — allows you to set console options

• Action — allows you to connect to an

organization or environment, group sites, set

global filters, create a health test, force

discovery, and import/export topologies

• View — allows you to show and hide items in the

MMC

• Windows — allows you to set the view of the

current window and indicates what windows are

open

• Help — allows you to open help topics and view

the version number of the MMC and Spotlight on

Messaging

Treeview Allows you to:

• configure Global Settings

• view Web Reports

• view organizations, groups, and servers. Groups

are displayed as a collection of servers, and

servers are displayed as icons within the

collections in the topology


13

Connecting to a Platform

The Management Console displays all your servers at a glance whether they

exist in a single location or span the globe. It is the framework where the layout

of your servers are displayed, tests are performed, notifications are configured,

and server data is displayed.

You can use the Management Console to connect to a BlackBerry, Exchange, or

OCS platform.

The first time you connect to a platform, all servers are discovered. Discovery

will find your available servers, then get the properties of those servers.

Results pane Allows you to:

• view the topology in a graphical format

• drag and drop servers for better organization

• view the status and details about discovery

• view test results

Actions pane Allows you see all the actions on the currently

selected object

Properties Pane • Shows details of your selected server, such as:

-Site name

-Exchange, BlackBerry, or OCS version

-Operating System Version

-Operating System Service Pack

• Shows details of your selected link, such as:

-Link name

-Relation of the link from one server to another

• Gives instructions on how to zoom, pan, and

auto-arrange your topology layout

Discovery can take some time depending on the size of your organization or

environment. For more information on discovery, see the Quest Spotlight on

Messaging Deployment Guide.

MANAGEMENT CONSOLE

SECTIONDESCRIPTION


14

Discovery then occurs every 24 hours to check for changes you may have made.

To connect to an Exchange organization

1. Right-click the Spotlight on Messaging node and select Connect

to an Exchange organization.

2. Enter a global catalog (or domain name or Exchange server name),

and click OK.

To connect to a BlackBerry server

You must be connected to an Exchange organization before you can connect to

a BlackBerry server.

1. Right-click the Exchange organization node and select Connect to

BlackBerry Servers.

2. In the Connect to BlackBerry Servers dialog box, click Add.

3. Enter the BlackBerry Database location and the BlackBerry Database

name, and click OK.

If you want to add multiple BlackBerry servers, repeat steps 2 and 3.

You can only add one BlackBerry server at a time.

If you select Repeat Discovery, discovery will run at the start time initially

indicated, then run at the new setting configured in the Every...hours box.

This overrides the daily start time.

If you are connecting to an Exchange cluster, you must use a virtual server

name.

If you are using a BlackBerry database that is installed on a named SQL

instance, you must specify the instance name, such as

MyServer/MySQLInstance, in the BlackBerry Configuration Database dialog

box. If the SQL instance hosting the BlackBerry database is configured to use

a non-default port, you can specify the port number in the Database Location

box separated by comma, such as: MyServer/MySqlInstance,1345 where

1345 is the port number.

Note: You do not need to specify a port number if your alias is configured for

the SQL named instance hosting BlackBerry database on the SQL server, or

the SQL Server Browser service is installed and running on SQL server.


15

To connect to an OCS environment

1. Right-click the Spotlight Management Console node and select

Connect to an OCS organization.

2. Enter a global catalog (or domain name or OCS 2007 or OCS 2007

R2 server name) and click Connect.

To customize connection properties

You can customize your connection properties to allow discovery to occur at

times other than every 24 hours.

• Right-click the connection in the treeview and select Properties.

Use the View Connection Properties dialog box to change or customize

parameters as necessary.

To disconnect from an organization/environment

1. From the treeview, right-click an organization or environment.

2. Select Disconnect from Organization (if you are connected to an

Exchange organization) or Disconnect from Environment (if you

are connected to an OCS environment).

Disconnecting from your organization/environment removes the

organization/environment from the treeview only. No data is deleted.

Scheduled tests will still execute, data will still be collected, and

discovery will still run.

To remove the organization/environment

1. From the treeview, right-click an organization or environment.

Because BlackBerry server and Exchange organization discovery takes place

at the same time, if you want to change BlackBerry connection properties,

you must change them at the Exchange organization level.

1. Right-click the BlackBerry server.

2. Select Edit BlackBerry Servers Connection Properties.

The next time you run OCS Management Console and connect to the same

environment, it will not rediscover upon connecting. If changes are made to

the environment and not shown in the OCS Management Console, right-click

the connection node in the treeview and select Force Discovery.


16

2. Select Remove Organization (if you are connected to an Exchange

organization) or Remove Environment (if you are connected to an

OCS environment).

Removing your organization/environment stops Spotlight on

Messaging from collecting any information about that

organization/environment. All data, such as test results history, web

report data, and test settings, related to the organization or

environment is permanently deleted.

You can reconnect to your organization/environment, but you must

reconfigure all test settings and web reports.

Connecting to Diagnostic Services

To use the Management Console, you must be connected to the Diagnostic

Services. The Management Console automatically connects to the Diagnostic

Services on the local host, if a Diagnostic Services server is available. If

Diagnostic Services are not available, you are prompted to enter the name of the

Diagnostic Services server.

Once you connect to a Diagnostic Services server, the connection is saved to a

.msc file. Once you have connected to the Diagnostic Services the first time, it

will not be necessary to do so again unless you wish to connect to Diagnostic

Services located on a different server.

To connect to the Diagnostic Services

1. Right-click Spotlight on Messaging and select Select Diagnostic

Services Server.

2. Enter the name of the Diagnostic Services Server.

3. Click OK.

The account used to run the Management Console must be a member

of the Local Administrators group on the server where the Diagnostic

Services are running, and have sufficient rights to access the

Spotlight Management Framework database. For more information,

see the Spotlight on Messaging Deployment Guide.

To remove a BlackBerry organization

1. From the treeview, right-click the Exchange organization node and select

Connect to BlackBerry Servers.

2. In the Connect to BlackBerry Servers dialog box, select a BlackBerry

server.

3. Click Remove.


17

Multiple consoles can be connected to the same Diagnostic Services

simultaneously, and have full read/write access to all Spotlight on Messaging

functionality. Changes made in one console will be appear in the other consoles.

If different users edit the same test at the same time, the user who saves their

changes last will have their settings preserved.

Information such as discovery, tests, credentials, test settings, custom groups,

and global settings are shared amongst the Management Consoles.

Global filters, Topology layout, and Group By settings are not shared amongst

the Management Consoles.

Different Management Consoles can be connected to different organizations. For

example, one Management Console can be connected to an Exchange

organization, while another is connected to an OCS environment.

When you connect to an Exchange organization, the Management Console will

discover and display your entire Exchange organization. Discovery is initially

configured to run automatically once a day to detect changes to your

environment.

Importing and Exporting Topology Layout

You can export your current topology layout to be imported to another topology.

In general, one topology layout is saved per grouping node in the .msc file. The

Importing and exporting function allows you to have several possible topology

layouts.

To export a topology layout

1. Right-click an organization in the treeview or right-click your

topology layout.

2. Select Export Topology Layout.

3. Enter the name for the file and save it as a .topology file.

You cannot save different topology layouts over different grouping modes.

For example, if you export a topology layout that was grouped by site, you

cannot import that layout if your current topology layout is grouped by

domain.


18

To import a topology layout

1. Right-click a server node in the treeview or right-click your topology

layout.

2. Select Import Topology Layout.

3. Select the .topology file you want to import.

Understanding Federated Partners in OCS

Federation provides your environment with the ability to communicate with

other environments to share IM and presence. You can also federate with an

audio conferencing provider.

You can allow automatic discovery of federated partners or manually configure

federation using the Computer Management administrative tool.

For more information, see

http://technet.microsoft.com/en-us/library/bb663635.aspx.

Understanding Server Properties

Right-click a server in your pool in your OCS environment to find the following

list of properties:

SERVER PROPERTY DESCRIPTION

General Lists the DNS name, IP address, and installed

roles of the server.

System Lists information related to the computer's

environment, such as Operating System, Memory

Usage and Processors.

Ports List the ports being used by the OCS 2007 or OCS

2007 R2 roles installed on the computer.

http://technet.microsoft.com/en-us/library/bb663635.aspx


19

You can also right-click a server that is not part of a pool to find the following

list of properties:

SERVER PROPERTY DESCRIPTION

General Lists the DNS name, IP address, and installed

roles of the server.

System Lists information related to the computer's

environment, such as Operating System, Memory

Usage, and Processors.

Archiving List the Archiving database server, Archiving

database name, threads available, MSMQ queue

name, and message retention period configured

for the Archiving server.

CWA Specifies the authentication type and modes,

timeout periods for public and private

connections, and ports used by the

Communicator Web Access server.

Note: The name in brackets represents the site

name configured when you install CWA.

Mediation Lists the encryption level, Media Gateway and

proxy settings, and the ports used by the

Mediation server.

QoE Monitor Lists the listening addresses and ports, data

retention period, database instance name, report

URL, MSMQ queues, and file system log settings

for the Quality of Experience (QoE) monitoring

server.

Access Edge Lists the external listening address and ports

used by the Access Edge server.

Ports Lists the ports being used by the server.

A/V Edge Lists the external IP address and the external and

internal ports used by the Audio/Video and MRAS

servers.

MRAS Lists the timeout periods if your session is either

left idle or running, and, if applicable, any

alternate TURN servers.

Web Conferencing Edge Lists the external listening address and ports

used by the Web Conferencing edge server.


20

Understanding Pool Properties in OCS

Right-click a pool in your Topology tab in your OCS environment to find the

following list of properties:

Understanding Links

Links show the flow of information from one server to another.

There are two types of links in your organization:

POOL PROPERTY DESCRIPTION

Settings Lists the connection pool settings.

Endpoints Lists the number of clients connected to each

Front-End in the pool.

Conferences Lists all types of participants in a conference such

as those that organize or control a conference

(Unique Organizers, Enterprise participants, and

external participants). It also tells you the

conferences that are queued (Allocated

Conferences) and those that are currently in

session (Active Conferences).

Client filters Displays the status and configuration settings for

the Client Filters.

IM files Displays configuration and settings information

related to the Instant Message Filter.

LINKS DESCRIPTION

Routing Group

Connectors

Shows the connectors that evaluate the optimal path for

emails from one server to another. The links can be

bidirectional or unidirectional. Routing groups are shown when

you group by Routing Group in Exchange 2000/2003 and

Exchange 2007 environments that contain Exchange 2003

servers.

The properties of a Routing Group connector (which are shown

in the Properties Pane when a Routing Group connector link is

selected) include Cost and Bridgeheads.


21

Managing Custom Groups

Custom groups allow you to create arbitrary groups of servers to simplify test

management. For example, you can a create a group of servers once and use

that custom group as the target for multiple tests. If you change the custom

group, the tests will automatically target the new group of selected servers.

Custom groups will appear under the Custom Groups node in the treeview. Since

custom groups are used as test targets, they are shared between all users of the

console.

There are two types of custom groups which you can create.

Creating a Static Custom Group

To create a static custom group

1. Select a group of servers.

2. Right-click and select New Custom Group.

Site Connectors Shows the connectors that evaluate the optimal path of

network traffic. Sites are shown when you group by sites in all

platforms.

The properties of a Site connector (which are shown in the

Properties Pane when a Site connector link is selected) include

Cost and Group Membership (which lists sites that are

associated with the connector).

CUSTOM GROUP TYPE DESCRIPTION

Static A user-selected group of arbitrary servers

Dynamic A group of servers that meet a set of criteria

defined by a user based on properties of the

servers

Custom groups do not appear in the topology view.

LINKS DESCRIPTION


22

3. In the New Custom Group dialog box, select the servers you want

included in the group.

4. Enter a name for the custom group and click OK.

Creating a Dynamic Custom Group

To create a dynamic custom group

1. Right-click the Custom Groups node in the treeview and select

Create Dynamic Custom Group.

2. In the New Custom Group dialog box, enter a name for the custom

group.

3. Select the type of server for which you want to search.

4. Click Add to insert criteria for the selected servers.

5. Click OK.

Editing a Custom Group

To edit a custom group

• Right-click your custom group node under the Custom Groups node

in the treeview and select Edit Custom Group.

Deleting a Custom Group

To delete a custom group

• Right-click your custom group node under the Custom Groups node

in the treeview and select Delete.

Property criteria are cumulative — only servers that match all of the selected

criteria will be part of the custom group.


23

Grouping Servers by Type

You can group OCS or Exchange servers by type.

To group servers by type

1. Right-click the connection in the treeview and select Group By.

2. Select the grouping that you want for the servers.

The servers appear in the treeview according to the grouping that you

have selected.

Managing Global Filters

A global filter allows you to hide any servers in which you are not interested. It

hides the servers from both the treeview and topology view.

To enable or customize global filter

1. Right-click your root connection node and select Set Global Filter.

2. In the Global Filter dialog box, select the servers you want to remain

visible and click OK.

SERVER GROUP BY

OCS • Pool

• Site

• Domain

Note: The default grouping for OCS is Pool

Exchange • Site

• Administrative Group

• Routing Group

• Domain

• None

Note: The default grouping for Exchange is Site.

If you would like to select all servers, right-click the top node and click

Select All. If you would like to clear your selection, right-click the top node

and click Clear All.


24

To remove global filters

• Right-click your root connection node and select Remove Global

Filter.

Global filters do not affect any tests that are scheduled to run against those

hidden servers.

Global filters are stored in the MMC configuration file (.msc), so different .msc

files can store different global filters. The MMC description bar indicates when

global filters are enabled to remind you that some servers are hidden.

Global filters can be customized per console. For example, if two different users

have their own console and are sharing the same Diagnostic Services, they can

each set different global filters.

Putting Servers in Maintenance Mode

Maintenance mode, which affects all users, allows you to mark servers as offline

so that you can perform maintenance on those servers. When any test runs,

Spotlight on Messaging Management Console will skip any servers that are in

maintenance mode.

To put a server into maintenance mode

1. Select target servers.

2. Right-click and select Start Maintenance Mode.

To remove a server from maintenance mode

1. Select target servers.

2. Right-click and select Stop Maintenance Mode.

While a server is in maintenance mode, the icon for the server darkens to

visually indicate the state of the server.


25

Managing Missing Objects

If you decommission a server, the server will remain in the topology and

treeview, but will be inactive. That is, you cannot perform any actions on that

server. The server remains to keep any historical data for Web Reports. If you

recommission the server, the server will become active again. If the server is no

longer required, you can delete it.

To delete a server

• Right-click the server and select Delete.

Viewing Database Availability Groups (DAG)

If you have DAGs configured in your Exchange organization, the DAGs dialog box

displays the following information for each DAG:

• member servers

• mailbox databases that are configured to replicate within the DAG

• database copies for each mailbox database

You can view DAGs in Exchange 2010 organizations only.

To view DAGs

1. From the treeview, right-click the Exchange 2010 organization node.

2. Select Database Availability Groups.

The facts shown are for informational purposes only. You cannot edit this

information in the dialog box. You can refresh the information by pressing F5 or

closing then reopening the dialog box.

In some situations, Spotlight on Messaging can fail to retrieve some of the

information. If this happens, the missing value will:

To view DAGs, you must:

• be part of the domain

• install Windows PowerShell 2.0 or later on the Management Console

computer

• have sufficient rights to connect to the remote PowerShell computer and

execute Exchange cmdlets


26

• be displayed as N/A

• be marked with the grey icon

• display the reason for the failure in the Details column

For more information on DAG, see

http://technet.microsoft.com/en-us/library/dd298065(EXCHG.140).aspx.

http://technet.microsoft.com/en-us/library/dd298065(EXCHG.140).aspx

Detecting Problems Using the Management Console

• Introducing Health Tests

• Types of Health Tests

• Managing Tests

3


28

Introducing Health Tests

You can use Spotlight on Messaging to monitor the health and performance of

individual servers or your entire platform. This, in turn, tells you the health of all

your servers. Health tests detect problems by collecting and analyzing data or

simulating user interaction with the server at regular intervals.

Because Spotlight on Messaging is a monitoring tool, its functions are to discover

the servers in your organization and run health tests against your servers. It

does not gather any other information.

Every health test can run against individual servers or entire groups. When you

create a test from the Home Page, the whole organization is targeted by default.

By default, health tests execute using the service account credentials you

entered when you installed this product. If you have entered alternate

credentials, the health tests will execute using those.

Only health tests relevant to available servers are shown when you right-click a

server and select Detect. You can configure any test against a group.

All health tests use global settings such as notifications and alternate

credentials. We recommend you configure your global settings before

configuring your health tests. For more information on configuring your global

settings, see “Configuring Test Settings” on page 42.

Types of Health Tests

The following health tests are included:

In a clustered environment, health tests run against the active node only.

Health tests read information from nodes as a whole through a virtual

server name.

DIAGNOSTIC PACK HEALTH TESTS

BlackBerry • Server Health Test

• BlackBerry Message Delivery Health Test


29

Exchange • Server Health Test

• Exchange Internal Message Delivery Health

Test

• Exchange External Message Delivery Health

Test

• Exchange Storage Health Test

• Exchange Queue Health Test

• Exchange Outlook Web Access Availability

Health Test

• Exchange Replication Health Test

OCS • Server Health Test

You can create a Generic Server Health Test. Using the Management Console,

you can see all the servers that have been discovered in your Exchange,

BlackBerry, and OCS platforms. Other servers critical to the functioning of

your environment, such as a domain controller server, are not automatically

discovered. If you would like to view these other servers in the topology and

run health tests against them, you must add them manually.

To create generic servers

1. From the treeview in the Management Console, right-click a Exchange or

BlackBerry organization or an OCS environment, and select Add Generic

Server.

2. Enter a server name and click OK.

These servers will have the same functionality as other servers, such as

the ability to launch Computer Management, Spotlight on Windows,

Services, and Event Viewer.

To delete generic servers

• Right-click a generic server and click Delete.

Note: To create a Generic Server Health Test, see “Creating a Health Test”

on page 41.

DIAGNOSTIC PACK HEALTH TESTS


30

Server Health Test

Use the Server Health test to monitor the overall health and performance of

BlackBerry, Exchange, or OCS servers. The test verifies various performance

counters, services, event logs, disk space, and network availability. You can

schedule the Server Health test to proactively check the status of your servers

before problems occur, or you can schedule tests to run after you fix an issue to

make sure the server problem has been resolved.

For information on creating a Server Health Test, see “Creating a Health Test”

on page 41.

BlackBerry Message Delivery Health Test

You can use the BlackBerry Message Delivery Health test to monitor the overall

message delivery health between your Exchange organization and your

BlackBerry devices. It also tracks the time it takes for an email message to be

sent and come back.

You need one test mailbox per server to run this test.

By default, we recommend running these tests every 30 minutes,

except for the Server Health Test. We recommend configuring two

server health tests - one without monitoring event logs with an

interval of 30 minutes and the second for monitoring event logs that

run only once a day. For more information on test settings, see

“Configuring Test Settings” on page 42.


31

The BlackBerry Message Delivery Health Test contains the following counters:

Exchange Internal Message Delivery Health Test

You can use the Exchange Internal Message Delivery Health test to monitor the

the sending and receipt of messages within an Exchange organization.You need

one test mailbox per server to run this test.

CATEGORY COUNTER

Device delivery • Organization exit time in seconds

• Organization exit status (within timeout)

• Device delivery time in seconds

• Device delivery status (within timeout)

• Delivery details

Round trip delivery • Round trip delivery time in seconds

• Round trip delivery status (within timeout)

• Round trip delivery details

The Exchange Internal Message Delivery Health test sends a test message

from each server you select to every other server that has been selected. For

example, if you select 10 servers in an organization, the test will send out a

total of 90 messages. For more information, see the Spotlight on Messaging

Deployment Guide.

For Exchange 2000/2003/2007 servers, a test mailbox that matches the

mailbox mask should be created in at least one store on each server in the

organization. However, it is recommended that the test mailbox be created in

each store on each server.

For Exchange 2010 servers, a test mailbox that matches the mailbox mask

should be created 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.

For more information see Spotlight on Messaging Deployment Guide.


32

You can enable this test to collect tracking information to trace the test message

that flows through the Exchange servers.

To enable this test to collect tracking information

• From the All Exchange Servers tab, select the Collect message

tracking information check box.

The tracking information will be found in the Delivery details counter.

The Exchange Internal Delivery Message Health Test contains the following

counters:

Exchange External Message Delivery Health Test

You can use the Exchange External Message Delivery Health test to monitor the

health of message delivery to and from an external target.

You need one test mailbox to run this test.

For this test, you must enter the names of:

• Source mailbox to send a message to an SMTP address and receive

replies from that address

• Destination email address to indicate where test messages will be

sent

The Exchange External Message Delivery Health 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.

CATEGORY COUNTER

Internal Message Delivery • Delivery time in seconds

• Delivery status (within timeout)

• Delivery details

By default, the round trip counters are disabled because the external email

account needs to be configured to automatically bounce the test message

back to the originating mailbox. Then, enable Round-Trip Delivery counters in

the test.

For more information, see Quest Spotlight on Messaging Deployment Guide.


33

This test targets your entire organization, not individual servers.

You must create a test mailbox to run this test. For more information, see the

Spotlight on Messaging Deployment Guide.

The Exchange External Message Delivery Health test includes the following

counters:

Exchange Storage Health Test

The Exchange Storage Health test monitors the overall function of storage

subsystems.

WMI is required to support retrieving accurate disk space information when

using mount points. If you do not use mount points, you can disable the

requirement for WMI. For information on enabling WMI, see “Volumes” on page

53.

The Exchange Storage Health test contains the following counters for Exchange

2000/2003:

CATEGORY COUNTER

Organization Exit • Organization exit time in seconds

• Organization exit status (within timeout)

• Organization exit details

Round-trip delivery • Round trip delivery time in seconds

• Round trip delivery status (within timeout)

• Round trip delivery details

CATEGORY COUNTER

Exchange System • Application Path

• Available space in MB

• % Free space


34

The Exchange Storage Health Test contains the following counters for Exchange

2007:

Storage Groups • Transaction log file path

• Transaction log file base name

• Transaction log files total size in MB


• % Free space

• Age of oldest transaction log file in hours

Stores • Store Type

• Store Status

• Database file path (EDB)

• File size in MB (EDB)

• Available space in MB (EDB)

• % Free space (STM)

• Database file path (STM)

• File size in MB (STM)

• Available space in MB (STM)

• % Free space (STM)

The Exchange System and Storage Group counters are the same as

those listed in Exchange 2000/2003.

CATEGORY COUNTER

Stores • Store Type

• Store Status

• Database file path

• Database file size in MB


• % Free space

CATEGORY COUNTER


35

The Exchange Storage Health test contains the following counters for Exchange

2010:

CATEGORY COUNTER

Exchange System • Application path


• % free space

Active Mailbox Database Copy • Database status



• Database available space in MB

• Database % free space

• Transaction log file path



• % free space



Passive Mailbox Database Copy • Mounted on server

• Database status









• % free space



36

Exchange Queue Health Test

Use the Exchange Queue Health test to monitor the health and performance of

email and message queues.

The Exchange Queue Health test contains the following counters for Exchange

2000/2003:

Public Folder • Status


• Database file size







• % free space


CATEGORY COUNTER

For all queues combined • Total Queue Count

• Total Queue Length

• Total Queue Size in KB

For individual queues • Queue Length

• Queue Size in KB

• Age of oldest message in hours

• Queue Status

• Next scheduled connection time (if available)

• Extended State Information (if available)

CATEGORY COUNTER


37

The Exchange Queue Health test contains the following counters for Exchange

2007 and Exchange 2010:

Exchange Outlook Web Access Availability Health Test

The Exchange Outlook Web Access Availability Health test verifies a test mailbox

can logon to a mailbox through Outlook Web Access (OWA) from within your

organization.

This test allows you to ensure the following:

• Mailbox is accessible

• Mailbox logon latency is within expected threshold

CATEGORY COUNTER

For all queues combined • Total Queue Count

• Total Queue Length

• Total Queue Size in KB

For individual queues • Queue Length

• Queue Size in KB

• Age of oldest message in hours

• Queue Status

• Last error (if available)

• Last retry time (if available)

• Next retry time (if available)

This test uses internal server URL names only. It does not test external

availability or OWA using your public URL.


38

The Exchange Internal Outlook Web Access Availability Health test contains the

following counters for all Exchange Servers:

OWA Health Test for Exchange 2007/2010 Considerations

For Exchange 2010 Client Access (CAS) role servers, we will attempt to log on

to Exchange 2010 mailbox in the same site, if one exists.

For Exchange 2007 Client Access (CAS) role servers, we will attempt to log on to:

• Exchange 2007 mailbox if there are Exchange 2007 mailbox role

servers in the same site. If logon fails or no mailbox role servers are

found, we will log on to any Exchange 2007 mailbox server in the

organization.

• Exchange 2000/2003 mailbox if there are Exchange 2000/2003

servers and the mailbox name is specified.

The OWA Health Test for Exchange 2007 requires at least one Exchange 2007

mailbox server within your organization.

The OWA Health Test for Exchange 2010 requires at least one Exchange 2010

mailbox server in the same site.

The OWA Health Test for Exchange 2007 does not support alternate credentials.

If you specify alternate credentials in the test, the test will run using service

credentials. This occurs because the specific PowerShell cmdlet used for this test

does not support impersonation.

For Exchange 2007 and Exchange 2010, you must specify a logon method and

timeout to signify the maximum amount to time to wait between logon attempts.

CATEGORY COUNTER

Mailbox logon • Mailbox logon time in seconds

• Mailbox logon status within timeout

• Mailbox logon details


39

OWA Health Test for Exchange 2000/2003 Considerations

For Exchange 2000/2003 servers, we will attempt to log on to Exchange

2000/2003 back-end servers.For Exchange 2000/2003, you must specify a

mailbox logon name and a logon method. You can select all logon methods by

selecting the All checkbox, or select one or several logon methods. The test

attempts to logon to the mailbox using the logon methods in the order listed until

an attempt is successful.

This test uses the following different authentication methods in the following

order until the test succeeds:

• Basic authentication

• Windows integrated authentication

• Embedded credentials

• Form-based authentication

If you do not specify alternate credentials, the test uses Basic and Windows

integrated authentications. For the test to use embedded and form-based

authentications, you must specify alternate credentials.

Exchange Replication Health Test

The Exchange Replication Health test monitors the health of transaction log

replication on your Exchange 2007 and Exchange 2010 mailbox servers. This

test detects whether replication is configured and what type of replication is

configured.

The Exchange Replication Health test contains the following counters for

Exchange 2007:

Ensure the credentials used to execute the test has "ReceiveAs" access to the

test mailbox.

CATEGORY COUNTER

Cluster Continuous Replication • Copy status

• Copy queue length

• Replay queue length

• Hours since last log inspection

• Target transaction log path


40

The Exchange Replication Health test contains the following counters for

Exchange 2010:

For Exchange 2010, transaction log replication is handled by Database

Availability Group (DAG). For more information, see “Viewing Database

Availability Groups (DAG)” on page 28.

Local Continuous Replication • Copy status





Standby Continuous Replication • Copy status





For more information on LCR, CCR, and SCR, refer to Microsoft’s website.

CATEGORY COUNTER

Passive Mailbox Database Copy • Master

• Mounted on server

• Copy status




• Activation preference

CATEGORY COUNTER


41

Managing Tests

You can perform the following functions with health tests:

• Creating a Health Test

• Configuring Test Settings

• Editing a Health Test

• Enabling/Disabling a Health Test

• Running a Health Test Now

• Deleting a Health Test

• Cloning a Health Test

• Viewing Test Results

Creating a Health Test

To create a Health test

1. Select a server whose health you want to monitor.

2. Right-click the selected server and select Detect | <test name>.

3. Use the General Test Information dialog box to specify the Test Name

and Test Targets then click Next.

4. Review the test execution schedule, test credentials and notification

settings in the Test Settings dialog box and click Next.

For more information on configuring Test Settings, see “Configuring

Test Settings” on page 42.

5. Select the server type in the left pane of the New <platform type>

Server Health Test dialog box to indicate the type of server whose

metrics you want to specify.

If you select a container, the test will run against all servers in that group at

the time of execution. Typically, the test would be configured for all servers. If

you add a new server, the test automatically runs against that server (without

needing to be updated).

You can configure a test to run only once or at regular intervals during a

specified time period.


42

6. Review the metrics you want to monitor for the selected target by

configuring and selecting the Network, Volumes, Services,

Performance Counters and Event Log metrics.

You can set the conditions, error thresholds, and warning thresholds

You can also enter the number of alarms to skip before sending

notifications if you want to ignore notifications on occasional spikes in

the counter values, and only be notified when there are consecutive

alarms occurring.

For example, if your tests are configured to alert on errors only, you

may ignore if a counter exceeds its error threshold three times

consecutively. If you enter 3 in the Alarms to skip before sending

notifications box, you will be notified after the error threshold is

exceeded four times in a row.

7. The Server Health test is preconfigured with general defaults. Some

tests have counters preconfigured to skip an alarm the first time it

occurs before sending a notification. For a list of these counters, see

“Counters with Non-Zero Alarm Values” on page 151. Review the

Condition, Warning Threshold and Error Threshold values and click

Next.

8. Use the Summary page to review and confirm the general, test and

notification settings you have made then click Finish to accept the

settings.

Once the test is created, it runs immediately.

Configuring Test Settings

When scheduling health tests, you need to provide details about the following

setting options:

• Configuring the Execution Schedule

• Configuring Notification Settings

• Configuring Credentials Settings

• Managing Database Settings

We recommend configuring two server health tests - one without

monitoring event logs with an interval of 30 minutes and the second

for monitoring event logs that run only once a day. For more

information on test settings, “Managing Tests” on page 41.


43

Configuring the Execution Schedule

Use the Execution schedule panel to set up the frequency and the time frames

during which you want the tests to run.

The following options are available in the Execution Schedule panel:

For information on setting notifications and credentials, see “Configuring

Notification Settings” on page 43 and see “Configuring Credentials Settings” on

page 49 respectively.

Configuring Notification Settings

Use the Notification Settings panel to select the group that will be notified when

server counter values (configured to generate notifications) exceed the

configured threshold.

You can configure notification settings to alert users of errors only or errors and

warnings.

You can set up notification groups to allow specified groups to receive messages

on alarms, warnings, or errors on a per counter basis. You can send notifications

to groups only, not individual users. The members of each group are based on

the users added in the Add Recipients dialog box. For more information, see

“Adding Recipients” on page 44.

You can reuse notification users across groups.

OPTION DESCRIPTION

Run once Select this to run the test immediately, and on

demand.

Run every (minutes) Select this to enter the time interval in minutes after

which the next test starts.

Note: If a test is scheduled to run every ten minutes

(for example 12:00), but a test iteration takes 15

minutes, the test will skip the next iteration (that is,

12:10), and the next iteration does not run until the

next scheduled time (that is 12:20).

Use execution window Select this check box to only run within a specific time

window. You must specify a Start time and End time

for the Test Execution Schedule.

Run every day at Select this to schedule the test to run once daily at

this specific time.


44

You can specify the following parameters:

• if you would like the emails in HTML or Plain Text format

• the level of severity on which you want to receive email messages

• an arbitrary command line executable to run

Adding Recipients

To set up recipients to receive notifications

1. Expand the Global Settings node in the Management Console

treeview and select Notifications.

2. Enter the name of an SMTP server.

3. From the Recipients section, select Add.

4. Enter the recipient’s name and email address.

5. Select the format of emails the recipient is to receive: either HTML or

Plain Text.

6. Select the type of alarms the user is to receive: either errors and

warnings or only errors.

7. Click OK.

Adding Notification Groups

To add a notification group

1. Expand the Global Settings node in the Management Console

treeview and select Notifications.

2. From the Groups section, select Add.

3. Enter the sender’s name and email address.

4. Select the recipients to receive notification messages.

To save time, configure the global settings before configuring your tests.

You can send a test message to see if your recipients get the error and/or

warning by clicking the Send Test button.


45

5. Select an external application command line to execute processes

such as SNMP traps.

6. Set limits on notifications. For more information, see “Setting Limits

on Notifications” on page 45.

7. Click OK.

Setting Limits on Notifications

You can configure notification groups to:

• receive unlimited notification messages

• receive a notification when an alarm clears

The following lists the tokens supported for the external application command

line. The tokens will be replaced with corresponding real time results, when

the external application is run.

Notification tokens:

• $SenderName$

• $SenderEmail$

Counter tokens:

• $CounterName$

• $CounterGroupName$

• $CounterValue$

• $CounterOutcome$

• $CounterOperator$

• $CounterThreshold$

Server tokens:

• $ServerName$

• $ServerOutcome$

Test tokens:

• $TestOutcome$

• $TestName$

Note: These token dictate how many times the external application is called.

The Notifications tokens are general tokens. With the Counter tokens, the

external application is called once per test per each server per counter. With

the Server tokens, the external application is called once per test per each

server. With the Test tokens, the external application is called once per test.


46

• set the maximum number of notification messages a user is to receive

per each alarm

To receive messages on cleared alarms

A cleared alarm is an alarm that recipients do not need to manage - either the

problem has been resolved or has become less severe. For example, if you are

receiving notifications on errors only, and the status changes from error to

warning, the alarm is considered cleared. If you are receiving notifications on

both errors and warnings, and the status changes to success, the alarm is

considered cleared.

1. Add a notification group. See “Adding Notification Groups” on

page 44.

2. Select the Send alarm cleared notification when alarm ends

check box.

We recommend the following best practices when setting notifications:

• You can receive a notification when an error occurs for a specified

number of times. Then if the error still occurs after the specified

number of times, you will not receive further notifications. You will

need to receive another notification when the alarm clears. To do

this:

1. Deselect the Send unlimited notifications for an alarm check

box.

2. In the Maximum number of notifications to send per alarm

box, enter a number for the maximum number of times you would

like to receive a notification.

3. Select the Send alarm cleared notification when alarm ends

check box.

• You can receive unlimited error or warning notifications, but do

not receive cleared notifications. This assumes that once you stop

receiving error or warning notifications, the alarm has been

cleared. To do this:

1. Select the Send unlimited notifications for an alarm check

box.

2. Deselect the Send alarm cleared notification when alarm

ends check box.


47

3. Click OK.

To receive unlimited notification messages

This feature allows you to receive unlimited notifications about alarms on

counters.


page 44.

2. Select the Send unlimited notifications for an alarm check box.

3. Click OK.

To set the maximum number of notification messages per alarm

This feature can help you limit the number of notification emails you receive if

you encounter problems with the same counter.


page 44.

2. Enter a number in the Maximum notifications to send per alarm

box.

3. Click OK.

For example, if you have a recipient configured to receive a maximum

number of 3 notifications, you will receive a notification the first time

the alarm occurs, then two other times, if there is still a problem with

the counter.

There is a special behavior of the notification engine while handling event

logs monitored by Server Health Tests.

If a specific event was found in the event log while you are running a Server

Health Test (such as an Exchange Server Health Test), a notification about

this event is sent to the recipients with the corresponding severity (if a

notification group is specified for the test). When the Server Health Test runs

the next time, it will only scan event logs starting from the time of the

previous test run. If there is no identical event found during this second run,

the notification engine will not issue the cleared notification for this event.

This behavior is due to the nature of the event log counters: if the event is

not found during the second test run, the problem is not necessarily

resolved. It only means there are no new events logged for the exact same

problem.

Selecting this option overrides the maximum number of notification messages

you may have set.


48

Also, you can have your notifications set to receive errors only if your

performance counters on your Front-End server exceeds its error

threshold, and you have selected the Send alarm cleared

notification when problem ends check box. You will receive a

notification the first time the error occurs, and two more times if the

error occurs on that performance counter again. If the fourth time,

the error threshold is no longer exceeded, you will receive a cleared

notification.

SNMP

You can pass alerts to external applications using Simple Network Management

Protocol (SNMP).


page 44.

2. Click in the Execute command line box, and enter "<Program

Files>\Quest Software\Spotlight on

Messaging\ManagementConsole\Binaries\iwsnmptrap.exe"

<server> <community name> 6 0 "$CounterOutcome$ on

$ServerName$ - $CounterName$ = $CounterValue$".

3. Click OK.

• <Program Files> indicates the Program Files directory path of

the computer running Diagnostic Services

• <server> indicates the computer name to receive the SNMP trap

• <community name> indicates the SNMP community name

(usually "public")

For example, you can enter:

"C:\Program Files\Quest Software\Spotlight on

Messaging\ManagementConsole

\Binaries\iwsnmptrap.exe" 10.4.60.95 public 6 0

"CounterOutcome$ on $ServerName$ - $CounterName$ =

$CounterValue$"


49

Apply the notification group to the tests for which you want to

generate SNMP traps.

Configuring Credentials Settings

By default, user credentials are specified when initially installing the Diagnostic

Services used for test execution. You can override the initial credentials for a

specific test by specifying and configuring alternate credentials. You can add,

edit, and delete credentials used to run tests under different credentials than

those specified in the Diagnostic Test Engine (DTE). The credentials are stored

encrypted in the database.

To manage alternate credentials

• Expand the Global Settings node in the Management Console treeview

and select Alternate Credentials.

Managing Database Settings

Database Settings tell you the server name where your database is installed, the

size of your database, and how much free space you have within your database.

If you want to pass errors only using SNMP, you can create a batch file that

contains the tokens you want to use in your notifications.

1. Create a batch file, and enter If %1 == error "C:\Program

Files\Quest Software\Spotlight on

Messaging\ManagementConsole\Binaries\iwsnmptrap.exe"

10.4.60.95 public 6 0 "%1 on %2 - %3 = %4".

2. Name the batch file snmp.bat.

3. In the Notifications dialog box, add a Notifications group. Enter a Sender

name and email address.

4. In the External application command line, enter "<directory of

snmp.bat file>\snmp.bat" "$CounterOutcome$" "$ServerName$"

"$CounterName$" "$CounterValue$", and save the notification group.

You cannot run PowerShell cmdlets across domains with alternate

credentials.

To save time, configure the global settings before configuring your tests.


50

Database retention controls the length of time health test result data is kept in

the database before being purged. You can set the database settings for weekly

or hourly retention rates. The test result data is aggregated into hourly and daily

historical data. This data is used for Web Reports.

You can also use Database Settings to set Test Results History and purge test

results from the database after the specified number of days.

If you want to purge the data from the daily Web Reports and Test Results before

the specified execution time, click the Purge Now button next to the Web Reports

daily data retention (days) or the Test Results data retentions days boxes.

Customizing Counters

The Server Health Tests allow you to perform the following functions:

• Adding Services

• Adding Performance Counters

• Adding Event Log Entries

• Editing Services, Performance Counters, and Event Log Entries

• Deleting Services, Performance Counters, and Event Log Entries

Adding Services

You can include additional services that you want to monitor for the specific

server health test that you want to run.

To add services

1. Click <Add Services> located under the Services sections in the

listview of the server health test that you select.

The test results are purged upon the next test execution after midnight

(UTC).

If you try to view test results that have already been purged, but the test is

still visible in the Test Results tab, you will receive an error message that the

test results have been purged.

Due to the amount of space test history requires in the database, if

you want to increase the value for Test History retention (days), see

the section "Historical Reporting Database Usage Estimates" in the

Spotlight on Messaging Deployment Guide.


51

2. Enter a name to query a list of current services you want to monitor

and the services you want to add in the Select Services dialog box

and click OK.

3. Configure the thresholds you want to monitor for the new service

you have added.

Adding Performance Counters

You can include additional performance counters that you want to monitor for

the specific server health test that you want to run.

To add performance counters

1. Click <Add Performance Counters> located under the

Performance Counters section in the listview of the server health test

that you select.

2. Enter the name of the server you want to monitor, the performance

object and counter you want to add, and select the instances, if

applicable, you want to monitor in the Performance Counters dialog

box and click OK.

3. Configure the thresholds you want to monitor for the new

performance counter you have added.

Adding Event Log Entries

You can include additional Event Log Entries that you want to monitor for the

specific server health test that you want to run.

To add event log entries

1. Click Add Event Log Entries located under the Event Log section in

the listview of the server health test you select.

2. Enter the event log name, the source, and the event IDs you want to

add in the Event Log Entry dialog box and click OK.

You may specify to indicate a wild card character at the end of the source

string. For example, BlackBerry* will match BlackBerry Policy Service,

BlackBerry Router, etc.


52

3. Configure the metrics you want to monitor for the new event log

entry you have added.

Editing Services, Performance Counters, and Event Log Entries

You can change the descriptions of the performance counter and event log

entries to customize them for your environment or organization. You can change

the role, condition, warning threshold, and error thresholds of services,

performance counters, and event log entries.

You can monitor specific event logs by filtering by event IDs or by text in the

event ID descriptions. You can specify the following:

• a specific event ID, such as 1000

• multiple event IDs separated by commas

• ranges, such as 1000 - 2000

• "*" to monitor all event IDs

• an event ID or range of event IDs with text separated by a colon, as in the

following examples:

-1000:Error to monitor events with event ID 1000 and containing the

word ’Error’

-1000–2000:Error to monitor events within the range of event IDs 1000

to 2000 and containing the word ’Error’

-1004:!Error to monitor events with the event ID 1004 and not

containing the word ’Error’

-1004–1005:!Succeeded to monitor events within the range of event

IDs 1004 to 1005 and not containing the word ’Succeeded’

-1000–2000:Error,1010:!Warning to monitor all events between event

ID 1000 and 2000 that contains the word ’Error’, except those with event

ID 1010 that contains the word ’Warning’

-1000:Long Phrase to monitor events with the event ID 1000 that

contains the specified long phrase. It cannot contain a comma.

-1000:Error, 1000:Warning to monitor all events with the event ID

1000 and contains the word ’Error’ or ’Warning’

Note: If you have both an inclusive filter and an exclusive filter for the same

ID, the exclusion filter takes precedence.

Note: If you want to look for multiple words that are not a phrase, you need

to add them separately.

You cannot edit the description of services.


53

To edit the description of performance counters and event log entries

1. Right-click the description of the performance counter or event log

entry, and click Edit.

2. Change the description in place.

If you made an error while changing the description, such as entering

invalid characters, the description will not change.

To edit the condition or threshold of services, performance counters,

and event log entries

• Either select a value from a drop-down menu or edit a value in place

from one of the following columns: Role, Condition, Warning

Threshold, or Error Threshold.

Deleting Services, Performance Counters, and Event Log Entries

To delete services, performance counters, and event log entries

• Right-click the description of a service, performance counter, or event

log entry, and select Delete.

Data Collection Options

Data collection options affect the test results returned by:

• Volumes

• Network Availability

Volumes

WMI is used to retrieve accurate disk space information when using mount

points. If you do not use mount points, you can configure your tests to use

Windows API if WMI fails.

When you make this change in one server type, all other server types will be

changed for the test.

You cannot edit a warning threshold or error threshold if the value in the

Condition column is set to Informational.

You can select multiple services, performance counters, or event log entries

to delete them at the same time.


54

To allow Windows API fallback

1. In the Server Health Test, select a server type.

2. Click Data collection options.

3. In the Volumes tab, select Allow API fallback if WMI fails.

4. Click OK.

Network Availability

The Server Health test always performs a reverse DNS lookup to validate that

DNS server has a record mapping IP address of the target server to host name.

By default, the reverse DNS lookup alarm is enabled. If you do not want the test

to alarm if the names returned by a DNS lookup do not match the FQDN of the

target server, you can disable this option.

When you make this change in one server type, all other server types will be

changed.

To disable alarm on reverse DNS lookup

1. From the Server Health Test, select a server.

2. Click Data collection options.

3. In the Network Availability tab, clear the Alarm on reverse DNS

lookup check box.

4. Click OK.

Editing a Health Test

To edit a test

1. Expand the Tests node in the Management Console treeview,

right-click the test you want to edit, and select Edit.

2. Edit the existing settings you want to change in the Execution

Schedule, Notification Settings, and Alternate Credentials Settings

dialog boxes and click Next.

3. Edit the metrics you want to change in the test-specific pages and

click Finish.

The edited test is displayed under the Tests node.

Do not use Allow Windows API fallback if WMI fails if the volume is mounted

on a network-attached storage device because the metrics returned may not

be accurate.


55

Enabling/Disabling a Health Test

To enable/disable a test

• Expand the Tests node in the Management Console treeview,

right-click the test you want to edit, and select Enable or Disable.

Running a Health Test Now

To run the test now


right-click the test you want to edit, and select Run Now.

Deleting a Health Test

To delete a test


right-click the test you want to delete, and select Delete.

Cloning a Health Test

To clone a test


right-click the test that you want to clone, and select Clone.

When you click Clone, the Edit wizard appears with the information in

all dialog boxes identical to those in the original test, except for the

test name (the test name appears as Copy of <name of original

test>). You can change the name of the test, notifications, schedule,

credentials, and make other changes to the server counters. When

you finish editing the cloned test, the new test will appear in the

treeview.

You can run the test now on scheduled or unscheduled tests.

Raw historical data is deleted; aggregated data is kept and is purged as

scheduled.


56

A cloned test allows you to create a new health test based on an

existing one, thus eliminating the need to create a new test from the

beginning.

Viewing Test Results

The Spotlight on Messaging Management Console allows you to view the results

of generated tests.

Test results are available by clicking a target in the Topology or treeview, then

selecting the Test Results tab.

If you click a group in the treeview, results are displayed for all targets in that

group.

Colored icons adjacent to a test in the Test node, servers in the organization

node, or tests in the Test Results window indicate the following test status:

If the server is part of a group, the group will show the colored icon of the server

with the worst severity. For example, if the group contains three servers: one

server has a green icon, the other has a red icon, and the last has a grey icon.

The group will appear red.

ICON DEFINITION

test has completed successfully

error threshold was violated

warning threshold was violated

value could not be retrieved

No icon no tests are currently running


57

Viewing More Details on Test Results

You can click a counter test result to get detailed results about the test per target

server, such as target name and test start and completion time. You can view

details about a warning, error, or an incomplete test result on counters in any

test. You can also see details on some successful counters and informational

counters, such as more information associated with an event log (if the event

log is marked as informational).

If the counter is not successful, the details will give you a summary of the

warning or error, possible reasons why the counter is not successful, and

possible solutions to help remedy the problem.

To view more information

• Select a counter, the click the Details button.

Hiding Successful Results

You can hide the counters with successful results or hide informational counters

to focus on the counters with errors or warnings.

To hide successful results

• From the Test Results tab, select Hide successful results from the

Display drop-down.

The selection is applied to all test results in your organization.

Browsing Test Result History

You can view the data of test results that has been collected in the last seven

days (by default), or configure to view the data from tests results that have been

collected more than seven days ago.

To set the test results history

1. From the treeview, select Global Settings | Database Settings.

2. In the Test Results History data retention (days) box, enter the

number of days.

To view the test results history

• From the Test Results tab, click the Results drop-down arrow to pick

a date of which test results you would like to view.

You can also use the left and right arrows to pick a date.


58

Each test result has a colored icon attached to the left of the date to

indicate if the test was successful or had warnings or errors.

Clearing the Health Test Results

To clear the test results


right-click the test whose results you want to clear, and select Clear

Test Results.

You can run the test again to bring back the results by right-clicking the test

and selecting Run Now.

The test results are cleared only in the Management Console. The next time

you open the Management Console, the test results appear.

Resolving Problems Using the Management Console

• Launching Native Tools

4


60

Launching Native Tools

Spotlight on Messaging allows you access to native management tools to help

you troubleshoot and resolve problems with your BlackBerry, Exchange, and

OCS servers.

The following table identifies the management tools available for your

BlackBerry servers:

The following table identifies the management tools available for your Exchange

servers:

TOOL DESCRIPTION

Computer Management Allows you to manage a single local or remote

computer. The Computer Management console

combines several administration utilities you can use

to do the following:

• monitor system events

• create and manage shared resources

• view a list of users connected to a local or

remote computer

• set properties for storage devices

• view device configurations and add new device

drivers

• manage applications and services

Event Viewer Allows you to gather information about hardware,

software, system problems, and to monitor Windows

security events. Event Viewer records events in the

application, security, and system.

Services Allows you to start, stop, and configure Windows

services.

BlackBerry Manager Allows you to manage and configure your BlackBerry

devices to receive messages.

BlackBerry Server

Configuration

Allows you to configure the database for your

BlackBerry server.

TOOL DESCRIPTION

Event Viewer See “Event Viewer” on page 60

Services See “Services” on page 60.

Resolving Problems Using the Management Console

61

The following table identifies the management tools available for your OCS 2007

or OCS 2007 R2 servers:

To launch each tool

• Right-click a server and select Resolve | Launch <tool name>.

Computer Management See “Computer Management” on page 60.

Exchange Management

Console

Allows you to manage your Exchange 2007 servers

organization

Exchange System Manager Allows you to manage servers and configure users

for your Exchange 2000/2003 organization

Active Directory Users and

Computers

Allows you to administer user accounts, computer

accounts, groups, and organizational units (OUs)

TOOL DESCRIPTION

OCS Administrator Console Allows you to configure your OCS 2007 or OCS 2007

R2 environment.

Note: You cannot launch the OCS Administrator

Console from an Edge server directly. You can access

the OCS Administrator Console through the

Computer Management native tool.

Active Directory Users and

Computers

See “Active Directory Users and Computers” on

page 61.

Computer Management See “Computer Management” on page 60.

Event Viewer See “Event Viewer” on page 60.

Services See “Services” on page 60.

CWA Administration Console Allows you to configure Communication Web Access

(CWA) server for your OCS 2007 R2 organization.

Note: The CWA Administration Console is not

available from an OCS 2007 environment.

Group Chat Administrator

Console

Allows you to configure Group Chat settings for your

OCS 2007 R2 organization.

Note: The Group Chat Administrator Console is not

available from an OCS 2007 environment.

TOOL DESCRIPTION


62

Diagnosing Problems Using the Management Console

• Launching the Diagnostic Console from the Management Console

5


64

Launching the Diagnostic Console from the Management Console

You can use the Diagnostic Console plug-in to diagnose your servers. The

Diagnostic Console allows you to further diagnose and resolve issues within

individual servers in your organization.

To launch the Diagnostic Console plug-in from the Management Console

• Right-click a server and select Diagnose | Launch Diagnostic

Console.

For more information on the Diagnostic Console, see “Diagnosing Problems

using the Diagnostic Console” on page 65.

Diagnosing Problems using the Diagnostic Console

• Introducing the Diagnostic Console

• Launching and Connecting to the Diagnostic Console

• Understanding the Diagnostic Console

• Understanding the BlackBerry Diagnostic Console

• Understanding the Exchange 2000/2003 Diagnostic Console

• Understanding the Exchange 2007 Diagnostic Console

• Understanding the Exchange 2010 Diagnostic Console

• Understanding the OCS Diagnostic Console

6


66

Introducing the Diagnostic Console

The Diagnostic Console provides you with a real-time representation of the

messaging system processes and components within a server.

You can diagnose and resolve issues using the Diagnostic Console, which

features the traditional Spotlight user interface.

The Diagnostic Console contains the following:

• Home Pages that highlight targeted areas of server activity.

• Graphical flows that illustrate the rate at which data is moving

between server components. Colorful buttons, gauges, spinners, and

containers display the value of key statistics and metrics.

• Visual warnings if the performance metrics exceed acceptable

thresholds, which you can adjust. The buttons, gauges, and other

visual objects, collectively referred to as components, change color to

show you the source of the problem.

• Warning messages that are displayed well before the traffic levels of

a server become critical.

• A range of reports and graphs that provide you with detailed

information about a server. You can view this information on the

screen or you can print it.

The Diagnostic Console retrieves a large amount of data from a server

frequently, which can place excessive stress on a server, actually affecting

the server's performance. Also, using the Diagnostic Console for an

extended period of time can consume critical system resources, affecting

the stability of Spotlight on Messaging as a whole.

We recommend that the Diagnostic Console view a maximum of 10 servers at

any one time.

While the Management Console can run tests when it is closed, the Diagnostic

Console cannot perform any actions when it is closed.

If you are using the Diagnostic Console as a monitoring tool, you

must disconnect from, then reconnect to the Diagnostic Console

daily.


67

Launching and Connecting to the Diagnostic Console

To launch and connect to the Diagnostic Console

1. Select Start | Programs | Quest Software | Spotlight |

Spotlight.

2. Select File | Connect.

3. Click the Tools button, then select Create New Connection to

create a plug-in connection to the server.

4. Select a connection type, enter a connection name, and click OK.

5. Enter the address of target computer, and click OK.

6. In the Welcome to Spotlight page, select File | Connect.

7. Select the plug-in connection you created, and click Connect.

Before you launch and connect to the OCS Diagnostic Console, you need read

access to the following:

• Perfmon on the target server

• Event Logs on the target server

• Back-End database tables (rtc and rtcdyn) for the pool where the

target server is located

• Back-End database stored procedures (rtc and rtcconfig) for the pool

where the target server is located

To get read access

1. Create a new Security Group (Quest OCS Diagnostic Users).

2. Map Quest OCS Diagnostic Users into the Back-End Database and

provide a User Mapping to the rtc, rtcconfig and rtcdyn databases

with the public and db_datareader role.

3. Add Quest OCS Diagnostic Users to the

RTCUniversalReadOnlyAdmins group.

You may see your service account in the security log of the Exchange

organization being monitored. If you are using the Exchange Diagnostic

Console, you connect to Exchange server using the user credentials of the

user who is currently logged in. Kerberos will log events in the event log

during authentication.


68

4. Add Quest OCS Diagnostic Users to the Power Users and

Performance Monitor Users security group on each OCS server

through a GPO or some other mechanism.

Understanding the Diagnostic Console

When you connect to the Diagnostic Console, the Home Page displays a

high-level summary of your BlackBerry, Exchange, or OCS server.

The Home Page contains the various panels, message flows, and drilldowns to

help you perform an extensive analysis of the major components on your server.

Alternatively, you can be a member of RTCUniveralServerAdmin, and update

the Back-End databases to give the db_datareader user role for the rtc,

rtcconfig, and rtcdyn tables to the RTCUniveralServerAdmin group.

To view more information about the Diagnostic Console such as icons,

components, the Spotlight Assistant, Metrics, or Properties, see the Spotlight

Basics Online Help.

To view detailed information on specific components, right-click a

component, message flow, and drilldown, and select What’s This, Metrics, or

Properties.


69

Understanding the BlackBerry Diagnostic Console

The BlackBerry Diagnostic Console contains the following:

• Panels

• Message Flows

• Drilldowns

• Metrics

Panels

The BlackBerry Server Home Page displays a high-level operational summary of

the BlackBerry server and is comprised of the following panels:

• Service Health Panel

• SRP Panel

• System Panel

• Server Panel

• Users Panel

• OS Subsystem Panel

Before connecting to the BlackBerry Diagnostic Console, you can specify SQL

Database Authentication information and a private SNMP Community. To do

so:

1. Right-click a SOM-BlackBerry Server plug-in connection, and select

Properties.

2. Select the Details tab.

3. Select the BlackBerry Configuration Database Authentication check

box, and enter a username and password.

4. Select the Non-Public SNMP Community check box, and enter a name

for the SNMP Community.

5. Click OK.

Note: If a private SNMP community is set on the server, the SNMP

community name must be entered.


70

Service Health Panel

The Service Health panel displays the CPU and memory usage status of the

BlackBerry services identified and described in the following table:

SRP Panel

This panel indicates whether or not the BlackBerry server is connected to the

Server Relay Protocol. This point-to-point protocol runs on top of TCP/IP, and

defines transactions between the BlackBerry services and the Relay Server.

The following table describes the SRP panel components:

SERVICE DESCRIPTION

BlackBerry Attachment

Service

Converts supported attachments into a format that

users can view on their BlackBerry handheld devices.

BlackBerry Dispatcher

Service

Compresses and encrypts all BlackBerry data and routes

the data through the BlackBerry router to and from the

wireless network.

BlackBerry Messaging

Agents Service

Connects to BlackBerry to provide wireless enterprise

activation, and delivers messages to and from the user’s

mailboxes on the BlackBerry server.

BlackBerry Policy Service Performs administrative services over the wireless

network, such as sending IT policies and IT commands.

BlackBerry Router Service Connects to the wireless network to route data to and

from BlackBerry handheld devices.

BlackBerry Synchronization

Service

Synchronizes organizer data between BlackBerry

handheld devices and the messaging server over the

wireless network.


Reconnections Indicates the number of times the BlackBerry

Dispatcher Service has successfully reconnected to

SRP since it was started.

Failed Connections Indicates the number of times the BlackBerry

Dispatcher Service has tried, but failed to connect to

SRP since it was started.

SRP Time Not Connected (sec) Indicates the total time, (in seconds), that the

BlackBerry Dispatcher Service has not been

connected to SRP since startup.


71

System Panel

The System panel identifies the BlackBerry server version, the server UID, the

Microsoft Windows version, the AD site, and uptime on this BlackBerry server.

The following table describes examples of the System panel components:

Server Panel

The Server panel shows server-specific information such as licenses in use,

messaging statistics, and critical events on this BlackBerry server.

The following table identifies and describes the components that comprise the

Server panel:

SRP Last Connect Indicates the following:

• Time of Last SRP Error — indicates the time of

the last SRP error.

• Last SRP Error — displays the error message of

the last failed SRP connection attempt.

COMPONENT (EXAMPLE) DESCRIPTION

BES Version 4.1.3.16 Indicates that the BlackBerry server is running version

4.1.3.16.

SRPID: T95475585 Indicates that the SRPID of the BlackBerry server is

T95475585.

Windows Server 2003 SP 2 Indicates that the version of Windows running on this

server is Windows Server 2003 Service Pack 2.

Database Identifies the server on which the BlackBerry

Configuration Database for this BlackBerry server is

located.

Uptime: 13d 01:16 Indicates how long the computer hosting the BlackBerry

server has been running.


Pending Messages Indicates the number of messages pending delivery to

handheld devices serviced by this BlackBerry server.



72

Expired Messages Indicates the number of messages which expired before

delivery to handheld devices serviced by this BlackBerry

server.

Error Messages Indicates the number of messages that were

undeliverable due to error.

MORE Requests Indicates the number of MORE requests issued from

devices.

Global Filtered Indicates the number of messages to which the

BlackBerry Server applied global filters and did not

forward to handhelds. Filters are rules applied to

messages as they arrive in your Exchange mailbox, and

determine whether to redirect the message to your

BlackBerry device.

User Filtered Indicates the number of messages to which the

BlackBerry Server applied user-defined filters and did

not forward to handhelds. Filters are rules applied to

messages as they arrive in your Exchange mailbox, and

determine whether to redirect the message to your

BlackBerry device

OTAC Users Indicates the number of users enabled for Over the Air

Calendar (OTAC) access. OTAC support allows wireless

calendar synchronization for handheld devices.

WER Users Indicates the number of users enabled for Wireless

Email Reconciliation (WER). WER enables you to move

or change the status of email messages on the handheld

and synchronize these changes to your desktop

wirelessly, and vice versa.

Note: WER is not supported on handhelds running OS

versions less than 2.6.

Failed Users Indicates the number of users which failed to initialize

correctly.

Critical Events Indicates the number of critical events which have not

been addressed on the BlackBerry server.

Licenses in Use Indicates the total number of user licenses currently in

use on the BlackBerry Server. A Client Access License

(CAL) is a license that allows the specified number of

users to use the BlackBerry Server.



73

Users Panel

The Users panel contains components that indicate the number of users serviced

by this BlackBerry server, the number of dormant users, messaging statistics,

user latency, and the most recent user error.

The following table identifies and describes the components that comprise the

Users panel:

Messaging Agents Indicates the number of Messaging Agents running on

the BlackBerry Server. BlackBerry Messaging Agents run

on demand. Thus, if there are no active users on a

particular Messaging Agent, the Messaging Agent will

not be running.

Service Connections Indicates the number of services currently connected to

the BlackBerry Router

Device Connections Indicates the number of devices currently connected to

the BlackBerry Router.

COMPONENTS DESCRIPTION

Total Users Indicates the number of users serviced by this

BlackBerry server

Dormant Users Indicates the number of users whose last contact with

the BlackBerry server occurred over 30 days ago

Messages Sent Indicates the number of messages sent by handheld

devices serviced by this BlackBerry server

Messages Received Indicates the number of messages received by handheld

devices serviced by this BlackBerry server

Calendar Sent Indicates the number of calendar events sent by

handheld devices serviced by this BlackBerry server

Calendar Received Indicates the number of calendar events received by

handheld devices serviced by this BlackBerry server

Average Latency Indicates the average latency of the last 10 messages

sent to the handheld devices for all users

Last Error Indicates the time of the most recent error that

occurred for users



74

OS Subsystem Panel

The OS Subsystem panel displays the status of the components that represent

the health of critical subsystem features as described in the following table:

Message Flows

The Diagnostic Console contains the following message flows that show the

amount of information being sent to various components in your Blackberry

environment.

COMPONENTS DESCRIPTION

CPU Usage Shows the total amount of CPU usage on this BlackBerry

server

Top CPU Consumer Identifies the process that is consuming the most CPU

on this BlackBerry server

Top Memory Consumer Identifies the process that is consuming the most

memory on this BlackBerry server

Network Output Queue Indicates the network output queue length for all

network adapters on this BlackBerry server

Network Bytes per Sec Indicates the number of bytes sent and received per

second by the network adapters on this BlackBerry

server

Processor Queue Indicates the processor queue length on this BlackBerry

server

System Memory Indicates the amount of RAM that is currently being

consumed on this BlackBerry server

System Disk Indicates the amount of free and used disk space on this

BlackBerry server

MESSAGE FLOW DESCRIPTION

Msgs Received/min Indicates the number of messages received by

handhelds per minute.

Note: This value reflects server activity since the

last time the BlackBerry Server restarted.


75

Drilldowns

Each drilldown page contains displays that provide you with specific information

about the components of your system. Drilldowns mainly use two different types

of displays – tables and charts. Spotlight drilldowns have the following features:

• They can be configured to show all or some of the metrics associated

with components.

• You can access further information about displays in drilldowns by

moving the mouse over the displays, or by clicking or right-clicking

them.

• You can copy the data shown in drilldowns to other applications or

save it to a file.

• You can view a brief description of a drilldown by hovering your

mouse over a component, such as a button, dataflow, status ball, or

Toolbar button.

Msgs Sent/min Indicates the number of messages sent by

handhelds per minute.

Note: This value reflects server activity since the

last time the BlackBerry Server restarted.

Bytes Read/sec Indicates the rate at which data is being read

from the disk on the BlackBerry Server

Bytes Written/sec Indicates the rate at which data is being written

to the disk on the BlackBerry Server



76

To view a drilldown

Right-click a component in a panel and select Show Details.

DRILLDOWN DESCRIPTION ASSOCIATED CHARTS/TABS

Service Health The Service Health panel

displays the CPU and

memory usage status of

the BlackBerry services.

• Blackberry Attachment Service

• Blackberry Dispatcher Service

• Blackberry Messaging Agents

Service

• Blackberry Policy Service

• Blackberry Router Service

• Blackberry Synchronization

Service

For a description of these charts, see

“Service Health Panel” on page 70.

SRP The SRP drilldown

indicates whether or not

the BlackBerry server is

connected to the Server

Relay Protocol.

• SRP Status – indicates whether or

not the BlackBerry Server is

connected to RIM's Server Relay

Protocol (SRP) server using port

3101

For a description on the other charts,

see “SRP Panel” on page 70.

Server The Server drilldown

identifies server-specific

information such as

licenses in use and

messaging statistics on

this BlackBerry server.

• Message and Users – Shows

messages and user information.

Message charts includes:

Pending, Expired, Error, MORE,

Global Filtered, and User Filtered.

User charts include: OTAC, WER,

and Failed Initializations.

• Licenses and Connections –

Shows license and connection

information. License charts

include information on licenses

currently in use. Connection

charts include: Message Agents,

Service Connections, and Device

Connections.

For a description on these charts, see

“Server Panel” on page 71.


77

Metrics

A metric is an individual piece of information that Spotlight has collected about

the performance of a system. The information may be a numeric value (a

number or percentage), a string of text, or some other piece of data.

Every time that the Spotlight window is refreshed, Spotlight retrieves the latest

value of the metric, which can then be displayed in a drilldown or on the home

page.

Users The Users drilldown

displays BlackBerry

server user information.

• User Configuration – shows

configuration data for the users

hosted by this BlackBerry Server

• User Devices – shows users'

handheld device information on

this BlackBerry Server

• User Statistics – shows statistical

information related to the users

on this BlackBerry Server

OS/Subsystem The OS/Subsystem

drilldown displays the

status of components

that represent the health

of various subsystem

features on your

BlackBerry server. These

include CPU usage, RAM

usage, disk space

availability, the network

output queue length of

network adapters, the

number of bytes sent

and received by the

network adapters, and

the processor queue

length.

• CPU Usage

• System Disk

• Network Bytes per Sec

• System Memory

• Network Output Queue

• Processor Queue Length

For a description of these charts, see

“OS Subsystem Panel” on page 74.

Processes The Processes drilldown

shows a list of all the

processes running on the

BlackBerry Server, along

with their CPU and

memory usage.

• Process Name

• CPU Usage

• Physical Memory

• Virtual Memory



78

The Metric editor allows you to view and edit the properties of Spotlight metrics,

including their thresholds and severities. You can open the Metric editor for a

component or a drilldown by right-clicking on the component and choosing

Metrics from the invoked shortcut menu.

When you open the Metric editor, the General tab is open by default. Several

metrics contain data source descriptions for the metric. The data source

descriptions use the following list of functions.

For more information on Metrics and Properties, see the Spotlight Basics Online

Help.

Understanding the Exchange 2000/2003 Diagnostic Console

The Exchange 2000/2003 Diagnostic Console contains the following:

• Common Home Page Elements

• The Main Home Page

• The IIS Home Page

• The Storage Groups Home Page

• The Directory Services Home Page

• The Best Practices Home Page

• Metrics

FUNCTION DESCRIPTION

max(x) the maximum of a set of values in list x

max(x,y) the maximum of x and y

min(x) the minimum of a set of values in list x

count(x) the number of values in list x

sum(x) the sum of a set of values in list x

if(x,y,z) if x is true, then return y, otherwise, return z

snull(x) if x could not be collected, then return true

avg(x) the average of values in list x


79

Common Home Page Elements

The Exchange 2000/2003 Diagnostic Console contains five home pages that

target and provide details about specific server activity. However, there are

some panels and features common to all home pages (except for Best Practices

Home Page) including:

HOME PAGE ELEMENT DESCRIPTION

Home Page Links You can access each of the Exchange 2000/2003

Diagnostic Console home pages by clicking the

home page title links as shown in this image.

These links appear on each page so that you can

easily switch views. The status ball beside each

title changes color to indicate the collective

operational status of all of the components on that

page. The white arrow indicates the current home

page view.

Media Connections Media Connections displays the status of

Exchange 2000/ 2003 Conferencing Server

features such as conference service, instant

messaging, and chat. You can see if these features

have been installed on the server and, if they have

been, how many connections to each feature have

been established. If the feature has not been

installed on the server, the status is displayed as

N/A.

Exchange CPU Usage Exchange CPU Usage appears on each page to

keep you informed of the service status, and the

CPU consumption of core Exchange 2000 or

Exchange 2003 services including the IIS,

Information Store, System Attendant, and the

MTA Stacks.

You can start, stop, and restart services using

Exchange CPU Usage.

Server and Platform Status This list indicates the service pack that is installed

on the Exchange server and the length of time the

server has been running since it was started. This

information will help you analyze the efficiency of

the server. The panel also shows the role of the

server. Knowing whether it is a front-end or a

back-end server will help you analyze the data

provided by Exchange 2000/2003 Diagnostic

Console. Front-end servers run one or more of the

Internet protocols, but do not house information

stores or databases.


80

The Main Home Page

The Main home page is comprised of panels, message flows, and drilldowns that

represent the flow of email messages through the Exchange 2000 or Exchange

2003 server to which you are connected.

Directory Services Panel The components of the Directory Services panel

include DS Access Status, Global Catalog, DNS,

and Recipient Update Service. These components

indicate how Exchange 2000 or Exchange 2003

interacts with directory services.

The DS Access Status, Global Catalog, DNS, and

Recipient Update Service points to the Directory

Services, Active Directory Servers, DNS Servers,

and Recipient Update Servers respectively. For

information on these drilldowns, see “Drilldowns”

on page 83.

OS Subsystem Panel The OS Subsystem panel displays components

that represent the health of important subsystem

features such as CPU and memory usage, the

amount of disk space used and disk space

available, as well as server response times.

The components on the OS Subsystem panel are

connected to Spotlight on Windows drilldowns.

Note: You can view Spotlight on Windows

drilldowns if you have formed a connection to the

server with Spotlight on Windows. For more

information on forming Spotlight connections,

refer to the Connecting and Disconnecting section

in the Spotlight Basics online help.

Manage Diagnostic Logging

Levels drilldown

You can control the current Diagnostic Logging

Levels for specific Exchange 2000/2003 service

categories on the Exchange server to which you

are connected.

If you change a threshold on one home pages, the change does not apply to

all pages. You must make any changes on each page individually.

HOME PAGE ELEMENT DESCRIPTION


81

Panels

The Main home page is a high-level operational summary of the Exchange 2000

or Exchange 2003 server and is comprised of the following panels:

Message Flows

The Main Home Page contains the following message flows:

PANEL DESCRIPTION

Inbound Shows the current connections to the Exchange

2000 or Exchange 2003 server. They include

SMTP connections, MTA connections, MAPI

connections, Outlook Web Access (OWA)

connections and Exchange events.

Queues Displays components representing the Exchange

queues that have received messages from SMTP

and MTA sources, and groups components that

represent the queues containing outgoing

messages from SMTP and MTA sources.

Information Store Shows information about messages being routed

from the MTA and incoming MAPI and OWA

connections. The Receive Queue and the Send

Queue show the number of messages being sent

to and from all of the Private and Public

Information Stores. The container components

show the amount of disk space used and disk

space available on the volumes containing the

mailbox stores, public folder, and transaction

logs.

Advanced Queuing Shows the Exchange engines responsible for

routing incoming messages. All messages

entering the Exchange 2000 or 2003 server are

sorted by the categorizer and routing engines.


SMTP Inbound Shows the rate of messages being received by

this Exchange server from other SMTP hosts

SMPT In To Categorizer Shows the rate of messages flowing from the

inbound SMTP queue to the Categorizer

Advanced Queuing to SMTP

Outflow

Shows the rate of messages from Advanced

Queuing to the SMTP outbound queue


82

Store To Advanced Queuing Shows the rate of messages flowing from the

Store to Advanced Queuing

Advanced Queuing to the Store Shows the rate of messages flowing from

Advanced Queuing to the Store

SMTP Out Queue Shows the rate of messages flowing from the

outbound SMTP queue to remote SMTP hosts

MTA Inbound Shows the rate messages are being submitted by

remote Exchange MTAs to the local MTAs work

queue for processing

MTA Out Queue to Message Shows the rate that messages are being

delivered from remote MTA queues on this

Exchange server to remote Exchange MTAs, or

MTAs on other X.400 mail systems

MTA Work Queue to Store Shows the current number of messages in transit

from the local MTA In work queue to the

Information Store

Store to MTA Out Queue Shows the current number of messages that are

leaving the store bound for a remote MTA queue

MAPI Inbound Shows the rate that RPC data is being written to

the information store by the current user and

system connections (for example, MAPI clients)

Disk Bytes Written to Disk

Subsystem

Shows the rate at which data is being written

from the information store to the disk, network,

and device subsystems of the Windows

2000/2003 server running Exchange

MAPI Outbound Shows the rate that data is being read by the

current user and system connections (such as

MAPI clients) from the information store

Disk Bytes Read from Disk

Subsystem

Shows the rate at which data is being read by the

information store from the disk, network, and

device subsystems of the Windows 2000/2003

server running Exchange

OWA Inbound Shows the rate that OWA clients are issuing

commands that write data to the store

OWA Outbound Shows the rate that OWA clients are issuing

commands that read data from the store

POP3/IMAP4 Shows the rate that POP3 and IMAP4 clients are

issuing commands to the store



83

Drilldowns



of displays — tables and charts. Spotlight drilldowns have the following features:


with components.


moving the mouse over the displays, or by clicking or right-clicking

on them.


save it to a file.

• You can view a brief description of a drilldown by hovering your

mouse over a component, such as a button, dataflow, status ball, or

Toolbar button.

To view a drilldown

• Right-click a component in a panel and select Show Details.


Active

Directory

Servers

Shows the status of

the domain

controllers used by

this Exchange server.

Active Directory Servers

DNS Servers Shows the status of

the DNS servers used

by this Exchange

server. These are the

DNS servers in the

network configuration

of this Exchange

server’s Windows

2000/2003 operating

system.

DNS Servers


84

Recipient

Update

Servers

Shows the status of

the Recipient Update

Servers used for the

domain

and enterprise to

which this Exchange

server belongs. If all

Recipient Update

Servers are available

on the network from

this client, and have a

System Attendant

service that is

running, the Recipient

Update Servers

health status is

green.

Recipient Update Servers



85

Protocols Displays detailed

information about

current connections

to the Exchange

server being

monitored.

Connections shows:

• the total number of SMTP connections to

other SMTP hosts.

• the current number of Remote

Procedure Call (RPC) active sessions

established to the information store by

Exchange RPC clients (MAPI Clients).

• the total number of POP3 and IMAP4

connections.

• the current number of active remote

MTA connections.

• the current number of HTTP connections

to the web service on this Exchange

2000/2003 server made by OWA clients.

• the current number of active

conferences, instant messaging

connections, and chat connections

established with this server.

Activity shows the rate at which:

• messages are sent to and received from

other SMTP hosts by this Exchange

server.

• RPC data is read to and written from the

store by Exchange RPC clients (MAPI

clients).

• POP3 and IMAP4 clients are issuing

commands to the store.

• messages are sent and received by the

local MTA.

• OWA clients are issuing commands that

place a load on the store.

• data is being sent and received by

the HTTP clients.



86

Directory

Services

Indicates how

Exchange 2000/2003

interacts with

directory services.

Directory Proxy shows:

• the rate of client connections by older

MAPI clients (such as Outlook 97/98) to

the Directory Proxy component

(DSProxy).

• the rate of bytes per second being

transmitted to and from the Directory

Services Proxy.

• the rate of directory referrals being

handed out by the Directory Proxy

component (DSProxy) to new MAPI

clients (such as Outlook 2000/XP).

• the number of threads in use and the

maximum number of concurrent

connections to the Directory Services

Proxy.

Directory Access Cache shows:

• the rate at which directory entries are

entering and exiting the cache.

• the rate of cache hits and misses per

second

• the cache hit percentage.

• the rate of LDAP requests being issued

by the Directory Access (DSAccess)

cache and one or more DSAccess

consumers (a context) to one or more

domain controllers.

• the total count of cache hits and misses.

• the number of current consumer

processes. (applications (processes)

that use the directory proxy for directory

lookups).



87

Queue

Management

Provides details about

all the SMTP virtual

servers and

associated message

queues installed on

the Exchange server.

You can perform the

following

management actions

using the Queue

Management

drilldown:

• Freezing and

unfreezing

queues

• Forcing a retry

• Freezing and

unfreezing

messages

• Deleting

messages

• Queue Management — shows crucial

operational properties for all virtual

Simple Mail Transfer Protocol (SMTP)

server messaging queues on this

Exchange server. The queues are

grouped by the virtual SMTP server to

which they belong.

• Queue Messages Management — shows

messages residing in the selected SMTP

queue that are waiting to be processed.

Each column represents a message

property.



88

Information

Store

Displays information

detailing current

activity of the

Information Store.

• Store Information — provides detailed

information about all public and private

stores on the connected server.

• Store Backup — provides detailed

information about backups performed

on storage groups on the connected

server.

• Store Whitespace — indicates the

amount of whitespace on stores, the

date and time of the last online

defragmentation, and the amount of

whitespace following defragmentation.

• Health — indicates the amount of

activity on the Information Store. It

provides a historical view of the rate at

which data is read by the store, CPU

usage, and the mount of physical and

virtual memory consumed by the

Information Store.

• Activity — provides information about

the amount of activity of the

Information Store, specifically the flow

of messages to and from the mailbox

stores and folders.

• Queues — provides a historical view of

the Information Store, specifically the

number of messages in various stages

of delivery.

• Storage Group Users and Mailboxes —

indicates the number of users and

mailboxes on a specific storage group.

You must have at least one storage

group installed.

• Storage Group Disk Usage — indicates

the amount of disk space used by each

mailbox store and public folder installed

on the server.

• Transaction Logs — indicates the

amount of disk pace used by the

transaction logs and the rate at which

the transaction logs are written.



89

The IIS Home Page

The IIS home page provides details of the health of the Microsoft Internet

Information Server (IIS) and the Exchange 2000 or Exchange 2003-specific

components of the IIS, specifically, the SMTP subsystem.

Panels

The IIS home page displays the following panels:

IIS Shows the health of

the IIS, including the

amount of time used

to execute IIS

instructions and the

physical and virtual

memory used in the

process.

• Health — provides a historical view of

the elapsed time used by the IIS to

execute instructions and the physical

and virtual memory used in the process,

and shows the uptime of the Web

service.

• Routing — shows the amount of activity

of the Exchange server, specifically the

activity of the Routing engine.

• Failures — shows the amount of activity

of the Categorizer engine.

Known

Exchange

Problematic

Events

Lists application log

and system log

events for the

Exchange server.

Only entries that

have occurred within

the configured time

frame are shown

here.

• Application Log Problematic Events —

shows the application-related event log

entries pertinent to this Exchange server

that indicate an operational problem.

• System Log Problematic Events —

shows the system-related event log

entries have an operational problem

with the Exchange 2000/2003 server.

PANEL DESCRIPTION

Inbound Shows the inbound Web and SMTP connections to

the Exchange 2000 or Exchange 2003 server and

include SMTP In connections, Peak HTTP

connections, and HTTP connections.

Categorizer Shows the queues containing messages that have

entered the Exchange 2000 or Exchange 2003

server and are about to be processed by the

categorizer and routing engines. These include the

Messages Awaiting Directory Lookup, Failed

Categorizations and Rate of NDRs components.



90

Message Flows

The IIS Home Page contains the following message flows:

Routing Show the messages in transit, such as those

waiting to be delivered to the local mailbox or

public folder, or messages about to be sent to

other SMTP hosts. These include the Messages

Waiting to be Routed, Messages Currently

Undeliverable and Routing Table Lookups/sec

components.

SMTP Shows the key SMTP messaging queues on the

Exchange 2000 or Exchange 2003 server currently

being diagnosed. These include the Local Delivery

Queue, Queued SMTP Out, SMTP Out Connections,

Virtual Servers and Bad Mail Messages

components.

IIS Health Shows the status of the services critical to the

operation of the Exchange 2000 or Exchange 2003

Web service. These include the IIS Services, Web

Service Uptime, OWA Operations/sec, Memory

Usage and CPU components.

With this panel, you can start, stop, and restart

services.

The services listed in the IIS Services section of

the panel are connected to the Services tab of the

Spotlight on Windows Processes drilldown.


Messages Submitted to the

Categorizer per second

Shows the rate of messages flowing from the

inbound SMTP queue to the Categorizer

Messages Completed

Categorization per second

Shows the rate, messages per second, that

messages are categorized. At this point the

message is ready to be routed to the appropriate

destination.

Local Delivery Rate Shows the rate of messages flowing from

Advanced Queuing to the Store

SMTP Messages Sent per second Shows the rate of messages flowing from the

outbound SMTP queue to remote SMTP hosts

PANEL DESCRIPTION


91

Drilldowns

The IIS Home Page contains the following drilldowns:

• Protocol

• Queue Management

• IIS

• Information Store

For more information on these drilldowns, see “Drilldowns” on page 83.

The Storage Groups Home Page

The Storage Groups home page contains detailed information on the Exchange

2000 or Exchange 2003 storage subsystem. Messaging traffic, bound for a

storage group, enters on the left side of the home page and flows through to a

storage group on the right side.

HTTP Bytes In per second Shows the rate, in bytes per second, that data is

received by the Internet Information Services

(IIS) subsystem

HTTP Bytes Out per second Shows the rate, in bytes per second, that data is

sent by the IIS subsystem

IIS Disk Bytes Read per second Shows the rate at which data is being read by the

IIS from the disk, network, and

device subsystems of the Windows 2000/2003

server running Exchange

IIS Disk Bytes Written per

second

Shows the rate at which data is written from the

IIS to the disk, network and device subsystems

of the Windows 2000/2003 server that is running

Exchange



92

Panels

The Storage Groups home page displays the following panels:

PANEL DESCRIPTION

Information Store Shows the queues containing messages about to

be processed by the Information Store, and the

queues with messages that have been processed.

These include the Receive Queue, Send Queue,

Active Connectors, Connections, Connected Users,

CPU, and Memory Usage components. You can see

the number of user and system connections that

have shown recent activity by viewing the Active

Connections component.

Storage Group Shows a high-level overview of the storage groups

installed on the Exchange 2000 or Exchange 2003

server. If only one storage group is installed, the

panel shows the details of that storage group. The

panel demonstrates that more storage groups can

be installed. The title of each storage group

displayed in the panel is a link to more detailed

information provided in the larger Storage Group

panel to the right. The titles are updated as the

groups are installed and named.

Storage Group Details Is the largest panel on the Storage Groups home

page. It is a dynamic panel that displays an

expanded view of the currently selected storage

group. The name of the currently selected storage

group is the title of this panel. The components

include the Receive Queue, Send Queue, Active

Connections, Connections, Transaction Logs,

Mailbox Stores, Public Folder Stores and the Not

Installed components.

You can mount and dismount stores using this

panel.


93

Message Flows

The Storage Groups Home Page contains the following message flows:

Drilldowns

The Storage Groups Home Page contains the following drilldowns:

• Information Store

• Protocols


The Directory Services Home Page

The Directory Services home page displays the status of the Exchange server

connection to and use of Active Directory server, a critical dependency of

Exchange 2000 and Exchange 2003.


Information Store to Storage

Groups

Shows the flow of messages per minute into the

storage groups. The information store determines

the destination of the intended recipients and

delivers the message to the appropriate Storage

Group.

Storage Group to Mailbox

Stores/Public Folders

Shows the flow of messages, per minute, into the

mailbox stores and public folders.

Storage Group to Information

Store

Shows the flow of messages per minute from the

storage groups.

Mailbox Stores/Public Folders to

Storage Group

Shows the flow of messages per minute from the

mailbox stores and public folders.

Transaction Log Writes per

second

Shows the rate at which the log buffer is

committed to the transaction logs.


94

Panels

The Directory Services home page displays the following panels:

PANEL DESCRIPTION

Connections The Connections panel contains one component

that displays the number of MAPI email clients

using the Directory Service Proxy (DSProxy)

component on the Exchange 2000 or Exchange

2003 server.

Clients Provides an indication of the immediate demands

that the Exchange server is putting on Active

Directory. These include the Consumer Processes,

Categorizer and SMTP Out components.

DS Proxy Shows the features of the Directory Service Proxy

(DSProxy). The components indicate the

immediate demand the Exchange server is placing

on the DSProxy by showing the number

of threads in use, and the number of peak client

connections. These include the Threads in Use,

Peak Client Connections and Directory Referrals

components.

DC Servers Shows the Global Catalog (GC) and domain

controller (DC) servers used by the Exchange

server. These include the Global Catalogs, Domain

Controllers, Configuration GC, Proxy GC

Overridden and Referral GC Overridden

components.

DS Access Cache Shows the features of the DSAccess cache. The

components show the rate at which directory

entries are entering and leaving the cache and the

percentage of space occupied by all directory

cache entries.

Note: You can change the maximum cache size

and timeout (TTL) parameters by using the

Manage menu.

DNS Shows the primary and secondary DNS servers

configured on the Windows 2000 or Windows 2003

operating system where the Exchange 2000 or

Exchange 2003 server resides. These include the

Primary DNS Server and Secondary DNS Server

components.


95

Message Flows

The Directory Services Home Page contains the following message flows:


Outlook Connections to DSProxy Shows the rate of client connections by older

MAPI clients (for example, Microsoft Outlook

97/98) to the directory proxy component

(DSProxy)

DSProxy to Outlook Connections Shows the rate at which directory referrals are

given by the Directory Proxy component

(DSProxy) to new MAPI clients (for example,

Microsoft Outlook 2000/XP)

Consumer Processes Shows the rate at which LDAP searches are

issued to the Directory Access (DSAccess) cache

by the consumers

DSAccess to DCServers Shows the rate of LDAP requests issued by the

Directory Access (DSAccess) cache to one or

more domain controllers

Categorizer to Global Catalog Shows the rate at which address lookups are

issued by the Categorizer to one or more Global

Catalog servers

SMTP Out DNS Queries Shows the rate at which DNS queries are issued

by the SMTP components on this Exchange server

to DNS

DSProxy to DCServers Shows the estimated rate at which data flows

from the Directory Proxy (DSProxy) component

to one or more domain controllers

DCServers to DSProxy Shows an estimated rate of data flowing from

one or more domain controllers to the DSProxy

component

DCServers to DSAccess Shows the rate of LDAP requests issued by the

Directory Access (DSAccess) cache to one or

more domain controllers


96

Drilldowns

The Storage Groups Home Page contains the following drilldowns:

• Directory Services

• Queue Management

• IIS

• Protocols

• DNS Servers

• Active Directory Servers

• Recipient Update Service


The Best Practices Home Page

The Best Practices home page helps you maximize the performance of your

Exchange server and alerts you to any situations which do not conform to

well-known Exchange 2000 or Exchange 2003 best practices.

The metrics, thresholds, and severities have been carefully configured for

the components on the Best Practices home page, and it is recommended

that you do not change these configurations.


97

Panels

The Best Practices home page displays the following panels:

PANEL DESCRIPTION

Exchange Update The Exchange 2000/2003 Diagnostic Console

detects whether or not the latest Exchange server

and Windows operating system updates have been

installed on the server being diagnosed.

If an update has been installed, the Exchange

2000/2003 Diagnostic Console displays the date

and time of the installation. You can click the

Details button to view the corresponding

drilldown. For example, if you click the Details

button for the latest Exchange update, you can

view the Exchange Updates tab of the Updates

drilldown.

The drilldown is divided into two sections. The top

section lists all of the installed Exchange updates.

The bottom section is an embedded Web browser

that is set to display the Microsoft Product Support

Services Web page. You can click any of the rows

of information in the top section of the drilldown

and the Web browser navigates to the

corresponding Microsoft Knowledge Base article.

If the Exchange 2000/2003 Diagnostic Console

detects that the latest updates have not been

installed, the following message is displayed: None

detected.


98

Security Configuration The Security Configuration panel provides

warnings and expert advice (Expert Help) about

how you can improve the security of the Exchange

2000 or Exchange 2003 server to which you are

connected.

The Exchange 2000/2003 Diagnostic Console

checks to see if:

• SMTP service version information is displayed

in the banner on incoming connections - The

Exchange 2000/2003 Diagnostic Console

checks to see if SMTP service version

information is displayed in the banner on

incoming connections. To improve security on

the Exchange 2000 or Exchange 2003 server,

this information should not be displayed.

• any SMTP virtual servers are used for relaying

mail - The Exchange 2000/2003 Diagnostic

Console detects whether SMTP virtual servers

could be used for relaying mail. This type of

SMTP virtual server use can be a security risk

for Exchange 2000 or Exchange 2003 server.

PANEL DESCRIPTION


99

Exchange Configuration The Exchange Configuration panel provides

warnings and expert advice (Expert Help) about:

• Mailbox Stores and Transaction Logs — The

Exchange 2000/2003 Diagnostic Console

detects whether or not the server being

diagnosed has mailbox stores and transaction

logs that share a physical drive. Transaction

logs are critical to the restoration of lost data

and, in case of disk failure, should not be

located on the same physical disk as the data

to be restored.

• Everyone Group is in access control lists

(ACLs) — In a default Exchange 2000 or Exchange 2003 installation, the access control

list (ACL) for the tracking logs share contains

the Everyone group. This poses a security risk

because unauthenticated users could access

the tracking logs and expose sensitive

information to all users on the network.

• Domain Controller Location — The Exchange

2000/2003 Diagnostic Console detects

whether or not the Exchange 2000 or

Exchange 2003 server to which you are

connected is also acting as a Windows 2000 or

Windows 2003 domain controller.

Note: It is recommended that the domain

controller resides in a separate location as it can

consume large amounts of server resources and

impede Exchange server performance.

PANEL DESCRIPTION


100

Maintenance Events The Exchange 2000/2003 Diagnostic Console

searches the event logs of the server being

diagnosed for well-known Exchange 2000 or

Exchange 2003 maintenance events that have

occurred, such as:

• Search Status and Oldest Event Read — By

viewing the Search Status and Oldest Event

Read labels, you can quickly see whether or

not the Diagnostic Pack for Exchange

2000/2003 component is still searching and

you can view the date and time of the oldest

event read.

• Last BSE Backup — If the Extensible Storage

Engine (ESE) is used to back up data on the

server, the Exchange 2000/2003 Diagnostic

Console can detect the date and time of this

event in the event log and will display this

information beside the Last Successful ESE

Backup label. If the ESE is not used to

perform the backup, the Exchange 2000/2003

Diagnostic Console displays: Not Detected.

• Last Online Defragmentation — The

Maintenance Events panel also displays the

date and time of the last online

defragmentation event for a store. The name

of the store is displayed as well as the

percentage of whitespace in the store.

• Oldest Transaction Logs — This provides the

names of storage groups, the date and time

that a backup occurred for each storage

group, and the age (in hours) of the

transaction log for each storage group.

PANEL DESCRIPTION


101

Drilldowns

The Best Practices Home Page contains the following drilldowns:.


Updates Provides details about

the latest Exchange

and Windows 2000 or

2003 updates

installed on the

Exchange server, as

well as the latest

updates available.

• Exchange Updates – shows all the

Exchange 2000/2003 hotfixes installed

on this server. The Q Name column

represents the Microsoft Knowledge

Base Article Number.

• Windows Updates – shows all

the Windows 2000/2003 hotfixes

installed on this server. The Q Name

column represents the Microsoft

Knowledge Base Article Number.

Security

Configuration

Provides details about

SMTP virtual servers

that may be a

security threat to the

Exchange 2000 or

Exchange 2003

server.

• SMTP Versions – Shows whether any of

the SMTP virtual servers are displaying

SMTP service version information in the

banner on incoming connections.

• SMTP Relay – Shows whether any of the

SMTP virtual servers could be used for

relaying mail.

Exchange

Configuration

Shows the stores and

storage groups that

share physical disk

space with

transaction logs on

the server being

diagnosed. If there is

a conflict, the

drilldown displays the

name of the store,

storage group, the

physical drive, and

the logical path of the

store.

• Exchange Storage Configuration –

shows if there are any Exchange

2000/2003 transaction log files located

on the same physical disk as a store

database file (STM or EDB).

Note: If Spotlight on Messaging detects

that no stores share space with transaction

logs on the server being diagnosed, you can

click the message, "There are no Mailbox

Stores sharing a physical drive with

Transaction Logs" on the Exchange

Configuration panel. The message, "No

conflicts detected" is displayed in the

Exchange Configuration drilldown.


102

Metrics

For information on Metrics, see “Metrics” on page 77.

Maintenance

Events

Displays the following

information:

• the status of the

search by

Spotlight on

Exchange

through the

event log.

• the oldest event

that has been

read from the

event log.

• the date and time

of the last

backup

performed by an

Extensible

Storage Engine

(ESE) compliant

backup utility (for

example, NT

Backup).


of the last online

defragmentation.


stamp of the

oldest

transaction log

for the storage

groups.

• Information Store – for more

information, see “Drilldowns” on page

83.



103

Understanding the Exchange 2007 Diagnostic Console

The Exchange 2007 Diagnostic Console contains the following:

• Panels

• Message Flows

• Drilldowns

• Metrics

Panels

The Exchange 2007 Diagnostic Console contains the following panels:

• AD/DNS Panel

• Server Role Status Panel

• Transport In Panel

• Transport Panel

• Transport Out Panel

• Clients Panel

• Information Store Panel

• Subsystem Panel

AD/DNS Panel

The components of the Directory Services panel indicate how Exchange 2007

interacts with directory services. This information includes:


AD Shows the status of the Active Directory (AD)

servers used by this Exchange 2007 server

DNS Shows the status about the Domain Name System

(DNS) servers in use by this Exchange 2007

server


104

Server Role Status Panel

This panel shows the Exchange 2007 roles that are installed. This information

includes:


MBX Shows whether the Mailbox role is installed on

this Exchange 2007 server. The Mailbox role is

responsible for hosting mailbox and public folder

data. It also provides MAPI access for Outlook

clients.

UM Shows whether the Unified Messaging role is

installed on this Exchange 2007 server. The

Unified Messaging role enables you to access their

mailbox, address book, and calendar using

telephone and voice. Note that IP-PBX or VoIP

gateway must be installed to use the functionality

of the Unified Messaging role.

CAS Shows whether the Client Access role is installed

on this Exchange 2007 server. The Client Access

role provides mailbox server protocol access apart

from MAPI. It is similar to an Exchange 2003

Front-End server in that it allows you access to

their mailboxes using Outlook Web Access (OWA),

POP3/IMAP4, and ActiveSync.

EDG Shows whether the Edge Transport role is

installed on this Exchange 2007 server. The Edge

Transport role provides mail quarantine and SMTP

services to enhance security. It is the first hop of

incoming mail and the last hop of outgoing mail.

Note that it does not require AD access so that it

can function with limited access to the corporate

network (for added security).

HUB Shows whether the Hub Transport role is installed

on this Exchange 2007 server. The Hub Transport

role handles mail flow by routing messages to

either another Hub Transport server, an Edge

server, or a Mailbox server. This role is similar to

the bridgehead server in an Exchange 2000/2003

organization, except that it uses AD site info to

determine the mail flow.


105

Transport In Panel

The Transport In panel groups components that represent current inbound

connections to this Exchange 2007 server. This information includes:

Transport Panel

The Transport panel groups components that identify the status of the various

transport queues on this Exchange 2007 server. This information includes:


Connections Shows the total number of inbound SMTP

connections established by other SMTP hosts to

this Exchange server. The number of connections

represents the sum of all SMTP inbound

connections from all remote domains to SMTP

Receive Connectors on this Exchange 2007 server.

Connectors Shows the number of SMTP Receive connectors on

this Exchange 2007 server that can accept mail

from other SMTP servers.

Submission Queue Shows the number of items in the Submission

Queue. The submission queue holds messages

before they are consumed by the Categorizer

which determines what to do with the messages

based on information about the intended

recipients. After the submission queue, the

Categorizer then routes the message to either an

Edge Server role, another Hub server in a

different AD Site, a mailbox on an Exchange

2000/2003 server, or the Unreachable Queue.


Unreachable Queue Shows the number of messages in the transport

unreachable queue on this Exchange 2007 server.

The Unreachable Queue contains any messages

that cannot be routed to their final destination.

Poison Queue Shows the number of potentially harmful

messages on this Exchange 2007 server.

Messages that contain content that might be

damaging to the Exchange Server system are by

default delivered to this Poison Queue and

suspended. If messages in this queue are deemed

not harmful, message delivery can be resumed,

and the message enters the Submission Queue.


106

Transport Out Panel

The Transport Out panel groups components that represent current outbound

activity from the Exchange 2007 server. This information includes:

Mailbox Delivery Queue Represents the number of items in the Transport

Mailbox Delivery Queue on this Exchange server.

The mailbox delivery queue holds messages that

are being delivered to mailbox recipients whose

mailbox data is stored on a Mailbox server role

located in the same site as this Transport server.

The next hop for a message in this queue is the

distinguished name of the destination mailbox

store.

LDAP Search Time (ms) Shows LDAP Search Time (in milliseconds) for the

transport to send an LDAP search request to

Active Directory, and receive a response on this

Exchange 2007 server. Exchange 2007 uses

Active Directory (AD) as a repository for mailbox

and mail routing configuration data. Exchange

2007 servers issue LDAP queries against Active

Directory to retrieve message routing data.


Connections Shows the current number of outbound SMTP

connections to other SMTP hosts. The number of

connections represents the sum of all SMTP

outbound connections from SMTP Send

Connectors on this Exchange 2007 server to all

remote SMTP domains.

Connectors Shows the number of SMTP Send connectors on

this Exchange 2007 server that can service

connections to other SMTP servers.



107

Clients Panel

The Clients panel groups components that represent current client connections

and associated latency to this Exchange 2007 server. This information includes:

Remote Delivery Queue Shows the number of messages in the transport

that are queued for delivery to a remote server

using SMTP. The Exchange 2007 Hub and Edge

roles can have multiple remote delivery queues.

Each queue contains messages with recipients

that share the same remote server destination.

On a Hub role server, the destination servers are

within the same Exchange Organization as this

Exchange server, but in a different AD Site. For

the Edge role, the destination servers are external

to the Organization, and handle message delivery

for external SMTP domains.


MAPI Indicates the number of MAPI user connections to

this Exchange 2007 server. The Mailbox role

provides MAPI access for Microsoft Outlook

clients, and enables these types of connections.

OWA Indicates the number of current unique OWA

users logged on to this Exchange 2007 server. The

Client Access role provides OWA to allow you to

access his or her mailbox from a web browser and

have full access to all the information in the

mailbox including task lists, calendar information,

mail items, public folders, UNC shares

(\\servername\share) and SharePoint documents.

This value is decremented when a you log off your

OWA session or the session times out.

ActiveSync Shows the number of current secure HTTP

connections (HTTPS) that are established from

Windows Mobile-based or Exchange

ActiveSync-enabled mobile devices and this

Exchange 2007 server. ActiveSync is a push

orientated protocol. Data such as user messages,

schedules, contact information and tasks are

synchronized over the HTTPS connection.



108

Information Store Panel

The Information Store panel displays key operational metrics for the information

store on this Exchange server. This information includes:

POP3 Shows the number of POP3 connections to this

Exchange 2007 server. The Client Access role

provides POP3 access to mailbox data for clients

that rely on this protocol.

IMAP4 Shows the number of IMAP4 connections to this


provides IMAP4 access to mailbox data for clients


Latency (ms) (for MAPI) Shows the average latency for MAPI clients

connected with Outlook to this Exchange 2007

server providing the Mailbox role.

Latency (ms) (for OWA) Shows the average latency for OWA clients on the

Exchange 2007 server.

Latency (ms) (for ActiveSync) Shows the average latency for ActiveSync clients

on the Exchange 2007 server.

Latency (ms) (for POP3) Shows the average latency for POP3 clients on the


Latency (ms) (for IMAP4) Shows the average latency for IMAP4 clients on

the Exchange 2007 server.


Average message delivery

time(sec)

Indicates the average time in milliseconds

between the submission of a message to the

mailbox store and the delivery to all local

recipients (recipients on the same server) for the

last ten messages.

Clients with RPC (Remote

Procedure Calls) latency > 2 sec

Indicates the number of client reported Remote

Procedure Calls (RPCs) with a latency greater

than two seconds. The most commonly used RPC

protocol is MAPI, and a high RPC latency can

cause MAPI clients such as Microsoft Outlook to

hang and stop responding when users send email,

receive email, or use calendar functionality such

as creating or viewing appointments.



109

Average mailbox database size Indicates the average size of the mailbox

database.

Total Logons Indicates the total number of logons to the

information store on this Exchange 2007 server.

This includes end-user client connections and

system processes that are currently logged-on to

any storage group in the local information store.

There can be multiple logons per connection for

most client applications. As a result, it is possible

to see the number of client logons exceed the

number of mailboxes on a server.

Average client RPC latency (ms) Shows the average time (in milliseconds) that it

takes the server to respond to RPC connected

clients. The average is for the past 1024 packets.

The most commonly used RPC protocol is MAPI. A

high RPC latency can cause MAPI clients such as

Microsoft Outlook to hang and stop responding

when users send email, receive email, or use any

type of calendar functionality such as creating or

viewing appointments.

Mailbox Stores Shows the percentage of disk space consumed by

the mailbox stores on this server. This also shows

how much of the server disk consumption is

attributable to mailbox store consumption versus

other data.

Public Folders Shows the percentage of public store disk space

consumption on this server. This allows you to

assess how much of the server disk consumption

is attributable to public store data versus other

data.

Transaction Logs Shows the total percentage of disk space

consumed by the transaction logs on this server.

It can be used to quickly assess how much server

disk consumption is attributable to transaction log

data versus other data on the Exchange server.

Send Queue Shows the number of messages in the send queue

of the information store. This queue holds all

outgoing messages from the information store.

Receive Queue Shows the number of messages in the receive

queue of the information store. These messages

are waiting to be processed by the information

store.



110

Subsystem Panel

The Subsystem panel displays components that represent the health of

important subsystem features. This information includes:

Storage Groups Shows the number of storage groups installed on


Store Memory Shows the total physical memory of the store

process.

Mailbox Count Shows the total number of mailboxes that reside

in all mailbox stores and public folders.


Exchange Services Indicates the sum of CPU utilization for all of the

Exchange 2007 services running on this server.

System Disk Shows the percentage of disk usage for the

Windows system disk on this Exchange 2007

server.

System Memory Shows the amount of physical memory (RAM)

Windows is using. Physical memory usage can

normally remain close to the total amount of

physical memory installed on the system unless

the amount of physical memory exceeds the

amount of virtual memory that Windows is using.

Windows normally keeps some physical memory

available for immediate use.



111

Message Flows

The Exchange 2007 Diagnostic Console contains the following message flows

that show the amount of information being sent to various components in your

Exchange 2007 environment.


Msgs Submitted/sec Indicates the rate of messages being submitted per

second to this Exchange 2007 transport queues.

Msgs Received/sec Indicates the rate of messages received by SMTP

Receive connector on this Exchange 2007 server.

MAPI Msgs Submitted/sec Indicates the rate that messages are submitted to

the Information Store on the Exchange server by

MAPI clients (connected with Outlook).

OWA Msgs Received/sec Indicates the rate that bytes are received by

Exchange server from OWA clients.

ActiveSync Bytes

Received/sec

Indicates the rate that bytes are received by

Exchange this server from ActiveSync mobile

devices.

POP3/IMAP4 Bytes

Received/sec

Indicates the number of bytes per second received

from POP3 and IMAP4 clients.

Msgs Sent/sec Indicates the number of messages sent per second

to the transport.

Msgs Delivered/sec Indicates the rate of messages delivered to all

recipients with mailboxes on this Exchange 2007

server.

Bytes Received/sec Indicates the number of bytes received per second

from all RPC clients on this Exchange 2007 server

information store. RPC clients includes all internal

Exchange system components.

Bytes Sent/sec Indicates the number of bytes sent per second to all

RPC clients from this Exchange 2007 server


Exchange system component.

Bytes Read/sec Indicates the rate at which data is being read from

the disk, network, and device subsystems of the

Windows server running Exchange. The data is

primarily being read from the disk subsystem.


112

Drilldowns





with components.


moving the mouse over the displays, or by clicking or right-clicking on

them.


save it to a file.

• You can view a brief description of a drilldown by hovering your mouse

over a component, such as a button, dataflow, status ball, or Toolbar

button.

Bytes Written/sec Indicates the rate at which data is being written to



primarily being written to the disk subsystem.

Msgs Queued/sec Indicates the number of messages queued for

delivery per second on this Exchange 2007 server.



113

To view a drilldown


DRILLDOWN DESCRIPTIONASSOCIATED

CHARTS/TABS

AD/DNS Health The AD Servers drilldown displays information about the Active Directory and Active Directory servers currently in use by this Exchange 2007 server.

• Active Directory Servers — shows information about the Active Directory servers in use by this Exchange 2007 server. Exchange 2007 stores all configuration and recipient information in the Active Directory directory service database. All Exchange 2007 roles use Active Directory except the Edge role, which does not have access to Active Directory. The Edge role uses Active Directory Application Mode (ADAM) to store schema and configuration information.

• Active Directory Servers Details — shows information about the currently selected Active Directory. Exchange 2007 stores all configuration and recipient information in the Active Directory directory service database. All Exchange 2007 roles use Active Directory except the Edge role which does not have access to Active Directory. The Edge role uses ADAM to store schema and configuration information.

• DNS Servers — shows information about the DNS servers in use by this Exchange 2007 server. The Exchange 2007 server uses the DNS server that is configured in the IP properties of the network adapter to locate domain controllers and global catalog servers, other Exchange servers, and remote domains. DNS lookup settings can be specified on the Hub Transport server, which override the settings on the network adapter to route messages.


114

Transport In/Transport/Transport Out

The Transport drilldown presents connector/connection information about this Exchange 2007 server.

• Inbound Connections — shows the total number of inbound SMTP connections established by other SMTP hosts to this Exchange server

• Outbound Connections — shows the current number of outbound SMTP connections to other SMTP hosts

• Inbound Connectors — shows the number of SMTP Receive connectors on this Exchange 2007 server that are required to accept mail from other SMTP servers

• Outbound Connectors — shows the number of SMTP Send connectors on this Exchange 2007 server that are required to handle connections to other SMTP servers

• LDAP Search Time — shows LDAP Search Time (in ms) that is taken to send an LDAP search request and receive a response on this Exchange 2007 server

• Transport Queues — shows the number of messages in the transport queues on this Exchange 2007 server


CHARTS/TABS


115

Clients The Clients drilldown displays detailed information about current connections to the Exchange 2007 server being monitored.

• MAPI — indicates the number of MAPI connections to this Exchange 2007 server. The Mailbox role provides MAPI access to Microsoft Outlook clients.

• OWA — indicates the number of OWA connections to this Exchange 2007 server. The Client Access role provides OWA to allow a you to access to your mailbox information through a web browser.

• ActiveSync — shows the number of ActiveSync connections to this Exchange 2007 server. The Client Access role uses ActiveSync to allow mailbox access from mobile devices.

• POP3 — shows the number of POP3 connections to this Exchange 2007 server. The Client Access role provides POP3 access to mailbox data for clients that rely on this protocol.

• IMAP4 — shows the number of IMAP4 connections to this Exchange 2007 server. The Client Access role provides IMAP4 access to mailbox data for clients that rely on this protocol.


CHARTS/TABS


116

Information Store The Information Store drilldown displays performance graphs for key information store status metrics.

• Average Message Delivery Time — indicates the average time in seconds between the submission of a message to the mailbox store and the delivery to all local recipients (recipients on the same server) for the last 10 messages.

• Total Logons — indicates the number of clients (including system processes) currently logged to any storage group in the information store.

• Clients with RPC Latency > 2 sec – indicates the number of client reported RPCs (Remote Procedure Calls) with a latency greater than two seconds.

• Average Client RPC Latency — shows the average time (in milliseconds) that it takes the server to respond to RPC connected clients.

Storage Groups The Storage Groups drilldown displays information about the storage groups on this Exchange 2007 server. Exchange 2007 Standard Edition has a maximum limit of 5 storage groups. Exchange 2007 Enterprise Edition has a maximum limit of 50 storage groups. Each storage group can have a maximum of five mailbox databases, but best practice is to have one mailbox database per storage group.

• Storage Groups table — shows the status of each storage group, the name of each storage group, the percentage of unused disk space for each transaction logs on the server, whether LCR is enabled on each storage group, copy status of any database replicas, whether or not circular logging is enabled, and the system path of each storage group.

• Status — indicates the average time in seconds between the submission of a message to the mailbox store and the delivery to all local recipients (recipients on the same server) for the last ten messages, the number of clients (including system processes) currently logged to the selected Storage Group, and the number of incoming and outgoing messages.

• Mailbox Stores — indicates the percentage of space taken up by this mailbox store or public folder on the disk on which it resides.


CHARTS/TABS


117

Metrics


Exchange Services The Exchange Services drilldown displays a list that represents the status of the Exchange 2007 services, and a graph that shows the CPU and memory usage of a selected Exchange 2007 service.

• Exchange Services List — lists the Exchange services that are running on this Exchange 2007 server. Both required and optional services for the roles installed on this Exchange server are listed, along with their service status.

• Service Details — shows the CPU and memory usage of the currently selected Exchange 2007 service.

Subsystem The Subsystem drilldown displays components that represent the health of important subsystem features.

• CPU Usage — indicates the processor CPU usage on this Exchange 2007 server.

• System Memory — shows the amount of physical memory (RAM) Windows is using.

• System Disk — shows the amount of used and free space on the Windows system disk on this Exchange 2007 server.

• Ping Time — shows the ping time (in milliseconds) from the client (Spotlight on Exchange) to the Exchange 2007 server.

Processes The Processes drilldown displays a list of all the processes currently running on this Exchange 2007 server.

• Process Name — indicates the image name of the application itself.

• CPU Usage — indicates the percentage of CPU time that the program is currently consuming. This is an instantaneous result.

• Physical Memory — indicates the current size of the working set of the process.

• Virtual Memory — indicates current memory allocated to this process that cannot be shared with other processes.


CHARTS/TABS


118

Understanding the Exchange 2010 Diagnostic Console

The Exchange 2010 Diagnostic Console contains the following:

• Panels

• Message Flows

• Drilldowns

• Metrics

Panels

The Exchange 2010 Diagnostic Console contains the following panels:

• AD/DNS Panel

• Server Role Status Panel

• Transport In Panel

• Transport Panel

• Transport Out Panel

• Clients Panel

• Information Store Panel

• Subsystem Panel

AD/DNS Panel

The components of the Directory Services panel indicate how Exchange 2010

interacts with directory services. This information includes:


AD Shows the status of the Active Directory (AD)

servers used by this Exchange 2010 server

DNS Shows the status about the Domain Name System

(DNS) servers in use by this Exchange 2010

server


119

Server Role Status Panel

This panel shows the Exchange 2010 roles that are installed. This information

includes:


MBX Shows whether the Mailbox role is installed on

this Exchange 2010 server. The Mailbox role is

responsible for hosting mailbox and public folder

data. It also provides MAPI access for Outlook

clients.

UM Shows whether the Unified Messaging role is

installed on this Exchange 2010 server. The

Unified Messaging role enables you to access their

mailbox, address book, and calendar using

telephone and voice.

Note: The IP-PBX or VoIP gateway must be

installed to use the functionality of the Unified

Messaging role.

CAS Shows whether the Client Access role is installed

on this Exchange 2010 server. The Client Access

role provides mailbox server protocol access apart

from MAPI. It is similar to an Exchange 2003

Front-End server in that it allows you access to

their mailboxes using Outlook Web Access (OWA),

POP3/IMAP4, and ActiveSync.

EDG Shows whether the Edge Transport role is

installed on this Exchange 2010 server. The Edge

Transport role provides mail quarantine and SMTP

services to enhance security. It is the first hop of

incoming mail and the last hop of outgoing mail.

Note that it does not require AD access so that it

can function with limited access to the corporate

network (for added security).

HUB Shows whether the Hub Transport role is installed

on this Exchange 2007 server. The Hub Transport

role handles mail flow by routing messages to

either another Hub Transport server, an Edge

server, or a Mailbox server. This role is similar to

the bridgehead server in an Exchange 2000/2003

organization, except that it uses AD site info to

determine the mail flow.


120

Transport In Panel

The Transport In panel groups components that represent current inbound

connections to this Exchange 2010 server. This information includes:

Transport Panel

The Transport panel groups components that identify the status of the various

transport queues on this Exchange 2010 server. This information includes:


Connections Shows the total number of inbound SMTP

connections established by other SMTP hosts to

this Exchange server. The number of connections

represents the sum of all SMTP inbound

connections from all remote domains to SMTP

Receive Connectors on this Exchange 2010 server.

Connectors Shows the number of SMTP Receive connectors on

this Exchange 2010 server that can accept mail

from other SMTP servers.

Submission Queue Shows the number of items in the Submission

Queue. The submission queue holds messages

before they are consumed by the Categorizer

which determines what to do with the messages

based on information about the intended

recipients. After the submission queue, the

Categorizer then routes the message to either an

Edge Server role, another Hub server in a

different AD Site, a mailbox on an Exchange

2000/2003 server, or the Unreachable Queue.


Unreachable Queue Shows the number of messages in the transport

unreachable queue on this Exchange 2010 server.

The Unreachable Queue contains any messages

that cannot be routed to their final destination.

Poison Queue Shows the number of potentially harmful

messages on this Exchange 2010 server.

Messages that contain content that might be

damaging to the Exchange Server system are by

default delivered to this Poison Queue and

suspended. If messages in this queue are deemed

not harmful, message delivery can be resumed,

and the message enters the Submission Queue.


121

Transport Out Panel

The Transport Out panel groups components that represent current outbound

activity from the Exchange 2010 server. This information includes:

Mailbox Delivery Queue Represents the number of items in the Transport

Mailbox Delivery Queue on this Exchange server.

The mailbox delivery queue holds messages that

are being delivered to mailbox recipients whose

mailbox data is stored on a Mailbox server role

located in the same site as this Transport server.

The next hop for a message in this queue is the

distinguished name of the destination mailbox

store.

LDAP Search Time (ms) Shows LDAP Search Time (in milliseconds) for the

transport to send an LDAP search request to

Active Directory, and receive a response on this

Exchange 2010 server. Exchange 2010 uses

Active Directory (AD) as a repository for mailbox

and mail routing configuration data. Exchange

2010 servers issue LDAP queries against Active

Directory to retrieve message routing data.


Connections Shows the current number of outbound SMTP

connections to other SMTP hosts. The number of

connections represents the sum of all SMTP

outbound connections from SMTP Send

Connectors on this Exchange 2010 server to all

remote SMTP domains.

Connectors Shows the number of SMTP Send connectors on

this Exchange 2010 server that can service

connections to other SMTP servers.



122

Clients Panel

The Clients panel groups components that represent current client connections

and associated latency to this Exchange 2010 server. This information includes:

Remote Delivery Queue Shows the number of messages in the transport

that are queued for delivery to a remote server

using SMTP. The Exchange 2010 Hub and Edge

roles can have multiple remote delivery queues.

Each queue contains messages with recipients

that share the same remote server destination.

On a Hub role server, the destination servers are

within the same Exchange Organization as this

Exchange server, but in a different AD Site. For

the Edge role, the destination servers are external

to the Organization, and handle message delivery

for external SMTP domains.


MAPI Indicates the number of MAPI user connections to

this Exchange 2010 server. The Mailbox role

provides MAPI access for Microsoft Outlook

clients, and enables these types of connections.

OWA Indicates the number of current unique OWA

users logged on to this Exchange 2010 server. The

Client Access role provides OWA to allow you to

access his or her mailbox from a web browser and

have full access to all the information in the

mailbox including task lists, calendar information,

mail items, public folders, UNC shares

(\\servername\share) and SharePoint documents.

This value is decremented when a you log off your

OWA session or the session times out.

ActiveSync Shows the number of current secure HTTP

connections (HTTPS) that are established from

Windows Mobile-based or Exchange

ActiveSync-enabled mobile devices and this

Exchange 2010 server. ActiveSync is a push

orientated protocol. Data such as user messages,

schedules, contact information and tasks are

synchronized over the HTTPS connection.



123

Information Store Panel

The Information Store panel displays key operational metrics for the information

store on this Exchange 2010 server. This information includes:

POP3 Shows the number of POP3 connections to this


provides POP3 access to mailbox data for clients


IMAP4 Shows the number of IMAP4 connections to this


provides IMAP4 access to mailbox data for clients


Latency (ms) (for MAPI) Shows the average latency for MAPI clients

connected with Outlook to this Exchange 2010

server providing the Mailbox role.

Latency (ms) (for OWA) Shows the average latency for OWA clients on the


Latency (ms) (for ActiveSync) Shows the average latency for ActiveSync clients

on the Exchange 2010 server.

Latency (ms) (for POP3) Shows the average latency for POP3 clients on the


Latency (ms) (for IMAP4) Shows the average latency for IMAP4 clients on



Average message delivery

time(sec)

Indicates the average time in milliseconds

between the submission of a message to the

mailbox store and the delivery to all local

recipients (recipients on the same server) for the

last ten messages.

Clients with RPC (Remote

Procedure Calls) latency > 2 sec

Indicates the number of client reported Remote

Procedure Calls (RPCs) with a latency greater

than two seconds. The most commonly used RPC

protocol is MAPI, and a high RPC latency can

cause MAPI clients such as Microsoft Outlook to

hang and stop responding when users send email,

receive email, or use calendar functionality such

as creating or viewing appointments.



124

Average mailbox database size Indicates the average size of the mailbox

database.

Total Logons Indicates the total number of logons to the

information store on this Exchange 2010 server.

This includes end-user client connections and

system processes that are currently logged-on to

any storage group in the local information store.

There can be multiple logons per connection for

most client applications. As a result, it is possible

to see the number of client logons exceed the

number of mailboxes on a server.

Average client RPC latency (ms) Shows the average time (in milliseconds) that it

takes the server to respond to RPC connected

clients. The average is for the past 1024 packets.

The most commonly used RPC protocol is MAPI. A

high RPC latency can cause MAPI clients such as

Microsoft Outlook to hang and stop responding

when users send email, receive email, or use any

type of calendar functionality such as creating or

viewing appointments.

Mailbox Stores Shows the percentage of disk space consumed by

the mailbox stores on this server. This also shows

how much of the server disk consumption is

attributable to mailbox store consumption versus

other data.

Public Folders Shows the percentage of public store disk space

consumption on this server. This allows you to

assess how much of the server disk consumption

is attributable to public store data versus other

data.

Transaction Logs Shows the total percentage of disk space

consumed by the transaction logs on this server.

It can be used to quickly assess how much server

disk consumption is attributable to transaction log

data versus other data on the Exchange server.

Send Queue Shows the number of messages in the send queue

of the information store. This queue holds all

outgoing messages from the information store.

Receive Queue Shows the number of messages in the receive

queue of the information store. These messages

are waiting to be processed by the information

store.



125

Subsystem Panel

The Subsystem panel displays components that represent the health of

important subsystem features. This information includes:

DAG Name Shows the Database Accessibility Group (DAG)

name. DAG allows you to replicate your database

where your mail is stored across any number of

servers.

Store Memory Shows the total physical memory of the store

process.

Mailbox Count Shows the total number of mailboxes that reside

in all mailbox stores and public folders.


Exchange Services Indicates the sum of CPU utilization for all of the

Exchange 2010 services running on this server.

System Disk Shows the percentage of disk usage for the

Windows system disk on this Exchange 2010

server.

CPU Usage Shows the amount of CPU used on this Exchange

2010 server.

System Memory Shows the amount of physical memory (RAM)

Windows is using. Physical memory usage can

normally remain close to the total amount of

physical memory installed on the system unless

the amount of physical memory exceeds the

amount of virtual memory that Windows is using.

Windows normally keeps some physical memory

available for immediate use.

Ping Time Indicates the amount of time it takes the

computer running the Diagnostic Console to ping

the target server.

Top CPU Consumer Identifies the process that is consuming the most

CPU on this Exchange 2010 server.

Top Memory Consumer Identifies the process that is consuming the most

memory on this Exchange 2010 server.



126

Message Flows

The Exchange 2010 Diagnostic Console contains the following message flows

that show the amount of information being sent to various components in your

Exchange 2010 environment.


Msgs Submitted/sec Indicates the rate of messages being submitted per

second to this Exchange 2010 transport queues.

Msgs Received/sec Indicates the rate of messages received by SMTP

Receive connector on this Exchange 2010 server.

MAPI Msgs Submitted/sec Indicates the rate that messages are submitted to

the Information Store on the Exchange server by

MAPI clients (connected with Outlook).

OWA Msgs Received/sec Indicates the rate that bytes are received by

Exchange server from OWA clients.

ActiveSync Bytes

Received/sec

Indicates the rate that bytes are received by

Exchange this server from ActiveSync mobile

devices.

POP3/IMAP4 Bytes

Received/sec

Indicates the number of bytes per second received

from POP3 and IMAP4 clients.

Msgs Sent/sec Indicates the number of messages sent per second

to the transport.

Msgs Delivered/sec Indicates the rate of messages delivered to all

recipients with mailboxes on this Exchange 2010

server.

Bytes Received/sec Indicates the number of bytes received per second

from all RPC clients on this Exchange 2010 server


Exchange system components.

Bytes Sent/sec Indicates the number of bytes sent per second to all

RPC clients from this Exchange 2010 server


Exchange system component.

Bytes Read/sec Indicates the rate at which data is being read from



primarily being read from the disk subsystem.


127

Bytes Written/sec Indicates the rate at which data is being written to



primarily being written to the disk subsystem.

Msgs Queued/sec Indicates the number of messages queued for

delivery per second on this Exchange 2010 server.



128

Drilldowns





with components.



them.


save it to a file.



button.


129

To view a drilldown



CHARTS/TABS

AD/DNS Health The AD Servers drilldown displays information about the Active Directory and Active Directory servers currently in use by this Exchange 2010 server.

• Active Directory Servers — shows information about the Active Directory servers in use by this Exchange 2010 server. Exchange 2010 stores all configuration and recipient information in the Active Directory directory service database. All Exchange 2010 roles use Active Directory except the Edge role, which does not have access to Active Directory. The Edge role uses Active Directory Application Mode (ADAM) to store schema and configuration information.

• Active Directory Servers Details — shows information about the currently selected Active Directory. Exchange 2010 stores all configuration and recipient information in the Active Directory directory service database. All Exchange 2010 roles use Active Directory except the Edge role which does not have access to Active Directory. The Edge role uses ADAM to store schema and configuration information.

• DNS Servers — shows information about the DNS servers in use by this Exchange 2010 server. The Exchange 2010 server uses the DNS server that is configured in the IP properties of the network adapter to locate domain controllers and global catalog servers, other Exchange servers, and remote domains. DNS lookup settings can be specified on the Hub Transport server, which override the settings on the network adapter to route messages.


130

Transport In/Transport/Transport Out

The Transport drilldown presents connector/connection information about this Exchange 2010 server.

• Inbound Connections — shows the total number of inbound SMTP connections established by other SMTP hosts to this Exchange server

• Outbound Connections — shows the current number of outbound SMTP connections to other SMTP hosts

• Inbound Connectors — shows the number of SMTP Receive connectors on this Exchange 2010 server that are required to accept mail from other SMTP servers

• Outbound Connectors — shows the number of SMTP Send connectors on this Exchange 2010 server that are required to handle connections to other SMTP servers

• LDAP Search Time — shows LDAP Search Time (in ms) that is taken to send an LDAP search request and receive a response on this Exchange 2010 server

• Transport Queues — shows the number of messages in the transport queues on this Exchange 2010 server


CHARTS/TABS


131

Clients The Clients drilldown displays detailed information about current connections to the Exchange 2010 server being monitored.

• MAPI — indicates the number of MAPI connections to this Exchange 2010 server. The Mailbox role provides MAPI access to Microsoft Outlook clients.

• OWA — indicates the number of OWA connections to this Exchange 2010 server. The Client Access role provides OWA to allow a you to access to your mailbox information through a web browser.

• ActiveSync — shows the number of ActiveSync connections to this Exchange 2010 server. The Client Access role uses ActiveSync to allow mailbox access from mobile devices.

• POP3 — shows the number of POP3 connections to this Exchange 2010 server. The Client Access role provides POP3 access to mailbox data for clients that rely on this protocol.

• IMAP4 — shows the number of IMAP4 connections to this Exchange 2010 server. The Client Access role provides IMAP4 access to mailbox data for clients that rely on this protocol.


CHARTS/TABS


132

Information Store The Information Store drilldown displays performance graphs for key information store status metrics.

• Average Message Delivery Time — indicates the average time in seconds between the submission of a message to the mailbox store and the delivery to all local recipients (recipients on the same server) for the last 10 messages.

• Total Logons — indicates the number of clients (including system processes) currently logged to any storage group in the information store.

• Clients with RPC Latency > 2 sec – indicates the number of client reported RPCs (Remote Procedure Calls) with a latency greater than two seconds.

• Average Client RPC Latency — shows the average time (in milliseconds) that it takes the server to respond to RPC connected clients.


CHARTS/TABS


133

Exchange Mailbox Databases

The Exchange Mailbox Databases drilldown lists mailbox database information about the Exchange 2010 servers.

• Transaction Log Free Space — shows the amount of free space on the transaction log disk with the least amount of free space on the server. There should be enough free disk space to accommodate foreseeable future growth in the transaction logs. If circular logging is turned off on the transaction logs, there should be enough free space to accommodate at least 25% of the current transaction log size.

• Database Free Space — shows the amount of free space on the store disk with the least amount of free space on the server. There should be enough free disk space to accommodate foreseeable future growth in the mailbox store(s) and to defragment any store on this server.

• Database Mount Status — shows the mount status of the mailbox stores on the server. Mailboxes contained in unmounted mailbox stores cannot receive incoming messages.

• Exchange Mailbox Database List — shows information such as status, Database Name, Logons Currently Hosted, and Database Path for Exchange 2010 servers.

Exchange Services The Exchange Services drilldown displays a list that represents the status of the Exchange 2010 services, and a graph that shows the CPU and memory usage of a selected Exchange 2010 service.

• Exchange Services List — lists the Exchange services that are running on this Exchange 2010 server. Both required and optional services for the roles installed on this Exchange server are listed, along with their service status.

• Service Details — shows the CPU and memory usage of the currently selected Exchange 2010 service.


CHARTS/TABS


134

Metrics


Understanding the OCS Diagnostic Console

The OCS Diagnostic Console contain the following:

• Panels

• Message Flows

• Drilldowns

• Metrics

Subsystem The Subsystem drilldown displays components that represent the health of important subsystem features.

• CPU Usage — indicates the processor CPU usage on this Exchange 2010 server.

• System Memory — shows the amount of physical memory (RAM) Windows is using.

• System Disk — shows the amount of used and free space on the Windows system disk on this Exchange 2010 server.

• Ping Time — shows the ping time (in milliseconds) from the client (Spotlight on Exchange) to the Exchange 2010 server.

Processes The Processes drilldown displays a list of all the processes currently running on this Exchange 2010 server.

• Process Name — indicates the image name of the application itself.

• CPU Usage — indicates the percentage of CPU time that the program is currently consuming. This is an instantaneous result.

• Physical Memory — indicates the current size of the working set of the process.

• Virtual Memory — indicates current memory allocated to this process that cannot be shared with other processes.


CHARTS/TABS


135

Panels

The Diagnostic Console contains the following panels:

• Server Information Panel

• Clients/Network Panel

• Server Load Panel

• Server Roles Panel

• OS/Subsystem Panel

Server Information Panel

The Server Information panel, located below the toolbar, displays information

about the OCS 2007 or OCS 2007 R2 environment you are currently viewing.

This information includes:.


OCS Version Indicates the OCS version to which you are connected -

either OCS 2007 or OCS 2007 R2.

Server FQDN Indicates the Fully Qualified Domain Name of the server

being monitored.

Operating System Indicates the operating system running on the server

being monitored.

OCS Pool Indicates the name of the pool to which the server being

monitored belongs.

Back-End Database Indicates the server (and possible instance) hosting the

Back-End database for the pool.

Server Certificate (CRT)

Status Ball

Validates the identification of the remote server.

AS Status Ball Indicates if the Application Sharing (AS) server is present

and registered in the environment. Use the drilldown to

monitor the performance and requests of the AS Server.

Note: The AS Status Ball is active only if you are

connected to an OCS 2007 R2 server. If you are

connected to an OCS 2007 server, the AS Status Ball is

greyed out.

QMS Status Ball Indicates that there is a Quality of Monitoring Experience

(QMS) server configured in the environment. Use the

drilldown to see what server(s) is (are) hosting the role.


136

Clients/Network Panel

The Clients/Network panel displays information about the connections and

messages waiting to be sent from your OCS 2007 or OCS 2007 R2 environment.

This panel includes:

CDR Status Ball Indicates there is a Call Details Report (CDR) Server Role

configured in the environment. Use the drilldown to see

what server(s) is (are) hosting the role.

CWA Status Ball Indicates there is a Communicator Web Access (CWA)

Server Role configured in the environment. Use the

drilldown to see what server(s) is (are) hosting the role.


Secure Connections Indicates the number of active secure connections

(clients) that have been made to this server. Connections

are secured using Transport Layer Security (TLS).

Registered Endpoints Indicates the number of connected endpoints registered.

AD Search Latency (ms) Indicates the average latency related to queries (in ms)

sent to the Active Directory.

Outstanding RPC Calls Indicates the number of RPC calls waiting to be sent.

Network Output Queue Indicates the number of network packets waiting to be

sent.

Authentication Queue Indicates the number of authentication requests waiting

to be handled.

Theoretical Bandwidth Indicates the level of network traffic graphed against a

"theoretical" maximum bandwidth. The maximum

bandwidth is calculated by totaling the capacity of all

network devices reported by the operating system. If you

are running on an Ethernet network, the actual maximum

is approximately 50% of the theoretical bandwidth

because of the methods involved in sending data. Having

the actual bandwidth equal the theoretical bandwidth is

only possible using full duplex Ethernet. Token passing

network topologies, such as Token ring and FDDI, enable

a theoretical maximum bandwidth much closer to the

actual bandwidth.

Ping Time Indicates the amount of time it takes the computer

running the Diagnostic Console to ping the target server.



137

Server Load Panel

The Server Load panel displays information flow controlled connections, SIP and

C3P messages, and database. This panel includes:

Server Roles Panel

The Server Roles panel displays information about the amount of CPU being used

by your Front-End server and conferencing servers. This panel includes:


Flow Controlled

Connections

Indicates the number of connections currently operating

in a flow-controlled manner. When a connection is

flow-controlled, it can only have one outstanding

transaction.

Average Holding Time(s) Indicates the average time an incoming message waits

before being processed.

SIP Messages

Outstanding

Indicates the total number of SIP Messages currently

being processed by the server.

Message Processing

Time(s)

Indicates the average amount of time to process

incoming messages.

Conf. Allocation Latency

(ms)

Indicates the average time to allocate a new conference.

Outstanding C3P

Transactions

Indicates the number of outstanding C3P transactions

waiting to be processed.

Database Queue Latency

(ms)

Indicates the average amount of time a database request

waits in the processing queue for the database to

become available.

Database Sproc Latency

(ms)

Indicates the average amount of time to execute a stored

procedure (Sproc) on the Back-End database.


Front-End (RTCSrv) Indicates the amount of CPU usage from the OCS

Front-End service.

Front-End (RTCHost) Indicates the amount of CPU usage from the OCS

Front-End host process.

IM Conferencing Indicates the amount of CPU usage from the OCS IM

Conferencing server. It also indicates the number of

Allocated Conferences.


138

OS/Subsystem Panel

The OS/Subsystem panel displays information about the amount of CPU being

used by all processes. It also indicates the amount of System Memory and

System Disk being used, and reports on any errors. This panel includes:

PSTN Conferencing Indicates the amount of CPU usage from the OCS PSTN



Web Conferencing Indicates the amount of CPU usage from the OCS Web



A/V Conferencing Indicates the amount of CPU usage from the OCS A/V




CPU Usage Indicates the amount of CPU used by all processes.

Top CPU Consumer Indicates the top CPU consumer.

Top CPU Memory Indicates the top user of CPU memory.

System Memory Indicates the amount of system memory used by all

processes.

Processor Queue Indicates the number of threads waiting to execute.

System Disk Indicates the amount of system disk space being used.

Event Log Errors Indicates the number of OCS-related errors in the Event

Log.

Last AB Update Indicates the date stamp of the most recent file in the

Address Book share location.



139

Message Flows

The Diagnostic Console contains the following message flows that show the

amount of information being sent to various components in your OCS 2007 or

OCS 2007 R2 environment.

Drilldowns



of displays – tables and charts. Spotlight drilldowns have the following features:


with components.


Unavailable/Sec Indicates the amount of errors per second

SIP In/Sec Indicates the amount of incoming SIP

messages/second

SIP Out/Sec Indicates the amount of outgoing SIP

messages/second

Authentications/Sec Indicates the number of authentications created per

second

Authentication Errors/Sec Indicates the number of authentication errors per

second

Com Failures/Sec Indicates the number of communication failures per

second

Req Drop/Sec Indicates the number of requests dropped per

second

Resp Drop/Sec Indicates the number of responses dropped per

second

C3P Rec/Sec Indicates the number of C3P messages received per

second

C3P Sent/Sec Indicates the number of C3P messages sent per

second

Archiving/Sec Indicates the number of messages sent to the MSMQ

per second

User Replication Updates/Sec Indicates the number of user replicator updates

occurring per second


140



them.


save it to a file.



button.

To view a drilldown

• Right-click a component in a panel and select Show Details.


Clients/

Network

The Clients/Network

drilldown displays

detailed information

about each

component in your

Clients/Network

Panel and the

Authentications/Sec

and Authentication

Errors/Sec message

flows.

• Network — indicates the number of

packets waiting to be sent through the

network.

• TCP/IP — indicates the TCP segments,

UDP datagrams, IP Fragments, and IP

Datagrams that are transferred.

• NBT — indicates the computers that

have an active connection to the

system being diagnosed.

• Authentication — indicates how many

Authentications/sec and Authentication

Errors/sec are occurring.

• AD Search Latency — indicates the

average amount of time to perform an

LDAP search against the first Global

Catalog found in the domain.

• Outstanding RPC Calls — indicates the

number of RPC calls waiting to be sent

between Front-End servers.

• Connected Endpoints — allows you to

enter a search filter to limit the number

of endpoints returned.


141

Server Load The Server Load

drilldown displays


about each

component in your

Server Load Panel

and the following

message flows:

Unavailable/Sec, SIP

In/Sec, SIP Out/Sec,

Com Failures/Sec,

Req Dropped/Sec,

and Resp

Dropped/Sec.

• Flow Controlled — indicates the

number of flow controlled connections

per connections source, average

holding time of connections, how many

connections have been dropped, and

average delay of connections.

• SIP — indicates the number of

incoming and outgoing SIP messages,

messages outstanding, dropped, or

held, and memory usage of the SIP

Proxy.

• C3P — indicates the average time to

allocate a new conference and the

number of C3P transactions being

processed.

• Database — indicates the average

amount of time a database request or

database stored procedure waits

before it is sent to the database.

Server Roles The Server Roles

drilldown displays


about each

component in your

Server Roles Panel

and the C3P Rec/Sec

and C3P Sent/Sec

message flows.

• Roles — indicates the amount of CPU

usage per Front-End server, and

number of allocated conferences by

type.

• IM Conferences — indicates the

number of connected users, the

number of incoming and outgoing

messages, and overall health per IM

conference.

• Telephony (PSTN) Conferences —

handles the C3P messages that flow

between Focus and the ACP.

• Web Conferences — indicates the

number of participants, number of

slides, and number of errors in the Web

Conference.

• A/V Conferences — indicates the

number of users, number of

audio/video messages being sent and

received, the average time it takes to

process Audio packets, and the number

of buffers sent to users.



142

Metrics


OS/

Subsystem

The OS/Subsystem

drilldown displays


about each

component in your

OS/Subsystem Panel

and the

Archiving/Sec and

User Replicator

Updates/Sec

message flows.

• CPU — indicates the CPU usage by all

processes.

• Memory — indicates the amount of

memory used by all users.

• Top CPU/Memory Consumers —

indicates the top consumers of CPU

and memory.

• Logical Disk – indicates the number of

read and write requests, disk queue,

and transfer time.

• User Replicator/Address Book —

indicates the user replicator updates

and the contents of the Address Book

file share.

• Archiving — indicates various

characteristics of the Archiving server

such as CPU and memory usage,

database queue latencies, database

queue depth, and MSMQ messages.


Reporting Using Web Reports

• Understanding Web Reports

• Types of Reports

7


144

Understanding Web Reports

Web reports are a collection of reports that are accessible from the following

URL: http://<servername>/SpotlightonMessaging.

The reports provide administrators and CIOs with a tool to report on the usage

and trends of users. These reports help them make informed decisions about the

various methods of collaboration taking place in the environment.

You can perform the following using Web reports:

• Use subscriptions to generate specific reports on a regular schedule.

You can set up email notifications that either link to the reports or

include attachments that contain actual report data.

• Create custom reports using the Web Report Wizard. You can build

your own reports based on existing data sources. You can select

fields, filters, format, grouping, and sorting options. Custom reports

can be edited, depending on your security permissions within the Web

reports, and saved for future use.

• Browse reports using the Reports Console, Toolbar Buttons, File Menu

Commands, Treeview, Listview, Report Parts, Report Information,

and Report and Quick Filters.

• Use Tooltips for moving your pointing device over column headings or

over items in graphs to reveal detailed information.

Other tasks you can perform include:

• Group, insert, append, remove, and sort fields on reports. Quick

Filters allow you to change relevant report parameters quickly and

easily to better focus your report.

• Display report data in bar graphs, line graphs, and pie charts.

• Export reports in Microsoft Excel, text (as comma-separated values or

tab-separated values), XML, Word file, HTML, or MHTML

For more information on configuring Web Reports, see the Web Reports

Online Help.


145

Types of Reports

The Web Reports hosts two types of reports: Custom Reports and Preconfigured

Reports.

Custom Reports

You can create custom reports using the Web Report Wizard. The Web Report

Wizard allows you to build your own reports based on existing data sources. You

can select fields, filters, format, grouping, and sorting options. Custom reports

can be edited, depending on your security clearance within Quest Web Reports.

For more information about the Web Report Wizard, see the Web Reports Online

Help.

Preconfigured Reports

Preconfigured Reports are specific to the application, and are delivered with the

Quest Software product purchased.

The Spotlight on Messaging Diagnostic Pack for BlackBerry contains the

following Web Reports:

To get data for a Web Report, you must first create a test. The test you run

depends on the Web Report you want generated. For example, if you want to

generate the CPU Utilization report or the BlackBerry Any Counter report,

you must first run the BlackBerry Server Health test.

You cannot create a chart from a custom report. You can create a chart from

the Any Counter report.

WEB REPORT DESCRIPTION

BlackBerry Any Counter Allows you to report on any numeric counter

available for the selected server.

This report can be generated from data from the

BlackBerry Server Health test only.

BlackBerry CPU Utilization Displays the BlackBerry servers in your Exchange

organization and their respective CPU utilization.

BlackBerry Message Delivery Displays message delivery information between

Exchange and BlackBerry devices.


146

The Spotlight on Messaging Diagnostic Pack for Exchange contains the following

Web Reports:

BlackBerry Physical Memory

Utilization

Displays the BlackBerry servers in your Exchange

organization and their respective physical memory

utilizations.

BlackBerry SRP Status Displays connection status information between

BlackBerry servers and SRP servers.

BlackBerry System Disk

Utilization

Displays the BlackBerry servers in your BlackBerry

organization and their respective system disk

utilizations.


Exchange Any Counter Allows you to report on any numeric counter

available for the selected server.

This report can be generated from data from the

Exchange Server Health test only.

Exchange CPU Utilization Displays the servers in your Exchange

organization and their respective CPU utilization.

Exchange External Message

Delivery

Displays message delivery information between

Exchange and external email addresses.

Exchange Internal Message

Delivery

Displays message delivery information between

Exchange servers.

Exchange Physical Memory

Utilization

Displays the servers in your Exchange

organization and their respective physical memory

utilizations.

Exchange Queues Displays the servers in your Exchange

organization and their respective queues.

Exchange Storage Group Disk

Utilization

Displays the storage groups in your Exchange

organization and their respective disk utilizations.

Exchange System Disk

Utilization

Displays the servers in your Exchange

organization and their respective system disk

utilizations.



147

The Spotlight on Messaging Diagnostic Pack for OCS contains the following Web

Reports:


Server at a Glance Provides a summary of the specified Office

Communications Server configuration and the activity

occurring on that server.

CPU Utilization Displays the servers in your OCS organization and their

respective CPU utilization.

Critical Process Time Displays the servers in your OCS environment and their

respective critical process times.

Critical Process Working

Set

Displays the servers in your OCS environment and their

critical process working sets.

Physical Memory Utilization Displays the servers in your OCS organization and their

respective physical memory utilizations.

System Disk Utilization Displays the servers in your OCS environment and their

respective system disk utilizations.

Active Connections Displays the servers in your OCS environment and their

respective Active Connections.

TLS Active Connections Displays the servers in your OCS environment and their

respective TLS Active Connections.

Database Latency Displays the amount of time a request, such as a

stored procedure, spends in the database queue before

it is executed.

Database Physical Disk

Usage

Displays the servers in your OCS organization and their

physical disk usage.

Audio/Video Conferencing

Load

Shows how many Audio Video conferences are running

on the servers, and how many users are connected to

those conferences.

IM Conferencing Load Shows how many IM conferences are running on the

servers, and how many users are connected to those

conferences.

Telephony Conferencing

Load

Shows how many Telephony conferences are running

on the servers, and how many users are connected to

those conferences.

Web Conferencing Load Shows how many Web conferences are running on the

servers, and how many users are connected to those

conferences.


148

OCS Any Counter Allows you to report on any numeric counter available

for the selected server.

You can specify counter names available in the server on which you want to

report.

To report on a specific counter

1. Select File | New Custom Report, and click Next.

2. Select OCS Any Counter Daily or OCS Any Counter Hourly, and click

Next.

3. Move Counter Value and/or Counter Name to Selected Fields, and

click Next.

4. As filter criteria, select Counter Name and/or Counter Value, then

select a parameter, then select a counter name or value. Click Next.

5. If necessary, click Add New Filters to define additional filters. When

done, click Next.

6. Select how you would like to group the new reports, and click Next.

7. Select how you would like to sort the report, and click Next.

8. Configure how you would like to format your report, and click Next.

9. Add a description if desired, and click Next.

10.Click Finish.


Appendix A Counters with Non-Zero Alarm Values

Some counters are preconfigured to skip alarms the first, second, or third time

it occurs before sending you a notification message.

A


152

BlackBerry Configuration Server

BlackBerry Enterprise Server

Exchange 2000 Server Back-End

Exchange 2000 Server

COUNTER PRECONFIGURED VALUE

Physical Disk\Current Disk Queue Length 1

Processor\Processor Time 1



Memory\Available MBytes 1

Network Interface\Output Queue Length 1

Network Interface\Bytes Total 1


MSExchangeISMailbox\Send Queue Size 1

MSExchangeISMailbox\Receive Queue Size 1

MSExchangeISPublic\Send Queue Size 1

MSExchangeISPublic\Receive Queue Size 1

MSExchangeIS\RPC Operations/sec 1




Memory\Pages/sec 1


153

Exchange 2003 Server Back-End



MSExchangeISMailbox\Send Queue Size 1

MSExchangeISMailbox\Receive Queue Size 1

MSExchangeISPublic\Send Queue Size 1

MSExchangeISPublic\Receive Queue Size 1

MSExchangeIS\RPC Average Latency 1

MSExchangeIS\RPC Operations/sec 1


SMTP Server\Local Queue Length 2

SMTP Server\Remote Queue Length 2

Physical Disk\Avg.Disc sec\Read 1

Physical Disk\Avg.Disc sec\Write 1


Physical Disk\Current Disk Queue

Length(_Total)

2


Memory\Pages/sec 1

Memory\Pool Paged Bytes 2

Memory\Pool Nonpaged Bytes 2

MSExchangeDSAccess Processes\LDAP Read

Time

1

MSExchangeDSAccess Processes\LDAP Search

Time

1


154

Exchange 2007 Server Client Access

Exchange 2007 Server Edge Transport

Exchange 2007 Server Hub


MSExchangeOWA\Average Response Time 3


MSExchangeTransportQueues\Active Mailbox

Delivery Queue Length

1

MSExchangeTransportQueues\Active

Non-SMTP Delivery Queue Length

1

MSExchangeTransportQueues\Aggregate

Delivery Queue Length (All Queues)

1

MSExchangeTransportQueues\Largest


1

MSExchangeTransportQueues\Submission

Queue Length

1




1


Non-SMTP Delivery Queue Length

1


Delivery Queue Length (All Queues)

1



1


Queue Length

1


155


Exchange 2007 Server Mailbox

Exchange 2010 Server Client Access


PhysicalDisk\Avg. Disc sec/Read 1

PhysicalDisk\Avg. Disc sec/Write 1

PhysicalDisk\Current Disk Queue Length (<All

instances except _Total>)

1


Memory\Pool Pages Bytes 1

Memory\Pool Non-Paged Bytes 1

Network Interface\Bytes Total/sec 1


MSExchangeISClient\RPC Average Latency

(<All instances>)

1

MSExchangeISMailbox\Messages Queued for

Submission (_Total)

1

MSExchangeISMailbox\Receive Queue Size

(_Total)

1

MSExchangeISPublic\Messages Queued for

Submission (_Total)

1

MSExchangeISPublic\Receive Queue Size

(_Total)

1

MSExchangeIS\RPC Average Latency 1


MSExchangeOWA\Average Response Time 3


156

Exchange 2010 Server Edge Transport

Exchange 2010 Server Hub




Delivery Queue Length (<All instances>)

1


Non-SMTP Delivery Queue Length (<All

instances>)

1


Delivery Queue Length (All Queues) (<All

instances>)

1



1


Queue Length (<All instances>)

1




1


Non-SMTP Delivery Queue Length (<All

instances>)

1


Delivery Queue Length (All Queues) (<All

instances>)

1



1


Queue Length (<All instances>)

1


PhysicalDisk\Avg. Disc sec/Read (<All


1


157

Exchange 2010 Server Mailbox

PhysicalDisk\Avg. Disc sec/Write (<All


1

PhysicalDisk\Current Disk Queue Length (<All


1



Memory\Pool Non-Paged Bytes 1

Network Interface\Bytes Total/sec (<All


1


MSExchangeISClient\RPC Average Latency

(<All instances>)

1

MSExchangeISMailbox\Messages Queued for

Submission (_Total)

1

MSExchangeISMailbox\Receive Queue Size

(_Total)

1

MSExchangeISPublic\Messages Queued for

Submission (_Total)

1

MSExchangeISPublic\Receive Queue Size

(_Total)

1

MSExchangeIS\RPC Averaged Latency 1



158

OCS Server 2007 R2

OCS Archiving


Process\% Processor Time 1


Memory\Pages/sec 1

Memory\Pool Nonpaged Bytes 1



PhysicalDisk\% Idle Time 1

PhysicalDisk\Av.g Disk Read Queue Length 1

PhysicalDisk\Avg.Disk sec/Read 1

PhysicalDisk\Avg. Disk sec/Transfer 1

PhysicalDisk\Avg. Disk sec/Writer 1

PhysicalDisk\Avg. Disk Writer Queue Length 1

PhysicalDisk\Current Disk Queue Length (_Total) 1

PhysicalDisk\Current Disk Queue Length 1

System\Processor Queue Length 1


Process\% Processory Time (RTCARCH) 1

LC:Arch Service - 00 - DBArch\Arch Service - 002 - Queue Latency (msec)

1

LC:Arch Service - 00 - DBArch\Arch Service - 000 - Queue Depth

1

LC:Arch Service - 00 - DBArch\Arch Service - 004 - Sproc Latency (msec)

1


159

OCS Server 2007 R2 Archiving

OCS Conferencing Web

OCS Server 2007 R2 Conferencing Web

OCS Conferencing


Process\% Processory Time (RTCARCH) 1

LC:Arch Service - 00 - DBArch\Arch Service - 002 - Queue Latency (msec)

1

LC:Arch Service - 00 - DBArch\Arch Service - 000 - Queue Depth

1

LC:Arch Service - 00 - DBArch\Arch Service - 004 - Sproc Latency (msec)

1


Process\% Processory Time (DATAMCUSVC) 1

LC:DATAMCU - 01 - CCCP Processing\DATAMCU - 0259 - Average processing time of incoming CCCP messages

3


Process\% Processory Time (DATAMCUSVC) 1

AVMCU - 03 - CCCP Processing\AVMCU - 029 - Average Processing time of incoming CCCP messages

3


Process\% Processory Time (AVMCUSVC) 1


160

OCS Server 2007 R2 Conferencing Application Sharing

OCS Server 2007 R2 Conferencing Application Sharing

OCS Server 2007 R2 Conferencing AV

OCS Server 2007 R2 Conferencing IM

OCS CWA


AVMCU - 03 - CCCP Processing\AVMCU - 029 - Average processing time of incoming CCCP messages

1



3


Process\% Processory Time (AVMCUSVC) 1


3


Process\% Processory Time (IMMCUSVC) 1

LC:ImMcu - 01 - CCCP Processing\IMMCU - 029 - Average processing time of incoming CCCP messages

3


CWA - 01 - Authentication Module\CWA - 016 - Average latency for successful authorization (_Total)

1


161

OCS Database

OCS Server 2007 R2 Database

OCS Director

OCS Edge Access


Process\Page Faults/sec(SQLSERVER*) 1

Process\% Processor Time (SQLSERVER*) 1

Memory\Pages/sec 1


Process\Page Faults/sec(SQLSERVER*) 1

Process\% Processor Time (SQLSERVER*) 1

Memory\Pages/sec 1


PhysicalDisk\Avg. Disk sec/Read 1

PhysicalDisk\Avg. Disk sec/Write 1

PhysicalDisk\Current Disk Queue Length 1


Memory\Pages/sec 1


Memory\Pool Non-Pages Bytes 1



Process\% Processor Time(RTCSRV) 1

LC:SIP - 01 - Peers\SIP - 019 - Sends Timed-Out/sec(_Total)

1


162

LC:SIP - 01 - Peers\SIP - 020 - Average Outgoing Queue Delay(_Total)

1

LC:SIP - 02 - Protocol\SIP - 005 - Incoming Requests Dropped/sec:

1

LC:SIP - 02 - Protocol\SIP - 009 - Incoming Responses Dropped/sec

1

LC:SIP - 02 - Protocol\SIP - 021 - Average Incoming Message Processing Time

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 003 - External Messages/sec Received With Allowed Partner Server Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 005 - External Messages/sec Received With IM Service Provider Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 007 - External Messages/sec Received With a Configured Allowed Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 009 - External Messages/sec Received With a Discovered Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 021 - Messages/sec Dropped Due To Unknown Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 027 - External Messages/sec Dropped Due To Blocked Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 029 - Remote User Client Messages/sec Dropped Due To Unsupported Internal Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 049 - Messages/sec From Users Not Enabled For Federation

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 051 - Messages/sec From Users Not Enabled For Public IM Providers

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 053 - External Messages/sec Dropped Due To Unresolved Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 055 - External Messages/sec Dropped Due To Blocked IM Service Provider Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 057 - External Messages/sec Dropped Due To Unauthorized IM Service Provider Domain

1



163

OCS Server 2007 R2 Edge Access

OCS Edge AV

LC:SIP - 09 - Access Edge Server Messages\SIP - 059 - External Messages/sec Dropped Due To Unauthorized Allowed or Discovered Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 061 - External Messages/sec Dropped Due To Incompatible Message Domain

1

LC:SIP - 09 - Access Edge Server Messages\SIP - 063 - Messages/sec Dropped Due To Incompatible Asserted Identity

1


Process\% Processor Time(RTCSRV) 1

LC:SIP - 02 - Protocol\SIP - 005 - Incoming Requests Dropped/sec:

1

LC:SIP - 02 - Protocol\SIP - 009 - Incoming Responses Dropped/sec

1


Process\% Processor Time (MRASSVC) 1

Process\% Processor Time (MEDIARELAYSVC) 1

A/V Edge - 02 - Total Counters\-023 - Packets Dropped/sec (_Total)

1



164

165

Glossary

This glossary contains definitions taken from Microsoft publications.

AActive Directory

The Windows directory service.

CCustom Group

An arbitrary group of servers created to simplify test

management.

DDatabase Availability Group (DAG)

For Exchange 2010 servers only, a set of up to sixteen

Exchange mailbox servers.

Diagnostic ConsoleA console that allows you to monitor and troubleshoot one

server at a time.

DomainA logical collection of resources consisting of computers,

printers, and computer and user accounts. A domain also

has a system of logon authentication of computer and

user accounts.

Domain Controller (DC)A server that authenticates domain logon passwords. It

maintains security policy and the security accounts master

database for a domain.

FFederation

Allows users to provide presence information with external

clients.

ForestA collection of domains and domain trees.


166

GGlobal Filter

Allows you to hide any servers in which you are not

interested. It hides the servers from both the treeview and

topology view.

HHealth Test

Detects problems by collecting and analyzing data or

simulating user interaction with the server at regular

intervals

MMaintenance Mode

Allows you to mark servers as offline so that you can

perform maintenance on those servers

Management ConsoleA console that unifies and simplifies day-to-day system

management tasks. It hosts tools and displays them as

consoles. These tools, consisting of one or more

applications, are built with modules called snap-ins.

OOffice Communications Server (OCS)

A Microsoft application that brings together email, instant

messaging, video, and voice.

WWeb Reports

A tool that provides administrators with a tool to report on

usage and trends.

167

INDEX

A

Active Connections report 148Active Directory Users and

Computers 61AD Servers drilldown 113, 129AD/DNS Panel 103AD/DNS Panel_Ex2010 118adding notification groups 44adding recipients 44advanced functionsmanaging global filters 23managing missing objects 25putting servers in maintenance

mode 24Advanced Queuing panel 81, 107, 122alternate credentialsconfiguring 49

Any Counter report 147Audio/Video Conferencing Load

report 148

B

Best Practices home page 96BlackBerry Any Counter report 146BlackBerry Diagnostic Console 69drilldowns 75message flows 74metrics 77panels 69

BlackBerry Manager 60BlackBerry Message Delivery Health

Test 30BlackBerry Server Configuration 60browsing test result history 57browsing the Management

Console 12

C

Categorizer panel 89clearing test results 58Clients Panel 107, 122Clients panel 94, 107, 122cloning a test 55common home page elements 79Computer Management 60, 61configuring alternate credentials 49configuring settings 42configuring the execution

schedule 43configuring the notification

settings 43connecting to a platform 13connecting to Diagnostic Services 16Connections panel 94connector linksrouting group 20site 20

counterscustomizing 50

counters with non-zero alarm values to skip 151

CPU Utilization report 146, 147, 148creating dynamic custom groups 22creating static custom groups 21Critical Process Time report 148Critical Process Working Set

report 148custom groupsdeleting 22dynamic 22editing 22managing 21static 21


168

Custom reports 146customizing counters 50CWA Administration Console 61

D

DAG 25, 125data collection options 53database availability group (DAG) 25,

125Database Latency report 148database settingsmanaging 49

DC Servers panel 94deleting a test 55deleting custom groups 22detecting problems with the

Management Console 27device delivery 31diagnosing problems using the

Diagnostic Console 65diagnosing problems using the

Management Console 63Diagnostic Console 9BlackBerry 69diagnosing problems 65drilldowns 139Exchange 2000/2003 78Exchange 2007 103Exchange 2010 118launching 64launching and connecting to 67message flows 139metrics 142OCS 134panels 135understanding 68

Diagnostic Servicesconnecting to 16

Directory Services home page 93Directory Services panel 103, 118Directory Services status panel 103,

118disabling a test 55disconnecting from a platform 15discovery 14DNS panel 94drilldowns 75, 83, 91, 93, 96, 101, 112,

128, 139DS Access Cache panel 94dynamic custom groupscreating 22

E

editing a test 54editing custom groups 22enabling a test 55enabling data collection options 53event log filtering 52Event Viewer 60, 61Exchange 2000/2003 Diagnostic

Console 78drilldowns 83, 91, 93, 96, 101message flows 81, 90, 93, 95metrics 102panels 81, 89, 92, 94, 97

Exchange 2007 Diagnostic Console 103

drilldowns 112, 128message flows 111, 126metrics 117, 134panels 103, 118

Exchange 2010 Diagnostic Console 118

Exchange External Message Delivery Health Test 32

Exchange Internal Message Delivery Health Test 31

Exchange Mailbox Databases drilldown 133

Exchange Management Console 61Exchange Outlook Web Access

Availability Health Test 37Exchange Queue Health Test 36Exchange Replication Health Test 39Exchange Storage Health Test 33Exchange System Manager 61execution scheduleconfiguring 43

exporting topology layout 17External Message report 147

F

federated partners 18filteringevent logs 52

G

getting started using the Management Console 11

global filtersmanaging 23

global settingsdatabase settings 49

169

Group Chat Administration Console 61

grouping servers by type 23

H

Health Tests 28BlackBerry Message Delivery 30Exchange External Message

Delivery 32Exchange Internal Message

Delivery 31Exchange Outlook Web Access

Availability 37Exchange Queue 36Exchange Replication 39Exchange Storage 33Server Health 41

hiding successful results 57Home PageDiagnostic Console 66Management Console 10viewing 10

home pageBest Practices 96Directory Services 93IIS 89Main 80

I

IISHealth panel 90home page 89

IIS home page 89IM Conferencing Load report 148importing topology layout 17Inbound Connections 114, 130Inbound Connectors 114, 130Inbound panel 81, 89, 105Information Storepanel 81, 92, 106, 121

Information Store drilldown 116, 132Information Store Panel 108, 123Information Store panel 108, 123Internal Message report 147introducing the Spotlight on

Messaging 7

L

launching and connecting to the Diagnostic Console 67

launching Native Tools 60launching the Diagnostic Console 64LDAP Search Time 114, 130

M

Main home page 80maintenance modeservers 24

Management Console 8browsing 12detecting problems 27diagnosing problems 63getting started 11opening 12resolving problems 59

managing custom groups 21managing database settings 49managing global filters 23managing tests 41Message Delivery report 146message flows 74, 81, 90, 93, 95, 111,

126, 139metrics 77, 102, 117, 134, 142missing objects 25

N

Native ToolsActive Directory Users and

Computers 61BlackBerry Manager 60BlackBerry Server Configuration 60Computer Management 60, 61CWA Administration Console 61Event Viewer 60, 61Exchange Management Console 61Exchange System Manager 61Group Chat Administration

Console 61launching 60OCS Administrator Console 61Services 60, 61


170

notification groupsadding 44adding recipients 44

notification settingsconfiguring 43

O

OCS Administrator Console 61OCS Any Counter report 149OCS Diagnostic Console 134OCS environmentfederated partners 18pool properties 20server properties 18

opening the Management Console 12OS Subsystem Panel 74Outbound Connections 114, 130Outbound Connectors 114, 130Outbound panel 108, 123

P

panelAdvanced Queuing 81, 107, 122Categorizer 89Clients 94Connections 94DC Servers 94DNS 94DS Access Cache 94IIS Health 90Inbound 81, 89, 105Information Store 81, 92, 106, 121Outbound 108, 123Queues 81, 105, 120Routing 90SMTP 90Storage Groups 92

panels 69, 81, 89, 92, 94, 97, 103, 118, 135

passing external application using SNMP 48

Physical Disk Usage report 148Physical Memory report 147, 148platformconnecting to 13disconnecting from 15removing 15

pool properties 20Preconfigured reports 146Active Connections 148Any Counter 147

Audio/Video Conferencing Load 148

BlackBerry Any Counter 146CPU Utilization 146, 147, 148Critical Process Time 148Critical Process Working Set 148Database Latency 148External Message 147IM Conferencing Load 148Internal Message 147Message Delivery 146OCS Any Counter 149Physical Disk Usage 148Physical Memory 147, 148Queues 147Server at a Glance report 148SRP Status 147Storage Group Disk Utilization 147System Disk 148System Disk Utilization 147Telephony Conferencing Load 148TLS Active Connections 148Web Conferencing Load 148

purging test result history 49purging the results of a test 49

Q

Queuespanel 81, 105, 120

Queues report 147

R

receiving messages on cleared alarms 46

receiving unlimited messages 47removing a platform 15report types 146custom 146preconfigured 146

resolving problems using the Management Console 59

reverse DNS lookup 54round trip delivery 31Routingpanel 90

171

routing group connector links 20running a test now 55

S

Server and platform status 104Server at a Glance report 148Server Health Panel 70Server Health Test 41Server Panel 71server properties 18Server Role Status Panel 104, 119servers in maintenance mode 24Services 60, 61setting the maximum number of

notification messages per alarm 47

settingsconfiguring 42

site connector links 20skipping alarms before sending

notifications 42SMTP panel 90SNMPpassing external applications 48

Spotlight on Messagingintroducing 7

SRP Panel 70SRP Status report 147static custom groupscreating 21

Storage Group Disk Utilization report 147

Storage Groupspanel 92

Storage Groups drilldown 116Storage Groups home page 91Subsystem Panel 110, 125successful resultshiding 57

System Disk report 148System Disk Utilization report 147System Panel 71

T

Telephony Conferencing Load report 148

test results historyviewing 57

test status 49, 56, 57testsbrowsing test result history 57clear results 58

cloning 55deleting 55disabling 55editing 54enabling 55managing 41purging test result history 49running now 55viewing more details on results 57viewing results 56

TLS Active Connections report 148topology layoutimporting and exporting 17

Transport drilldown 114, 130Transport In Panel 105, 120Transport In panel 105Transport Out Panel 106, 121Transport Out panel 106, 121Transport Panel 105, 120Transport panel 105, 120Transport Queues 114, 130types of reports 146custom 146preconfigured 146

U

understanding the Diagnostic Console 68

understanding Web Reports 144Users Panel 73

V

viewing more details about the results of a test 57

viewing test results history 57viewing the Home Page 10viewing the results of a testcolored icons 56, 57

W

Web Conferencing Load report 148Web Reports 9, 143understanding 144

WMI 53


172

173

About Quest Software

Now more than ever, organizations need to work smart and improve efficiency.

Quest Software creates and supports smart systems management

products—helping our customers solve everyday IT challenges faster and easier.

Visit www.quest.com for more information.

Contacting Quest Software

Refer to our Web site for regional and international office information.

Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest

product or who have purchased a commercial version and have a valid

maintenance contract. Quest Support provides around the clock coverage with

SupportLink, our web self-service. Visit SupportLink at

http://support.quest.com/.

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase

articles/documents).

• Download patches and upgrades.

• Seek help from a Support engineer.

• Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs,

online services, contact information, and policy and procedures. The guide is

available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

Email [email protected]

Mail Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656

USA

Web site www.quest.com

http://www.quest.com

http://support.quest.com/

http://support.quest.com/

http://support.quest.com/pdfs/Global Support Guide.pdf

mailto:[email protected]

http://www.quest.com


174

Spotlight on Messaging User Guide

Documents

quest spotlight

quest software logo

blackberry diagnostic

ocs diagnostic console

server health test

exchange queue health

exchange replication

software license