User guide

NetIQ

®

AppManager

®

for

Microsoft Exchange Server 2007,

2010, and 2013

Management Guide

September 2015

www.netiq.com/documentation

Legal Notice

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE

SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS

EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ

CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS"

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT

ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS

STATEMENT MAY NOT APPLY TO YOU.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S.

Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-

4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government’s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

© 2015 NetIQ Corporation. All Rights Reserved.

For information about NetIQ trademarks, see https://www.netiq.com/company/legal/ .

Contents

About this Book and the Library

About NetIQ Corporation

1 Introducing AppManager for Exchange Server

9

1.1

Understanding Microsoft Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2

How AppManager Can Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5

7

2 Installing and Configuring AppManager for Exchange Server

13

2.1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2

Installing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3

Deploying the Module with Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4

Silently Installing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5

Permissions for Discovering Exchange Server Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.6

Discovering Exchange Server Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.7

Configuring and Monitoring Database Availability Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8

Configuring and Monitoring Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.9

Upgrading Knowledge Script Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.10

Configuring the PowerShell Execution Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.11

Changing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.12

Troubleshooting PowerShell Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3 Reporting with Analysis Center

33

3.1

System Requirements for Analysis Center Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2

Installing the Report Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.3

Exchange Server 2007 or later Analysis Center Report Templates . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Exchange 2007 Knowledge Scripts

37

4.1

All_BestPracticesAnalyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.2

All_ClockSynchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.3

All_EventLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.4

All_ServiceStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.5

CAS_Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.6

CAS_Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.7

CAS_OABAvailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.8

CAS_PublicFolderAvailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.9

ETS_ExternalMail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.10

ETS_MessageHygiene . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4.11

HTS_Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4.12

HTS_SafetyNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.13

HTS_SendersAndRecipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.14

HTS_TransportDumpster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.15

MBS_ClientActivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

4.16

MBS_ClientConnectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4.17

MBS_ClusterOwner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Contents

3

4.18

MBS_DatabaseStateChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.19

MBS_DatabaseStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.20

MBS_MailboxAccessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.21

MBS_MailboxUsage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4.22

MBS_MailFlow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.23

MBS_MessagingRecordsMgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4.24

MBS_PublicFolderUsage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

4.25

MBS_Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4.26

Transport_BackPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4.27

Transport_ConnectorStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

4.28

Transport_QueueStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4.29

UMS_CallActivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4.30

UMS_Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

4.31

UMS_Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

4.32

UMS_Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

4.33

Recommended Knowledge Script Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

4

NetIQ AppManager for Microsoft Exchange Server Management Guide

About this Book and the Library

The NetIQ AppManager product (AppManager) is a comprehensive solution for managing, diagnosing, and analyzing performance, availability, and health for a broad spectrum of operating environments, applications, services, and server hardware.

AppManager provides system administrators with a central, easy-to-use console to view critical server and application resources across the enterprise. With AppManager, administrative staff can monitor computer and application resources, check for potential problems, initiate responsive actions, automate routine tasks, and gather performance data for real-time and historical reporting and analysis.

Intended Audience

This guide provides information for individuals responsible for installing an AppManager module and monitoring specific applications with AppManager.

Other Information in the Library

The library provides the following information resources:

Installation Guide for AppManager

Provides complete information about AppManager pre-installation requirements and step-bystep installation procedures for all AppManager components.

User Guide for AppManager Control Center

Provides complete information about managing groups of computers, including running jobs, responding to events, creating reports, and working with Control Center. A separate guide is available for the AppManager Operator Console.

Administrator Guide for AppManager

Provides information about maintaining an AppManager management site, managing security, using scripts to handle AppManager tasks, and leveraging advanced configuration options.

Upgrade and Migration Guide for AppManager

Provides complete information about how to upgrade from a previous version of AppManager.

Management guides

Provide information about installing and monitoring specific applications with AppManager.

Help

Provides context-sensitive information and step-by-step guidance for common tasks, as well as definitions for each field on each window.

The AppManager library is available in Adobe Acrobat (PDF) format from the AppManager

Documentation page of the NetIQ Web site.

About this Book and the Library

5

6

NetIQ AppManager for Microsoft Exchange Server Management Guide

About NetIQ Corporation

We are a global, enterprise software company, with a focus on the three persistent challenges in your environment: Change, complexity and risk—and how we can help you control them.

Our Viewpoint

Adapting to change and managing complexity and risk are nothing new

In fact, of all the challenges you face, these are perhaps the most prominent variables that deny you the control you need to securely measure, monitor, and manage your physical, virtual, and cloud computing environments.

Enabling critical business services, better and faster

We believe that providing as much control as possible to IT organizations is the only way to enable timelier and cost effective delivery of services. Persistent pressures like change and complexity will only continue to increase as organizations continue to change and the technologies needed to manage them become inherently more complex.

Our Philosophy

Selling intelligent solutions, not just software

In order to provide reliable control, we first make sure we understand the real-world scenarios in which IT organizations like yours operate — day in and day out. That's the only way we can develop practical, intelligent IT solutions that successfully yield proven, measurable results. And that's so much more rewarding than simply selling software.

Driving your success is our passion

We place your success at the heart of how we do business. From product inception to deployment, we understand that you need IT solutions that work well and integrate seamlessly with your existing investments; you need ongoing support and training post-deployment; and you need someone that is truly easy to work with — for a change. Ultimately, when you succeed, we all succeed.

Our Solutions

 Identity & Access Governance

 Access Management

 Security Management

 Systems & Application Management

 Workload Management

 Service Management

About NetIQ Corporation

7

Contacting Sales Support

For questions about products, pricing, and capabilities, contact your local partner. If you cannot contact your partner, contact our Sales Support team.

Worldwide:

United States and Canada:

Email:

Web Site:

www.netiq.com/about_netiq/officelocations.asp

1-888-323-6768 [email protected]

www.netiq.com

Contacting Technical Support

For specific product issues, contact our Technical Support team.

Worldwide:

North and South America:

Europe, Middle East, and Africa:

Email:

Web Site:

www.netiq.com/support/contactinfo.asp

1-713-418-5555

+353 (0) 91-782 677 [email protected]

www.netiq.com/support

Contacting Documentation Support

Our goal is to provide documentation that meets your needs. The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at www.netiq.com/ documentation . You can also email [email protected]

. We value your input and look forward to hearing from you.

Contacting the Online User Community

NetIQ Communities, the NetIQ online community, is a collaborative network connecting you to your peers and NetIQ experts. By providing more immediate information, useful links to helpful resources, and access to NetIQ experts, NetIQ Communities helps ensure you are mastering the knowledge you need to realize the full potential of IT investments upon which you rely. For more information, visit http://community.netiq.com

.

8

NetIQ AppManager for Microsoft Exchange Server Management Guide

1

Introducing AppManager for Exchange

Server

AppManager for Exchange Server 2007, 2010, and 2013 (AppManager for Exchange Server) lets you monitor the operation, performance, and availability of Microsoft Exchange Server 2007, 2010, and 2013.

1.1

Understanding Microsoft Exchange Server

Previous versions of Microsoft Exchange employed traditional communication methods whereby email, voice mail, and fax traffic not only traveled different paths through communication networks

(frequently requiring separate sites and servers), but were accessible only by different tools such as telephones, computers, and fax machines.

With Exchange Server, users receive e-mail, voice mail, fax messages, and calendar data directly into one inbox, and can access the inbox from a variety of applications, such as Microsoft Office

Outlook, Outlook Web Access, mobile devices, or the telephone. This unified messaging system simplifies the user experience and reduces the number of servers required to provide e-mail, voice mail, and fax services.

Server roles provide flexibility in deploying Exchange Server. There are five server roles in Exchange

Server 2007 and 2010 and two server roles in Exchange Server 2013. With the exception of the Edge

Transport server role, which must be deployed on a server in the perimeter network, all other roles can run on one server or multiple servers, depending on the needs and size of your organization.

Hub Transport server role moves messages between the other server roles and applies compliance policies to messages while they are in transit.

Client Access server role enables users to access their inbox from Outlook Web Access,

POP3, IMAP 4, Outlook Anywhere, and Exchange Server ActiveSync.

Edge Transport server role provides antivirus and anti-spam protection for your Exchange organization.

Mailbox server role holds users’ mailbox databases, which contain e-mail, calendar, contact, task, voice mail, and fax data.

Unified Messaging server role lets users receive voice mail, e-mail, fax messages, and calendar data in their Exchange inboxes. It also enables voice access to the inbox from any telephone, and hosts any speech-enabled Automated Attendant that your organization may employ.

NOTE: Exchange Server 2013 has only two server roles: Client Access and Mailbox. The Mailbox role includes all the traditional server components found in Exchange 2007/2010: the Client Access protocols, Transport service, Mailbox databases, and Unified Messaging. The Client Access role provides authentication, limited redirection, and proxy services. AppManager for Exchange server will discover the Hub Transport and Unified messaging roles under Mailbox role for Exchange 2013.

Introducing AppManager for Exchange Server

9

1.2

How AppManager Can Help

AppManager for Exchange Server monitors Exchange Server 2007, 2010, and 2013 resources installed in both clustered and non-clustered environments, as well as DAG environments. The module supports the following environments:

Cluster continuous replication (CCR) combines the replication and replay features in

Exchange Server 2007 with the failover features of Microsoft Cluster services. CCR is a solution that can be deployed with no single point of failure in a single data center or between two data centers.

Single copy clusters (SCC), known as shared storage clusters in previous versions of

Exchange Server, are present in Exchange Server 2007. They are not present in Exchange

Server 2010 and 2013.

Local continuous replication (LCR) is a single-server solution that uses creates and maintains a copy of a storage group on a second set of disks that are connected to the same server as the production storage group. LCR provides asynchronous log shipping, log replay, and a quick manual switch to a copy of the data.

Database availability group (DAG) is a set of up to 16 Microsoft Exchange Server 2010 or

2013 Mailbox servers that provides automatic database-level recovery from a database, server, or network failure. DAG replaces CCR, SCC, and LCR on Exchange 2010 and 2013 servers. For more information, see

Section 2.7, “Configuring and Monitoring Database Availability Groups,” on page 20

.

The Exchange2007 Knowledge Scripts raise events in the AppManager Operator Console or Control

Center. The scripts collect information about server roles that you can use for trend analysis and reporting.

With AppManager for Exchange Server, you can monitor the following:

 The Windows Event Log for warnings and errors whose source is either the Best Practices

Analyzer or Exchange services

 Running status of all Exchange Server 2007, 2010, and 2013 services

 Clock synchronization

 Response time for ActiveSync, Outlook Web Access, Outlook Web services, and the

Autodiscovery service

 Number of messages in queue and change in queue size

 Status of send, receive, foreign, and delivery agent connectors

 Speed of mail flow to a specified e-mail address or Mailbox server

 Availability of offline address books and public folders

 Accessibility of mailbox database

 Communication between Hub Transport server and Mailbox server

 Synchronization between Hub Transport server and Edge Transport server

 Response to SMTP requests

 Replication health

 Mailbox database status

 Available disk space

 Cluster ownership

10

NetIQ AppManager for Microsoft Exchange Server Management Guide

 Message management: deleting, journaling, moving

 Performance for the Unified Messaging server, including user response latency, operation response time, queued messages, queued OCS user notifications, and disconnected calls, and access to the Mailbox server, Hub Transport server, and Active Directory

Introducing AppManager for Exchange Server

11

12

NetIQ AppManager for Microsoft Exchange Server Management Guide

2

Installing and Configuring AppManager for Exchange Server

This chapter provides installation instructions and describes system requirements for AppManager for

Exchange Server.

This chapter assumes you have AppManager installed. For more information about installing

AppManager or about AppManager system requirements, see the Installation Guide for AppManager, which is available on the AppManager Documentation page.

2.1

System Requirements

For the latest information about supported software versions and the availability of module updates, visit the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AppManager for Exchange Server has the following system requirements:

Item Requirement

NetIQ AppManager installed on the

AppManager repository (QDB) computers, on the Exchange computers you want to monitor (AppManager agents), and on all console computers

7.0.1 or later

Support for Windows Server 2008 on AppManager 7.x requires

AppManager Windows Agent hotfix 71704 or later

Hotfix 72040 or later for the AppManager repository (QDB) is required

Hotfix 71647 or later for Control Center is required

For more information, see the AppManager Suite Hotfixes Web page.

Microsoft Windows operating system installed on agent computers

AppManager for Microsoft Windows module installed on the repository, agent, and console computers

One of the following:

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2

Windows Server 2008 (64-bit)

Windows Server 2003 R2 (64-bit)

Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page.

Installing and Configuring AppManager for Exchange Server

13

Item Requirement

Microsoft Exchange Server installed on the agent computers

One of the following:

Microsoft Exchange Server 2013

Microsoft Exchange Server 2010

Microsoft Exchange Server 2007

Microsoft Exchange Server Role installed on the agent computers

At least one of the following Exchange Server roles installed:

Client Access Role

Edge Transport Role

Hub Transport Role

Mailbox Role

Unified Messaging Role

Microsoft .NET Framework installed on the agent computers

3.0 and 3.5

Windows PowerShell Engine 2.0 - for Exchange Server 2007 and 2010

3.0 - for Exchange Server 2013

2.2

Installing the Module

Run the module installer on the Exchange servers you want to monitor (agents) to install the agent components, and run the module installer on all console computers to install the Help and console extensions.

Access the AM70-Exchange2007-7.x.x.0.msi module installer from the AM70-Exchange2007-

7.x.x.0

self-extracting installation package on the AppManager Module Upgrades & Trials page.

If you are upgrading from the previous version of this module, version 7.4, you need to perform

additional steps to install version 7.5 correctly. For more information, see Section 2.2.2, “Upgrading from Version 7.4 of the Module,” on page 16

.

For Windows environments where User Account Control (UAC) is enabled, install the module using an account with administrative privileges. Use one of the following methods:

 Log in to the server using the account named Administrator. Then, run the module installer .msi file from a command prompt or by double-clicking it.

 Log in to the server as a user with administrative privileges and run the module installer .msi file as an administrator from a command prompt. To open a command-prompt window at the administrative level, right-click a command-prompt icon or a Windows menu item and select Run

as administrator.

You can install the Knowledge Scripts and the Analysis Center reports into local or remote

AppManager repositories (QDBs). The module installer installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager.

14

NetIQ AppManager for Microsoft Exchange Server Management Guide

2.2.1

Manually Installing the Module

You can install the module manually, or you can use Control Center to deploy the module on a remote

computer where an agent is installed. For more information, see Section 2.3, “Deploying the Module with Control Center,” on page 16 . However, if you use Control Center to deploy the module, Control

Center only installs the agent components of the module. The module installer installs the QDB and console components as well as the agent components on the agent computer.

To install the module manually:

1

Double-click the module installer .msi file.

2

Accept the license agreement.

3

Review the results of the pre-installation check. You can expect one of the following three scenarios:

No AppManager agent is present: In this scenario, the pre-installation check fails, and the installer does not install agent components.

An AppManager agent is present, but some other prerequisite fails: In this scenario, the default is to not install agent components because of one or more missing prerequisites.

However, you can override the default by selecting Install agent component locally. A missing application server for this particular module often causes this scenario. For example, installing the AppManager for Microsoft SharePoint module requires the presence of a Microsoft SharePoint server on the selected computer.

All prerequisites are met: In this scenario, the installer installs the agent components.

4

To install the Knowledge Scripts into the QDB and to install the Analysis Center reports into the

Analysis Center Configuration Database:

4a

Select Install Knowledge Scripts to install the repository components.

4b

Select Install report package to install the Analysis Center reports.

4c

Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive

QDB name.

4d

Specify the SQL Server name of the server hosting the Analysis Center Configuration

Database.

5

(Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to

Control Center.

6

(Conditional) If you use Control Center 8.x, run the module installer only for the primary QDB, and Control Center automatically replicates this module to secondary QDBs.

7

Run the module installer on all console computers to install the Help and console extensions.

8

Run the module installer on the Exchange computers you want to monitor (agents) to install the agent components.

9

Configure the PowerShell Execution policy, and, if necessary, establish a trust relationship between NetIQ Corporation and the user accounts that will run the Exchange2007 category of

Knowledge Scripts. For more information, see

Section 2.10, “Configuring the PowerShell

Execution Policy,” on page 26 .

10

Ensure proper permissions and memberships are set before discovering Exchange Server 2007,

2010, and 2013 resources. For more information, see Section 2.5, “Permissions for Discovering

Exchange Server Resources,” on page 18

.

Installing and Configuring AppManager for Exchange Server

15

11

(Conditional) If you have not discovered Exchange resources, run the Discovery_Exchange2007

Knowledge Script on all agent computers where you installed the module. For more information, see

Section 2.6, “Discovering Exchange Server Resources,” on page 19 .

12

To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see

Section 2.9, “Upgrading Knowledge Script Jobs,” on page 24 .

After the installation has completed, the Exchange2007_Install.log and

PowerShellHost_Install.log files, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred.

2.2.2

Upgrading from Version 7.4 of the Module

If you are upgrading from the previous release, version 7.4, to this version, 7.5, install version 7.5 on each Exchange Server agent, AppManager repository (QDB), and console

AppManager for Microsoft Exchange 7.5 version 7.5 uses PowerShell scripts throughout the module, so you must set the PowerShell execution policy. For more information, see

Section 2.10,

“Configuring the PowerShell Execution Policy,” on page 26 .

To upgrade from version 7.4 to version 7.5:

1

Stop the version 7.4 ad hoc jobs and remove all Exchange Server monitoring policies.

2

Install version 7.5 of the module on all AppManager repositories (QDBs), consoles, and agents.

For more information about running the installer, see

Section 2.2, “Installing the Module,” on page 14

.

3

The module installer automatically runs the Discovery Knowledge Script. If it does not, manually run Discovery_Exchange2007. For more information about the Discovery Knowledge Script, see

Section 2.6, “Discovering Exchange Server Resources,” on page 19

.

4

Recreate the ad hoc jobs and create new Exchange Server monitoring policies.

2.3

Deploying the Module with Control Center

You can use Control Center to deploy the module on a remote computer where an agent is installed.

This topic briefly describes the steps involved in deploying a module and provides instructions for checking in the module installation package. For more information, see the Control Center User

Guide for AppManager, which is available on the AppManager Documentation page.

2.3.1

Deployment Overview

This section describes the tasks required to deploy the module on an agent computer.

To deploy the module on an agent computer:

1

Verify the default deployment credentials.

2

Check in an installation package. For more information, see Section 2.3.2, “Checking In the

Installation Package,” on page 17 .

3

Configure an email address to receive notification of a deployment.

4

Create a deployment rule or modify an out-of-the-box deployment rule.

5

Approve the deployment task.

6

View the results.

16

NetIQ AppManager for Microsoft Exchange Server Management Guide

2.3.2

Checking In the Installation Package

You must check in the installation package, AM70-Exchange2007-7.x.x.0.xml, before you can deploy the module on an agent computer.

To check in a module installation package:

1

Log on to Control Center using an account that is a member of a user group with deployment permissions.

2

Navigate to the Deployment tab (for AppManager 8.x) or Administration tab (for AppManager

7.x).

3

In the Deployment folder, select Packages.

4

On the Tasks pane, click Check in Deployment Packages (for AppManager 8.x) or Check in

Packages (for AppManager 7.x).

5

Navigate to the folder where you saved AM70-Exchange2007-7.x.x.0.xml and select the file.

6

Click Open. The Deployment Package Check in Status dialog box displays the status of the package check in.

7

To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see

Section 2.9, “Upgrading Knowledge Script Jobs,” on page 24 .

2.4

Silently Installing the Module

To silently (without user intervention) install a module using the default settings, run the following command from the folder in which you saved the module installer: msiexec.exe /i "AM70-Exchange2007-7.x.x.0.msi" /qn where x.x is the actual version number of the module installer.

To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see

Section 2.9, “Upgrading Knowledge Script Jobs,” on page 24

.

To create a log file that describes the operations of the module installer, add the following flag to the command noted above:

/L* "AM70-Exchange2007-7.x.x.0.msi.log"

The log file is created in the folder in which you saved the module installer.

NOTE: To perform a silent install on an AppManager agent running Windows 2008 R2, open a command prompt at the administrative level and select Run as administrator before you run the silent install command listed above.

To silently install the module on a remote AppManager repository, you can use Windows authentication or SQL authentication.

Windows authentication:

AM70-Exchange2007-7.x.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_MOINSTALL=0

MO_B_SQLSVR_WINAUTH=1 MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName

Installing and Configuring AppManager for Exchange Server

17

SQL authentication:

AM70-Exchange2007-7.x.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_MOINSTALL=0

MO_B_SQLSVR_WINAUTH=0 MO_SQLSVR_USER=SQLLogin MO_SQLSVR_PWD=SQLLoginPassword

MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName

2.5

Permissions for Discovering Exchange Server

Resources

Before discovering and monitoring Exchange Server resources, ensure that the user account running the AppManager agent service (netiqmc) has the following memberships and permissions:

 Membership in the Exchange View-Only Administrators group (for Exchange Server 2007)

 Membership in View-Only Organization Management group (for Exchange Server 2010/2013)

 Membership in the Local Administrators group on the Exchange Server

 Permission to access the File Share Witness folder

In addition to the minimum permissions required for any role, following are the specific Exchange

Server roles that require additional permissions:

Component

Client Access Server role

Edge Transport Server role

Hub Transport Server role

Mailbox Server role

Unified Messaging

Server role

Required Permissions and

Memberships for Exchange Server

2007

Membership in the Exchange Server

Administrators group

Membership in the Exchange Server

Administrators group

Membership in the Exchange

Organization Administrators group

Membership in the

Builtin\Administrators

group on the Active Directory server

Membership in the Exchange Server

Administrators group

Membership in the Exchange

Recipient Administrators group

Membership in the Exchange Server

Administrators group, for support for the

UMS_Connectivity

Knowledge

Script

Required Permissions and

Memberships for Exchange Server

2010/2013

Membership in Server Management group

Membership in the Organization

Management group

Membership in Server Management group

Membership in the Organization

Management Group

Membership in the

Builtin\Administrators

group on the Active Directory server

Membership in Server Management group

Membership in Recipient

Management group

Membership in the Organization

Management group

Membership in Server Management group, for support for the

UMS_Connectivity

Knowledge

Script

18

NetIQ AppManager for Microsoft Exchange Server Management Guide

Component

Exchange Best

Practices Analyzer tool

(for all Exchange

Server roles)

Directory Server

Required Permissions and

Memberships for Exchange Server

2007

Designation as the Domain

Administrator, or membership in the

Builtin\Administrators

group on the Active Directory server, for enumerating the Active Directory information and calling the Microsoft

Windows Management

Instrumentation (WMI) providers on the domain controller and global catalog servers.

Membership in the Local

Administrators group on each

Exchange server for calling the WMI providers and accessing the registry and the metabase

Delegation for at least Exchange

View-Only Permissions on the

Exchange organization

Membership in the Local

Administrators group on the local computer

Delegation for at least Exchange

View-Only Permissions

Required Permissions and

Memberships for Exchange Server

2010/2013

Designation as the Domain

Administrator, or membership in the

Builtin\Administrators

group on the Active Directory server, for enumerating the Active Directory information and calling the Microsoft

Windows Management

Instrumentation (WMI) providers on the domain controller and global catalog servers

Membership in the Local

Administrators group on each

Exchange server for calling the WMI providers and accessing the registry and the metabase

Delegation for at least View-Only

Organization Management

Permissions on the Exchange organization

Delegation for at least Exchange

View-Only Permissions

2.6

Discovering Exchange Server Resources

Use the Discovery_Exchange2007 Knowledge Script to discover configuration and resources for

Microsoft Exchange Server 2007, 2010, and 2013 in both clustered and non-clustered environments.

Before using this Knowledge Script, set up the proper accounts and permissions. For more information, see

Section 2.5, “Permissions for Discovering Exchange Server Resources,” on page 18 .

NOTE: If you delete a resource object or add a resource object, such as a Mailbox or Public Folder database in your Exchange Server, you will need to run the Discovery_Exchange2007 Knowledge

Script again to update the remaining objects. This behavior occurs on DAG and standalone Mailbox roles.

Run this script on an NT_MachineFolder object, or an NT_VIR_MachineFolder object. By default, this script runs once.

Set the Values tab parameters as needed:

Parameter

General Settings

Job failure event notification

How to Set It

Installing and Configuring AppManager for Exchange Server

19

Parameter How to Set It

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the Discovery_Exchange2007 job fails. The default is 5.

Discovery

Event Notification

Raise event if discovery succeeds?

Select Yes to raise an event if discovery succeeds. The default is No.

Event severity when discovery succeeds

Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery succeeds. The default is 25.

Raise event if discovery fails? Select Yes to raise an event if discovery fails. The default is Yes.

Event severity when discovery fails

Raise event if discovery partially succeeds?

Event severity when discovery partially succeeds

Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery fails. The default is 5.

Select Yes to raise an event if discovery returns some data but also generates warning messages. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery returns some data but also generates warning messages.

The default is 10.

2.7

Configuring and Monitoring Database Availability

Groups

A database availability group (DAG) is a set of up to 16 Microsoft Exchange Server 2010 or 2013

Mailbox servers that provides automatic database-level recovery from a database, server, or network failure. Mailbox servers in a DAG monitor each other for failures. When you add a Mailbox server to a

DAG, that Mailbox server works with the other servers in the DAG to provide automatic, databaselevel recovery from database, server, and network failures.

2.7.1

New Functionality in Exchange Server 2010 and 2013

In Microsoft Exchange Server 2010 and 2013, DAG functionality replaces the following clustering functionality used with Microsoft Exchange Server 2007: cluster continuous replication (CCR), single copy cluster (SCC), and Local Continuous Replication (LCR). Exchange Server 2010 and 2013 do not use storage groups.

2.7.2

Adding a DAG for Monitoring

Add the computers that represent the individual computers of a DAG to the Master Management

Group of an AppManager repository in Control Center. When you have added all DAG computers, create a server group, for example, EX2K_DAG_1, and add each DAG computer to that group.

For more information about adding computers to the Master Management Group of a repository and creating server groups, see the Control Center User Guide for AppManager.

20

NetIQ AppManager for Microsoft Exchange Server Management Guide

2.7.3

Discovering Resources on a DAG

Use the Discovery_ExchangeDAG Knowledge Script to discover configuration and resources for a

Microsoft Exchange Server 2010 and 2013 Database Availability Group (DAG). Run

Discovery_ExchangeDAG on an Exchange Server 2010 and 2013 server to discover the virtual object for DAG. After you discover the virtual object, you must run Discovery_Exchange2007 on the

newly discovered object so you can discover the databases. For more information, see Section 2.6,

“Discovering Exchange Server Resources,” on page 19

.

Before using the Discovery_ExchangeDAG Knowledge Script, set up the proper accounts and

permissions. For more information, see Section 2.5, “Permissions for Discovering Exchange Server

Resources,” on page 18 .

To discover resources in an Exchange Server 2010 and 2013 DAG, run the following Discovery

Knowledge Scripts in the order listed:

Knowledge Script Resources Discovered

Discovery_NT Run this script on each physical server that is a member of the DAG to discover

Windows configuration and resources.

Discovery_Exchange2007 Run this script on each physical server that is a member of the DAG to discover

Exchange Server 2010 and 2013 databases.

Discovery_ExchangeDAG Run this script on any one of the physical servers that is a member of the DAG to discover Exchange Server 2010 and 2013 DAG virtual objects. Running this script creates a new top-level object that represents the DAG in the TreeView of the

Operator Center console.

Discovery_Exchange2007 Run this script on the new top-level DAG node discovered in the previous step to discover the mailbox database resources in the DAG (which is the set of all mailbox databases managed by all servers in the DAG).

Set the Values tab parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the Discovery_ExchangeDAG job fails. The default is 5.

Discovery

Event Notification

Raise event if DAG discovery succeeds?

Select Yes to raise an event if DAG discovery succeeds. The default is No.

Event severity when DAG discovery succeeds

Set the severity level, from 1 to 40, to indicate the importance of an event in which DAG discovery succeeds. The default is 25.

Raise event if DAG discovery fails?

Select Yes to raise an event if discovery fails. The default is Yes.

Event severity when DAG discovery fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery fails. The default is 5.

Installing and Configuring AppManager for Exchange Server

21

NOTE: If you previously ran the Discovery_Cluster Knowledge Script on nodes that now belong to a

DAG, the Discovery_Cluster script discovered the Windows Cluster resource object,

NT_CLU_MachineFolder. If you later run Discovery_ExchangeDAG on any node that belongs to the

DAG, the script will not discover any new objects, because an object with same name was added using Discovery_Cluster KS. As a result, you will not be able to use Discovery_Exchange2007 KS to discover the databases on the DAG object, because Discovery_Exchange2007 does not work with the NT_CLU_MachineFolder resource object.

To address this situation, remove the Windows Cluster object that was discovered with the

Discovery_Cluster Knowledge Script and use the Discovery_ExchangeDAG to discover the DAG object.

2.7.4

Monitoring Resources on a DAG

The following Mailbox server Knowledge Scripts can monitor DAGs in Exchange Server 2010 and

2013:

MBS_DatabaseStateChange

MBS_DatabaseStatus

MBS_MailboxUsage

MBS_PublicFolderUsage (only for Exchange2013)

2.8

Configuring and Monitoring Clusters

Cluster groups are features of Windows Server 2003 and Windows Server 2008. You can install

Exchange Server 2007 on the nodes of a cluster group and have the advantages of clustering available to your messaging environment. Exchange 2010 and 2013 do not support cluster groups.

Cluster continuous replication (CCR) configurations support active/passive mode.

AppManager for Exchange Server supports up to eight physical nodes for single copy cluster (SCC)

configurations. For more information, see Section 2.8.3, “Monitoring Resources on Cluster Nodes,” on page 23 .

NOTE: If you have clusters set up on Exchange Server 2007 and you upgrade to Exchange Server

2010 or 2013, you must manually delete the Exchange2007 objects from the Navigation pane or

TreeView in AppManager and run discovery again after you upgrade to Exchange Server 2010 or

2013.

2.8.1

Adding an Exchange Server Cluster to the Master View

Add the computers that represent the individual nodes of a cluster to the master view of an

AppManager repository in Control Center. Then group the nodes by cluster.

For example, if EX2KSVR_1 and EX2KSVR_2 are the two nodes of an Exchange Server 2007 cluster, add each computer to the master view.

When you have added all node computers, create a server group, for example, EX2K_CLUSTER_1, and add each node computer to that group.

For more information about adding computers to the master view of a repository and creating server groups, see the Control Center User Guide for AppManager.

22

NetIQ AppManager for Microsoft Exchange Server Management Guide

2.8.2

Discovering Resources on Cluster Nodes

To discover resources in an Exchange Server 2007 cluster, run the following Discovery Knowledge

Scripts in the order listed:

Knowledge Script Resources Discovered

Discovery_NT

Discovery_MSCS

Windows configuration and resources, such as memory, physical and logical disks, and CPU.

Microsoft Cluster Service configuration and resources, such as cluster services and nodes in a cluster.

NOTE: The MSCS module is not mandatory to monitor the Exchange server cluster. It is only used if you want to monitor additional services for Microsoft

Cluster configuration and resources, such as cluster services and nodes in a cluster.

Discovery_Cluster Clustered Mailbox Server (CMS) objects.

Discovery_Exchange2007 Exchange Server 2007, 2010, and 2013 configuration and resources, such as services, server view, and protocols.

When you discover Exchange resources, AppManager for Exchange Server lists each CMS that a computer can own as a child object of that computer, regardless of whether the CMS is active at the time of discovery.

2.8.3

Monitoring Resources on Cluster Nodes

Use cluster-aware Knowledge Scripts on both physical and virtual server to monitor resources on

each node in a cluster and on each CMS as it moves from node to node as a result of failover. The

All_* Knowledge Scripts and the Knowledge Scripts that run on a Mailbox server can monitor

Windows cluster resources. Microsoft supports clustering only on the Mailbox server role.

All_BestPracticesAnalyzer

All_ClockSynchronization

All_EventLog

All_ServiceStatus

MBS_DatabaseStateChange

MBS_DatabaseStatus

MBS_MailboxAccessibility

MBS_MailboxUsage

MBS_MailFlow

MBS_MessagingRecordsMgmt

MBS_PublicFolderUsage

MBS_Replication

You can run the MBS_* Knowledge Scripts on physical and virtual nodes.

Installing and Configuring AppManager for Exchange Server

23

2.8.4

Collecting Data for Clustered Mailbox Servers

When you monitor a CMS, AppManager for Exchange Server associates the collected data with the physical node.

 A Knowledge Script job running on a CMS collects data for that CMS and for the associated physical node.

 A Knowledge Script job running on a physical node collects data for any CMS associated with that physical node.

Example 1: SCC cluster with Active/Active configuration

If CMS1 is active on EX2KSVR_1 and CMS2 is active on EX2KSVR_2, the job creates two datastreams when you run the job on CMS1:

 Datastream for CMS1

 Datastream for EX2KSVR_1

When you run a job on EX2KSVR_1, the job collects data for CMS1. If CMS2 fails over to EX2KSVR_1 and you run a job on EX2KSVR_1, the job creates two datastreams:

 Datastream for CMS1

 Datastream for CMS2

Example 2: CCR cluster with Active/Passive configuration

If CMS1 is active on EX2KSVR_1, the job creates two datastreams when you run the job on CMS1:

 Datastream for CMS1

 Datastream for EX2KSVR_1

If CMS1 fails over to EX2KSVR_2, and you run a job on EX2KSVR_2 the job creates two datastreams:

 Data stream for CMS1

 Datastream for EX2KSVR_2

2.9

Upgrading Knowledge Script Jobs

If you are using AppManager 8.x or later, the module upgrade process now retains any changes you may have made to the parameter settings for the Knowledge Scripts in the previous version of this module. Before AppManager 8.x, the module upgrade process overwrote any settings you may have made, changing the settings back to the module defaults.

As a result, if this module includes any changes to the default values for any Knowledge Script parameter, the module upgrade process ignores those changes and retains all parameter values that you updated. Unless you review the management guide or the online Help for that Knowledge Script, you will not know about any changes to default parameter values that came with this release.

This release of AppManager for Exchange Server might contain updated Knowledge Scripts. You can push the changes for updated scripts to running Knowledge Script jobs in one of the following ways:

 Use the AMAdmin_UpgradeJobs Knowledge Script.

 Use the Properties Propagation feature.

24

NetIQ AppManager for Microsoft Exchange Server Management Guide

2.9.1

Running AMAdmin_UpgradeJobs

The AMAdmin_UpgradeJobs Knowledge Script can push changes to running Knowledge Script jobs.

Your AppManager repository (QDB) must be at version 7.0 or later. Upgrading jobs to use the most recent script version allows the jobs to take advantage of the latest script logic while maintaining existing parameter values for the job.

For more information, see the Help for the AMAdmin_UpgradeJobs Knowledge Script.

2.9.2

Propagating Knowledge Script Changes

You can propagate script changes to jobs that are running and to Knowledge Script Groups, including recommended Knowledge Script Groups and renamed Knowledge Scripts.

Before propagating script changes, verify that the script parameters are set to your specifications.

New parameters may need to be set appropriately for your environment or application.

If you are not using AppManager 8.x or later, customized script parameters may have reverted to default parameters during the installation of the module.

You can choose to propagate only properties (specified in the Schedule and Values tabs), only the script (which is the logic of the Knowledge Script), or both. Unless you know specifically that changes affect only the script logic, you should propagate both properties and the script.

For more information about propagating Knowledge Script changes, see the “Running Monitoring

Jobs” chapter of the Operator Console User Guide for AppManager.

2.9.3

Propagating Changes to Ad Hoc Jobs or Knowledge Script

Groups

You can propagate the properties and the logic (script) of a Knowledge Script to ad hoc jobs started by that Knowledge Script. Corresponding jobs are stopped and restarted with the Knowledge Script changes.

You can also propagate the properties and logic of a Knowledge Script to corresponding Knowledge

Script Group members. After you propagate script changes to Knowledge Script Group members, you can propagate the updated Knowledge Script Group members to associated running jobs. Any monitoring jobs started by a Knowledge Script Group member are restarted with the job properties of the Knowledge Script Group member.

To propagate changes to ad hoc Knowledge Script jobs or Knowledge Script Groups:

1

In the Knowledge Script view, select the Knowledge Script or Knowledge Script Group for which you want to propagate changes.

2

Right-click the script or group and select Properties propagation > Ad Hoc Jobs.

Installing and Configuring AppManager for Exchange Server

25

3

Select the components of the Knowledge Script that you want to propagate to associated ad hoc jobs or groups and click OK:

Select

Script

Properties

To propagate

The logic of the Knowledge Script.

Values from the Knowledge Script Schedule and Values tabs, such as schedule, monitoring values, actions, and advanced options. If you are using AppManager

8.x or later, the module upgrade process now retains any changes you might have made to the parameter settings for the Knowledge Scripts in the previous version of this module.

2.10

Configuring the PowerShell Execution Policy

This chapter describes the procedure for configuring the Microsoft PowerShell Execution Policy. The

PowerShell Execution Policy determines whether PowerShell scripts are allowed to run.

2.10.1

Understanding PowerShell Cmdlets

Microsoft Exchange Server 2007, 2010, and 2013 use the Microsoft scripting and command environment known as PowerShell. PowerShell is made up of hundreds of executable objects called

cmdlets, pronounced command-lets. In addition to the base cmdlets provided by PowerShell, installation of the Exchange Management Console adds approximately 300 Exchange Server 2007,

2010, or 2013 cmdlets.

When running the Exchange2007 category of Knowledge Scripts, AppManager makes a series of calls to PowerShell and the Exchange Server 2007, 2010, or 2013 cmdlets. The combination of cmdlets depends on the version of Exchange Server. AppManager executes the cmdlets to manipulate Exchange Server 2007, 2010, or 2013 objects such as Outlook Web Access, virtual directories, mailboxes, distribution groups, and storage groups (2007 only).

For more information about using Powershell, see your Microsoft PowerShell documentation.

2.10.2

Configuring the PowerShell Execution Policy

The PowerShell Execution Policy determines whether PowerShell scripts are allowed to run. By default, the Execution Policy is set to Restricted. If you try to run scripts under the Restricted policy, AppManager generates error messages.

The Execution Policy directly affects the Exchange2007 Knowledge Scripts. Although the scripts that ship with AppManager for Exchange Server is written in VBScript and installed as

<scriptname>.qml, the logic for the scripts is contained in complementary PowerShell scripts that are installed on the agent computer along with the module. The PowerShell scripts use the same name as the Exchange2007 Knowledge Scripts, but with a .ps1 extension.

26

NetIQ AppManager for Microsoft Exchange Server Management Guide

NOTE: The digital signature encoded in an Exchange2007 Knowledge Script is tied to the contents of the script. If you change the script, the signature is no longer valid and you cannot execute the script.

If you change an Exchange2007 Knowledge Script, you must do one of the following:

 Re-sign the scripts using your own digital certificate.

 Change the Execution Policy to either RemoteSigned or Unrestricted.

A group policy that governs script execution overrides any policy changes you make with the

Set-ExecutionPolicy

cmdlet. For example, if the group policy forbids script execution, you cannot change the policy by running Set-ExecutionPolicy. First change the group policy to allow script execution, and then run Set-ExecutionPolicy to select a specific Execution Policy.

Before AppManager can execute the PowerShell scripts, you must change the Execution Policy from

Restricted

to one of the following policy options:

AllSigned, which allows execution of scripts that have been digitally signed by a trusted publisher. If you select the AllSigned policy, perform the steps outlined in

Section 2.10.3,

“Trusting Exchange 2007, 2010, and 2013 PowerShell Scripts,” on page 27 .

RemoteSigned, which allows local scripts to run regardless of signature, and requires trusted digital signatures only for remote scripts. Exchange2007 Knowledge Scripts are local scripts.

Unrestricted, which allows both local and remote scripts to run, regardless of signature.

To change the PowerShell Execution Policy:

1

Open the Exchange Command Shell on the agent computer.

2

Run the following cmdlet:

Set-ExecutionPolicy <policy> where <policy> is the name of the Execution Policy you choose.

3

Repeat Steps 1 and 2 on all agent computers, including Server role computers.

2.10.3

Trusting Exchange 2007, 2010, and 2013 PowerShell Scripts

When a PowerShell script is executed under an AllSigned policy, PowerShell verifies that the script contains a digital signature and that the signature is associated with a trusted publisher. NetIQ

Corporation signs the Exchange 2007, 2010, and 2013 PowerShell scripts. If you use the AllSigned policy, you must choose to trust NetIQ Corporation by importing the NetIQ Corporation digital certificate into the local certificate store on each Exchange Server in your environment.

You can import the digital certificate by running one of the Exchange2007 PowerShell scripts from the command line.

To import the digital certificate:

1

Open the Exchange Command Shell on the agent computer.

2

Change to the AppManager\bin\PowerShell\Scripts directory.

3

Type .\Exchange2007_All_EventLog.ps1

4

Press Enter.

5

Type A at the prompt asking whether the script should be allowed to run.

6

Press Enter.

These steps allow the NetIQ Corporation digital certificate to be imported into the certificate store for the user running the script. Run any script once to establish trust.

Installing and Configuring AppManager for Exchange Server

27

At this point, trust is established only between NetIQ Corporation and the user running the script.

Trust is not established for any other user. If the AppManager agent runs under a different user account such as Local System, a domain account, or a local computer account, the agent will not have a trust relationship and will not be allowed to execute the Exchange 2007, 2010, or 2013

PowerShell scripts.

To extend trust to all other user accounts, see

Section 2.10.4, “Extending Trust to All User Accounts,” on page 28 .

To establish trust between all users accounts and the Microsoft digital certificate, see Section 2.10.5,

“Establishing Trust for the Microsoft Certificate,” on page 29 .

2.10.4

Extending Trust to All User Accounts

To execute PowerShell scripts under the AllSigned Execution Policy, extend trust to all user accounts. Extending trust is a two-phase process that involves exporting the digital certificate from the current user and importing the digital certificate to all users on the local computer.

Exporting the NetIQ Corporation Digital Signature Certificate

To extend trust to all user accounts, first export the NetIQ Corporation digital signature certificate from the current user using the Microsoft Management Console.

To export the NetIQ Corporation digital signature certificate from the current user:

1

On the Start menu, click Run.

2

In the Open field, type mmc.exe, and then click OK.

3

On the File menu in the Microsoft Management Console window, click Add/Remove Snap-in.

4

Click Add and then select the Certificates snap-in.

5

Click Add, select My user account, and then click Finish.

6

Click Close and then click OK. The Certificates-Current User node is displayed in the tree view of the Console window.

7

Expand Certificates - Current User.

8

Expand Trusted Publishers and select Certificates.

9

In the right pane, right-click the NetIQ certificate, select All Tasks, and then select Export.

10

Click Next in the Certificate Export Wizard.

11

Select DER encoded binary and then click Next.

12

Click Browse, select the Desktop icon, type NetIQ in the File name field, and then click Save.

13

Click Next, and then click Finish.

Importing the NetIQ Corporation Digital Signature

The next phase of extending trust to all user accounts involves importing the NetIQ Corporation digital signature to all users on the local computer. Use the Microsoft Management Console to execute the import procedure.

To import the NetIQ Corporation digital certificate to all users on the local computer:

1

On the File menu in the Microsoft Management Console window, click Add/Remove Snap-in.

2

Click Add and then select the Certificates snap-in.

28

NetIQ AppManager for Microsoft Exchange Server Management Guide

3

Click Add, select Computer account, and then click Next.

4

Select Local computer and then click Finish.

5

Click Close and then click OK.

6

Expand Certificates (Local Computer) and select Trusted Publishers.

7

Right-click in the right pane, select All Tasks, and then select Import.

8

Click Next in the Certificate Import Wizard.

9

Click Browse, click the Desktop icon, select NetIQ.cer, and then click Open.

10

Click Next in the Wizard.

11

Select Place all certificates in the following store.

12

Click Browse and then select Show physical stores.

13

Expand Trusted Publishers and select Local Computer.

14

Click OK.

15

Click Next in the Certificate Import Wizard, and then click Finish.

After you complete both the phases of the trust process, the NetIQ Corporation certificate is contained in the certificate store for the local computer, allowing all users to execute the PowerShell scripts.

2.10.5

Establishing Trust for the Microsoft Certificate

The Exchange2007 Knowledge Scripts access a file called Exchange.Format.ps1xml, which

Microsoft ships with Exchange Server 2007, 2010, and 2013. For the Exchange2007 Knowledge

Scripts to run properly, the Microsoft digital signature certificate must have a trust relationship with the

Microsoft digital signature certificate.

To create this trust relationship, perform the steps outlined in

Section 2.10.4, “Extending Trust to All

User Accounts,” on page 28

, with the following exceptions:

 In

Step 9 on page 28 , right-click the Microsoft certificate instead of the NetIQ certificate.

 In

Step 12 on page 28

, type Microsoft instead of NetIQ.

 In

Step 9 on page 29 , select Microsoft.cer instead of NetIQ.cer.

2.11

Changing Configuration Settings

AppManager for Exchange Server includes the following components:

 A client object, MCPSHostClient.dll, which runs within the AppManager agent. This client object starts the server program and asks it to run jobs.

 A server program, MCPSHostServer.exe, which provides the PowerShell environment in which the Exchange2007 scripts are executed.

Both components have associated configuration files that define certain operational parameters. You can modify these settings to fine-tune performance or to specify resource usage limits.

The configuration files are in XML format. After making changes, ensure that the files retain their wellformed XML format. Also do not remove or change settings other than those documented here. NetIQ

Corporation strongly recommends that you create backup copies of these files before modifying them.

Installing and Configuring AppManager for Exchange Server

29

NOTE: This topic does not discuss all configuration settings. As a rule, if a configuration setting is not discussed in this topic, you should not change the value of that setting.

2.11.1

Client Configuration Settings

The client configuration file, MCPSHostClient.dll.config, resides in the

AppManager\bin\PowerShell

directory. You can change the following settings.

In the <appSettings> section:

maxActiveServers Use this setting to specify the maximum number of servers that can be active at any time. Use this setting in conjunction with maxMemoryUsage to specify a lower memory threshold with an increased number of servers that can be used. This combination is beneficial for situations in which a server exceeds the memory limitation and has to shut down. If only one server can be active at a time, job requests are blocked until the server restarts. If you allow more than one server to be active, job requests can be executed in other server processes or on new servers if the current number of active servers is less than maxActiveServers.

serverStartupTimeout If MCPSHostServer.exe is not already running when a job is scheduled for execution, the client starts the server automatically. After starting the server, the client attempts to contact it. Use this configuration setting to specify the number of seconds that the client should attempt to contact the server. An error event is raised if the client cannot contact the server within the specified period.

In the <log4net> section:

file Use this setting to specify the pathname of the log file. If the pathname is a relative path, it is considered to be relative to the \AppManager\bin\PowerShell directory.

appendToFile Use this setting to indicate whether the client overwrites the existing log file or appends to it, at the time the client is loaded into the AppManager agent.

maxSizeRollBackups Use this setting to specify the number of old log files you want to retain.

maximumFileSize Use this setting to specify the maximum size of a log file. After a log file reaches this size, it is deleted, or renamed if the maxSizeRollBackups value is greater than 0.

2.11.2

Server Configuration Settings

The server configuration file, MCPSHostServer.exe.config, resides in the

AppManager\bin\PowerShell

directory. You can change the following settings.

In the <appSettings> section:

serverShutdownTimeout Use this setting to specify the number of seconds that the server will remain running when no jobs are executing. If no jobs are submitted to the server during this period, the server shuts down and will restart the next time a client needs to run a job.

upperMaxRunspaceHosts The PowerShell runspace pool allocates runspaces as needed.

Each execution of a job requires one runspace. Runspaces return to the pool after use and are then available for other jobs. Use this setting to set the absolute limit on the number of runspaces allocated for a pool. If a client requests a runspace when none is available and the pool has reached this limit, the client is blocked from running until a runspace becomes available.

30

NetIQ AppManager for Microsoft Exchange Server Management Guide

If you do not specify the runspace setting, the pool always allocates a new runspace, even if all others are in use, thereby ensuring that clients never have to wait for a runspace to be available.

maxMemoryUsage Use this setting to specify the maximum amount of memory, in megabytes, that the server process should consume. If memory usage exceeds the maximum size, the server blocks additional requests from clients and restarts automatically after the last client has finished job execution. Because Exchange2007 Knowledge Script jobs use Exchange cmdlets, which require a large amount of memory, server memory usage can grow excessively.

In the <log4net> section:

file Use this setting to specify the pathname of the log file. If the pathname is a relative path, it is considered to be relative to the \AppManager\bin\PowerShell directory.

appendToFile Use this setting to indicate whether the client overwrites the existing log file or appends to it, at the time the client is loaded into the AppManager agent.

maxSizeRollBackups Use this setting to specify the number of old log files you want to retain.

maximumFileSize Use this setting to specify the maximum size of a log file. After a log file reaches this size, it is deleted, or renamed if the maxSizeRollBackups value is greater than 0.

2.12

Troubleshooting PowerShell Errors

Knowledge Scripts in the Exchange2007 category may raise such events as "PowerShell script failed to run to completion”

or "Error executing PowerShell script." These errors can occur when Knowledge Scripts take a long time to run, or when there is contention for access to the server that executes the PowerShell scripts, MCPSHostServer.exe. The following are some recommendations for resolving these issues:

Increase the amount of memory that can be used by MCPSHostServer.exe. Increasing the memory limit reduces the frequency with which the server restarts due to excessive memory usage. Increasing the memory limit also reduces the number of PowerShell errors; each time the server recognizes that it is exceeding its memory usage threshold, the server prevents new jobs from executing until all existing jobs have completed and the server restarts. If existing jobs take a significant amount of time to complete, the waiting jobs may time out and return errors. To increase the amount of memory MCPSHostServer.exe can use, modify the value of the maxMemoryUsage

setting. For more information, see Section 2.11, “Changing Configuration

Settings,” on page 29 .

Increase the number of PowerShell execution environments, or runspaces that

MCPSHostServer.exe can host. The default number of runspaces is eight, which means no more than eight Knowledge Script jobs can be running simultaneously in the server. If you attempt to run additional jobs, the jobs are held back until runspaces become available as existing jobs complete their iterations. Being held back in this manner increases the chance that jobs will time out before running, or before completing their iteration. To increase the number of available runspaces, modify the upperMaxRunspaceHosts setting. For more information, see

Section 2.11, “Changing Configuration Settings,” on page 29

.

Increasing this value will be beneficial if you are running more than eight Exchange2007

Knowledge Script jobs, but even then the benefit may not be significant.

NOTE: The client’s maxActiveServers configuration option specifies the maximum number of servers that can be active at any time (the default is five). The maxActiveServers configuration value and the UpperMaxRunspaceHosts server configuration value determine the total number of jobs that can be serviced at any one time. You can have more than this number of jobs in the

“Running” state in AppManager, but only if some of the jobs are between iterations, and not actually running at the same time.

Installing and Configuring AppManager for Exchange Server

31

32

NetIQ AppManager for Microsoft Exchange Server Management Guide

3

Reporting with Analysis Center

NetIQ Analysis Center is designed to import raw data from multiple AppManager repositories, transform that data into useful information about the computing infrastructure that supports your business, and publish that information in the form of reports.

AppManager for Exchange Server 2007 or later ships with a package of Analysis Center report templates designed specifically for Exchange Server 2007 or later data. With these reports, you can capture and distribute vital information such as average daily and hourly response time for mail flow.

You can find the reports in the Analysis Center Navigation pane sorted by server role within the

Reports > AppManager > Application Specific > Exchange2007 folder.

3.1

System Requirements for Analysis Center Reports

Exchange Reports for Analysis Center have the following system requirements:

 Analysis Center version 2.7 or later

 AppManager for Microsoft Exchange version 7.3 or later

3.2

Installing the Report Package

You can install the Analysis Center reports for this module to either local or remote databases. You need to install the reports only once per database.

To install the report package:

1

Launch the module installer, AM70-Exchange2007-7.x.x.0.msi.

2

From the Knowledge Script and Report Package Installation Options page of the installation wizard, select Install report package.

3

In the SQL Server name\instance field, specify the SQL Server name of the server hosting the

Analysis Center Configuration Database.

4

In the Analysis Center configuration database name field, type the name of the configuration database and click Next.

Reporting with Analysis Center

33

5

Select either Windows or SQL Server authentication and click Next.

6

When the installer finishes, launch the Analysis Center console.

3.3

Exchange Server 2007 or later Analysis Center

Report Templates

The Analysis Center report package for AppManager for Exchange Server 2007 or later contains the following templates.

Template Description

Client Access Server Report Templates

Average OWA login failures Two reports based on the datastreams generated by the

CAS_Activity Knowledge Script. The daily report and the hour

report present the average number of Outlook Web Access login failures for the period you specify.

Average number of current OWA users A daily report and an hourly report that present the average number of users logged on to Outlook Web Access for the period you specify.

Average number of OWA user sessions Two reports based on the datastreams generated by the

CAS_Activity Knowledge Script. The daily report and the hourly

report present the average Outlook Web Access login rate for user sessions for the period you specify.

General Exchange Report Templates

NOTE: Unlike the other report templates in the Exchange2007 report package, the General templates allow you to report on any datastream generated by any Knowledge Script in the Exchange2007 category.

Exchange Server 2007 performance data filtered by data source

Examines performance data for Exchange Server 2007 or later based on data source for the period you specify.

Exchange Server 2007 performance data filtered by Knowledge Script

Examines performance data for Exchange Server 2007 or later, based on the Knowledge Scripts that generated the datastreams, for the period you specify.

Hub Transport Server Report Templates

Average use of Transport Dumpster queue

Two reports based on the datastreams generated by the

HTS_TransportDumpster Knowledge Script. The daily report and

the hourly report present average use of the Transport Dumpster queue for the period you specify: number of items in the queue, size of items in the queue, insertion rate, deletion rate, and number of re-deliveries.

Mailbox Server Report Templates

Average length of the copy queue Two reports based on the datastreams generated by the

MBS_Replication

Knowledge Script. The hourly report and the daily report present the average number of logs in the copy queue for the period you specify.

34

NetIQ AppManager for Microsoft Exchange Server Management Guide

Template Description

Average disk usage

Average use of File Share Witness

Two reports based on the datastreams generated by the

MBS_DatabaseStatus Knowledge Script. The daily report and the

hourly report present average disk usage for the period you specify, including disk access time, disk read time, disk write time, and queued requests.

Two reports based on the datastreams generated by the

MBS_Replication

Knowledge Script. The daily report and the hourly report present average use of File Share Witness by server for the period you specify.

Average number of mailboxes in a storage group

Examines the average number of mailboxes in a storage group

(Exchange 2007 only) for the period you specify. This report uses

the datastreams generated by the MBS_MailboxUsage

Knowledge

Script.

Average size of largest mailboxes

Average mail flow response time

Average number of messages in top n mailboxes

Examines the average size of the top n mailboxes for the period you specify. This report uses the datastreams generated by the

MBS_MailboxUsage

Knowledge Script.

Two reports based on the datastreams generated by the

MBS_MailFlow Knowledge Script. The daily report and the hourly

report present average mail flow response time for the period you specify.

Examines the average number of messages in the top n mailboxes for the period you specify. This report uses the datastreams generated by the

MBS_MailboxUsage

Knowledge Script.

Average number of logs in the replay queue

Two reports based on the datastreams generated by the

MBS_Replication

Knowledge Script. The daily report and the hourly report present the average number of logs in the replay queue for the period you specify.

Unified Messaging Server Report Templates

Average call activity per UMS call type Two reports based on the datastreams generated by the

UMS_CallActivity

Knowledge Script. The daily report and the hourly report present average call activity for each UMS call type.

Average number of UMS-related failures Two reports based on the datastreams generated by the

UMS_Failures

Knowledge Script. The daily report and the hourly report present the average number of UMS-related failures: calls disconnected due to internal or external errors, redirection failures, and failures for accessing the Mailbox server, the Hub Transport server, and Active Directory.

Average number of Unified Messaging operations

Two reports based on the datastreams generated by the

UMS_Performance Knowledge Script. The daily report and the

hourly report present the average number of Unified Messaging operations based on response time.

Reporting with Analysis Center

35

36

NetIQ AppManager for Microsoft Exchange Server Management Guide

4

Exchange 2007 Knowledge Scripts

AppManager for Exchange Server provides Knowledge Scripts for monitoring Microsoft Exchange

Server 2007, 2010, and 2013.

The Exchange Server 2007 Knowledge Scripts supports Microsoft Exchange Server 2007 resources installed in non-clustered environments and the following clustered environments:

Cluster continuous replication (CCR) combines the log shipping and replay functionality in

Exchange Server 2007 with the failover functionality in the Microsoft cluster service. CCR is a solution that can be deployed with no single point of failure in a single datacenter or between two datacenters.

Single copy clusters (SCC), known as shared storage clusters in previous versions of Exchange

Server, are present in Exchange Server 2007.

In a clustered environment, AppManager raises error events if failover occurs while jobs are running.

These error events are expected results of the failover process and can be safely ignored.

A subset of the Knowledge Scripts support Microsoft Exchange Server 2010 and 2013 resources installed in a database availability group (DAG). A DAG is a set of up to 16 Microsoft Exchange

Server 2010 or 2013 Mailbox servers that provides automatic database-level recovery from a database, server, or network failure. Exchange Server 2010 and 2013 do not use storage groups.

NOTE: You should review the permissions required for different roles in the

Section 2.5, “Permissions for Discovering Exchange Server Resources,” on page 18

before you run the Knowledge Scripts.

From the Knowledge Script view of Control Center, you can access more information about any

NetIQ-supported Knowledge Script by selecting it and clicking Help. Or in the Operator Console, click any Knowledge Script in the Knowledge Script pane and press F1.

Knowledge Script

All_BestPracticesAnalyzer

All_ClockSynchronization

All_EventLog

All_ServiceStatus

CAS_Activity

CAS_Connectivity

CAS_OABAvailability

CAS_PublicFolderAvailability

What It Does

Monitors the Windows event log for errors and warnings raised by the

Exchange Best Practices Analyzer.

Monitors the synchronization of clocks for one or more Domain

Controllers.

Monitors the Windows Application event log for errors and warning events related to Exchange Server 2007, 2010, or 2013.

Monitors the status of Exchange Server 2007, 2010, and 2013 services.

Monitors Client Access server services and functions.

Monitors connectivity for Client Access server services on Exchange

Server 2007 and 2010: ActiveSync, Outlook Web Access, Outlook

Web services, and the Autodiscover service.

Monitors whether offline address books can be downloaded.

Monitors the accessibility of public folders on the Client Access server.

Exchange 2007 Knowledge Scripts

37

Knowledge Script

ETS_ExternalMail

ETS_MessageHygiene

HTS_Connectivity

HTS_SafetyNet

HTS_SendersAndRecipients

HTS_TransportDumpster

MBS_ClientActivity

MBS_ClientConnectivity

MBS_ClusterOwner

MBS_DatabaseStateChange

MBS_DatabaseStatus

MBS_MailboxAccessibility

MBS_MailboxUsage

MBS_MailFlow

MBS_MessagingRecordsMgmt

MBS_PublicFolderUsage

MBS_Replication

Transport_BackPressure

Transport_ConnectorStatus

Transport_QueueStatus

UMS_CallActivity

What It Does

Monitors e-mail sent to and from your Exchange environment.

Monitors message hygiene functions for the Edge Transport server.

Monitors the connectivity with a Mailbox server, and monitors the time of the last synchronization with the Edge Transport server.

Monitors the Safety Net availability in Exchange Server 2013. It replaces the Transport Dumpster Knowledge script available for

Exchange Server 2007 and 2010.

Measures number of messages in a mailbox and total message size for senders and recipients.

Monitors Transport Dumpster activity, availability, and the number of items in the Transport Dumpster.

Monitors Exchange Server 2013 Mailbox server services and functions.

Monitors connectivity for Mailbox server services on Exchange

Server 2013: ActiveSync, Outlook Web services, and the

Autodiscover service.

Determines whether an Exchange Server is the owner of the node and whether the CMS is down. This script only runs on servers with

Exchange Server 2007.

Monitors changes in the state of mailbox databases on an Exchange

Server. States include active, passive, suspended, removed, or unmounted.

Monitors Exchange Server 2007, 2010, and 2013 mailbox databases for size of online maintenance window, defragmentation time, free log space, free file space, and number of mailboxes.

Monitors the ability of the Mailbox server to access individual mailboxes.

Measures the size of mailboxes by the number of messages in the mailbox or by total message size in MB.

Sends test e-mail to local or remote Mailbox servers.

Monitors message management tasks such as deleting, journaling, moving, and retention.

Measures the size of public folders by the number of messages in the folders or by total message size in MB.

Monitors replication status and performance for a Mailbox server.

Monitors the status of back pressure for the Hub Transport server.

Monitors the status of send, receive, foreign, and delivery agent connectors on Exchange Servers.

Monitors the status of queues on the Hub Transport server: submission queue, mailbox delivery queue, remote delivery queue, poison message queue, and unreachable destination queue.

Monitors call activity on the Unified Messaging server: voice, fax, play on phone, auto attendant, subscriber access, prompt editing.

38

NetIQ AppManager for Microsoft Exchange Server Management Guide

Knowledge Script

UMS_Connectivity

UMS_Failures

UMS_Performance

Recommended Knowledge Script

Group

What It Does

Monitors connectivity to Hub Transport servers, Mailbox servers,

Active Directory, and Unified Messaging-enabled mailboxes.

Monitors failures related to redirected calls, disconnected calls, and access to Active Directory, the Hub Transport server, and the Mailbox server.

Monitors the performance of the Unified Messaging server: user response latency, operation response time, queued messages for call answering, queued OCS user notifications, and calls disconnected while playing audio hourglass tones.

Performs essential monitoring of your Exchange Server 2007, 2010, or 2013 environment.

4.1

All_BestPracticesAnalyzer

Use this Knowledge Script to monitor the Windows event log for errors and warnings whose source is

BPA (Exchange Best Practices Analyzer). This script raises an event if the Knowledge Script job fails or the event log contains error and warning messages.

If you are not running the BPA, you can use this script to execute the BPA each time the script runs. If you set the Execute Best Practices Analyzer during job? parameter to Yes, AppManager runs the

BPA at each iteration of the Knowledge Script job. AppManager then stops the BPA and analyzes the event log for errors and warnings raised by the BPA.

NOTE

 This script may raise duplicate events on computers where multiple Exchange Server 2007 and

2010 roles are installed. These duplicate events are raised because the BPA populates the event log with errors and warnings for each role when the error or warning is applicable for the entire

Exchange Server 2007 or 2010 organization.

 This script is not applicable for Exchange Server 2013.

 Most BPA events do not indicate which role they are associated with. Therefore, this script raises events that are not associated with a role. However, the AppManager event messages include the text of the BPA event, which should help you determine which role is affected.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.1.1

Running the ExBPAcmd.exe Tool Manually

The BPA must be running so that it can submit any errors or warnings to the event log. This script will not work if you are not running the BPA and do not enable the Execute Best Practices Analyzer

during job? parameter.

If you do not enable this script to launch the BPA, then run the ExBPAcmd.exe tool manually to monitor the Windows Event Log for errors and warnings.

Exchange 2007 Knowledge Scripts

39

To run the ExBPAcmd.exe tool manually:

1

Open the Exchange Management Shell.

2

Run the following command:

$exBPAoutput = . "C:\Program Files\Microsoft\Exchange Server\Bin\ExBPAcmd.exe"

-p Events:Enable -r "5,$role,$scan_type,Server=<ExchangeServerName>" where $role is one of the following values enclosed in quotation marks (“ ”): Mailbox, Gateway,

Bridgehead

, ClientAccess, ClusterMailbox where $scan_type is one of the following values enclosed in quotation marks (“ ”): Health,

ConnectivityTask

, Ex2007Readiness, Perf, Permissions where <ExchangeServerName> is the name of the Exchange server where you want to run the

ExBPAcmd.exe

tool.

3

Run the following command to display the output of the ExBPAcmd.exe tool:

Write-Host $exBPAoutput

These commands enable the event log register.

4.1.2

Prerequisites

Before running this script, ensure that the following permissions and memberships exist.

Component

Account running the AppManager agent service (netiqmc)

Exchange Best Practice Analyzer tool

(for all Exchange Server roles)

Required Permissions and Memberships

Membership in the Builtin\Administrators group on the Active

Directory server

Membership in the local Administrators group on the local computer

Delegation for at least Exchange View-Only permissions

Designation as the Domain Administrator, or membership in the

Builtin\Administrators group on the Active Directory server, for enumerating the Active Directory information and calling the

Microsoft Windows Management Instrumentation (WMI) providers on the domain controller and global catalog servers

Membership in the Local Administrators group on each

Exchange server for calling the WMI providers and accessing the registry and the metabase

Delegation for at least Exchange View-Only Permissions on the

Exchange organization

4.1.3

Resource Object

Exchange_Server

4.1.4

Default Schedule

By default, this script runs every one hour.

40

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.1.5

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the All_BestPracticesAnalyzer job fails. The default is 5.

Analyze Exchange Server 2007/2010 Best Practices

Execute Best Practices

Analyzer during job?

Select Yes to allow AppManager to launch the BPA using a command-line execution of

ExBPACmd.exe

at each iteration of this script. If you are already running the BPA, then clear this option. The BPA must be running so that it can submit any errors or warnings to the event log.

The default is Yes.

Type of scan to execute Select the type of scan the BPA should perform:

Connectivity Test. To scan network connections and permissions for the selected Exchange server.

Exchange 2007 Readiness Check. To assess your organization's readiness for Exchange Server 2007.

Health Check. To perform a full scan, checking for errors, warnings, and configuration information. This option is selected by default.

Permission Check. To ensure that your Exchange Server 2007 deployment has the proper credentials as defined by your organization.

Event Notification

Comma-separated list of event

IDs to ignore

Provide a list of error and warning ID numbers that this script should ignore when scanning the event log. Separate the numbers with a comma.

Raise event for errors found in Windows Event Log?

Select Yes to raise an event when the event log contains error messages raised by the BPA. The default is Yes.

Event severity when errors found in the Windows Event Log

Set the severity level, from 1 to 40, to indicate the importance of an event in which the event log contains error messages. The default is 5.

Raise event for warnings found in Windows Event Log?

Select Yes to raise an event when the event log contains warning messages raised by the BPA. The default is Yes.

Event severity for warnings found in the Windows Event Log

Set the severity level, from 1 to 40, to indicate the importance of an event in which the event log contains warning messages raised by the BPA. The default is 15.

4.2

All_ClockSynchronization

Use this Knowledge Script to monitor the synchronization of clocks for one or more Domain

Controllers. This script raises an event if the number of seconds of difference between clocks exceeds the threshold you set.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

Exchange 2007 Knowledge Scripts

41

4.2.1

Resource Object

Exchange_Server

4.2.2

Default Schedule

By default, this script runs every 15 minutes.

4.2.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the All_ClockSynchronization job fails. The default is 5.

Monitor Clock Synchronization with Domain Controller

Comma-separated list of

Domain Controllers to test

Use this parameter to limit the number of Domain Controller (DC) clocks that are tested for synchronization with the clock on the server running the

ClockSynchronization Knowledge Script.

Provide a list of fully qualified hostnames, separating multiple names by commas.

Leave this parameter blank to test all DC clocks in your organization.

Event Notification

Raise event if clocks are not synchronized?

Threshold - Maximum clock difference

Event severity when clock difference exceeds threshold

Select Yes to raise an event if the clock on the server running the

ClockSynchronization Knowledge Script is not synchronized with the clock on the DC. The default is Yes.

Set the maximum number of seconds that the server clock can be out of sync with the DC. For example, setting the threshold to 2 indicates that it is acceptable for the clock to be two seconds faster or slower than the clock on the DC. The default is 10 seconds.

If you want the server clock to be in sync with the DC clock, set this parameter to 0.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the clock synchronization offset exceeds the threshold you set. The default is 25.

4.3

All_EventLog

Use this Knowledge Script to monitor the Windows Application event log for errors and warnings that contain the word exchange. This script raises an event if event log entries match your search criteria.

You can filter your search by event ID, event category, and event source.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

42

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.3.1

Resource Object

Exchange_Server

4.3.2

Default Schedule

By default, this script runs every 15 minutes.

4.3.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the All_EventLog job fails. The default is 5.

Monitor Windows Event Log

Event Notification

Comma-separated list of event sources to ignore

Provide a list of event sources that this script should ignore when scanning the Application event log. Separate the source names with a comma.

Event sources are computers whose names are displayed in the Source column of the event log.

Comma-separated list of event categories to ignore

Provide a list of event categories that this script should ignore when scanning the Application event log. Separate the category names with a comma.

Comma-separated list of event

IDs to ignore

Provide a list of error and warning ID numbers that this script should ignore when scanning the Application event log. Separate the numbers with a comma.

Raise event if Exchange error events are found?

Select Yes to raise an event if the Application event log contains error events that match your search criteria. The default is Yes.

Event severity when Exchange error events are found

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Application event log contains error events. The default is 10.

Raise event if Exchange warning events are found?

Select Yes to raise an event if the Application event log contains warning events that match your search criteria. The default is Yes.

Event severity when Exchange warning events are found

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Application event log contains warning events. The default is 20.

4.4

All_ServiceStatus

Use this Knowledge Script to monitor the status of Exchange Server 2007, 2010, and 2013 services.

This script raises an event when services are not running and when stopped services fail to start.

This script monitors and restarts the following Exchange Server 2007, 2010, and 2013 services:

Mailbox Server Role Services

Exchange 2007 Knowledge Scripts

43

Monitoring

Mailbox Assistants

System Attendant

Transport Log Search

Active Directory Topology

Mail Submission

Search Indexer

Search (Exchange)

Information Store

Replication Service

Service Host

Server Extension for Windows

Server Backup

Client Access Server Role Services

Service Host Active Directory Topology

Hub Transport Server Role Services

EdgeSync Active Directory Topology

Transport Log Search

Edge Transport Server Role Services

ADAM Credential Service

Anti-SPAM Update Monitoring

Unified Messaging Server Role Services

Active Directory Topology

Unified Messaging

File Distribution

Speech Engine

File Distribution

Transport

Transport

Transport Log Search

Monitoring

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.4.1

Resource Objects

 Exchange2007_Services

 Exchange2007_Service

 Exchange2010_Services

 Exchange2010_Service

 Exchange2013_Services

 Exchange2013_Service

4.4.2

Default Schedule

By default, this script runs every 15 minutes.

4.4.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

Job failure event notification

How to Set It

44

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the All_ServiceStatus job fails. The default is 5.

Monitor Status of Exchange 2007/2010/2013 Services

Services to be Monitored

Monitor services configured to start automatically?

Select Yes to monitor Exchange Server 2007, 2010, and 2013 services that are configured to start automatically. The default is Yes.

When you enable this parameter, the All_ServiceStatus job does not raise events for services that are configured to start manually, nor does it start manual services that are not running.

Monitor services configured to start manually?

Select Yes to monitor Exchange Server 2007, 2010, or 2013 services that are configured to start manually. The default is No.

When enabled, the All_ServiceStatus job does not raise events for services that are configured to start automatically.

Event Notification

Raise event if Exchange 2007/

2010/2013 services are not running?

Select Yes to raise an event if at least one Exchange Server service is not running. The default is Yes.

When you enable this parameter, the All_ServiceStatus job raises events only for those services you selected in the Services to be Monitored parameters.

Event severity when services are not running

Start services not currently running?

Set the severity level, from 1 to 40, to indicate the importance of an event in which at least one Exchange Server service is not running. The default is 10.

Select Yes to start Exchange Server 2007, 2010, or 2013 services that are not running. The default is Yes.

When you enable this parameter, the All_ServiceStatus job starts only those services you selected in the Services to be Monitored parameters.

Threshold - Timeout for service startup

Set the number of seconds that AppManager should wait for Exchange

Server 2007, 2010, or 2013 services to restart before raising an event. The default is 60 seconds.

Raise event if stopped services fail to start?

Event severity when stopped services fail to start

Select Yes to raise an event if AppManager cannot start Exchange Server services that are not running. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which Exchange Server services fail to start after the specified timeout period. The default is 5.

4.5

CAS_Activity

Use this Knowledge Script to monitor Client Access server (CAS) services and functions:

 Availability Service activity

 ActiveSync response time and request rate

 Outlook Web Access response time, search time, login rate, and login failures

 Outlook Web Services request rate and current connections

Exchange 2007 Knowledge Scripts

45

 IMAP4 (Internet Message Access protocol) processing time, current connections, and active

SSL connections

 POP3 (Post Office Protocol) processing time, login rate, current connections, and active SSL connections

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

NOTE: This Knowledge Script is available only for Exchange Server 2007 and 2010. For Exchange

Server 2013, see Section 4.15, “MBS_ClientActivity,” on page 72 .

4.5.1

Resource Objects

 Exchange2007_ClientAccessServer

 Exchange2010_ClientAccessServer

4.5.2

Default Schedule

By default, this script runs every 15 minutes.

4.5.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to set it

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the CAS_Activity job fails. The default is 5.

Monitor Availability Service Activity

Event Notification

Raise event if response time for free/busy requests exceeds threshold?

Select Yes to raise an event if the response time for free or busy requests to Microsoft Outlook exceeds the threshold you set. The default is Yes.

Threshold - Maximum free/busy request response time Set the maximum length of time that Microsoft Outlook can take to respond to free/busy requests before an event is raised. The default is 5000 milliseconds.

Event severity when response time for free/busy requests exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the response time for free/busy requests exceeds the threshold. The default is 15.

Data Collection

Collect data for free/busy request response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

46

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to set it

Monitor ActiveSync Activity

Monitor ActiveSync Response Time

Event Notification

Raise event if ActiveSync response time exceeds threshold?

Select Yes to raise an event if the response time for

ActiveSync exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time Set the maximum length of time that ActiveSync can take to respond to requests before an event is raised.

The default is 100 milliseconds.

Event severity when response time exceeds threshold Set the severity level, from 1 to 40, to indicate the importance of an event in which ActiveSync response time exceeds the threshold. The default is 15.

Data Collection

Collect data for response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

Monitor ActiveSync Request Rate

Event Notification

Raise event if ActiveSync request rate exceeds threshold?

Select Yes to raise an event if the rate of synchronization requests to ActiveSync exceeds the threshold you set. The default is Yes.

Threshold - Maximum request rate Set the maximum number of requests that can occur per second before an event is raised. The default is 10 synchronization requests per second.

Event severity when request rate exceeds threshold Set the severity level, from 1 to 40, to indicate the importance of an event in which the ActiveSync request rate exceeds the threshold. The default is 15.

Data Collection

Collect data for request rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the rate of synchronization requests during the monitoring interval. The default is No.

Monitor Outlook Web Access Activity

Monitor Outlook Web Access Response Time

Event Notification

Raise event if Outlook Web Access response time exceeds threshold?

Select Yes to raise an event if the response time for

Outlook Web Access (OWA) exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time Set the maximum amount of time that it can take for

OWA to respond to requests before an event is raised.

The default is 100 milliseconds.

Exchange 2007 Knowledge Scripts

47

Parameter How to set it

Event severity when response time exceeds threshold Set the severity level, from 1 to 40, to indicate the importance of an event in which OWA response time exceeds the threshold. The default is 15.

Data Collection

Collect data for response time?

Select Yes to collect .data for charts and reports.

When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

Monitor Outlook Web Access Search Time

Event Notification

Raise event if Outlook Web Access search time exceeds threshold?

Threshold - Maximum search time

Event severity when search time exceeds threshold

Select Yes to raise an event if Outlook Web Access

(OWA) search time exceeds the threshold. The default is Yes.

The OWA search feature allows users to find items in a mailbox.

Set the maximum length of time that OWA can spend performing a search before an event is raised. The default is 100 milliseconds.

Set the severity level, from 1 to 40, to indicate the importance of an event in which OWA search time exceeds the threshold. The default is 15.

Data Collection

Collect data for search time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the length of search time during the monitoring interval. The default is No.

Monitor Outlook Web Access Login Rate

Event Notification

Raise event if login rate exceeds threshold?

Threshold - Maximum login rate

Event severity when login rate exceeds threshold

Select Yes to raise an event if the rate at which users log in to Outlook Web Access (OWA) exceeds the threshold. The default is Yes.

Set the maximum rate at which users can log in to

OWA before an event is raised. The default is 10 logins per second.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the rate at which users log in to OWA exceeds the threshold. The default is 15.

Data Collection

Collect data for login rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the OWA log in rate for the monitoring interval. The default is No.

Monitor Outlook Web Access Login Failures

Event Notification

48

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to set it

Raise event if login failures exceed threshold?

Threshold - Maximum percentage of login failures

Event severity when login failures exceed threshold

Select Yes to raise an event if the failures for logging in to Outlook Web Access (OWA), expressed as a percentage of all login attempts, exceed the threshold.

The default is Yes.

Set the maximum percentage of OWA login failures that can occur before an event is raised. The default is

10%.

Set the severity level, from 1 to 40, to indicate the importance of an event in which percentage of OWA login failures exceeds the threshold. The default is 15.

Data Collection

Collect data for login failures?

Select Yes to collect data for charts and reports. When enabled, data collection returns the percentage of

OWA login failures for the monitoring interval. The default is No.

Monitor Outlook Web Services Activity

Monitor Outlook Web Services Request Rate

Event Notification

Raise event if Outlook Web Services request rate exceeds threshold?

Select Yes to raise an event if the rate of requests to

Outlook Web Services exceeds the threshold you set.

The default is Yes.

Threshold - Maximum request rate

Event severity when request rate exceeds threshold Set the severity level, from 1 to 40, to indicate the importance of an event in which the rate of requests to

Outlook Web Services exceeds the threshold. The default is 15.

Data Collection

Set the maximum number of requests that can occur per second before an event is raised. The default is 10 requests per second.

Collect data for request rate?

Monitor Outlook Web Services Current Connections

Select Yes to collect data for charts and reports. When enabled, data collection returns the rate of requests during the monitoring interval. The default is No.

Event Notification

Raise event if number of current connections exceeds threshold?

Select Yes to raise an event if the number of connections established with Outlook Web Services exceeds the threshold you set. The default is Yes.

By knowing the number of current connections, you can determine user load for Outlook Web Services

Threshold - Maximum number of current connections Set the maximum number of connections to Outlook

Web Services that can be established before an event is raised. The default is 25 connections.

Exchange 2007 Knowledge Scripts

49

Parameter How to set it

Event severity when number of current connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of connections established with Outlook Web Services exceeds the threshold. The default is 15.

Data Collection

Collect data for number of current connections?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of connections established during the monitoring interval.

The default is No.

Monitor IMAP4 Activity

Monitor IMAP4 Command Processing Time

Event Notification

Raise event if command processing time exceeds threshold?

Select Yes to raise an event if the amount of processing time for IMAP4 commands exceeds the threshold you set. The default is Yes.

Threshold - Maximum command processing time

Event severity when command processing time exceeds threshold

Set the maximum amount of time that can be spent processing IMAP4 commands before an event is raised. The default is 100 milliseconds.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of processing time for IMAP4 commands exceeds the threshold. The default is 15.

Data Collection

Collect data for command processing time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the amount of processing time spent during the monitoring interval.

The default is No.

Monitor IMAP4 Connections Rate

Event Notification

Raise event if connections rate exceeds threshold?

Threshold - Maximum connections rate

Event severity when connections rate exceeds threshold

Select Yes to raise an event if the number of IMAP4 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Set the maximum number of IMAP4 connection requests that can occur per second before an event is raised. The default is 10 connections per second.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4 connection requests exceeds the threshold. The default is 15.

Data Collection

Collect data for connections rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of IMAP4 connection requests for the monitoring intervals. The default is No.

50

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to set it

Monitor IMAP4 Current Connections

Event Notification

Raise event if number of current connections exceeds threshold?

Data Collection

Collect data for number of current connections?

Select Yes to raise an event if the number of current

IMAP4 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of current connections Set the maximum number of IMAP4 connections that can be established before an event is raised. The default is 10 connections.

Event severity when number of current connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4 connections exceeds the threshold. The default is 15.

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of IMAP4 connections established during the monitoring interval.

The default is No.

Monitor IMAP4 Active SSL Connections

Event Notification

Raise event if number of active SSL connections exceeds threshold?

Threshold - Maximum number of active SSL connections

Select Yes to raise an event if the number of current

IMAP4 connections to your Exchange server over SSL

(Secure Sockets Layer) exceeds the threshold you set.

The default is Yes.

Set the maximum number of IMAP4 connections that can be established over SSL before an event is raised.

The default is 50 connections.

Event severity when number of active SSL connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4

SSL connections exceeds the threshold. The default is

15.

Data Collection

Collect data for number of active SSL connections?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of IMAP4

SSL connections established during the monitoring interval. The default is No.

Monitor POP3 Activity

Monitor POP3 Command Processing Time

Event Notification

Raise event if command processing time exceeds

threshold?

Select Yes to raise an event if the amount of processing time for POP3 commands exceeds the threshold you set. The default is Yes.

Threshold - Maximum command processing time Set the maximum amount of time that can be spent processing POP3 commands before an event is raised. The default is 10 milliseconds.

Exchange 2007 Knowledge Scripts

51

Parameter How to set it

Event severity when command processing time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of processing time for POP3 commands exceeds the threshold. The default is 15.

Data Collection

Collect data for command processing time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the amount of processing time spent during the monitoring interval.

The default is No.

Monitor POP3 Connections Rate

Event Notification

Raise event if connections rate exceeds threshold?

Threshold - Maximum connections rate

Event severity when connections rate exceeds threshold

Data Collection

Collect data for connections rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of POP3 connection requests for the monitoring intervals. The default is No.

Monitor Current POP3 Current Connections

Event Notification

Raise event if number of current connections exceeds threshold?

Threshold - Maximum number of current connections Set the maximum number of POP3 connections that can be established before an event is raised. The default is 10 connections.

Event severity when number of current connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3 connections that are currently established exceeds the threshold. The default is 15.

Data Collection

Collect data for number of current connections?

Select Yes to raise an event if the number of current

POP3 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of POP3 connections established during the monitoring interval.

The default is No.

Monitor POP3 Active SSL Connections

Select Yes to raise an event if the number of POP3 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Set the maximum number of POP3 connection requests that can occur per second before an event is raised. The default is 10 connections per second.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3 connection requests exceeds the threshold. The default is 15.

52

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to set it

Event Notification

Raise event if number of active SSL connections exceeds threshold?

Threshold - Maximum number of active SSL connections

Event severity when number of active SSL connections exceeds threshold

Select Yes to raise an event if the number of current

POP3 connections to your Exchange server over SSL

(Secure Sockets Layer) exceeds the threshold you set.

The default is Yes.

Set the maximum number of POP3 connections that can be established over SSL before an event is raised.

The default is 25 connections.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3

SSL connections exceeds the threshold. The default is

15.

Data Collection

Collect data for number of active SSL connections Select Yes to collect data for charts and reports. When enabled, data collection returns the number of POP3

SSL connections established during the monitoring interval. The default is No.

4.6

CAS_Connectivity

Use this Knowledge Script to monitor the connectivity of Client Access server (CAS) services on

Exchange Server 2007 and 2010: ActiveSync, Outlook Web Access, Outlook Web services, and the

Autodiscover service. This script raises an event when a connectivity test fails and when response time exceeds the threshold you set.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

NOTE: This Knowledge Script is available only for Exchange Server 2007 and 2010. For Exchange

Server 2013, see Section 4.16, “MBS_ClientConnectivity,” on page 79 .

4.6.1

Configuring Security Manager to Test Outlook Web Access

Connectivity

Before you can run the CAS_Connectivity Knowledge Script to test Outlook Web Access connectivity using a custom URL, you need to configure Security Manager for the Client Access server where the job will run. You do not need to configure Security Manager if you are using an internal or external

URL.

To configure AppManager Security Manager to test connectivity:

1

On the Extensions menu in the Operator Console, click Security Manager.

2

Select the Client Access server you want to test.

3

On the Custom tab, click Add.

4

In the Label field, type Exchange2007.

5

In the Sub-label field, type MailboxCredentials

Exchange 2007 Knowledge Scripts

53

6

In the Value 1 field, specify the mailbox name, which is also referred to as the user account, to be used in the test.

7

In the Value 2 field, specify the password for the mailbox.

8

Leave the Value 3 field blank.

9

Select Extended application support to encrypt the password when it is stored in the repository.

10

Click OK.

11

Click Apply to save the Security Manager settings.

4.6.2

Running CAS_Connectivity on a Client Access Server

When you run the CAS_Connectivity Knowledge Script on a Client Access server, the script automatically creates a CAS test user mailbox on each Mailbox server in the Exchange deployment if those mailboxes do not already exist. In an Exchange deployment containing Exchange 2007 and

Exchange 2010 servers, if you run the CAS_Connectivity script on an Exchange 2010 Client Access

Server, the script will not be able to create the mailboxes on Exchange 2007 Mailbox Servers, and

AppManager raises an error event about the problem. This is due to the issue that Microsoft does not support creating mailboxes across different version types. To resolve, you must manually create the

CAS test user mailboxes on the Exchange 2007 Mailbox Servers.

To create CAS test user mailboxes on an Exchange 2007 Mailbox Server:

1

Log in to one of the Exchange 2007 Mailbox Servers and open the Exchange Management

Shell.

2

Change directories to the Scripts directory under the Microsoft Exchange installation directory.

3

Run the following command:

Get-MailboxServer | .\New-TestCasConnectivityUser.ps1

.

4

Follow the on-screen instructions to create the CAS test user mailbox on each Mailbox server.

4.6.3

Resource Objects

 Exchange2007_ClientAccessServer

 Exchange2010_ClientAccessServer

4.6.4

Default Schedule

By default, this script runs every 30 minutes.

4.6.5

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

How to Set It

54

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Communicate only with

Exchange Servers in the local domain?

Ignore these Mailbox servers when testing CAS to MBS communications

Select Yes to test only Exchange Servers in the same domain as the server on which you run the CAS_Connectivity job.

When this option is unselected, certain tests for the Client Access server attempt to contact all Mailbox servers in your organization. These tests will fail if the Exchange accounts in one domain do not have access to other domains.

Leave this option unselected if you specify a Mailbox server in the Mailbox

server to be used for connectivity tests parameter.

Provide a comma-separated list of the hostnames of the Mailbox servers that you want to exclude from connectivity testing between the Client Access server and the Mailbox server.

Leave this option blank if you specify a Mailbox server in the Mailbox server

to be used for connectivity tests parameter.

By default, the CAS_Connectivity job tests connectivity to all Mailbox servers. Use this parameter to enable testing to one Mailbox server.

Mailbox server to be used for connectivity tests

Enter the hostname of the computer that hosts the Mailbox server with which you want to check connectivity. The hostname need not be fully qualified unless DNS lookup does not resolve the simple name.

If you monitor Outlook web access connectivity and specify a custom URL, that custom URL will be used to test Outlook web access connectivity instead of this mailbox server.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the CAS_Connectivity job fails. The default is 5.

Connectivity Test User

Configuration

Use alternate test mailbox configured in Security Manager?

Select Yes to use the test mailbox that you have specified in the Security

Manager. The default is No.

Create default test mailbox automatically?

Select Yes to create a default test mailbox automatically. The default is Yes.

Create non-existent test mailboxes every N job iterations

(specify N)

Specify the number of job iterations for which the non-existent test mailboxes will be created on the Mailbox server. The default is 1.

Monitor ActiveSync Connectivity

Event Notification

Raise event if ActiveSync connectivity test fails?

Select Yes to raise an event if AppManager cannot check connectivity to

ActiveSync. The default is Yes.

Event severity when ActiveSync connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to ActiveSync. The default is

5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to

ActiveSync exceeds the threshold you set. The default is Yes.

Exchange 2007 Knowledge Scripts

55

Parameter How to Set It

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait for connectivity with ActiveSync before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time it takes to connect to ActiveSync exceeds the threshold that you set. The default is 15.

Data Collection

Collect data for ActiveSync response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to ActiveSync.

The default is No.

Monitor Outlook Web Access Connectivity

Allow unsecure (http) communication?

Select Yes if you want to allow unsecure communication using of http

instead https

when testing the Web access connectivity. The default is No.

URL type to be used for connectivity test

Select whether you want to use an internal URL, an external URL, or a custom URL for the connectivity test. If you select a custom URL, configure the credentials in Security Manager before you run a job. The default type is

Internal.

Specify the URL you want to use for the connectivity test. The default is blank.

Custom URL to be used for connectivity test

Event Notification

Raise event if Outlook Web

Access connectivity test fails?

Select Yes to raise an event if AppManager cannot check connectivity to

Outlook Web Access (OWA). The default is Yes.

Event severity when Outlook

Web Access connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to OWA. The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to

Outlook Web Access exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait to confirm connectivity with OWA before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time it takes to connect to OWA exceeds the threshold that you set.

The default is 15.

Data Collection

Collect data for Outlook Web

Access response time?

Monitor Outlook Web Services Connectivity

Use SSL (HTTPS) for connectivity test?

Select Yes to use Secure Socket Layer (SSL) to test connectivity to Outlook

Web services. The default is No.

If you select Yes, AppManager will use only SSL to test connectivity. If you clear the option, AppManager will first use SSL to test connectivity. If that attempt fails, AppManager will then try to test connectivity without using SSL.

Event Notification

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to OWA. The default is No.

56

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event if Outlook Web services connectivity test fails?

Select Yes to raise an event if AppManager cannot check connectivity to

Outlook Web services. The default is Yes.

Event severity when Outlook

Web services connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to Outlook Web services. The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to

Outlook Web services exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait to confirm connectivity with Outlook

Web services before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time taken for testing connectivity to Outlook Web services exceeds the threshold that you set. The default is 15.

Data Collection

Collect data for Outlook Web services response time?

Raise event if Autodiscover service connectivity test fails?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to Outlook Web services. The default is No.

Monitor Autodiscover Service Connectivity

Event Notification

Select Yes to raise an event if AppManager cannot check connectivity to the

Autodiscover service. The default is Yes.

The Autodiscover service allows Outlook 2007 clients and mobile devices to be recognized when they connect to the Client Access server.

Event severity when

Autodiscover service connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to the Autodiscover service.

The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to the

Autodiscover service exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait to confirm connectivity with the

Autodiscover service before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time taken for testing connectivity to the Autodiscover service exceeds the threshold that you set. The default is 15.

Data Collection

Collect data for Autodiscover service response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to the

Autodiscover service. The default is No.

Exchange 2007 Knowledge Scripts

57

4.7

CAS_OABAvailability

Use this Knowledge Script to monitor the availability of offline address books (OABs) for a Client

Access server. This script raises an event if OABs cannot be downloaded.

This Knowledge Script monitors the offline address books only if they are hosted in a virtual directory.

If they are in a public folder, this Knowledge Script does not monitor those.

NOTE: This script is currently not supported for use with Exchange Server 2013.

4.7.1

Resource Objects

 Exchang2007_ClientAccessServer

 Exchange2010_ClientAccessServer

4.7.2

Default Schedule

By default, this script runs every 15 minutes.

4.7.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Communicate only with

Exchange Servers in the local domain?

Ignore these Mailbox servers when testing CAS to MBS communications

Mailbox server hosting offline address books to be accessed

Select Yes to test only Exchange Servers in the same domain as the server on which you run the CAS_OABAvailability job.

When this option is unselected, certain tests for the Client Access server attempt to contact all Mailbox servers in your organization. These tests will fail if the Exchange accounts in one domain do not have access to other domains.

Leave this option unselected if you specify a Mailbox server in the Mailbox

server hosting offline address books to be accessed parameter.

Provide a comma-separated list of the host names of the Mailbox servers that you want to exclude from availability testing between the Client Access server and the Mailbox server.

Leave this option blank if you specify a Mailbox server in the Mailbox server

hosting offline address books to be accessed parameter.

By default, the OABAvailability job tests connectivity to all Mailbox servers.

Use this parameter to enable testing to one Mailbox server.

Enter the hostname of the Mailbox server computer that hosts the OABs you want to monitor. The hostname need not be fully qualified unless DNS lookup does not resolve the simple name.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the OABAvailability job fails. The default is 5.

58

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Monitor Offline Address Book Availability

Event Notification

Raise event if offline address books cannot be downloaded?

Select Yes to raise an event if the Client Access server’s offline address books cannot be downloaded. The default is Yes.

Event severity when offline address books cannot be downloaded

Set the severity level, from 1 to 40, to indicate the importance of an event in which offline address books cannot be downloaded. The default is 5.

4.8

CAS_PublicFolderAvailability

Use this Knowledge Script to monitor the accessibility of public folders on a Client Access server. This script raises an event when public folders are inaccessible.

4.8.1

Resource Objects

 Exchange2007_ClientAccessServer

 Exchange2010_ClientAccessServer

 Exchange2013_ClientAccessServer

4.8.2

Default Schedule

By default, this script runs every 15 minutes.

4.8.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

Communicate only with

Exchange Servers in the local domain?

Ignore these Mailbox servers when testing CAS to MBS communications

How to Set It

Select Yes to test only Exchange Servers in the same domain as the server on which you run the CAS_PublicFolderAvailability job.

When this option is unselected, certain tests for the Client Access server attempt to contact all Mailbox servers in your organization. These tests will fail if the Exchange accounts in one domain do not have access to other domains.

Leave this option unselected if you specify a Mailbox server in the Mailbox

server hosting public folders to be accessed parameter.

Provide a comma-separated list of the hostnames of the Mailbox servers that you want to exclude from availability testing between the Client Access server and the Mailbox server.

Leave this option blank if you specify a Mailbox server in the Mailbox server

hosting public folders to be accessed parameter.

Exchange 2007 Knowledge Scripts

59

Parameter How to Set It

Mailbox server hosting public folders to be accessed

By default, the CAS_PublicFolderAvailability job tests connectivity to all

Mailbox servers. Use this parameter to enable testing to one Mailbox server.

Enter the hostname of the Mailbox server computer that hosts the public folders you want to monitor. The hostname need not be fully qualified unless

DNS lookup does not resolve the simple name.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the CAS_PublicFolderAvailability job fails. The default is 5.

Monitor Public Folder Availability

Event Notification

Raise event if public folders are inaccessible?

Event severity when public folders are inaccessible

Select Yes to raise an event if the public folders on the Client Access server are inaccessible. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which public folders on the Client Access server are inaccessible. The default is 5.

4.9

ETS_ExternalMail

Use this Knowledge Script to monitor e-mail sent to and from your Exchange environment. This script raises an event when average mail volume for recipients, recipient domains, senders, and sending domains exceeds the threshold you set. You select whether mail volume is measured by number of messages or total size of messages in MB.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.9.1

Resource Objects

 Exchange2007_EdgeTransportServer

 Exchange2010_EdgeTransportServer

4.9.2

Default Schedule

By default, this script runs daily.

4.9.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Measure mail volume by message count or total message size

Select how this script measures the volume of mail sent to and from your

Exchange environment. Choose from Message count or Total message

size. Total message size is measured in MB.

60

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the ETS_ExternalMail job fails. The default is 5.

Monitor Recipient Domains of Outgoing Mail

Number of top recipient domains of outgoing mail

Set the top n recipient domains to be monitored for average mail volume.

The default is 10 domains, the minimum is 0, and the maximum is

2147483647.

To monitor all recipient domains for average mail volume, enter 0.

Event Notification

Raise event if average mail volume for top recipient domains exceeds threshold?

Threshold - Maximum average mail volume for top recipient domains

Select Yes to raise an event if the average mail volume for the top n recipient domains exceeds the threshold you set. The default is Yes.

Set the maximum value that average mail volume can attain before an event is raised. The default is 1000.

Event severity when average mail volume for top recipient domains exceeds threshold

Data Collection

Set the event severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n recipient domains exceeds the threshold. The default is 15.

Collect data for average mail volume for top recipient domains?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n recipient domains during the monitoring interval. The default is Yes.

Monitor Sending Domains of Incoming Mail

Number of top sending domains of incoming mail

Set the top n sending domains to be monitored for average mail volume. The default is 10 domains, the minimum is 0, and the maximum is 2147483647.

To monitor all domains for average mail volume, enter 0.

Event Notification

Raise event if average mail volume for top sending domains exceeds threshold?

Threshold - Maximum average mail volume for top sending domains

Select Yes to raise an event if the average mail volume for the top n sending domains exceeds the threshold you set. The default is Yes.

Set the maximum value that average mail volume can attain before an event is raised. The default is 1000.

Event severity when average mail volume for top sending domains exceeds threshold

Data Collection

Set the event severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n sending domains exceeds the threshold. The default is 15.

Collect data for average mail volume for top sending domains?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n sending domains during the monitoring interval. The default is Yes.

Monitor Senders of Outgoing Mail

Exchange 2007 Knowledge Scripts

61

Parameter How to Set It

Number of top senders of outgoing mail

Set the top n senders of mail to be monitored for average mail volume. The default is 10 senders, the minimum is 0, and the maximum is 2147483647.

To monitor all senders for average mail volume, enter 0.

Event Notification

Raise event if average mail volume for top senders of outgoing mail exceeds threshold?

Select Yes to raise an event if the average mail volume for the top n senders of mail exceeds the threshold you set. The default is Yes.

Threshold - Maximum average mail volume for top senders of outgoing mail

Set the maximum value that average mail volume can attain before an event is raised. The default is 1000.

Event severity when average mail volume for top senders of outgoing mail exceeds threshold

Set the event severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n senders of mail exceeds the threshold. The default is 15.

Data Collection

Collect data for average mail volume for top senders of outgoing mail?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n senders of mail during the monitoring interval. The default is Yes.

Monitor Recipients of Incoming Mail

Number of top recipients of incoming mail

Set the top n recipients of mail to be monitored for average mail volume. The default is 10 recipients, the minimum is 0, and the maximum is 2147483647.

To monitor all recipients for average mail volume, enter 0.

Event Notification

Raise event if average mail volume for top recipients of incoming mail exceeds threshold?

Select Yes to raise an event if the average mail volume for the top n recipients of mail exceeds the threshold you set. The default is Yes.

Threshold - Maximum average mail volume for top recipients of incoming mail

Set the maximum value that average mail volume can attain before an event is raised. The default is 1000.

Event severity when average mail volume for top recipients of incoming mail exceeds threshold

Set the event severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n recipients of mail exceeds the threshold. The default is 15.

Data Collection

Collect data for average mail volume for top recipients of incoming mail?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n recipients of mail during the monitoring interval. The default is Yes.

62

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.10

ETS_MessageHygiene

Use this Knowledge Script to monitor Edge Transport server message hygiene functions: whether the anti-spam update service is running, the total number of messages that have been filtered as spam, and the number of messages that have been filtered as spam from any one user. You determine which content filter to monitor.

4.10.1

Resource Objects

 Exchange2007_EdgeTransportServer

 Exchange2010_EdgeTransportServer

4.10.2

Default Schedule

By default, this script runs every hour.

4.10.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails

Monitor Anti-Spam Update Service

Event Notification

Set the severity level, from 1 to 40, to indicate the importance of an event in which the ETS_MessageHygiene job fails. The default is 5.

Raise event if anti-spam update service is not running?

Select Yes to raise an event if the anti-spam update service is not running.

The default is Yes.

Event severity when anti-spam update service is not running

The anti-spam update service provides daily updates to your content filter.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the anti-spam update service is not running. The default is 15.

Start anti-spam update service if not running?

Select Yes to start the anti-spam update service if it is not running.The default is Yes.

Threshold - Timeout for anti-spam update service to start

Set the number of seconds that AppManager should wait for the anti-spam update service to start before raising an event. The default is 60 seconds.

Raise event if anti-spam update service fails to start?

Select Yes to raise an event if AppManager cannot start the anti-spam update service. The default is Yes.

Event severity when anti-spam update service fail to start

Monitor Total Messages Filtered

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot start the anti-spam service. The default is 5.

Exchange 2007 Knowledge Scripts

63

Parameter How to Set It

Include only those messages filtered for these reasons

Provide a comma-separated list of the names of the content filters whose activity you want to monitor. The names do not need to be case-sensitive.

One of the many fields in a message is a field titled “Reason.” The content of the Reason field is the filter name you provide in this parameter.

Possible filter names are

SCLAtORAboveDeleteThreshold

,

ACLAtOrAboveRejectThreshold

,

BlockListProvide

, and

LocalBlockList

. To monitor all messages, leave this parameter blank.

NOTE: Quotation marks (“) are not supported in this field. This script returns an error if you enter quotation marks as part of a content filter name.

Event Notification

Raise event if number of filtered messages exceeds threshold?

Select Yes to raise an event if the number of filtered messages from all users exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of filtered messages

Set the maximum number of messages that can be filtered for the reason you specified in Include only those messages filtered for these reasons.

AppManager raises an event if the number of messages exceeds the threshold. The default is 1000.

Event severity when number of filtered messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of filtered messages exceeds the threshold. The default is 5.

Data Collection

Collect data for number of filtered messages?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages filtered for the reason you specified in Include only those messages filtered for these reasons. The default is No.

Monitor Worst Offenders

Include only those messages filtered for these reasons

Maximum number of worst offenders to display

Provide a comma-separated list of the names of the content filters whose activity you want to monitor. The names in the list do not need to be casesensitive.

One of the many fields in a message is a field titled “Reason.” The content of the Reason field is the filter name you provide in this parameter. To monitor all messages, leave this parameter blank.

NOTE: Quotation marks (“) are not supported in this field. This script returns an error if you enter quotation marks as part of a content filter name.

Set the maximum number of worst-offending users to include in an event.

These offenders will have sent e-mail that has been filtered as spam for the reasons you indicated in Include only those messages filtered for these

reasons.

The default is 10.

Event Notification

Raise event if number of filtered messages received from a user exceeds threshold?

Select Yes to raise an event if the number of filtered messages from any one user exceeds the threshold you set. The default is Yes.

64

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Threshold -- Maximum number of filtered messages received from a user

Set the maximum number of messages that can be filtered for the reason you specified in Include only those messages filtered for this reason.

AppManager raises an event if the number of messages from one user exceeds the threshold. The default is 100.

Event severity when number of filtered messages received from a user exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of filtered messages from any one user exceeds the threshold. The default is 15.

Data Collection

Collect data for number of filtered messages received from worst offenders?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of filtered messages that fit the following criteria:

The messages were filtered for the reasons you specified in Include

only those messages filtered for these reasons.

The messages were sent from the top n worst offending senders. You determine the value of n in Maximum number of worst offenders to

display.

The default is No.

4.11

HTS_Connectivity

Use this Knowledge Script to monitor the connectivity with a Mailbox server and to monitor the time of the last synchronization with the Edge Transport server. This script raises an event if a threshold is exceeded.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.11.1

Resource Objects

 Exchange2007_HubTransportServer

 Exchange2010_HubTransportServer

 Exchange2013_HubTransportServer

4.11.2

Default Schedule

By default, this script runs every 15 minutes.

4.11.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

How to Set It

Exchange 2007 Knowledge Scripts

65

Parameter How to Set It

Communicate only with

Exchange Servers in the local domain?

Select Yes to test only Exchange Servers in the same domain as the server on which you run the HTS_Connectivity job.

When this option is unselected, the tests attempt to contact all Mailbox servers in your organization. These tests will fail if the Exchange accounts in one domain do not have access to other domains.

Provide a comma-separated list of the hostnames of the Mailbox servers that you want to exclude from availability testing between the Hub Transport server and the Mailbox server.

Ignore these Mailbox servers when testing HTS to MBS communications

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the HTS_Connectivity job fails. The default is 5.

Monitor Mailbox Server Communication

Event Notification

Raise event if unable to communicate with a Mailbox server?

Select Yes to raise an event when the Hub Transport server cannot communicate with a Mailbox database on the Mailbox server. The default is

Yes.

The Hub Transport server transports e-mail to and from the Mailbox server.

Therefore, ensuring uninterrupted communication is vital to the health of your

Exchange Server 2007, 2010, or 2013 environment.

Threshold - Maximum number of seconds to wait before timing out

Set the maximum length of time the Hub Transport server should attempt to contact the Mailbox server before timing out and raising an event. The default is 15 seconds.

Event severity when unable to communicate with a Mailbox server

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Hub Transport server cannot communicate with a Mailbox database on the Mailbox server. The default is 5.

Monitor Edge Synchronization

Event Notification

Raise event if this Hub

Transport server is not subscribed to any Edge

Transport servers?

Select Yes to raise an event if the Hub Transport server you are monitoring is not subscribed to an Edge Transport server. AppManager cannot monitor synchronization if the Hub Transport server is not subscribed to the Edge

Transport server.

Disable this parameter if you will not monitor synchronization with the Edge

Transport server. Subscription to the Edge Transport server is not required for AppManager to monitor Mailbox server communication or connector availability.

Event severity when this Hub

Transport server is not subscribed to any Edge

Transport servers

The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Hub Transport server is not subscribed to an Edge Transport server. The default is 15.

66

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event if time of last

Edge synchronization exceeds threshold?

Select Yes to raise an event if synchronization between the Edge Transport server and the Hub Transport server has not occurred within the last n minutes. The default is Yes.

Use the Threshold - Maximum number of minutes since last Edge

synchronization parameter to determine the value of n.

Threshold - Maximum number of minutes since last Edge synchronization

Set the maximum number of minutes that can elapse since the last synchronization before an event is raised. The default is 30 minutes.

Event severity when time of last

Edge synchronization exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of minutes since the last synchronization exceeds the threshold you set. The default is 15.

4.12

HTS_SafetyNet

Use this Knowledge Script to monitor the Safety Net availability in Exchange Server 2013. It replaces the HTS_TransportDumpster Knowledge script available for Exchange Server 2007 and 2010. You can use this Knowledge Script to monitor Safety Net activities like, average safety net resubmit request time span, resubmit latency average time, resubmit request count, safety net resubmission count, safety net resubmission request count, shadow safety net resubmission count, and shadow safety net resubmission request count.

NOTE: This Knowledge Script runs only on servers with Exchange Server 2013.

4.12.1

Resource Objects

 Exchange2013_HubTransportServer

4.12.2

Default Schedule

By default, this script runs every 15 minutes.

4.12.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the HTS_SafetyNet job fails. The default is 5.

Monitor Safety Net Availability

Event Notification

Exchange 2007 Knowledge Scripts

67

Parameter How to Set It

Raise event if Safety Net is unavailable?

Event severity when Safety Net is unavailable

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Safety Net cannot be accessed. The default is 5.

Monitor Safety Net Activity

Select Yes to raise an event if the Safety Net cannot be accessed. The default is Yes.

Data Collection

Collect data for average Safety

Net resubmit request time span?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average time span of resubmit request of all e-mail messages in Safety Net during the monitoring interval. The default is No.

Collect data for resubmit latency average time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time of resubmit requests of e-mail messages in the Safety Net during the monitoring period. The default is No.

Collect data for resubmit request count?

Select Yes to collect data for charts and reports. When enabled, data collection returns the resubmit request count of e-mail messages in the

Safety Net during the monitoring interval. The default is No.

Collect data for Safety Net resubmission count?

Collect data for Safety Net resubmission request count?

Select Yes to collect data for charts and reports. When enabled, data collection returns the total resubmission count of e-mail messages in the

Safety Net during the monitoring interval. The default is No.

Select Yes to collect data for charts and reports. When enabled, data collection returns the total resubmission request count of e-mail messages in the Safety Net during the monitoring interval. The default is No

Collect data for Shadow Safety

Net resubmission count?

Select Yes to collect data for charts and reports. When enabled, data collection returns the total resubmission count of e-mail messages in the shadow Safety Net during the monitoring interval. The default is No

Collect data for Shadow Safety

Net resubmission request count?

Select Yes to collect data for charts and reports. When enabled, data collection returns the total resubmission request count of e-mail messages in the shadow Safety Net during the monitoring interval. The default is No

4.13

HTS_SendersAndRecipients

Use this Knowledge Script to measure average and individual e-mail volume for senders and recipients. This script raises an event if the number of messages or the total size in MB of all messages exceeds the threshold you set.

4.13.1

Resource Objects

 Exchange2007_HubTransportServer

 Exchange2010_HubTransportServer

 Exchange2013_HubTransportServer

4.13.2

Default Schedule

By default, this script runs every one hour.

68

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.13.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Measure mail volume by message count or total message size

Select how this script measures the volume of mail sent to and from your

Exchange environment. Choose from Message count or Total message

size. Total message size is measured in MB. The default is Message count.

Comma-separated list of senders and recipients to ignore

Provide a list of e-mail addresses that this script should ignore when measuring e-mail volume. Separate multiple addresses with a comma.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the HTS_SendersAndRecipients job fails. The default is 5.

Monitor Recipients of Internal Mail

Monitor Average Mail Volume for Recipients of Internal Mail

Number of top recipients to monitor for average volume

Set the top n e-mail recipients whose average internal mail volume you want to monitor. The default is 10 recipients, the minimum is 0, and the maximum is 2147483647.

To monitor all recipients for average volume, enter 0.

Event Notification

Raise event if average volume for top recipients of internal mail exceeds threshold?

Select Yes to raise an event if the average mail volume for the top n recipients exceeds the threshold you set. The default is Yes.

Threshold - Maximum average volume for top recipients of internal mail

Set the maximum value that average mail volume can attain before an event is raised. The default is 250.

Use the Measure mail volume by message count or total message size parameter to indicate whether the threshold is in number of messages or

Megabytes of message.

Event severity when average volume for top recipients of internal mail exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n recipients exceeds the threshold.

The default is 15.

Collect data for average volume of top recipients of internal mail?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n recipients during the monitoring interval. The default is Yes.

Monitor Individual Mail Volume for Recipients of Internal Mail

Number of top recipients to monitor for individual volume

Set the top n e-mail recipients whose individual internal mail volume you want to monitor. The default is 10 recipients, the minimum is 0, and the maximum is 2147483647.

To monitor all recipients for individual volume, enter 0.

Event Notification

Exchange 2007 Knowledge Scripts

69

Parameter How to Set It

Raise event if mail volume for top individual recipients exceeds threshold?

Select Yes to raise an event if the individual mail volume for the top n recipients exceeds the threshold you set. The default is Yes.

Threshold - Maximum mail volume for individual recipients

Set the maximum value that individual mail volume can attain before an event is raised. The default is 250.

Use the Measure mail volume by message count or total message size parameter to indicate whether the threshold is in number of messages or

Megabytes of message.

Event severity when mail volume for individual recipients exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which individual mail volume for the top n recipients exceeds the threshold.

The default is 15.

Data Collection

Collect data for mail volume for individual recipients?

Select Yes to collect data for charts and reports. When enabled, data collection returns the individual mail volume for the top n recipients during the monitoring interval. The default is No.

Monitor Senders of Internal Mail

Monitor Average Mail Volume for Senders of Internal Mail

Number of top senders to monitor for average volume

Set the top n e-mail senders whose average internal mail volume you want to monitor. The default is 10 senders, the minimum is 0, and the maximum is

2147483647.

To monitor all senders for average volume, enter 0.

Event Notification

Raise event if average volume for top senders of internal mail exceeds threshold?

Select Yes to raise an event if the average mail volume for the top n senders exceeds the threshold you set. The default is Yes.

Threshold - Maximum average volume for top senders of internal mail

Set the maximum value that average mail volume can attain before an event is raised. The default is 50.

Use the Measure mail volume by message count or total message size parameter to indicate whether the threshold is in number of messages or

Megabytes of message.

Event severity when average volume for top senders of internal mail exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which average mail volume for the top n senders exceeds the threshold. The default is 15.

Data Collection

Collect data for average volume of top senders of internal mail?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average mail volume for the top n senders during the monitoring interval. The default is Yes.

Monitor Individual Mail Volume for Senders of Internal Mail

Number of top senders to monitor for individual volume

Set the top n e-mail senders whose individual internal mail volume you want to monitor. The default is 10 senders, the minimum is 0, and the maximum is

2147483647.

To monitor all senders for individual volume, enter 0.

Event Notification

70

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event if mail volume for top individual senders exceeds threshold?

Select Yes to raise an event if the individual mail volume for the top n senders exceeds the threshold you set. The default is Yes.

Threshold - Maximum mail volume for individual senders

Set the maximum value that individual mail volume can attain before an event is raised. The default is 50.

Event severity when mail volume for individual senders exceeds threshold

Use the Measure mail volume by message count or total message size parameter to indicate whether the threshold is in number of messages or

Megabytes of message.

Set the severity level, from 1 to 40, to indicate the importance of an event in which individual mail volume for the top n senders exceeds the threshold.

The default is 15.

Data Collection

Collect data for mail volume for individual senders?

Select Yes to collect data for charts and reports. When enabled, data collection returns the individual mail volume for the top n senders during the monitoring interval. The default is No.

4.14

HTS_TransportDumpster

Use this Knowledge Script to monitor Transport Dumpster availability, the number and size of items in the Transport Dumpster, and activity:

 Rate at which items are inserted into the Transport Dumpster

 Rate at which items are deleted from the Transport Dumpster

 Number of items redelivered by the Transport Dumpster

The Transport Dumpster is a container in which recently delivered e-mail is stored. It allows the Hub

Transport server to defer the deletion of e-mail so that it can redeliver e-mail after an unscheduled outage.

NOTE: This Knowledge Script is available only for Exchange Server 2007 and 2010. For Exchange

Server 2013, see Section 4.12, “HTS_SafetyNet,” on page 67

.

4.14.1

Resource Objects

 Exchange2007_HubTransportServer

 Exchange2010_HubTransportServer

4.14.2

Default Schedule

By default, this script runs every 15 minutes.

Exchange 2007 Knowledge Scripts

71

4.14.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the HTS_TransportDumpster job fails. The default is 5.

Monitor Transport Dumpster Availability

Event Notification

Raise event if Transport

Dumpster is unavailable?

Event severity when Transport

Dumpster is unavailable

Select Yes to raise an event if the Transport Dumpster cannot be accessed.

The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Transport Dumpster cannot be accessed. The default is 5.

Monitor Size of Transport Dumpster

Data Collection

Collect data for number of items in Transport Dumpster?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of e-mail messages in the Transport Dumpster during the monitoring interval. The default is No.

Collect data for total size of items currently in Transport

Dumpster?

Select Yes to collect data for charts and reports. When enabled, data collection returns the size of all e-mail messages in MB in the Transport

Dumpster during the monitoring interval. The default is No.

Monitor Transport Dumpster Activity

Data Collection

Collect data for item insertion rate?

Collect data for item deletion rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the rate at which e-mail messages were inserted in the

Transport Dumpster during the monitoring interval. The default is No.

Select Yes to collect data for charts and reports. When enabled, data collection returns the rate at which e-mail messages were deleted from the

Transport Dumpster during the monitoring interval. The default is No.

Collect data for item redelivery count?

Select Yes to collect data for charts and reports. When enabled, data collection returns the rate at which e-mail messages were redelivered from the Transport Dumpster during the monitoring interval. The default is No.

4.15

MBS_ClientActivity

In Exchange Server 2013, the performance counters for Client Access Server (CAS) activity is available only from Mailbox Server. Use this Knowledge Script to monitor Exchange Server 2013

Mailbox server services and functions:

 Availability Service activity

 ActiveSync response time and request rate

 Outlook Web Access response time, search time, login rate, and login failures

72

NetIQ AppManager for Microsoft Exchange Server Management Guide

 Outlook Web Services request rate and current connections

 IMAP4 (Internet Message Access protocol) processing time, current connections, and active

SSL connections

 POP3 (Post Office Protocol) processing time, login rate, current connections, and active SSL connections

NOTE: This Knowledge script only runs on servers with Exchange Server 2013. This script replaces the CAS_Activity Knowledge script available for Exchange Server 2007 and 2010.

4.15.1

Resource Objects

 Exchange2013_MailboxServer

4.15.2

Default Schedule

By default, this script runs every 15 minutes.

4.15.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_ClientActivity job fails. The default is 5.

Monitor Availability Service Activity

Event Notification

Raise event if response time for free/busy requests exceeds threshold?

Select Yes to raise an event if the response time for free and busy requests to Microsoft Outlook exceeds the threshold you set. The default is Yes.

The Availability Service monitors free/busy requests.

Threshold - Maximum free/busy request response time

Event severity when response time for free/busy requests exceeds threshold

Set the maximum length of time that Microsoft Outlook can take to respond to free/busy requests before an event is raised. The default is 5000 milliseconds.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the response time for free/busy requests exceeds the threshold.

The default is 15.

Data Collection

Collect data for free/busy request response time?

Select Yes to collect data for charts and reports on the response time for free/busy requests. When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

Monitor ActiveSync Activity

Monitor ActiveSync Response Time

Exchange 2007 Knowledge Scripts

73

Parameter How to Set It

Event Notification

Raise event if ActiveSync response time exceeds threshold?

Threshold - Maximum response time

Event severity when response time exceeds threshold

Select Yes to raise an event if the response time for ActiveSync exceeds the threshold you set. The default is Yes.

Set the maximum length of time that ActiveSync can take to respond to requests before an event is raised. The default is 100 milliseconds.

Set the severity level, from 1 to 40, to indicate the importance of an event in which ActiveSync response time exceeds the threshold. The default is

15.

Data Collection

Collect data for response time?

Monitor ActiveSync Request Rate

Event Notification

Select Yes to collect data for charts and reports on ActiveSync response time. When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

Raise event if ActiveSync request rate exceeds threshold?

Select Yes to raise an event if the rate of synchronization requests to

ActiveSync exceeds the threshold you set. The default is Yes.

Threshold - Maximum request rate Set the maximum number of requests that can occur per second before an event is raised. The default is 10 synchronization requests per second.

Event severity when request rate exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the ActiveSync request rate exceeds the threshold. The default is

15.

Data Collection

Collect data for request rate?

Select Yes to collect data for charts and reports on ActiveSync request time. When enabled, data collection returns the rate of synchronization requests during the monitoring interval. The default is No.

Monitor Outlook Web Access Activity

Monitor Outlook Web Access Response Time

Event Notification

Raise event if Outlook Web

Access response time exceeds threshold?

Select Yes to raise an event if the response time for Outlook Web Access

(OWA) exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time

Event severity when response time exceeds threshold

Set the maximum amount of time that it can take for OWA to respond to requests before an event is raised. The default is 100 milliseconds.

Set the severity level, from 1 to 40, to indicate the importance of an event in which OWA response time exceeds the threshold. The default is 15.

Data Collection

Collect data for response time?

Select Yes to collect data for charts and reports on the response time of

OWA. When enabled, data collection returns the length of response time during the monitoring interval. The default is No.

Monitor Outlook Web Access Search Time

74

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event Notification

Raise event if Outlook Web

Access search time exceeds threshold?

Select Yes to raise an event if Outlook Web Access (OWA) search time exceeds the threshold. The default is Yes.

The OWA search feature allows users to find items in a mailbox.

Threshold - Maximum search time Set the maximum length of time that OWA can spend performing a search before an event is raised. The default is 100 milliseconds.

Event severity when search time exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which OWA search time exceeds the threshold. The default is 15.

Collect data for search time?

Select Yes to collect data for charts and reports on Outlook Web Access

(OWA) search time. When enabled, data collection returns the length of search time during the monitoring interval. The default is No.

Monitor Outlook Web Access Login Rate

Event Notification

Raise event if login rate exceeds threshold?

Select Yes to raise an event if the rate at which users log in to Outlook Web

Access (OWA) exceeds the threshold. The default is Yes.

Threshold - Maximum login rate Set the maximum rate at which users can log in to OWA before an event is raised. The default is 10 logins per second.

Event severity when login rate exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the rate at which users log in to OWA exceeds the threshold. The default is 15.

Data Collection

Collect data for login rate?

Select Yes to collect data for charts and reports on the rate at which users log in to OWA. When enabled, data collection returns the OWA log in rate for the monitoring interval. The default is No.

Monitor Outlook Web Access Login Failures

Event Notification

Raise event if login failures exceed threshold?

Select Yes to raise an event if the failures for logging in to Outlook Web

Access (OWA), expressed as a percentage of all login attempts, exceed the threshold. The default is Yes.

Threshold - Maximum percentage of login failures

Set the maximum percentage of OWA login failures that can occur before an event is raised. The default is 10%.

Event severity when login failures exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which percentage of OWA login failures exceeds the threshold. The default is 15.

Data Collection

Collect data for login failures?

Select Yes to collect data for charts and reports on the percentage of OWA login failures. When enabled, data collection returns the percentage of

OWA login failures for the monitoring interval. The default is No.

Monitor Outlook Web Services Activity

Monitor Outlook Web Services Request Rate

Exchange 2007 Knowledge Scripts

75

Parameter How to Set It

Event Notification

Raise event if Outlook Web

Services request rate exceeds threshold?

Select Yes to raise an event if the rate of requests to Outlook Web

Services exceeds the threshold you set. The default is Yes.

Threshold - Maximum request rate Set the maximum number of requests that can occur per second before an event is raised. The default is 10 requests per second.

Event severity when request rate exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the rate of requests to Outlook Web Services exceeds the threshold. The default is 15.

Data Collection

Collect data for request rate?

Select Yes to collect data for charts and reports on the rate of requests to

Outlook Web Services. When enabled, data collection returns the rate of requests during the monitoring interval. The default is No.

Monitor Outlook Web Services Current Connections

Event Notification

Raise event if number of current connections exceeds threshold?

Select Yes to raise an event if the number of connections established with

Outlook Web Services exceeds the threshold you set. The default is Yes.

By knowing the number of current connections, you can determine user load for Outlook Web Services.

Threshold - Maximum number of current connections

Set the maximum number of connections to Outlook Web Services that can be established before an event is raised. The default is 25 connections.

Event severity when number of current connections exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of connections established with Outlook Web Services exceeds the threshold. The default is 15.

Collect data for number of current connections?

Select Yes to collect data for charts and reports on the number of connections established with Outlook Web Services. When enabled, data collection returns the number of connections established during the monitoring interval. The default is No.

Monitor IMAP4 Activity

Monitor IMAP4 Command Processing Time

Event Notification

Raise event if command processing time exceeds threshold?

Select Yes to raise an event if the amount of processing time for IMAP4 commands exceeds the threshold you set. The default is Yes.

Threshold - Maximum command processing time

Set the maximum amount of time that can be spent processing IMAP4 commands before an event is raised. The default is 100 milliseconds.

Event severity when command processing time exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of processing time for IMAP4 commands exceeds the threshold. The default is 15.

76

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Collect data for command processing time?

Monitor IMAP4 Connections Rate

Select Yes to collect data for charts and reports on the amount of processing time for IMAP4 commands. When enabled, data collection returns the amount of processing time spent during the monitoring interval.

The default is No.

Event Notification

Raise event if connections rate exceeds threshold?

Select Yes to raise an event if the number of IMAP4 connections to your

Exchange server exceeds the threshold you set. The default is Yes.

Threshold - Maximum connections rate

Set the maximum number of IMAP4 connection requests that can occur per second before an event is raised. The default is 10 connections per second.

Event severity when connections rate exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4 connection requests exceeds the threshold.

The default is 15.

Data Collection

Collect data for connections rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of IMAP4 connection requests for the monitoring intervals. The default is No.

Monitor IMAP4 Current Connections

Event Notification

Raise event if number of current connections exceeds threshold?

Select Yes to raise an event if the number of current IMAP4 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of current connections

Set the maximum number of IMAP4 connections that can be established before an event is raised. The default is 10 connections.

Event severity when number of current connections exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4 connections exceeds the threshold. The default is 15.

Collect data for number of current connections?

Select Yes to collect data for charts and reports on number of IMAP4 connections established. When enabled, data collection returns the number of IMAP4 connections established during the monitoring interval.

The default is No.

Monitor IMAP4 Active SSL Connections

Event Notification

Raise event if number of active

SSL connections exceeds threshold?

Select Yes to raise an event if the number of current IMAP4 connections to your Exchange server over SSL (Secure Sockets Layer) exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of active SSL connections

Set the maximum number of IMAP4 connections that can be established over SSL before an event is raised. The default is 50 connections.

Event severity when number of active SSL connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of IMAP4 SSL connections exceeds the threshold.

The default is 15.

Exchange 2007 Knowledge Scripts

77

Parameter How to Set It

Data Collection

Collect data for number of active

SSL connections?

Select Yes to collect data for charts and reports on the IMAP4 connections that can be established over SSL. When enabled, data collection returns the number of IMAP4 SSL connections established during the monitoring interval. The default is No.

Monitor POP3 Activity

Monitor POP3 Command Processing Time

Event Notification

Raise event if command processing time exceeds threshold?

Select Yes to raise an event if the amount of processing time for POP3 commands exceeds the threshold you set. The default is Yes.

Threshold - Maximum command processing time

Set the maximum amount of time that can be spent processing POP3 commands before an event is raised. The default is 10 milliseconds.

Event severity when command processing time exceeds threshold

Data Collection

Collect data for command processing time?

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of processing time for POP3 commands exceeds the threshold. The default is 15.

Select Yes to collect data for charts and reports on the processing time for

POP3 commands. When enabled, data collection returns the amount of processing time spent during the monitoring interval. The default is No.

Monitor POP3 Connections Rate

Event Notification

Raise event if connections rate exceeds threshold?

Select Yes to raise an event if the number of POP3 connections to your

Exchange server exceeds the threshold you set. The default is Yes.

Threshold - Maximum connections rate

Set the maximum number of POP3 connection requests that can occur per second before an event is raised. The default is 10 connections per second.

Event severity when connections rate exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3 connection requests exceeds the threshold.

The default is 15.

Data Collection

Collect data for connections rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of POP3 connection requests for the monitoring intervals. The default is No.

Monitor Current POP3 Current Connections

Event Notification

Raise event if number of current connections exceeds threshold?

Select Yes to raise an event if the number of current POP3 connections to your Exchange server exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of current connections

Set the maximum number of POP3 connections that can be established before an event is raised. The default is 10 connections.

78

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when number of current connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3 connections that are currently established exceeds the threshold. The default is 15.

Data Collection

Collect data for number of current connections?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of POP3 connections established during the monitoring interval. The default is No.

Monitor POP3 Active SSL Connections

Event Notification

Raise event if number of active

SSL connections exceeds threshold?

Select Yes to raise an event if the number of current POP3 connections to your Exchange server over SSL (Secure Sockets Layer) exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of active SSL connections

Set the maximum number of POP3 connections that can be established over SSL before an event is raised. The default is 25 connections.

Event severity when number of active SSL connections exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of POP3 SSL connections exceeds the threshold. The default is 15.

Data Collection

Collect data for number of active

SSL connections?

Select Yes to collect data for charts and reports on POP3 SSL connections. When enabled, data collection returns the number of POP3

SSL connections established during the monitoring interval. The default is

No.

4.16

MBS_ClientConnectivity

Use this Knowledge Script to monitor the connectivity of Mailbox server (MBS) services on Exchange

Server 2013: ActiveSync, Outlook Web services, and the Autodiscover service. This script raises an event when a connectivity test fails and when response time exceeds the threshold you set.

NOTE: This Knowledge Script runs only on servers with Exchange Server 2013.

4.16.1

Running MBS_ClientConnectivity on a Mailbox Server

When you run the MBS_ClientConnectivity Knowledge Script on a Mailbox server, the script automatically creates a test user mailbox on each Mailbox server in the Exchange deployment if those mailboxes do not already exist.

You can also manually create the test user mailboxes on the Exchange 2013 Mailbox Servers.

To create test user mailboxes on an Exchange 2013 Mailbox Server:

1

Log in to one of the Exchange 2013 Mailbox Servers and open the Exchange Management

Shell.

2

Change directories to the Scripts directory under the Microsoft Exchange installation directory.

Exchange 2007 Knowledge Scripts

79

3

Run the following command:

Get-MailboxServer | .\New-TestCasConnectivityUser.ps1

.

4

Follow the on-screen instructions to create the test user mailbox on each Mailbox server.

4.16.2

Resource Objects

 Exchange2013_MailboxServer

4.16.3

Default Schedule

By default, this script runs every 30 minutes.

4.16.4

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_ClientConnectivity job fails. The default is 5.

Connectivity Test User

Configuration

Use alternate test mailbox configured in Security Manager?

Select Yes to use the test mailbox that you have specified in the Security

Manager. The defaut is No.

Create default test mailbox on

Mailbox servers automatically?

Select Yes to create a default test mailbox automatically. The default is Yes.

Create non-existent test mailboxes every N job iterations

(specify N)

Specify the number of job iterations for which the non-existent test mailboxes will be created on the Mailbox server. The default is 1.

Monitor ActiveSync Connectivity

ActiveSync URL to be used in connectivity test

Specify the URL for the ActiveSync that is used to monitor the connectivity in the following format: https://localhost:<port>/Microsoft-

Server-ActiveSync .

Event Notification

Raise event if ActiveSync connectivity test fails?

Select Yes to raise an event if AppManager cannot check connectivity to

ActiveSync. The default is Yes.

Event severity when ActiveSync connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to ActiveSync. The default is

5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to

ActiveSync exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait for connectivity with ActiveSync before raising an event. The default is 10000 milliseconds.

80

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time it takes to connect to ActiveSync exceeds the threshold that you set. The default is 15.

Data Collection

Collect data for ActiveSync response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to ActiveSync.

The default is No.

Monitor Outlook Web Services Connectivity

Event Notification

Select Yes to raise an event if AppManager cannot check connectivity to

Outlook Web services. The default is Yes.

Raise event if Outlook Web services connectivity test fails?

Event severity when Outlook

Web services connectivity test fails

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to Outlook Web services. The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to

Outlook Web services exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait to confirm connectivity with Outlook

Web services before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time taken for testing connectivity to Outlook Web services exceeds the threshold that you set. The default is 15.

Data Collection

Collect data for Outlook Web services response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to Outlook Web services. The default is No.

Monitor Autodiscover Service Connectivity

Event Notification

Raise event if Autodiscover service connectivity test fails?

Event severity when

Autodiscover service connectivity test fails

Select Yes to raise an event if AppManager cannot check connectivity to the

Autodiscover service. The default is Yes.

The Autodiscover service allows Outlook clients and mobile devices to be recognized when they connect to the Mailbox server.

Set the severity level, from 1 to 40, to indicate the importance of an event in which AppManager cannot check connectivity to the Autodiscover service.

The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to the

Autodiscover service exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for connectivity test

Set how long AppManager should wait to confirm connectivity with the

Autodiscover service before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time taken for testing connectivity to the Autodiscover service exceeds the threshold that you set. The default is 15.

Exchange 2007 Knowledge Scripts

81

Parameter

Data Collection

Collect data for Autodiscover service response time?

How to Set It

Select Yes to collect data for charts and reports. When enabled, data collection returns the average response time for connecting to the

Autodiscover service. The default is No.

4.17

MBS_ClusterOwner

Use this Knowledge Script to determine whether an Exchange Server is the owner of a node. This script raises an event if the selected server is not the node owner and if the selected Clustered

Mailbox Server (CMS) is down.

NOTE: This script only runs on servers with Exchange Server 2007.

4.17.1

Resource Object

Exchange2007_MailboxServer

4.17.2

Default Schedule

By default, this script runs every five minutes.

4.17.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_ClusterOwner job fails. The default is 5.

Monitor Node Ownership

Raise event if not node owner?

Event severity when not node owner

Select Yes to raise an event if the selected Exchange Server is not the owner of its node. The default is No.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the selected Exchange Server is not the owner of the node. The default is 20.

Data Collection

Collect data for ownership status?

Select Yes to collect data for charts and reports. When enabled, data collection returns “0” when the server is not the node owner and “100” if the server is the node owner. The default is Yes.

Monitor Node State

Event Notification

82

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event when node is down?

Event severity when node is down

Select Yes to raise an event if the node in which the Exchange Server resides is down. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the node in which the Exchange Server resides is down. The default is

5.

Raise event if CMS is down?

Select Yes to raise an event if the Clustered Mailbox Server (CMS) on which the Exchange Server resides is down. The default is Yes.

Event severity when CMS is down

Set the severity level, from 1 to 40, to indicate the importance of an event in which the CMS on which the Exchange Server resides is down. The default is 5.

4.18

MBS_DatabaseStateChange

Use this Knowledge Script to monitor changes in the database state, such as active, passive, or suspended, of the mailbox databases on an Exchange Server in a database availability group (DAG) or an Exchange Virtual Server (EVS). This script raises an event if a database is in a specified state, or moves into a specified state.

A job executed on a database in an Exchange Server 2010 DAG causes the job to run on all servers in the DAG. However, only the server that currently owns the database monitors that database.

NOTE

 Exchange Server 2010 and 2013 do not use storage groups.

 If you run the MBS_DataBaseStateChange Knowledge Script on an Exchange 2007 server, you can only use the database mount parameters found under the Monitor Database Mount State heading on the Values tab. If you run the script on an Exchange 2010 or 2013 server, you can use all the parameters on the Values tab.

4.18.1

Resource Objects

 Exchange2007_MailboxServer

 Exchange2007_Store_Database

 Exchange2007_Store_PFDatabase

 Exchange2010_MailboxServer

 Exchange2010_Store_Database

 Exchange2010_Store_PFDatabase

 Exchange2010_DAG_Databases

 Exchange2013_MailboxServer

 Exchange2013_Store_Database

 Exchange2013_Store_PFDatabase

 Exchange2013_DAG_Databases

Exchange 2007 Knowledge Scripts

83

4.18.2

Default Schedule

By default, this script runs every 15 minutes.

4.18.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_DatabaseStateChange job fails. The default is 5.

Monitor Database Mount State

Event Notification

Raise event if database is unmounted?

Raise event only when database first becomes unmounted?

Select Yes to raise an event if a database is unmounted. When a database is unmounted, the Exchange Server cannot store information in it or read information from it. The default is Yes.

Select Yes to raise an event only when the database first becomes unmounted. The default is Yes.

Event severity when database is or becomes unmounted

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database is or becomes unmounted. The default is 5.

Data Collection

Collect data for database mount state?

Click Yes to collect data for charts and reports. When enabled, data collection returns the mount status for each monitored mailbox and public folder database. A mounted mailbox or database has a value of 100, while an umounted mailbox or database has a value of 0. The default is No.

Automatically mount database if it is currently unmounted?

Select Yes to automatically mount a database that is currently unmounted.

The default is No.

Raise event if database is successfully remounted?

Select Yes to raise an event when the database has been successfully remounted. The default is No.

Event severity when database is successfully remounted

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database has been successfully remounted. The default is 25.

Raise event if database fails to mount?

Event severity when database fails to mount

Select Yes to raise an event if the database you want to automatically mount fails to mount. The default is no.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database you want to automatically mount fails to mount. The default is 5.

Monitor Database Copy State

Event Notification

Raise event if database copy is suspended?

Select Yes to raise an event if the process of copying a database is suspended. The default is Yes.

84

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event only when database first becomes suspended?

Select Yes to raise an event only when the database first becomes suspended. The default is Yes.

Event severity when database is or becomes suspended

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database is or becomes suspended. The default is 15.

Raise event if database copy is removed from server?

Select Yes to raise an event if a copy of the database is removed. The default is Yes.

Event severity when database copy is removed from the server.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database is removed from the server. The default is 15.

Monitor Database Active/Passive State

Event Notification - Database Instances

Raise event if database is passive?

Select Yes to raise an event if a database is passive. The default is Yes.

Raise event only when database first becomes passive?

Select Yes to raise an event only when the database first becomes passive.

The default is Yes.

Event severity when database is or becomes passive

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database is or becomes passive. The default is 25.

Raise event if database is active?

Select Yes to raise an event if a database is active. The default is Yes.

Raise event only when database first becomes active?

Select Yes to raise an event only when the database first becomes active.

The default is Yes.

Event severity when database is or becomes active

Set the severity level, from 1 to 40, to indicate the importance of an event in which the database is or becomes active. The default is 25.

Event Notification - Database Collection

Raise event if more than N databases are active?

Select Yes to raise an event if more than the specified number of databases are active. The default is Yes.

Raise event only when more than N databases become active?

Select Yes to raise an event only when more than the specified number of databases become active. The default is Yes.

Event severity when more than

N databases are or become active

Set the severity level, from 1 to 40, to indicate the importance of an event in which more than the specified number of databases are or become active.

The default is 15.

Threshold - Maximum number of active databases

Raise event if less than N databases are active?

Set the highest number of databases that can be active before an event is raised. The default is 3.

Select Yes to raise an event if less than the specified number of databases are active. The default is Yes.

Raise event only when less than

N databases become active?

Select Yes to raise an event only when less than the specified number of databases become active. The default is Yes.

Event severity when less than N databases are or become active

Set the severity level, from 1 to 40, to indicate the importance of an event in which less than the specified number of databases are or become active.

The default is 15.

Exchange 2007 Knowledge Scripts

85

Parameter How to Set It

Threshold - Minimum number of active databases

Set the lowest number of databases that can be active before an event is raised. The default is 1.

4.19

MBS_DatabaseStatus

Use this Knowledge Script to monitor mailbox databases for the size of online maintenance window, defragmentation time, free log space, free file space, and number of mailboxes. This script raises an event if a monitored value exceeds or falls below the threshold you set. In addition, this script generates data streams for number of mailboxes in a mailbox database and number of mailboxes in a storage group.

A job executed on a database in an Exchange Server 2010 and 2013 DAG cause the job to run on all servers in the DAG. However, only the server that currently owns the database monitors that database.

NOTE: Exchange Server 2010 and 2013 do not use storage groups.

4.19.1

Prerequisite

To run this Knowledge Script on clustered servers, run the AppManager agent as a domain account with Administrator privileges.

4.19.2

Resource Objects

 Exchange2007_Store_Group

 Exchange2007_Store_Database

 Exchange2007_MailboxServer

 Exchange2007_Store_PFDatabase

 Exchange2010_MailboxServer

 Exchange2010_Store_Database

 Exchange2010_Store_PFDatabase

 Exchange2010_DAG_Databases

 Exchange2013_MailboxServer

 Exchange2013_Store_Database

 Exchange2013_Store_PeFDatabas

 Exchange2013_DAG_Databases

4.19.3

Default Schedule

By default, this script runs every 15 minutes.

86

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.19.4

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_DatabaseStatus job fails. The default is 5.

Monitor Database Defragmentation

Monitor Size of Online Maintenance Window

Event Notification

Raise event if online maintenance window is too small or too large?

Select Yes to raise an event if online defragmentation occurs too often or not often enough. The default is Yes.

You want to ensure that defragmentation of Exchange database occurs often enough, but not too often. Microsoft recommends every 14 days. If you find that defragmentation takes less time, you can shorten your maintenance window.

This script compares the values of two Performance Counters to determine whether the size of the maintenance window should be changed:

Online Defrag Pages Freed/Sec

Online Defrag Pages Read/Sec

If the read-to-freed ratio is greater than 100:1, then this script raises an event indicating that the size of the maintenance window is too large and should be reduced.

If the read-to-freed ratio is less than 50:1, then this script raises an event indicating that the size of the maintenance window is too small and should be increased.

Event severity when online maintenance window is too small or too large

Monitor Defragmentation Time

Set the severity level, from 1 to 40, to indicate the importance of an event in which the maintenance window is too small or too large. The default is 15.

Event Notification

Raise event if time to defragment database exceeds threshold?

Select Yes to raise an event if the amount of time it takes to defragment a database exceeds the threshold you set. The default is Yes.

Threshold - Maximum database defragmentation time

Set the maximum length of time allowed for defragmentation before an event is raised. The default is 10 hours.

Event severity when time to defragment database exceeds threshold

Monitor Disk Space

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time it takes to defragment a database exceeds the threshold. The default is 15.

Event Notification

Exchange 2007 Knowledge Scripts

87

Parameter How to Set It

Raise event if free space for database files falls below threshold?

Select Yes to raise an event if the amount of disk space available for database files falls below the threshold you set. The default is Yes.

Threshold - Minimum free disk space for database files

Set the minimum amount of disk space that must be available for database files to prevent an event from being raised. The default is 1024 MB.

Event severity when free disk space for database files falls below threshold

Raise event if free space for log files falls below threshold?

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of disk space available for database files falls below the threshold. The default is 5.

Select Yes to raise an event if the amount of disk space available for log files falls below the threshold you set. The default is Yes.

Threshold - Minimum free disk space for log files

Set the minimum amount of disk space that must be available for log files to prevent an event from being raised. The default is 1024 MB.

Event severity when free disk space for log files falls below threshold

Monitor Mailbox Count

Set the severity level, from 1 to 40, to indicate the importance of an event in which the amount of disk space available for log files falls below the threshold. The default is 5.

Monitor Number of Mailboxes Per Storage Group (Exchange 2007 only)

Event Notification

Raise event if number of mailboxes in a storage group exceeds threshold?

Select Yes to raise an event if the number of mailboxes in a storage group exceeds the threshold you set. The default is Yes.

A storage group is a logical container only for Exchange Server 2007 databases and their associated system and transaction log files. Exchange

Server 2010 and 2013 do not use storage groups.

Threshold - Maximum number of mailboxes in a storage group

Set the maximum number of mailboxes that can be in a storage group before an event is raised. The default is 2500 mailboxes.

Event severity when number of mailboxes in a storage group exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of mailboxes in a storage group exceeds the threshold.

The default is 15.

Data Collection

Collect data for number of mailboxes in each storage group?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of mailboxes in a storage group during the monitoring period. The default is No.

Monitor Number of Mailboxes Per Mailbox Database

Event Notification

Raise event if number of mailboxes in a mailbox database exceeds threshold?

Select Yes to raise an event if the number of mailboxes in a database exceeds the threshold you set. The default is Yes.

A database stores data, data definitions, indexes, checksums, flags, and other information associated with user mailboxes or public folders.

Threshold - Maximum number of mailboxes in a mailbox database

Set the maximum number of mailboxes that can be in a database before an event is raised. The default is 1000 mailboxes.

88

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when number of mailboxes in a mailbox database exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of mailboxes in a database exceeds the threshold. The default is 15.

Data Collection

Collect data for number of mailboxes in each mailbox database?

Monitor Disk Activity and Usage

Data Collection

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of mailboxes in a database during the monitoring period. The default is No.

Collect data for percentage of elapsed time that the disk was busy servicing read and write requests?

Select Yes to collect data for charts and reports. When enabled, data collection returns the percentage of time that was spent servicing disk reads and disk writes during the monitoring period. The default is No.

Collect data for percentage of elapsed time that the disk was busy servicing read requests?

Collect data for percentage of elapsed time that the disk was busy servicing write requests?

Select Yes to collect data for charts and reports. When enabled, data collection returns the percentage of time that was spent servicing disk reads during the monitoring period. The default is No.

Select Yes to collect data for charts and reports. When enabled, data collection returns the percentage of time that was spent servicing disk writes during the monitoring period. The default is No.

Collect data for average number of both read and write requests that were queued for the disk during the sample interval?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of read and write requests queued for servicing during the monitoring period. The default is No.

4.20

MBS_MailboxAccessibility

Use this Knowledge Script to monitor whether the Mailbox server can access specified mailboxes.

This script raises an event if the time it takes to connect to a mailbox exceeds the threshold you set.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.20.1

Resource Objects

 Exchange2007_MailboxServer

 Exchange2007_Store_Group

 Exchange2007_Store_Database

 Exchange2010_MailboxServer

 Exchange2013_MailboxServer

4.20.2

Default Schedule

By default, this script runs every 15 minutes.

Exchange 2007 Knowledge Scripts

89

4.20.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_MailboxAccessibility job fails. The default is 5.

Monitor Mailbox Accessibility

Name of mailbox to be accessed Provide the name of the mailbox or the mailbox’s SMTP address. For example, a mailbox name, symadmin

, or an SMTP address, [email protected]

.

Event Notification

Raise event if the mailbox cannot be accessed?

Select Yes to raise an event if the Mailbox server cannot access the specified mailbox. The default is Yes.

A mailbox is inaccessible when it does not exist.

Event severity when the mailbox cannot be accessed

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Mailbox server cannot access the specified mailbox. The default is

5.

Raise event if response time for accessing the mailbox exceeds threshold?

Select Yes to raise an event if the amount of time it takes to connect to the specified mailbox exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time for accessing the mailbox

Set the maximum length of time that the Mailbox server should wait to connect with the specified mailbox before raising an event. The default is

1000 milliseconds. The minimum is 1 milliseconds.

Event severity when response time exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the time it takes to access the specified mailbox exceeds the threshold you set. The default is 15.

Data Collection

Collect data for mailbox access response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the response time for mailbox access during the monitoring period. The default is No.

4.21

MBS_MailboxUsage

Use this Knowledge Script to measure the size of mailboxes by either the number of messages in the mailbox, or by total message size in MB. You can monitor average mailbox size and individual mailbox size for the top n mailboxes. This script raises an event if average mailbox size and individual mailbox size exceed the threshold you set.

A job executed on a database in an Exchange Server 2010 and 2013 DAG cause the job to run on all servers in the DAG. However, only the server that currently owns the database monitors that database.

90

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.21.1

Resource Objects

 Exchange2007_MailboxServer

 Exchange2007_Store_Group

 Exchange2007_Store_Database

 Exchange2010_MailboxServer

 Exchange2010_Store_Database

 Exchange2010_DAG_Databases

 Exchange2013_MailboxServer

 Exchange2013_Store_Database

 Exchange2013_DAG_Databases

4.21.2

Default Schedule

By default, this script runs every hour.

4.21.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Measure mailbox size in MB or by number of messages

Select how you want to measure the size of mailboxes:

Choose Message count to measure the size of mailboxes by the number of messages in the mailboxes

Choose Total message size to measure the size of all messages in the mailboxes in MB.

The default is Total message size.

Comma-separated list of mailboxes to ignore

Provide a list of mailbox display names that this script should ignore when measuring mailbox size. Separate the names with a comma.

NOTE: Ensure you provide the mailbox display name, not the mailbox alias.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_MailboxUsage job fails. The default is 5.

Monitor Average Mailbox Size

Number of largest mailboxes to be averaged

Set the top n mailboxes whose average size you want to monitor. The default is 10 mailboxes, the minimum is 0, and the maximum is 2147483647

Event Notification

Exchange 2007 Knowledge Scripts

91

Parameter How to Set It

Raise event if average mailbox size exceeds threshold?

Select Yes to raise an event if the average size of the top n mailboxes exceeds the threshold you set. The default is Yes.

Use the Number of largest mailboxes to be averaged parameter to determine the value of n.

AppManager uses Exchange cmdlets to determine the largest mailboxes, based on number and size of mailboxes and messages.

Threshold -- Maximum average mailbox size in MB or by number of messages

Set the maximum average size that the top n mailboxes can attain before an event is raised. The default is 100.

The average is based on either the total number of messages in the top n mailboxes, or the total size in MB of the top n mailboxes, depending on your selection in the Measure mailbox size by total message size or message

count parameter.

Event severity when average mailbox size exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the average size of the top n mailboxes exceeds the threshold. The default is 5.

Data Collection

Collect data for average mailbox size?

Select Yes to collect data for charts and reports. When enabled, data collection returns one of the following data streams:

Average number of messages in n largest mailboxes

Average size in MB of the n largest mailboxes

The default is No.

Monitor Individual Mailbox Size

Number of largest mailboxes to be monitored

Set the top n mailboxes whose individual size you want to monitor. The default is 10 mailboxes, the minimum is 0, and the maximum is 2147483647.

Event Notification

Raise event if individual mailbox size exceeds threshold?

Select Yes to raise an event if the size of any one of the top n mailboxes exceeds the threshold you set. The default is Yes.

Use the Number of largest mailboxes to be monitored parameter to determine the value of n.

AppManager uses Exchange cmdlets to determine the largest mailboxes, based on number and size of mailboxes and messages.

Threshold - Maximum individual mailbox size in MB or by number of messages

Set the maximum size that any one of the top n mailboxes can attain before an event is raised. The default is 250.

The size is based on either the total number of messages in the top n mailboxes, or the total size in MB of the top n mailboxes, depending on your selection in the Measure mailbox size by message count or total message

size parameter.

Event severity when individual mailbox size exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the size of any one of the top n mailboxes exceeds the threshold. The default is 5.

Data Collection

92

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter

Collect data for individual mailbox size?

How to Set It

Select Yes to collect data for charts and reports. When enabled, data collection returns the following data streams:

Number of messages in each of the n largest mailboxes

Size in MB of each of the n largest mailboxes

Use the Number of largest mailboxes to be monitored parameter to determine the value of n.

The default is No.

4.22

MBS_MailFlow

Use this Knowledge Script to test the flow of mail by sending test e-mail to local or remote Mailbox servers. This script raises an event if the test fails or if response time exceeds the threshold you set.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.22.1

Resource Objects

 Exchange2007_MailboxServer

 Exchange2010_MailboxServer

 Exchange2013_MailboxServer

4.22.2

Default Schedule

By default, this script runs every 15 minutes.

4.22.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_MailFlow job fails. The default is 5.

Monitor Mail Flow

Comma-separated list of target

Mailbox servers

Provide the hostnames or IP addresses of the Mailbox servers to which you want to send test e-mail. Separate the names or addresses with a comma.

Comma-separated list of recipient e-mail addresses

Event Notification

Provide the e-mail addresses to which you want to send test e-mail.

Separate the addresses with a comma.

Exchange 2007 Knowledge Scripts

93

Parameter How to Set It

Raise event if mail flow test fails?

Event severity when mail flow test fails

Select Yes to raise an event if test mail cannot be sent to the selected

Mailbox servers. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which test mail cannot be sent to the selected Mailbox servers. The default is

5.

Select Yes to raise an event if the elapsed time to send mail to the Mailbox servers exceeds the threshold you set. The default is Yes.

Raise event if response time exceeds threshold?

Threshold - Maximum response time for mail flow test

Set the maximum number of milliseconds that can elapse while sending mail to the selected Mailbox servers before an event is raised. The default is

10,000 milliseconds.

Event severity when response time exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which response time exceeds the threshold you set. The default is 15.

Collect data for mail flow response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the response time for the mail flow tests during the monitoring period. The default is No.

4.23

MBS_MessagingRecordsMgmt

Use this Knowledge Script to monitor Messaging Records Management (MRM) tasks such as deleting, journaling, moving, and retention, and to monitor the Windows Event log for MRM-related events. This script raises an event if a threshold is exceeded.

4.23.1

Resource Objects

 Exchange2007_MailboxServer

 Exchange2010_MailboxServer

 Exchange2013_MailboxServer

4.23.2

Default Schedule

By default, this script runs every 15 minutes.

4.23.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_MessagingRecordsManagement job fails. The default is 5.

Monitor Messaging Records Management

94

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Monitor Messages Deleted But Recoverable

Event Notification

Raise event if number of messages deleted but recoverable exceeds threshold?

Select Yes to raise an event if the number of deleted, but recoverable, messages exceeds the threshold you set. The default is Yes.

Exchange can recover messages that users have deleted from their Deleted

Items folders. You can use Exchange System Manager to define how many days a deleted message stays in the mailbox store before being permanently deleted.

Event severity when number of messages deleted but recoverable exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of recoverable messages exceeds the threshold you set.

The default is 15.

Threshold - Maximum number of messages deleted but recoverable

Set the maximum number of recoverable messages that can be in the mailbox store before an event is raised. The default is 1000 messages.

Data Collection

Collect data for number of messages deleted but recoverable?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of recoverable messages deleted during the monitoring interval. The default is Yes.

Monitor Messages Permanently Deleted

Event Notification

Raise event if number of messages permanently deleted exceeds threshold?

Select Yes to raise an event if the number of permanently deleted messages exceeds the threshold you set. The default is Yes.

You can use Exchange System Manager to define how many days a deleted message stays in the mailbox store before being permanently deleted.

Event severity when number of messages permanently deleted exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of permanently deleted messages exceeds the threshold you set. The default is 15.

Threshold - Maximum number of messages permanently deleted

Set the maximum number of messages that can be permanently deleted before an event is raised. The default is 1000 messages.

Data Collection

Collect data for number of messages permanently deleted?

Monitor Messages Journaled

Event Notification

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages permanently deleted during the monitoring interval. The default is Yes.

Raise event if number of messages journaled exceeds threshold?

Select Yes to raise an event if the number of journaled, or archived, messages exceeds the threshold you set. The default is Yes.

The Exchange Journaling feature allows users to archive all incoming and outgoing e-mail for a specific mailbox store.

Event severity when number of messages journaled exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of archived messages exceeds the threshold you set. The default is 15.

Exchange 2007 Knowledge Scripts

95

Parameter How to Set It

Threshold - Maximum number of messages journaled

Set the maximum number of messages that can be archived before an event is raised. The default is 1000 messages.

Data Collection

Collect data for number of messages journaled?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages journaled during the monitoring interval. The default is Yes.

Monitor Messages Moved

Event Notification

Raise event if number of messages moved exceeds threshold?

Select Yes to raise an event if the number of messages moved from one managed folder to another exceeds the threshold you set. The default is Yes.

Event severity when number of messages moved exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of moved messages exceeds the threshold you set. The default is 15.

Threshold - Maximum number of messages moved

Set the maximum number of messages that can be moved before an event is raised. The default is 1000 messages.

Data Collection

Collect data for number of messages moved?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages moved during the monitoring interval. The default is Yes.

Monitor Messages Past Retention

Event Notification

Raise event if number of messages marked as past retention date exceeds threshold?

Select Yes to raise an event if the number of deleted messages that have passed their retention date exceeds the threshold you set. The default is

Yes.

Use Exchange System Manager to define how many days a deleted message stays in the mailbox store.

Event severity when number of messages marked as past retention date exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of expired messages exceeds the threshold you set. The default is 15.

Threshold - Maximum number of messages marked as past retention date

Set the maximum number of messages that can have passed their retention date before an event is raised. The default is 1000 messages.

Data Collection

Collect data for number of messages marked as past retention date?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages that expired during the monitoring interval. The default is Yes.

Monitor Windows Event Log for Messaging Records Management Events

Event Notification

96

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Comma-separated list of event sources to ignore

Provide a list of event sources that this script should ignore when scanning the Windows Event log. Separate the source names with a comma.

Comma-separated list of event categories to ignore

Event sources are computers whose names are displayed in the Source column of the event log.

Provide a list of event categories that this script should ignore when scanning the Windows Event log. Separate the category names with a comma.

Comma-separated list of event

IDs to ignore

Provide a list of error and warning ID numbers that this script should ignore when scanning the Windows Event log. Separate the numbers with a comma.

Raise event if MRM error events are found?

Select Yes to raise an event if MRM error events are found in the Windows

Event Log. The default is Yes.

Event severity when MRM error events are found

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Windows Event Log contains MRM error events. The default is 10.

Raise event if MRM warning events are found?

Event severity when MRM warning events are found

Select Yes to raise an event if MRM warning events are found in the

Windows Event Log. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the Windows Event Log contains MRM warning events. The default is

20.

4.24

MBS_PublicFolderUsage

Use this Knowledge Script to measure the size of public folders by the number of messages in the folders or by total message size in MB. You can monitor average folder size and individual folder size for the top n folders. This script raises an event if average folder size and individual folder size exceed the threshold you set.

4.24.1

Resource Objects

 Exchange2007_Store_Group

 Exchange2007_Store_PFDatabase

 Exchange2010_Store_PFDatabase

 Exchange2013_Store_PFDatabase

4.24.2

Default Schedule

By default, this script runs every one hour.

4.24.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

How to Set It

Exchange 2007 Knowledge Scripts

97

Parameter How to Set It

Measure public folder size by message count or total message size

Select how you want to measure the size of public folders:

Choose Message count to measure the size of folders by the number of messages in the mailboxes.

Choose Total message size to measure the size of all messages in the folders in MB.

The default is Total message size.

Comma-separated list of public folders to ignore

Provide a list of public folder names that this script should ignore when measuring folder size. Separate the names with a comma.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_PublicFolderUsage job fails. The default is 5.

Monitor Average Public Folder Size

Number of largest public folders to be averaged

Set the top n public folders whose average size you want to monitor. The default is 10 folders.

Event Notification

Raise event if average public folder size exceeds threshold?

Select Yes to raise an event if the average size of the top n public folders exceeds the threshold you set. The default is Yes.

Use the Number of largest public folders to be averaged parameter to determine the value of n.

AppManager uses Exchange cmdlets to determine the largest public folders, based on number and size of folders and messages.

Threshold - Maximum average public folder size

Set the maximum average size that the top n public folders can attain before an event is raised. The default is 25.

Event severity when average public folder size exceeds threshold

The average is based on either the total number of messages in the top n folders, or the total size in MB of the top n folders, depending on your selection in the Measure public folder size by message count or total

message size parameter.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the average size of the top n public folders exceeds the threshold. The default is 5.

Data Collection

Collect data for average public folder size?

Select Yes to collect data for charts and reports. When enabled, data collection returns one of the following data streams:

Average number of messages in n largest public folders

Average size (MB) of the n largest public folders

The default is No.

Monitor Individual Public Folder Size

Number of largest public folders to be monitored

Set the top n public folders whose individual size you want to monitor. The default is 10 folders.

Event Notification

98

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Raise event if individual public folder size exceeds threshold?

Select Yes to raise an event if the size of any one of the top n public folders exceeds the threshold you set. The default is Yes.

Use the Number of largest public folders to be monitored parameter to determine the value of n.

AppManager uses Exchange cmdlets to determine the largest public folders, based on number and size of folders and messages.

Threshold - Maximum individual public folder size

Set the maximum size that any one of the top n public folders can attain before an event is raised. The default is 100.

Event severity when individual public folder size exceeds threshold

The size is based on either the total number of messages in the top n public folders, or the total size in MB of the top n public folders, depending on your selection in the Measure public folder size by message count or total

message size parameter.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the size of any one of the top n public folders exceeds the threshold.

The default is 5.

Data Collection

Collect data for individual public folder size?

Select Yes to collect data for charts and reports. When enabled, data collection returns the following data streams:

Number of messages in each of the n largest public folders

Size (MB) of each of the n largest public folders

Use the Number of largest public folders to be monitored parameter to determine the value of n.

The default is No.

4.25

MBS_Replication

Use this Knowledge Script to monitor replication status and performance for a Mailbox server. This script raises an event when a threshold is exceeded and generates data streams for the following metrics:

 Replication latency

 Number of pending replication transactions

 Replication rate

 Number of replications in the copy and replay queues

This script also monitors the availability of the File Share Witness, a requirement for using the cluster continuous replication (CCR) functionality in Exchange Server 2007. CCR enables the continuous and asynchronous updating of a second copy of a database with the changes that have been made to the active copy of the database. The File Share Witness is a file share that is external to a cluster and helps determine the status of the cluster.

Exchange 2007 Knowledge Scripts

99

4.25.1

Prerequisite

The AppManager agent (netiqmc service) must have permission to access the File Share Witness folder to collect data for File Share Witness usage on a two-node CCR cluster.

4.25.2

Resource Objects

 Exchange2007_MailboxServer

 Exchange2010_MailboxServer

 Exchange2013_MailboxServer

4.25.3

Default Schedule

By default, this script runs every 15 minutes.

4.25.4

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Communicate only with

Exchange servers in the local domain?

Select Yes to test only Exchange servers in the same domain as the server on which you run the MBS_Replication job. The default is No.

When this option is unselected, the job attempts to contact all Exchange

Servers in your organization. These attempts will fail if the Exchange accounts in one domain do not have access to other domains.

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the MBS_Replication job fails. The default is 5.

Monitor Replication Agent

Event Notification

Raise event if replication agent is not running?

Select Yes to raise an event if the replication agent is not running. The default is Yes.

Event severity when replication agent is not running

Set the severity level, from 1 to 40, to indicate the importance of an event in which the replication agent is not running. The default is 5.

Select Yes to start the replication agent if it is not running. The default is Yes.

Start replication agent if not running?

Threshold - Maximum timeout for starting replication agent

Raise event if replication agent fails to start?

Set the maximum length of time the script can attempt to start the replication agent before timing out and raising an event. The default is 60 seconds.

Select Yes to raise an event if the script cannot start the replication agent.

The default is Yes.

Event severity when replication agent fails to start

Set the severity level, from 1 to 40, to indicate the importance of an event in which the script cannot start the replication agent. The default is 5.

Monitor Replication Copy Status

100

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event Notification

Raise event if replication is unhealthy?

Select Yes to raise an event if replication is unhealthy. The default is Yes.

This script uses the

Get-StorageGroupCopyStatus

cmdlet to determine the status, or health, of the replication function. If the status is

Failed

or

Not Supported

, then replication is considered unhealthy. Replication is also considered unhealthy if the number of transactions in the copy queue or the replay queue exceeds the threshold you set.

Threshold - Maximum length of copy queue

Set the maximum number of transactions that can be waiting in the copy queue before an event is raised. The default is 3 transactions.

Threshold - Maximum length of replay queue

Set the maximum number of transactions that can be waiting in the replay queue before an event is raised. The default is 20 transactions.

Event severity when replication is unhealthy

Set the severity level, from 1 to 40, to indicate the importance of an event in which replication is determined to be unhealthy. The default is 5.

Data Collection

Collect data for copy queue length?

Collect data for replay queue length?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of replication transactions in the copy queue for the monitoring period. The default is No.

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of replication transactions in the replay queue for the monitoring period. The default is No.

Monitor File Share Witness

Raise event if File Share

Witness is unavailable?

Select Yes to raise an event if the File Share Witness is unavailable. The default is Yes.

Event severity when File Share

Witness is unavailable

Set the severity level, from 1 to 40, to indicate the importance of an event in which the File Share Witness is unavailable. The default is 15.

Monitor File Share Witness Usage on Two-node CCR Setup

Data Collection

Collect data for File Share

Witness usage on two-node

CCR setup?

Monitor Replication Latency

Event Notification

Select Yes to collect data for charts and reports. When enabled, data collection returns the percentage of usage for the File Share Witness in a two-node cluster continuous replication environment. The default is No.

Exchange 2007 Knowledge Scripts

101

Parameter

Raise event if replication latency exceeds threshold?

How to Set It

Select Yes to raise an event if replication latency exceeds the threshold you set. The default is Yes.

When this parameter is set to Yes, the Extended ESE performance counters in the registry are enabled. The following updates are made automatically in the registry values:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ESE\Perform ance

Value Name: Show Advanced Counters

Data Type: REG_DWORD

Threshold -- Maximum replication latency

Value: 1

Set the maximum number of milliseconds allowed for replication latency before an event is raised. The default is 20000 milliseconds.

Event severity when replication latency exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which replication latency exceeds the threshold you set. The default is 15.

Data Collection

Collect data for replication latency?

Select Yes to collect data for charts and reports. When enabled, data collection returns the total latency for the monitoring period. The default is

No.

Monitor Replication Rate

Event Notification

Raise event if replication rate exceeds threshold?

Select Yes to raise an event if the replication rate exceeds the threshold you set. The default is Yes.

Threshold -- Maximum replication rate

Set the maximum number of replications allowed per minute before an event is raised. The default is 10000 transactions.

Event severity when replication rate threshold exceeded

Set the severity level, from 1 to 40, to indicate the importance of an event in which the replication rate exceeds the threshold you set. The default is 15.

Data Collection

Collect data for replication rate?

Select Yes to collect data for charts and reports. When enabled, data collection returns the replication rate for the monitoring period. The default is

No.

Monitor Pending Replication Transactions

Event Notification

Raise event if pending replication transactions exceed threshold?

Select Yes to raise an event if the number of transactions waiting to be replicated exceeds the threshold you set. The default is Yes.

Threshold -- Maximum number of pending replication transactions

Set the maximum number of transactions that can be awaiting replication before an event is raised. The default is 500 transactions.

Event severity when pending replication transactions exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of transactions waiting to be replicated exceeds the threshold you set. The default is 15.

Data Collection

102

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter

Collect data for pending replication transactions?

How to Set It

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of pending replication transactions for the monitoring period. The default is No.

4.26

Transport_BackPressure

Use this Knowledge Script to monitor the status of back pressure for the Hub Transport server.

Back pressure monitors system resources, such as available disk space and available memory, on computers that have the Hub Transport server role or Edge Transport server role installed. If resource usage exceeds a certain level, the Exchange server stops accepting new connections and messages, but may continue to deliver existing messages. When resource usage returns to a normal level, the

Exchange server accepts new connections and messages.

This script raises events for three levels of resource usage:

Normal. No back pressure is applied to the server: new connections and messages are accepted.

Medium. The resource is slightly overused. Limited back pressure is applied to the server: incoming mail from the authoritative domain is allowed, but new connections and messages from other sources are rejected.

High. The resource is severely overused. Full back pressure is applied to the server: all message flow stops, and all new connections and messages are rejected.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.26.1

Resource Objects

 Exchange2007_HubTransportServer

 Exchange2007_EdgeTransportServer

 Exchange2010_HubTransportServer

 Exchange2010_EdgeTransportServer

 Exchange2013_HubTransportServer

4.26.2

Default Schedule

By default, this script runs every five minutes.

4.26.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

Job failure event notification

How to Set It

Exchange 2007 Knowledge Scripts

103

Parameter How to Set It

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the Transport_BackPressure job fails. The default is 5.

Monitor Back Pressure Status

Event Notification

Raise event if back pressure is high?

Event severity when back pressure is high

Raise event if back pressure is medium?

Event severity when back pressure is medium

Select Yes to raise an event if resource usage is at a high level. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which resource usage is at a high level. The default is 5.

Select Yes to raise an event if resource usage is at a medium level. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which resource usage is at a medium level. The default is 10.

4.27

Transport_ConnectorStatus

Use this Knowledge Script to monitor the status of send, receive, foreign, and delivery agent connectors on Exchange Servers. This script raises an event if any of the connector is disabled or an

SMTP-based receive connector is not responding to SMTP requests.

NOTE: The delivery agent connectors are not applicable on Exchange Server 2007.

4.27.1

Resource Objects

 Exchange2007_HubTransportServer

 Exchange2007_EdgeTransportServer

 Exchange2010_HubTransportServer

 Exchange2010_EdgeTransportServer

 Exchange2013_ClientAccessServer

 Exchange2013_HubTransportServer

4.27.2

Default Schedule

By default, this script runs every 15 minutes.

4.27.3

Setting Parameter Values

Set the following parameters as needed:

Parameter

General Settings

Job failure event notification

How to Set It

104

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the Transport_ConnectorStatus job fails. The default is 5.

Monitor Connectors

Monitor Receive Connectors

Event Notification

Raise event if any receive connector is disabled

Select Yes to raise an event if any of the connector to receive messages on

Exchange Server is disabled. The default is Yes.

The receive connectors receive e-mail from a Mailbox server or from the

Internet when an Edge role is not set up in the Exchange environment.

Comma-separated list of receive connectors to ignore

Specify a list of receive connectors separated by a comma, in the

<hostname>\<connectorname>

format that you want to exclude from monitoring.

Event severity when any receive connector is disabled

Set the severity level, from 1 to 40, to indicate the importance of an event in which a connector to receive messages on Exchange Server is disabled.

The default is 5.

Raise event if an enabled receive connector does not respond to SMTP requests?

Event severity when a receive connector does not respond to

SMTP requests

Select Yes to raise an event if a receive connector is unable to respond to

SMTP requests. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which a receive connector is unable to respond to SMTP requests. The default is 5.

Monitor Send Connectors

Event Notification

Raise event if any send connector is disabled

Comma-separated list of send connectors to ignore

Event severity when any send connector is disabled

Select Yes to raise an event if a connector to send messages from Exchange

Server is disabled. The default is Yes.

The send connectors send e-mail to the mailbox of the intended recipient or to the Edge Transport server for delivery to another domain.

Specify a list of send connector names, separated by a comma, that you want to exclude from monitoring.

Set the severity level, from 1 to 40, to indicate the importance of an event in which a connector to send messages from Exchange Server is disabled. The default is 5.

Monitor Foreign Connectors

Raise event if any foreign connector is disabled?

Select Yes to raise an event if a foreign connector is disabled. The default is

Yes.

The foreign connectors move e-mail to a server within the organization that does not communicate using SMTP.

Comma-separated list of foreign connectors to ignore

Specify a list of foreign connector names, separated by a comma, that you want to exclude from monitoring.

Event severity when any foreign connector is disabled

Set the severity level, from 1 to 40, to indicate the importance of an event in which a foreign connector is disabled. The default is 5.

Monitor Delivery Agent Connectors

Exchange 2007 Knowledge Scripts

105

Parameter How to Set It

Raise event if any delivery agent connector is disabled?

Select Yes to raise an event if a delivery agent connector is disabled. The default is Yes.

Comma-separated list of delivery agent connectors to ignore

Specify a list of delivery agent connector names, separated by a comma, that you want to exclude from monitoring.

Event severity when any delivery agent connector is disabled

Set the severity level, from 1 to 40, to indicate the importance of an event in which a delivery agent connector is disabled. The default is 5.

4.28

Transport_QueueStatus

Use this Knowledge Script to monitor the number of messages in Hub Transport server queues:

Submission queue, which contains messages waiting to be categorized and routed to a delivery queue.

Mailbox delivery queue, which contains messages awaiting delivery to mailboxes on a Mailbox server that is located in the same site as the Hub Transport server.

Remote delivery queue, which contains messages awaiting delivery to mailboxes outside the

Active Directory site in which the Hub Transport server is located.

Poison message queue, which is a quarantine destination for messages identified as potentially fatal to your Exchange Server 2007, 2010, or 2013 environment.

Unreachable destination queue, which contains messages that cannot be routed to their destinations.

This script raises an event if the length of a queue or the change in the length of a queue exceeds the threshold you set.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.28.1

Resource Objects

 Exchange2007_Queue

 Exchange2007_EdgeTransportServer

 Exchange2007_HubTransportServer

 Exchange2010_Queue

 Exchange2010_EdgeTransportServer

 Exchange2010_HubTransportServer

 Exchange2013_Queue

 Exchange2013_HubTransportServer

4.28.2

Default Schedule

By default, this script runs every 15 minutes.

106

NetIQ AppManager for Microsoft Exchange Server Management Guide

4.28.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the Transport_QueueStatus job fails. The default is 5.

Monitor Submission Queue

Event Notification

Raise event if number of queued messages exceeds threshold?

Select Yes to raise an event if the number of messages in the submission queue exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of messages in queue

Set the maximum number of messages that can be waiting in the submission queue before an event is raised. The default is 100 messages.

Event severity when number of messages in queue exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in the submission queue exceeds the threshold you set. The default is 15.

Raise event if increase in queued messages exceeds threshold?

Select Yes to raise an event if the percentage of increase in the number of messages in the submission queue exceeds the threshold. The script measures the rate of increase since the last iteration of the job. The default is

No.

Threshold - Maximum percent increase in queued messages since last job iteration

Set the maximum acceptable percentage of increase in queue size since the last job iteration. AppManager raises an event if the percentage of increase exceeds this value. The default is 50%.

Event severity when increase in queued messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the percentage of increase in the number of messages in the submission queue exceeds the threshold. The default is 15.

Data Collection

Collect data for number of messages in the submission queue?

Monitor Mailbox Delivery Queue

Event Notification

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in the submission queue during the monitoring interval. The default is No.

Raise event if number of queued messages exceeds threshold?

Select Yes to raise an event if the number of messages in the mailbox delivery queue exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of messages in queue

Set the maximum number of messages that can be waiting in the mailbox delivery queue before an event is raised. The default is 250 messages.

Event severity when number of messages in queue exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in the mailbox delivery queue exceeds the threshold you set. The default is 15.

Exchange 2007 Knowledge Scripts

107

Parameter How to Set It

Raise event if increase in queued messages exceeds threshold?

Threshold - Maximum percent increase in queued messages since last job iteration

Select Yes to raise an event if the percentage of increase in the number of messages in the mailbox delivery queue exceeds the threshold. The script measures the rate of increase since the last iteration of the job. The default is

No.

Set the maximum acceptable percentage of increase in queue size since the last job iteration. AppManager raises an event if the percentage of increase exceeds this value. The default is 50%.

Event severity when increase in queued messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the percentage of increase in the number of messages in the mailbox delivery queue exceeds the threshold. The default is 15.

Data Collection

Collect data for number of messages in the mailbox delivery queue?

Monitor Remote Delivery Queue

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in the mailbox delivery queue during the monitoring interval. The default is No.

Event Notification

Raise event if number of queued messages exceeds threshold?

Select Yes to raise an event if the number of messages in the remote delivery queue exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of messages in queue

Set the maximum number of messages that can be waiting in the remote delivery queue before an event is raised. The default is 250 messages.

Event severity when number of messages in queue exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in the remote delivery queue exceeds the threshold you set. The default is 15.

Raise event if increase in queued messages exceeds threshold?

Threshold - Maximum percent increase in queued messages since last job iteration

Select Yes to raise an event if the percentage of increase in the number of messages in the remote delivery queue exceeds the threshold. The script measures the rate of increase since the last iteration of the job. The default is

No.

Set the maximum acceptable percentage of increase in queue size since the last job iteration. AppManager raises an event if the percentage of increase exceeds this value. The default is 50%.

Event severity when increase in queued messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the percentage of increase in the number of messages in the remote delivery queue exceeds the threshold. The default is 15.

Data Collection

Collect data for number of messages in the remote delivery queue?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in the remote delivery queue during the monitoring interval. The default is No.

Monitor Poison Message Queue

Event Notification

Raise event if number of queued messages exceeds threshold?

Select Yes to raise an event if the number of messages in the poison message queue exceeds the threshold you set. The default is Yes.

108

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Threshold - Maximum number of messages in queue

Set the maximum number of messages that can be waiting in the poison message queue before an event is raised. The default is 0 (zero) messages.

Event severity when number of messages in queue exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in the poison message queue exceeds the threshold you set. The default is 15.

Raise event if increase in queued messages exceeds threshold?

Select Yes to raise an event if the percentage of increase in the number of messages in the poison message queue exceeds the threshold. The script measures the rate of increase since the last iteration of the job. The default is

No.

Threshold - Maximum percent increase in queued messages since last job iteration

Set the maximum acceptable percentage of increase in queue size since the last job iteration. AppManager raises an event if the percentage of increase exceeds this value. The default is 50%.

Event severity when increase in queued messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the percentage of increase in the number of messages in the poison message queue exceeds the threshold. The default is 15.

Data Collection

Collect data for number of messages in the poison message queue?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in the poison message queue during the monitoring interval. The default is No.

Monitor Unreachable Destination Queue

Event Notification

Raise event if number of queued messages exceeds threshold?

Select Yes to raise an event if the number of messages in the unreachable destination queue exceeds the threshold you set. The default is Yes.

Threshold - Maximum number of messages in queue

Set the maximum number of messages that can be waiting in the unreachable destination queue before an event is raised. The default is 100 messages.

Event severity when number of messages in queue exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in the unreachable destination queue exceeds the threshold you set. The default is 15.

Raise event if increase in queued messages exceeds threshold?

Threshold - Maximum percent increase in queued messages since last job iteration

Select Yes to raise an event if the percentage of increase in the number of messages in the unreachable destination queue exceeds the threshold. The script measures the rate of increase since the last iteration of the job. The default is No.

Set the maximum acceptable percentage of increase in queue size since the last job iteration. AppManager raises an event if the percentage of increase exceeds this value. The default is 50%.

Event severity when increase in queued messages exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the percentage of increase in the number of messages in the unreachable destination queue exceeds the threshold. The default is 15.

Data Collection

Collect data for number of messages in the unreachable queue?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in the unreachable destination queue during the monitoring interval. The default is No.

Exchange 2007 Knowledge Scripts

109

4.29

UMS_CallActivity

Use this Knowledge Script to monitor call activity on a Unified Messaging server. This script raises an event if a threshold is exceeded and generates data streams for the following types of calls:

 Active voice calls

 Active fax calls

 Active play-on-phone calls

 Active auto-attendant calls

 Active subscriber-access calls

 Active prompt-editing calls

4.29.1

Resource Objects

 Exchange2007_UnifiedMessagingServer

 Exchange2010_UnifiedMessagingServer

 Exchange2013_UnifiedMessagingServer

4.29.2

Default Schedule

By default, this script runs every 15 minutes.

4.29.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the UMS_CallActivity job fails. The default is 5.

Monitor Voice Calls

Event Notification

Raise event if number of active voice calls exceeds threshold?

Select Yes to raise an event if the number of active voice calls exceeds the threshold you set. The default is Yes.

Active voice calls are calls that are currently connected to the Unified

Messaging server.

Threshold - Maximum number of active voice calls

Set the maximum number of calls that can be simultaneously connected to the Unified Messaging server before an event is raised. The default is 100 calls.

Event severity when number of active voice calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active voice calls exceeds the threshold. The default is

5.

Data Collection

110

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Collect data for number of active voice calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of voice calls that were active during the monitoring period. The default is No.

Monitor Fax Calls

Event Notification

Raise event if number of active fax calls exceeds threshold?

Select Yes to raise an event if the number of active fax calls exceeds the threshold you set. The default is Yes.

Voice calls become fax calls after a fax tone is detected.

Threshold - Maximum number of active fax calls

Set the maximum number of fax calls that can be simultaneously connected to the Unified Messaging server before an event is raised. The default is 100 calls.

Event severity when number of active fax calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active fax calls exceeds the threshold. The default is 5.

Data Collection

Collect data for number of active fax calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of fax calls that were active during the monitoring period. The default is No.

Monitor Play On Phone Calls

Event Notification

Raise event if number of active play on phone calls exceeds threshold?

Select Yes to raise an event if the number of active play-on-phone calls exceeds the threshold you set. The default is Yes.

The Exchange Server 2007 Unified Messaging play-on-phone feature enables users to access voice mail messages on the telephone rather than on their computer speakers.

Active play-on-phone calls are outbound calls initiated to play back messages.

Threshold - Maximum number of active play on phone calls

Set the maximum number of play-on-phone calls that can be simultaneously active before an event is raised. The default is 100 calls.

Event severity when number of active play on phone calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active play-on-phone calls exceeds the threshold. The default is 5.

Data Collection

Collect data for number of active play on phone calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of play-on-phone calls that were active during the monitoring period. The default is No.

Monitor Auto Attendant Calls

Event Notification

Exchange 2007 Knowledge Scripts

111

Parameter How to Set It

Raise event if number of active auto attendant calls exceeds threshold?

Select Yes to raise an event if the number of active auto-attendant calls exceeds the threshold you set. The default is Yes.

The Unified Messaging auto attendant is a set of voice prompts or .wav files played to callers in place of a human operator when they call into your organization.

Active auto-attendant calls are calls that are currently connected to the

Unified Messaging server by the auto attendant.

Threshold - Maximum number of active auto attendant calls

Set the maximum number of auto-attendant calls that can be simultaneously active before an event is raised. The default is 100 calls.

Event severity when number of active auto attendant calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active auto-attendant calls exceeds the threshold. The default is 5.

Data Collection

Collect data for number of active auto attendant calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of auto-attendant calls that were active during the monitoring period. The default is No.

Monitor Subscriber Access Calls

Event Notification

Raise event if number of active subscriber access calls exceeds threshold?

Select Yes to raise an event if the number of active subscriber-access calls exceeds the threshold you set. The default is Yes.

Subscriber access is used by users to access their individual mailboxes to retrieve e-mail, voice messages, contacts, and calendaring information.

Active subscriber-access calls are logged-on subscribers who are currently connected to the Unified Messaging server.

Threshold - Maximum number of active subscriber access calls

Set the maximum number of subscriber-access calls that can be simultaneously active before an event is raised. The default is 100 calls.

Event severity when number of active subscriber access calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active subscriber-access calls exceeds the threshold.

The default is 5.

Data Collection

Collect data for number of active subscriber access calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of subscriber-access calls that were active during the monitoring period. The default is No.

Monitor Prompt Editing Calls

Event Notification

Raise event if number of active prompt editing calls exceeds threshold?

Select Yes to raise an event if the number of active prompt-editing calls exceeds the threshold you set. The default is Yes.

Active prompt-editing calls are logged-on users who are editing custom prompts, such as voice-mail greetings.

Threshold - Maximum number of active prompt editing calls

Set the maximum number of prompt-editing calls that can be simultaneously active before an event is raised. The default is 100 calls.

112

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when number of active prompt editing calls exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of active prompt-editing calls exceeds the threshold. The default is 5.

Data Collection

Collect data for number of active prompt editing calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of prompt-editing calls that were active during the monitoring period. The default is No.

4.30

UMS_Connectivity

Use this Knowledge Script to monitor connectivity to Hub Transport servers, Mailbox servers, Active

Directory, and mailboxes enabled for Unified Messaging (UM). This script raises an event if a connectivity test fails or if response time exceeds the threshold you set.

A mailbox that is enabled for UM can receive e-mail, voicemail, and fax messages.

NOTE: On Exchange Server 2013, you must drop this script only on the Mailbox server that hosts the

Mailbox user that will be used for the test. This script displays an error if you drop this script on any other Mailbox Server that does not host the Mailbox user.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.30.1

Resource Objects

 Exchange2007_UnifiedMessagingServer

 Exchange2010_UnifiedMessagingServer

 Exchange2013_UnifiedMessagingServer

4.30.2

Default Schedule

By default, this script runs every 15 minutes.

4.30.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the UMS_Connectivity job fails. The default is 5.

Monitor UM-Enabled Mailbox Accessibility

Exchange 2007 Knowledge Scripts

113

Parameter How to Set It

Dial plan to use to connect to the

UM-enabled mailbox

Identify the dial plan to use to connect to the mailbox you want to monitor.

Phone extension of UM-enabled mailbox to use for accessibility test

Provide the extension number of the mailbox you want to monitor.

PIN of UM-enabled mailbox to use for accessibility test

Provide the Personal Identification Number (PIN) required to access the mailbox you want to monitor.

Event Notification

Raise event if UM-enabled mailbox cannot be accessed?

Select Yes to raise an event if the specified mailbox cannot be tested for connectivity. The default is Yes.

Event severity when UMenabled mailbox cannot be accessed

Set the severity level, from 1 to 40, to indicate the importance of an event in which the specified mailbox is unavailable for testing. The default is 5.

Raise event if response time exceeds threshold?

Select Yes to raise an event if the time to connect to the mailbox exceeds the threshold you set. The default is Yes.

Threshold - Maximum response time

Set the maximum number of seconds that AppManager should wait to connect with the mailbox before raising an event. The default is 10000 milliseconds.

Event severity when response time exceeds threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which response time exceeds the threshold you set. The default is 15.

Collect data for response time?

Select Yes to collect data for charts and reports. When enabled, data collection returns the length of response time during the monitoring period.

The default is No.

Monitor Mailbox Server Connectivity

Event Notification

Raise event if Mailbox servers are unavailable?

Select Yes to raise an event if Mailbox servers cannot be tested for connectivity. The default is Yes.

Event severity when Mailbox servers are unavailable

Set the severity level, from 1 to 40, to indicate the importance of an event in which Mailbox servers are unavailable for testing. The default is 5.

Monitor Hub Transport Server Connectivity

Event Notification

Raise event if Hub Transport servers are unavailable?

Event severity when Hub

Transport servers are unavailable

Select Yes to raise an event if Hub Transport servers cannot be tested for connectivity. The default is Yes.

Set the severity level, from 1 to 40, to indicate the importance of an event in which Hub Transport servers are unavailable for testing. The default is 5.

Monitor Mailbox Server Connectivity

Event Notification

Raise event if Mailbox servers are unavailable?

Select Yes to raise an event if Mailbox servers cannot be tested for connectivity. The default is Yes.

114

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when Mailbox servers are unavailable

Set the severity level, from 1 to 40, to indicate the importance of an event in which Mailbox servers are unavailable for testing. The default is 5.

Monitor Active Directory Connectivity

Event Notification

Raise event if Active Directory is unavailable?

Select Yes to raise an event if Active Directory cannot be tested for connectivity. The default is Yes.

Event severity when Active

Directory is unavailable

Set the severity level, from 1 to 40, to indicate the importance of an event in which Active Directory is unavailable for testing. The default is 5.

4.31

UMS_Failures

Use this Knowledge Script to monitor failures of the Unified Messaging server related to redirected calls, disconnected calls, and access to Active Directory, the Hub Transport server, and the Mailbox server. This script raises an event if a threshold is exceeded.

This script is a member of the Exchange2007 recommended Knowledge Script Group. For more information, see

Section 4.33, “Recommended Knowledge Script Group,” on page 121

.

4.31.1

Resource Objects

 Exchange2007_UnifiedMessagingServer

 Exchange2010_UnifiedMessagingServer

 Exchange2013_UnifiedMessagingServer

4.31.2

Default Schedule

By default, this script runs every 15 minutes.

4.31.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails Set the severity level, from 1 to 40, to indicate the importance of an event in which the UMS_Failures job fails. The default is 5.

Monitor Calls Disconnected Due to Internal Errors

Event Notification

Exchange 2007 Knowledge Scripts

115

Parameter How to Set It

Raise event if calls disconnected due to internal errors exceed threshold?

Select Yes to raise an event if the number of calls disconnected due to internal errors exceeds the threshold you set. The default is Yes.

This script uses the value of the

Calls Disconnected on

Irrecoverable Internal Error

performance counter, which is the number of calls that were disconnected after an internal system error occurred.

Threshold - Maximum number of calls disconnected due to internal errors

Set the maximum number of calls that can be disconnected due to an internal error before an event is raised. The default is 900 calls.

Event severity when calls disconnected due to internal errors exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of calls disconnected due to internal errors exceeds the threshold you set. The default is 5.

Data Collection

Collect data for calls disconnected due to internal errors

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of calls disconnected due to internal errors during the monitoring period. The default is No.

Monitor Calls Disconnected Due to External Errors

Event Notification

Raise event if calls disconnected due to external errors exceed threshold?

Select Yes to raise an event if the number of calls disconnected due to external errors exceeds the threshold you set. The default is Yes.

This script uses the value of the

Calls Disconnected by UM on

Irrecoverable External Error performance counter, which is the total number of calls that have been disconnected after an irrecoverable external error occurred.

Threshold - Maximum number of calls disconnected due to external errors

Set the maximum number of calls that can be disconnected due to an external error before an event is raised. The default is 900 calls.

Event severity when calls disconnected due to external errors exceed threshold

Data Collection

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of calls disconnected due to external errors exceeds the threshold you set. The default is 5.

Collect data for calls disconnected due to external errors?

Monitor Failures to Redirect Calls

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of calls disconnected due to external errors during the monitoring period. The default is No.

Event Notification

Raise event if failures to redirect calls exceed threshold?

Select Yes to raise an event if the number of failed attempts to redirect calls exceeds the threshold you set. The default is Yes.

This script uses the value of the

Failed to Redirect Call

performance counter, which is the number of times the Unified Messaging service did not redirect calls to a Unified Messaging worker process.

Threshold - Maximum number of failures to redirect calls

Set the maximum number of calls that can fail to be redirected before an event is raised. The default is 900 calls.

116

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event severity when failures to redirect calls exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of failed attempts to redirect calls exceeds the threshold you set. The default is 5.

Data Collection

Collect data for failures to redirect calls?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of attempts to redirect calls that failed during the monitoring period. The default is No.

Monitor Mailbox Server Access Failures

Event Notification

Raise event if Mailbox server access failures exceed threshold?

Select Yes to raise an event if the number of failed attempts to access the

Mailbox server exceeds the threshold you set. The default is Yes.

This script uses the value of the

Mailbox Server Access Failures performance counter, which is the number of times the Unified Messaging system did not access a Mailbox server.

Threshold - Maximum number of

Mailbox server access failures

Set the maximum number of attempts that can fail to access the Mailbox server before an event is raised. The default is 900 attempts.

Event severity when Mailbox server access failures exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of failed attempts to access the Mailbox server exceeds the threshold you set. The default is 5.

Data Collection

Collect data for Mailbox server access failures?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of attempts to access the Mailbox server that failed during the monitoring period. The default is No.

Monitor Hub Transport Server Access Failures

Event Notification

Raise event if Hub Transport server access failures exceed threshold?

Select Yes to raise an event if the number of failed attempts to access the

Hub Transport server exceeds the threshold you set. The default is Yes.

This script uses the value of the

Hub Transport Access Failures performance counter, which is the number of times that attempts to access a

Hub Transport server failed. This number increases only if all Hub Transport servers are unavailable.

Threshold - Maximum number of

Hub Transport server access failures

Set the maximum number of attempts that can fail to access the Hub

Transport server before an event is raised. The default is 900 attempts.

Event severity when Hub

Transport server access failures exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of failed attempts to access the Hub Transport server exceeds the threshold you set. The default is 5.

Data Collection

Collect data for number of Hub

Transport server access failures?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of attempts to access the Hub Transport server that failed during the monitoring period. The default is No.

Monitor Active Directory Access Failures

Event Notification

Exchange 2007 Knowledge Scripts

117

Parameter How to Set It

Raise event if Active Directory access failures exceed threshold?

Select Yes to raise an event if the number of failed attempts to access Active

Directory exceeds the threshold you set. The default is Yes.

This script uses the value of the

Directory Access Failures performance counter, which is the number of times that attempts to access

Active Directory failed.

Threshold - Maximum number of

Active Directory access failures

Set the maximum number of attempts that can fail to access Active Directory before an event is raised. The default is 900 attempts.

Event severity when Active

Directory access failures exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of failed attempts to access Active Directory exceeds the threshold you set. The default is 5.

Data Collection

Collect data for Active Directory access failures?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of attempts to access Active Directory that failed during the monitoring period. The default is No.

4.32

UMS_Performance

Use this Knowledge Script to monitor the performance of the Unified Messaging server: user response latency, operation response time, queued messages for call answering, queued OCS user notifications, and calls disconnected while playing audio hourglass tones. This script raises an event if a monitored value exceeds the threshold you set. In addition, this script generates data streams for monitored values.

4.32.1

Resource Objects

 Exchange2007_UnifiedMessagingServer

 Exchange2010_UnifiedMessagingServer

 Exchange2013_UnifiedMessagingServer

4.32.2

Default Schedule

By default, this script runs every 15 minutes.

4.32.3

Setting Parameter Values

Set the following parameters as needed:

Parameter How to Set It

General Settings

Job failure event notification

Event severity when job fails

Monitor User Response Latency

Set the severity level, from 1 to 40, to indicate the importance of an event in which the UMS_Performance job fails. The default is 5.

118

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter How to Set It

Event Notification

Raise event if user response latency exceeds threshold?

Select Yes to raise an event if the amount of time it takes for the system to respond to a user’s request exceeds the threshold you set. The default is

Yes.

Threshold - Maximum user response latency

Event severity when user response latency exceeds threshold

This script uses the value of the

User Response Latency

performance counter, which is the average response time, in milliseconds, for the system to respond to a user request. This average is calculated over the last 25 calls.

Set the maximum length of time it can take to respond to a user request before an event is raised. The default is 1 millisecond.

Set the severity level, from 1 to 40, to indicate the importance of an event in which user response time exceeds the threshold you set. The default is 15.

Data Collection

Collect data for user response latency?

Select Yes to collect data for charts and reports. When enabled, data collection returns the average user response latency value for the monitoring period. The default is No.

Monitor Operations Response Time

Event Notification

Raise event if percentage of operations exceeds threshold?

Select Yes to raise an event if Unified Messaging operations it takes a

Unified Messaging operation to complete a transaction exceeds the threshold you set. The default is Yes.

This script uses the MSExchangeUMPerformance category of performance counters.

Operations response time Set a response time, between 2 and 6 seconds. Operations with a response time greater than this value are considered for the Threshold - Maximum

percentage of operations that exceed response time parameter. The default is 6 seconds.

Threshold - Maximum percentage of operations that exceed the selected response time

The response time is the number of seconds it takes a Unified Messaging operation to complete, during which a caller is waiting for a response.

Set the maximum percentage of operations that can exceed the response time you specify in Operations response time. This script raises an event if the percentage is greater than the threshold value you specify here. The default is 1%.

Event severity when percentage of operations exceeds threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which operation response time exceeds the threshold you set. The default is

15.

Data Collection

Collect data for percentage of operations that exceeds threshold?

Select Yes to collect data for charts and reports. When enabled, data collection returns operation response time for the monitoring period. The default is No.

Monitor Call Answer Queued Messages

Event Notification

Exchange 2007 Knowledge Scripts

119

Parameter How to Set It

Raise event if call answer queued messages exceed threshold?

Select Yes to raise an event if the number of messages in queue to be answered exceeds the threshold you set. The default is Yes.

This script uses the

Call Answer Queued Messages

performance counter, which is the number of messages created and not yet submitted for delivery.

Threshold - Maximum call answer queued messages

Set the maximum number of messages that can be in queue to be answered before an event is raised. The default is 50 messages.

Event severity when call answer queued messages exceed threshold

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of messages in queue to be answered exceeds the threshold you set. The default is 15.

Data Collection

Collect data for call answer queued messages?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of messages in queue to be answered for the monitoring period. The default is No.

Monitor Queued OCS User Event Notifications

Event Notification

Raise event if queued OCS user event notifications exceed threshold?

If you are using Microsoft Exchange 2007, 2010, or 2013 without a service pack applied, select Yes to raise an event if the number of Office

Communications Server notifications in queue exceeds the threshold you set. The default is Yes.

This script uses the Queued OCS User Event Notifications performance counter, which is the number of notifications that have been created and not yet submitted for delivery. This performance counter is no longer available with Microsoft Exchange 2010 Service Pack 1.

Threshold - Maximum queued

OCS user event notifications

Event severity when queued

OCS user event notifications exceed threshold

Data Collection

Set the maximum number of notifications that can be in queue before an event is raised. The default is 0 notifications.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of notifications in queue exceeds the threshold you set.

The default is 15.

Collect data for queued OCS user event notifications?

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of notifications in queue for the monitoring period. The default is No.

Monitor Calls Disconnected During Audio Hourglass

Event Notification

Raise event if calls disconnected during audio hourglass exceed threshold?

Select Yes to raise an event if the number of calls disconnected during the audio hourglass exceeds the threshold you set. The default is Yes.

This script uses the

Calls Disconnected by Callers During UM

Audio Hourglass

performance counter, which is the number of calls during which the caller disconnected while Unified Messaging was playing the audio hourglass tones. Audio hourglass tones let users know they are still on hold or in queue.

120

NetIQ AppManager for Microsoft Exchange Server Management Guide

Parameter

Threshold - Maximum calls disconnected during audio hourglass

Event severity when calls disconnected during audio hourglass exceed threshold

Data Collection

Collect data for calls disconnected during audio hourglass?

How to Set It

Set the maximum number of calls that can be disconnected during the audio hourglass before an event is raised. The default is 0 calls.

Set the severity level, from 1 to 40, to indicate the importance of an event in which the number of disconnected calls exceeds the threshold you set. The default is 15.

Select Yes to collect data for charts and reports. When enabled, data collection returns the number of calls disconnected during audio hourglass for the monitoring period. The default is No.

4.33

Recommended Knowledge Script Group

The following Knowledge Scripts in the AppManager for Exchange2007 module are members of the

Exchange2007 recommended Knowledge Script Group (KSG).

All_BestPracticesAnalyzer

All_ClockSynchronization

All_EventLog

All_ServiceStatus

CAS_Activity

CAS_Connectivity

ETS_ExternalMail

HTS_Connectivity

MBS_MailboxAccessibility

MBS_MailFlow

Transport_BackPressure

Transport_QueueStatus

UMS_Connectivity

UMS_Failures

You can find the Exchange2007 KSG on the RECOMMENDED tab of the Knowledge Script pane of the Operator Console.

The parameters of all scripts in the KSG are set to recommended values. To run all of the recommended scripts at one time, click the RECOMMENDED tab, and then run the Exchange2007 group on an Exchange Server 2007, 2010, or 2013 resource.

The Exchange2007 KSG contains Knowledge Scripts for every server role. When you run the KSG on a particular server role, only the scripts in the KSG associated with that role will run. The All_*

Knowledge Scripts in the KSG will run on every role.

The Exchange2007 KSG provides a “best practices” usage of AppManager for monitoring Exchange

Server 2007, 2010, or 2013 in your organization. You can use this KSG with AppManager monitoring policies. A monitoring policy, which enables you to efficiently and consistently monitor all the

Exchange 2007 Knowledge Scripts

121

resources in your environment, uses a set of pre-configured Knowledge Scripts to automatically monitor resources as they appear in the TreeView. For more information, see “About Policy-Based

Monitoring” in the AppManager Help.

A KSG is composed of a subset of a module’s Knowledge Scripts. The script that belongs to a KSG is a different copy of the original script you access from the Exchange2007 tab. If you modify a script that belongs to a KSG, the parameter settings of the original script in the Exchange2007 tab are not affected.

When deployed as part of a KSG, a script’s default script parameter settings may differ from when the script is deployed alone. The default settings of a script within a group depend on its monitoring purpose within the larger group, and on the intended monitoring scope of that group.

If you modify or remove a script associated with the Exchange2007 KSG and want to restore it to its original form, you can reinstall AppManager for Exchange Server 2007 on the repository computer or check in the appropriate script from the

AppManager\qdb\kp\Exchange2007\RECOMMENDED_Exchange2007

directory.

In addition to the Knowledge Scripts in the KSG, NetIQ Corporation recommends using the following scripts for monitoring and managing an Exchange Server 2007, 2010, or 2013 environment. The tables below summarize the scripts that are applicable for the unique elements of an Exchange

Server 2007, 2010, or 2013 environment. For more information, see the AppManager Help for each script.

For performing benchmarking and trend analyses before deploying AppManager for Exchange

Server, run the following scripts from the NT and AD script categories.

Recommended Knowledge Script

NT_CPUByProcess

NT_CPULoaded

NT_LogicalDiskBusy

NT_LogicalDiskIO

NT_MemUtil

NT_NetworkBusy

AD_Authentications

Description

Monitors CPU usage for each process and the total CPU usage for all processes.

Monitors total CPU usage and queue length to determine CPU load.

Monitors the logical disk activity on one or more disks.

Monitors logical disk I/O activity, including disk transfers, and reads and writes per second.

Monitors physical memory, virtual memory, and paging files.

Monitors the traffic on the network interface cards on a Windows computer.

Monitors the number of Active Directory Kerberos and NT LAN

Manager (NTLM) authentications per second.

For monitoring the hardware and operating system of the Exchange Server 2007, 2010, or 2013 server and components, use the following scripts from the NT script category and from the categories appropriate for your hardware, such as CIM or Dell.

Recommended Knowledge Script

[HardwareModule]_

ArrayPhysicalDiskStatus or

ArrayPhysicalDrive

Description

Monitors the status of physical drives in an array set.

122

NetIQ AppManager for Microsoft Exchange Server Management Guide

Recommended Knowledge Script

[HardwareModule]_FanProbe or

FanIndividual

[HardwareModule]_NICError

[HardwareModule]_PowerSupply

NT_CPULoaded

NT_MemUtil

NT_PhysicalDiskQLen

NT_RunAwayProcesses

NT_SystemUptime

NT_DNSConnectivity

Description

Monitors the status of individual fans.

Monitors network interface transmission errors.

Monitors the status of the hardware power supplies.

Monitors total CPU usage and queue length to determine CPU load.

Monitors physical memory, virtual memory, and paging files.

Monitors the number of disk jobs waiting in the queue.

Detects runaway processes by sampling CPU usage.

Tracks the number of hours a computer has been operational since it was last rebooted.

Checks connectivity between a managed computer and its DNS server.

For reporting and analysis purposes, use the following script from the NT category.

Recommended Knowledge Script

NT_SystemUptime

Description

Tracks the number of hours a computer has been operational since it was last rebooted.

Exchange 2007 Knowledge Scripts

123

124

NetIQ AppManager for Microsoft Exchange Server Management Guide

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents