Installing the Microsoft Exchange Management Capabilities Revision 1

(1)

5.5.8 Foglight

®

Installing the Microsoft Exchange Management

Capabilities Revision 1

(2)

or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

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

If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters

LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656

www.quest.com

email: [email protected]

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

Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see http:// www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

Third Party Contributions

Foglight contains some third party components. For a complete list, see the License Credits page in Foglight online help. Installation Guide Revision 1

June 2012

(3)

Introduction to this Guide

This Installation Guide Revision 1 contains the procedures you must follow in order to integrate the Cartridge for Exchange with Foglight or vFoglight.

This guide is intended for any user who is responsible for installing and setting up the Cartridge for Exchange.

This guide is organized as follows:

• Chapter 1, “Installation and Upgrade”- provides procedures for installing and upgrading the Cartridge for Exchange.

• Chapter 2, “Prerequisites and Troubleshooting Tips”- provides information to assist you in troubleshooting issues that may be encounter when installing and using the Cartridge for Exchange.

(6)

About Quest Software, Inc.

Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT management solutions that enable more than 100,000 global customers to save time and money across physical and virtual environments. Quest products solve complex IT challenges ranging from database management, data protection, identity and access management, monitoring, user workspace management to Windows management. For more information, visit www.quest.com.

Contacting Quest Software

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

Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at http://www.quest.com/support.

From our Support Portal, you can do the following:

• Retrieve thousands of solutions from our Knowledge Base • Download the latest releases and service packs

• Create, update, and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures. The guide is available at: http://www.quest.com/ support.

Email [email protected]

Mail Quest Software, Inc.

World Headquarters 5 Polaris Way

Aliso Viejo, CA 92656 USA

(7)

1

Installation and Upgrade

Foglight for Microsoft Exchange provides performance and availability monitoring to help administrators detect, diagnose and resolve problems affecting the Exchange application environment and underlying infrastructure for both virtual and physical environments. This chapter steps you through the installation and upgrade procedure for the Cartridge for Exchange.

Before You Begin

It is recommended that you perform the following steps before you begin the installation procedure:

• If you do not already have the Cartridge for Exchange, you can download it from the Quest website at http://support.quest.com.

• Before you can download the product, you must register with Quest. If you are a registered Quest user, log on using your email address and password.

• Once you have registered or logged in, locate the product and version that you want to download from the product list.

• In the download window, click the link and save the file to an appropriate directory (e.g., C:\temp).

• Review the Requirements and Compatibility section.

• Read the Release Notes for updated or additional information about this version of the cartridge.

(8)

Requirements and Compatibility

The following are the requirements to successfully integrate the Cartridge for Exchange into Foglight or vFoglight.

Foglight Management Server

The Cartridge for Exchange is compatible with Foglight Management Server 5.5.8 or higher. It can be installed as a stand-alone cartridge on a Foglight platform. In this configuration, all Exchange metrics are collected as well as basic host metrics from both physical and virtual Exchange Servers.

Before installing the cartridge, ensure that your Foglight Management Server is properly installed and configured. For information on how to install and configure the Foglight Management Server, please refer to the appropriate Foglight Installation and Setup Guide.

vFoglight

The Cartridge for Exchange can also be used with a vFoglight platform in order to gain in-depth insight into the health of the virtual machine, the virtual host and the virtual environment as a whole. The minimum vFoglight version supported is 6.5.1.

Agent Components

In addition to meeting the minimum requirements for the Foglight Management Server, your system must meet the following minimum software requirements:

Cartridge for Active Directory Compatibility

If running the Cartridge for Exchange and Cartridge for Active Directory, ensure that both cartridges are running the same version and patch level.

Operating System Domain controllers specified in the Exchange agent properties must be Windows Server 2003 or newer.

Note If you are using Windows 2008 R2, please refer to the prerequisite described in Prerequisites and Troubleshooting Tips.

Note There has been no testing performed on Small Business Systems (SBS) versions.

Note Read Only Domain Controllers (RODCs) are NOT supported.

Additional Software Monitored Exchange servers must be running one of the following: • Microsoft Exchange 2007 SP1, SP2 or SP3

(9)

Installing the Microsoft Exchange Management Capabilities: Installation Guide Revision 1 9 Chapter 1—Installation and Upgrade

Installation Best Practices

If you are running the Cartridge for Exchange ‘out-of-the-box’ to monitor 50 or less Exchange servers, you can use the single-tier Foglight installation where you are running both the Foglight Management Server (JVM) and Foglight Database Repository on the same machine. You can also use one Foglight Agent Manager (FglAM) for up to 50 agent instances.

However, under the following situations, you should consult a qualified Quest Software

representative, to determine if you should use a multi-tier installation (which requires a separate machine for each of the Foglight Manager Server (JVM) and Foglight Database Repository) or install more Foglight Agent Managers (FglAMs):

• You are monitoring more than 50 servers.

• You intend to enable optional metrics on a frequent basis. • You intend to run diagnostic tests on a frequent basis.

For more information on Foglight’s hardware requirements, see the Foglight Requirements and

Platform Support Guide.

Installation and Setup

In order for the Cartridge for Exchange data to appear on the Foglight browser interface, you must first:

1 Install Foglight or vFoglight 2 Install the Cartridge for Exchange 3 Deploy Agent Packages*

4 Create Agents*

5 Activate Agents and Start Data Collection*

* These steps can be performed using the Exchange Agent Management dashboard or using the Agent Status dashboard. The Exchange Agent Management dashboard allows you to add new agents to multiple servers using the Agent Setup wizard. The Agent Status dashboard allows you to add and configure individual agents one at a time. The following procedures use the Exchange Agent Management dashboard. The steps for using the Agent Status dashboard are included as an alternate method.

Install Foglight or vFoglight

To install Foglight or vFoglight:

1 Obtain the Foglight installation package (Foglight or vFoglight).

2 Upload the installation package to your target machine, preferably a physical machine that will serve as the central collection point.

3 Click the executable file and follow the installation process using preferred settings (default settings are sufficient).

(10)

4 Ensure that the server has successfully started. Open your browser and navigate to: http://<yourserver>:8080

where <yourserver> is the address of the machine where you installed and set up Foglight. Note The default port is 8080; however, this is user configurable during installation.

Install the Cartridge for Exchange

To install the cartridge:

1 Log on to Foglight and using the navigation panel, navigate to Dashboards >

Administration > Cartridges > Cartridges Inventory.

2 On the Cartridges Inventory page, in the Install Cartridge area at the top of the page, enter the path and file name (ExchangeMonitoring-5_5_8_1.car) for the Cartridge for Exchange. • Type the path in the File on Local Computer field to upload the .car file from your local

computer to the Foglight Management Server. Alternatively, select Browse to navigate to the .car file on your local computer.

• Type the path in the File on Server field to install the .car file from a directory on the machine hosting the Foglight Management Server.

3 To enable the cartridge when it is installed, leave the Enable on install check box selected. To enable the cartridge after the installation, clear this check box.

4 Click Install Cartridge.

Note This may take some time to upload and validate, you will be notified of success.

If the installation is successful, a Cartridge has been installed successfully message appears and the ExchangeMonitoring cartridge displays in the Cartridge Inventory table.

5 Press F5 to refresh the browser interface to display the newly installed cartridge and its components.

Enable the Cartridge

Enabling a cartridge completes the process of adding it to Foglight and makes its components available for use.

The following procedure should be performed only if you did not enable your cartridge during the installation process, as outlined in step 3 of the Install the Cartridge for Exchange procedure.

To enable a cartridge:

1 Using the navigation panel in Foglight, navigate to Dashboards > Administration >

Cartridges > Cartridge Inventory.

2 In the Cartridge Inventory table, select the row that corresponds to the Cartridge for Exchange (ExchangeMonitoring). The row becomes highlighted.

3 Select Enable Selected at the bottom of the page.

When the cartridge is enabled, a success message appears and an Enabled status icon appears in the Status column for the selected cartridge.

(11)

Deploy Agent Package

Once the cartridge has been successfully installed, you will need to deploy the agent package for the cartridge to each Foglight Agent Manager that will host an Exchange agent instance.

To deploy the Exchange agent package:

1 Using the navigation panel in Foglight, navigate to Dashboards > Exchange > Agent

Management.

2 Click Deploy Agent Package in the task list at the top of the Exchange Agent Management dashboard.

3 On the Deploy Agent Package dialog, select the Foglight Agent Manager host to which the Exchange agent package is to be deployed. Click Deploy.

Note You can only select one Foglight Agent Manager host. To deploy the Exchange agent package to more than one Foglight Agent Manager host, repeat these steps for each host.

4 Wait for positive feedback from the web application. Select the close button in the upper right corner of the dialog to close the confirmation dialog.

Note Because you are only deploying agent packages at this time, the newly deployed package will NOT appear in the Agent Management list.

Configure Agent Properties

The Cartridge for Exchange needs the basic host metrics (CPU, Memory, Network, Storage). These host metrics can be collected by the Exchange, Hyper-V or VMWare cartridge. Using the agent’s properties page, you must specify the cartridge to be used to collect these host metrics:

• Exchange - if selected, all host collections are collected based on the interval set in the collection schedule.

• Hyper-V (must be installed) - if selected, only the memory utilization and disk I/O metrics will be collected based on the interval set in the collection schedule; all other host metrics are collected based on the settings in the Hyper-V cartridge.

• VMWare (must be installed) - if selected, the host collections are skipped regardless of the value in the collection schedule. That is, all host collections are collected based on the settings in the VMWare cartridge.

Note If you have the Hyper-V or VMWare cartridge installed and it is configured to monitor this server, it is best to select the corresponding option and use the metrics collected by that cartridge. If you are collecting host metrics on a virtual machine using the Exchange cartridge,

performance counters may be subject to known inconsistencies because in-guest performance counters can be skewed by virtualization. To collect the most accurate host metrics on a virtual machine, use the VMWare or Hyper-V cartridge to collect these metrics.

(12)

To configure agent properties:

1 Using the navigation panel of Foglight, navigate to Dashboards > Administration >

Agents > Agent Status.

2 Select an agent in the list and click Edit Properties.

The Agent Status dashboard refreshes, showing the current properties of the selected agent instance.

3 Select one of the following property scope options:

• Modify the private properties for this agent

• Modify the properties of all ExchangeAgent agents

Note It is best to configure the agent properties that are to be applied globally to the majority of the Exchange agent instances. Then go back and modify the private properties of those individual agents as required.

Selecting one of these options enables the agent’s properties allowing you to edit them. 4 In the Configuration panel, modify the agent’s properties as required.

In the Host Collector property, select the cartridge to be used to collect host metrics. • To collect host metrics using the Hyper-V cartridge, select the Hyper-V option. • To collect host metrics using the VMWare cartridge, select the VMWare option. • If neither the Hyper-V or VMWare cartridge is installed or configured to monitor this

server, select the Exchange option.

5 Select Save Changes and use the close button in the upper right-hand corner to close the dialog.

6 Select Save and click Back to Agent Status to return to the Agent Status dashboard.

Create Agents, Activate Agents and Start Data Collection

Once the agent packages for the cartridge have been successfully installed and configured, you will need to create and activate agent instances, and start collecting data. To perform these steps on multiple servers, use the Exchange Agent Management dashboard.

Note If you would prefer to perform these steps as individual operations on a single server, use the Agent Status dashboard. Please skip to Alternate Method for Deploying, Creating and Activating Agents.

Note Since the Edge Transport server is not a member of the Active Directory domain, you cannot use the Agent Setup wizard on the Exchange Agent Management dashboard to create an agent instance for that server. Use the Agent Status dashboard to create an agent instance on the Edge Transport server.

1 Using the navigation panel in Foglight, navigate to Dashboards > Exchange > Agent

Management.

2 In the Exchange Agent Management table, select Add to launch the Agent Setup wizard. (Or select the Add and Configure New Agents task in the task list at the top of the dashboard.)

(13)

3 On the Foglight Agent Manager Host page, select the Foglight Agent Manager (FglAM) host for the new Exchange agent instances.

4 On the Domain to Search for Exchange Servers page, enter the following information: • Domain - enter the fully qualified domain name (myDomain.com) of a domain to search

for Exchange servers.

• Account UPN - enter the user principal name ([email protected]) of the account that is to be used to query Active Directory on the selected domain.

• Password - enter the password associated with the account entered above.

5 On the Exchange Servers to Monitor page, select one or more Exchange servers that are to be monitored.

Note All selected servers will use the same user credentials for access.

6 On the Credentials for Exchange Server and Domain Controller page, enter the following: • Account UPN - enter the user principal name ([email protected]) of an account in

the selected domain that has access to the selected Exchange server(s).

Note This account must be an Active Directory account with elevated privileges (Domain Administrator) in the domain where the server is located.

Note The sAMAccountName and the account CN for this account should be identical and should not contain spaces or LDAP authentication errors may occur.

• Password - enter the password associated with the account entered above. • Domain Controller - enter the fully qualified domain name

(myDomainController.myDomain.com) of a DC in the domain where the selected Exchange server(s) reside.

• Account UPN - enter the user principal name ([email protected]) of an account that has access to the specified DC.

Note This account must be an Active Directory account with elevated privileges (Domain Administrator) in the domain where the server is located.

Note The sAMAccountName and the account CN for this account should be identical and should not contain spaces or LDAP authentication errors may occur.

• Password - enter the password associated with the account entered above. 7 Select Finish to close the wizard and create the selected Exchange agent instances. 8 Back on the Exchange Agent Management dashboard, select the agent instances to be

activated and select the Activate button.

9 Select the Refresh button. The Active and Data Collection cells will contain a green check mark when the selected Exchange agents are successfully activated and have started collecting data.

Note Neither the Browser refresh icon nor F5 will refresh the agent management table. 10 If an agent does not start collecting data once it is activated, select the agent from the list and

(14)

11 Using the navigation panel in Foglight, navigate to Dashboards > Exchange > Exchange

Environment to view Exchange health and performance metrics.

Note Once an agent has been successfully set up, it may take a couple of minutes to collect a large enough sample to observe.

Alternate Method for Deploying, Creating and Activating Agents

If you would prefer to deploy, create and activate individual agents one at a time, use the Agent Status dashboard as described below.

Deploy Agent Packages

Once the cartridge has been successfully installed, you will need to deploy the agent package for the cartridge to each Foglight Agent Manager that will host an Exchange agent instance.

1 Using the navigation panel in Foglight, navigate to Dashboards > Administration >

2 Click Deploy Agent Package in the lower left of the Agent Status dashboard. 3 On the Deploy Agent Package dialog, select the FglAM host and package file (e.g.,

ExchangeMonitoring.gar). Select Deploy.

4 Wait for positive feedback from the web application. Select OK to close the Deploy Agent Package dialog and return to the Agent Status list.

Note Because you are only deploying agent packages at this time, the newly deployed package will NOT appear in the Agent Status list.

Create Agents

Once the agent package has been successfully deployed, you will need to create an agent instance for each Exchange server to be monitored.

To create an agent instance:

1 Using the navigation panel of Foglight, navigate to Dashboards > Administration >

2 Click Create Agent in the lower left of the dashboard.

3 On the Create Agent dialog, select the FglAM host, select the Agent Type (ExchangeAgent) and enter an Instance Name for the agent. Select Create.

4 Wait for positive feedback that the agent was installed. Select OK to close the Create Agent Results dialog and return to the Agent Status dashboard.

5 After the agent is created, select the agent in the list and click Edit Properties. 6 Click the Modify the properties for this agent only link and enter the following

information:

• Host Name - enter the fully qualified domain name (myServer.myDomain.com) of the target server from which data is to be collected.

• Account UPN - enter the user principal name ([email protected]) of a user account that has elevated privileges (Domain Administrator) on the target server.

(15)

• Account Password - enter the password associated with the account entered above. • Domain Controller Name - enter the fully qualified domain name

(myServer.myDomain.com) of a DC in the same domain where the Exchange servers reside.

• Domain Controller Account UPN - enter the user principal name

([email protected]) of a user account that has elevated privileges (Domain Administrator) on the target DC.

• Domain Controller Password - enter the password associated with the account entered above.

7 In the Host Collector property, select the cartridge to be used to collect host metrics: • To collect host metrics using the Hyper-V cartridge, select the Hyper-V option. • To collect host metrics using the VMWare cartridge, select the VMWare option. • If neither the Hyper-V or VMWare cartridge is installed or configured to monitor this

server, select the Exchange option.

8 Select Save Changes and use the close button in the upper right-hand corner of the dialog to close the dialog.

Note If this step is not performed, the cartridge will not collect host metrics.

9 Select Save and click Back to Agent Status to return to the Agent Status dashboard.

Activate Agent and Start Data Collection

1 From the Agent Status dashboard, select the agent from the list and click Activate. 2 Click Refresh in the upper right corner of the dashboard.

Note Neither the Browser refresh icon nor F5 will refresh the agent status.

Note The first two columns in the Agent Status dashboard should show green icons for an active and healthy agent that is collecting data. It may be necessary to stop and start data collection, based upon agent state, configuration errors, etc. before the agent becomes active and successfully collects data.

3 If the agent does not start collecting data when it is activated, select the agent from the list and click Start Data Collection. Click Refresh.

(16)

Upgrading the Cartridge for Exchange

The latest version of the Cartridge for Exchange is 5.5.8.1.

Note All original rules in each cartridge are reset when the cartridge is upgraded; therefore if you applied custom conditions to any original rules these modifications will be lost. It is

recommended that when modifying rules you make a copy of the original, disable the original and enable the copy with the new condition. Use the Manage Rules dashboard (Dashboards >

Administration > Rules & Notifications > Manage Rules) to copy a rule.

To upgrade the cartridge:

1 Install version 5.5.8.1 of the cartridge. 2 Deactivate all of the Exchange agents.

Note If you deactivate agents and then install the cartridge, some of the agents may start back up.

3 Deploy the agent package to the Foglight Agent Manager that hosts an Exchange agent instance and wait for the version to update.

Note This may take two to three refresh cycles.

4 Verify the agent properties and update the properties as required. 5 Activate the agents and start collections.

Note If you are also running the Cartridge for Active Directory, upgrade the Active Directory agents. These cartridges share code and should be running the same version and patch level.

(17)

2

Prerequisites and Troubleshooting Tips

This chapter provides additional information to assist you in troubleshooting issues that may be encountered when installing or using the Cartridge for Exchange.

Prerequisites

The following prerequisite conditions must be in place in order to successfully initialize an Exchange agent. Failure to meet these prerequisites may result in missing metrics in the Cartridge for Exchange dashboards.

Important All prerequisite steps must be completed on the Exchange server as well as the Active Directory server because the Exchange agent collects information from the Active Directory server and requires access permissions.

Note The Remote Access Diagnostics utility, provided with this cartridge, checks the connectivity between the Foglight Agent Manager (FglAM) and Active Directory and Exchange servers that are being monitored. It also tests for the prerequisite conditions that must be met in order to initialize an Exchange agent. This utility requires .NET 2.0 libraries to run. For more information on running the Remote Access Diagnostics utility, see the Remote Access Diagnostics User

Guide.

Permissions

An Active Directory account with Domain Administrator permissions must be specified in agent properties. This is the account used to run remote scripts. The sAMAcountName and the account CN should be identical and should not contain spaces or LDAP authentication errors may occur. Symptoms

• An agent’s data collection status will not remain healthy. • Empty charts or missing server objects.

Resolution

• Ensure that the account has Domain Administrator permissions. • Re-enter passwords to guard against fat-finger mistakes.

(18)

Permissions: Exchange Agent

The Cartridge for Exchange uses PowerShell commands to capture the data for Exchange diagnostic tests, cluster metrics, role feature states and the archive user count in Exchange 2010. Therefore, the user account used by the Exchange agent must be assigned the ‘Log on as a service’ rights.

Symptoms

• Exchange diagnostic tests will not run successfully. • Exchange cluster metrics will be missing

• Role feature state queries will fail.

• In Exchange 2010, the archive user count will be missing. Resolution

• Ensure the user account used by the Exchange agent is assigned the ‘Log on as a service’ rights.

Agent Must be Able to Reach the Target Host

Server objects do not appear until at least one piece of data has been collected and recorded. If communication fails completely, you will not see objects.

Symptoms

• Agent activation or data collection status will not stay green. • Servers do not appear in the Cartridge for Exchange views. Resolution

• Test Ping by IP. You must be able to ping the collection target from the FglAM hosting the agent instance. If ping by IP fails, there are routing issues.

• Test Ping by host name. A DNS server or Hosts file must be available to the FMS server in order to resolve names. If ping by host name fails, there are DNS or Hosts file issues. • If a Hosts file is used it should contain an entry for each domain where hosts reside. For

example,

10.10.10.100 domain.local

10.10.10.200 childdomain.domain.local

In addition, individual servers must resolve to the NetBIOS names and the FQDN. For example,

10.10.10.101 server server.domain.local

(19)

Installing the Microsoft Exchange Management Capabilities: Installation Guide Revision 1 19 Chapter 2—Prerequisites and Troubleshooting Tips

Remote Scripting Must be Enabled

Since the Cartridge for Exchange uses an agent-less design, remote execution of scripts must be enabled on both Exchange servers and the Domain Controller. If communication fails completely, you will not see server objects. If partial data is collected, the server object will appear in the UI and the metrics with values will be displayed.

Symptoms

• Agent activation or data collection status will not stay green. • Servers do not appear in the Cartridge for Exchange views.

• There will be a log entry prompting you to read the getting started literature.

• If queries partially succeed, you may see some charts with no values and others with values. Resolution

1 Enable Distributed COM (DCOM) on all Exchange servers: • Start | Run.

• In the Run dialog, enter dcomcnfg and click OK. • Expand Component Services and then Computers.

• Right-click the My Computer object and select Properties.

• On the Default Properties tab, check the Enable Distributed COM on this computer option.

2 Enable Remote Script host on all Exchange servers:

Tip It is recommended that you create a backup copy of the Registry that you can revert to prior to making any changes.

• At the command line, enter: wscript -regserver • Run: regedit

• If you are asked to allow the Regedit program to make changes to the computer, click Yes. • Navigate to registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

(20)

• Set the String Value key named ‘Remote’ to 1. If the key does not exist under Settings, create it.

• If the server does not begin allowing remote connections, reboot the server to activate this setting.

Remote Registry Service Must be Running

The Remote Registry Service must be running on each Exchange server being monitored by the Cartridge for Exchange.

Symptoms

• Exception [0x00000005] is thrown with the message 'Access is denied, please check whether the [domain-username-password] are correct.'

• The agent will activate but collections will stop. Resolution

• Ensure the Remote Registry Service is running.

Windows 2008 R2 Prerequisite

For both the monitored Exchange servers and domain controllers, the account specified in the agent properties must have Full Control permissions on the registry keys for the following:

• CLSID 76A64158-CB41-11d1-8B02-00600806D9B6 (WBEM Scripting Locator)

• CLSID72C24DD5-D70A-438B-8A42-98424B88AFB8 (Windows Script Host Shell Object) Note In Windows operating systems prior to 2008 R2, these permissions are granted to members of

the Administrators group by default. However, in Windows 2008 R2, these permissions must be explicitly granted.

Symptom

Depending on the prerequisite, you will encounter a complete failure to collect data (missing servers) or subsets of missing values (empty charts).

(21)

Resolution

1 Login to the domain controller with an Administrator account that you are comfortable having ownership over these keys.

2 Run Regedit.

3 If you are asked to allow the Regedit program to make changes to the computer, click Yes. 4 Navigate to the registry item: HKEY_CLASSES_ROOT\CLSID\{clsid}.

5 Right-click the registry key and select Permissions. 6 Click Advanced.

7 Open the Owner tab.

8 In the Change Owner to box, select one of the following entries: • the user account that you are currently logged in

• the administrative group to which the account you are currently logged in as belongs 9 Select the Replace the owner on subcontainers and objects check box.

10 If the account is not listed, use the Other user or groups button to add the account. 11 Click OK.

12 Under Group or user names, select the account that will be specified in the agent properties. If the account is not listed, use the Add button to add the account.

13 Under Permission for account, select the Allow Full Control check box and click OK.

Register WMI Classes

The appropriate WMI classes must be registered or the associated queries will fail.

Note By default, Exchange may not automatically register some of the required classes with WMI. These WMI classes must be registered/checked for every Exchange server.

You can run the Prerequisite Test (included in the Remote Access Diagnostics utility) locally on servers to test if WMI classes are responding to queries. For more information on running this test, see the Remote Access Diagnostics User Guide.

The following list contains the WMI classes that are queried by the Cartridge for Exchange. EX (Mailbox)

• Win32_PerfRawData_ESE_MSExchangeDatabaseInstances • Win32_PerfRawData_ESE_MSExchangeDatabase

• Win32_PerfRawData_MSExchangeIS_MSExchangeISMailbox

(22)

• Win32_PerfRawData_MSExchangeMailSubmission_MSExchangeMailSubmission • Win32_PerfRawData_MSExchangeIS_MSExchangeISClient • Win32_PerfRawData_MSExchangeResourceBooking_MSExchangeResourceBooking • Win32_PerfRawData_MSExchangeSearchIndices_MSExchangeSearchIndices • Win32_PerfRawData_MSExchangeAssistants_MSExchangeAssistants • Win32_PerfRawData_MSExchangeStoreInterface_MSExchangeStoreInterface • Win32_PerfRawData_MSExchangeIS_MSExchangeISPublic • Win32_PerfRawData_MSExchangeCalendarAttendant_MSExchangeCalendarAttendant • Win32_PerfRawData_MSExchangeReplicaSeeder_MSExchangeReplicaSeeder • Win32_PerfRawData_MSExchangeIS_MSExchangeIS EX (ClientAccess) • Win32_PerfRawData_MSExchangeFDSOAB_MSExchangeFDSOAB • Win32_PerfRawData_Counters_RPCHTTPProxy • Win32_PerfRawData_MSExchangeActiveSync_MSExchangeActiveSync • Win32_PerfRawData_MSExchangeWS_MSExchangeWS • Win32_PerfRawData_MSExchangeAvailabilityService_MSExchangeAvailabilityService • Win32_PerfRawData_W3SVC_WebService • Win32_PerfRawData_MSExchangeOWA_MSExchangeOWA • Win32_PerfRawData_MSExchangeAutodiscover_MSExchangeAutodiscover EX (ClientAccess -additional for 2010)

• Win32_PerfRawData_MSExchangeRpcClientAccess_MSExchangeRpcClientAccess • Win32_PerfRawData_MSExchangeControlPanel_MSExchangeControlPanel • Win32_PerfRawData_MSExchangeAB_MSExchangeAB EX (Unified Messaging) • Win32_PerfRawData_MSExchangeUMSubscriberAccess_MSExchangeUMSubscriberAccess • Win32_PerfRawData_MSExchangeUMGeneral_MSExchangeUMGeneral • Win32_PerfRawData_MSExchangeUMCallAnswer_MSExchangeUMCallAnswer • Win32_PerfRawData_MSExchangeUMPerformance_MSExchangeUMPerformance • Win32_PerfRawData_MSExchangeUMAutoAttendant_MSExchangeUMAutoAttendant • Win32_PerfRawData_MSExchangeUMAvailability_MSExchangeUMAvailability • Win32_PerfRawData_MSExchangeUMFax_MSExchangeUMFax EX (Hub Transport) • Win32_PerfRawData_ESE_MSExchangeDatabase

(23)

• Win32_PerfRawData_ESE_MSExchangeDatabaseInstances • Win32_PerfRawData_MSExchangeStoreDriver_MSExchangeStoreDriver • Win32_PerfRawData_MSExchangeTransportQueues_MSExchangeTransportQueues • Win32_PerfRawData_MSExchangeExtensibilityAgents_MSExchangeExtensibilityAgents • Win32_PerfRawData_MSExchangeTransportDumpster_MSExchangeTransportDumpster • Win32_PerfRawData_MSExchangeEdgeSyncJob_MSExchangeEdgeSyncJob • Win32_PerfRawData_MSExchangeTransportSmtpReceive_MSExchangeTransportSmtp Receive • Win32_PerfRawData_MSExchangeTransportSmtpSend_MSExchangeTransportSmtpSend EX (Edge Transport) • Win32_PerfRawData_MSExchangeADAccess_MSExchangeADAccessProcesses • Win32_PerfRawData_ESE_MSExchangeDatabase • Win32_PerfRawData_MSExchangeSenderFilterAgent_MSExchangeSenderFilterAgent • Win32_PerfRawData_MSExchangeAttachmentFiltering_MSExchangeAttachmentFiltering • Win32_PerfRawData_MSExchangeTransportQueues_MSExchangeTransportQueues • Win32_PerfRawData_MSExchangeADAccess_MSExchangeADAccessDomainControllers • Win32_PerfRawData_MSExchangeStoreDriver_MSExchangeStoreDriver • Win32_PerfRawData_MSExchangeExtensibilityAgents_MSExchangeExtensibilityAgents • Win32_PerfRawData_MSExchangeTransportDumpster_MSExchangeTransportDumpster • Win32_PerfRawData_MSExchangeADAccess_MSExchangeADAccessCaches • Win32_PerfRawData_MSExchangeSenderIdAgent_MSExchangeSenderIdAgent • Win32_PerfRawData_MSExchangeRecipientFilterAgent_MSExchangeRecipientFilterAgent • Win32_PerfRawData_MSExchangeTransportSmtpReceive_MSExchangeTransportSmtp Receive • Win32_PerfRawData_MSExchangeTransportSmtpSend_MSExchangeTransportSmtpSend • Win32_PerfRawData_MSExchangeContentFilterAgent_MSExchangeContentFilterAgent • Win32_PerfRawData_DirectoryServices_DirectoryServices • Win32_PerfRawData_MSExchangeTransportRules_MSExchangeTransportRules • Win32_PerfRawData_MSExchangeEdgeSyncJob_MSExchangeEdgeSyncJob Host • Win32_ComputerSystem • Win32_OperatingSystem • Win32_Processor • Win32_PerfRawData_PerfOS_System • Win32_PerfRawData_PerfOS_PagingFile

(24)

• Win32_PerfRawData_PerfOS_Processor • Win32_PhysicalMemory • Win32_PerfRawData_PerfOS_Memory • Win32_PerfRawData_PerfDisk_PhysicalDisk • Win32_PerfRawData_PerfDisk_LogicalDisk • Win32_LogicalDisk • Win32_PerfRawData_Tcpip_NetworkInterface • Win32_PerfRawData_PerfProc_Process • Win32_ComputerSystem • Win32_PerfFormattedData_PerfOS_PagingFile • Win32_PerfRawData_PerfOS_Processor • Win32_LogicalDisk • Win32_Service

PowerShell Configurations Required for Feature State Queries

.

In order for the OWA feature states to work properly, the following PowerShell script must first be run: new-TestCasConnectivityUser.ps1.

Symptom

• On the Client Access Features view, the OWA feature states will be ‘unknown’. Resolution

• Use the new-TestCasConnectivityUser.ps1 PowerShell script per the instructions provided by Microsoft to configure the CAS Connectivity User. Once the user is configured, the Exchange agent will use it to run the Client Access - OWA role ‘feature state’ query. The new-TestCasConnectivityUser.ps1 script can be found in the Scripts folder of your Exchange install directory. If Exchange is installed at C:\Program Files\Microsoft\Exchange, then this script will be found at C:\Program Files\Microsoft\Exchange\Scripts.

(25)

Troubleshooting Tips

Active Directory\Exchange Cartridge Integration

The following domain controller specific metrics are not available in the Cartridge for Exchange unless an Active Directory agent is monitoring the domain controller:

• Replication Queue Length • Replication Failures Symptom

• Some domain controller specific metrics do not display in the Cartridge for Exchange views Resolution

• Install the Cartridge for Active Directory.

Exchange Server Discovery Feature

The Cartridge for Exchange now detects when an Exchange server is added or removed. Alarms are generated for the following cases:

• A new Exchange 2007/2010 server is detected and there is no agent monitoring it.

• A new Exchange server is detected, but the Exchange version on this server is not supported for monitoring.

• An existing Exchange server is removed and an associated agent still exists. Symptom

• Alarms are not being generated when an Exchange server is added or removed. Resolution

• There are two rules used for the Exchange Server Discovery feature. Disabling either one of these rules will disable alerting on server discovery. Ensure that the following rules are not disabled:

• EXC Server Discovery Search • EXC Server Discovery Alert

• The EXC Server Discovery Search rule fires every 24 hours and an LDAP query is made once for every domain that has an active, collecting agent. Therefore, depending on when the server was added or removed, there may be a delay in seeing the alarm. Also, if the agent is deactivated or not collecting data, the new or removed server will not be detected until the next server discovery search interval after the agent is re-activated and collecting data.

(26)

RPCs Failed (Server Too Busy) Performance Metric

The RPCs Failed (Server Too Busy) performance metric is a client-reported value. In order to send this type of data to the server in Outlook 2003 or later, the Exchange server’s registry must contain the ClientMonitoringReportLevel registry key with a value of either one or two.

Symptom

• RPCs Failed (Server Too Busy) performance metric is not being collected. Resolution

• Ensure that the server’s registry contains the ClientMonitoringReportLevel registry key with a value of either one or two.

• In Exchange 2007, the default behavior is to collect performance data only from Outlook clients that have high-speed network connectivity. (Functionally the same as when the value of the ClientMonitoringReportLevel registry key is set to one.)

• For clients that are using a low-bandwidth connection, set the value of the ClientMonitoringReportLevel to two.

• To modify the client-side monitoring levels for Outlook 2003 or later clients:

• On the Exchange server that contains the client mailboxes to be monitored, run: regedit. • If you are asked to allow the Regedit program to make changes to the computer, click Yes. • Navigate to the following registry key:

HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem • Right-click ParametersSystem and click New | DWORD Value.

• Name the new DWORD value ClientMonitoringReportLevel. • Double-click ClientMonitoringReportLevel.

• In the Value data field, enter the appropriate value:

0 = do not collect data from any Outlook 2003 and later clients

1 = collect performance data only from high-bandwidth Outlook 2003 and later clients

(default)

2 = collect performance data from all Outlook 2003 or later clients

• Close the registry editor.

The Exchange Information Store service automatically detects the changes. You do not need to restart the computer or any services.

(27)

Monitoring Microsoft Exchange Monitoring Service

The Microsoft Exchange Monitoring service is not monitored and alarms will not be raised for this service by default. However, if you use this service in your Exchange organization, you can enable monitoring.

Symptom

• Microsoft Exchange Monitoring service is not being monitored. Resolution

• Enable monitoring of this service.

• Navigate to Dashboards > Administration > Agents > Agent Status. • Under Monitor, select a Monitored Service and click Edit.

• Click Add Row in the ExchangeMonitoring - ExchangeAgent - monitoredServicesList table.

• Enter the Server Role and the Service Name for the service to be monitored. All entries are case sensitive.

win2k3\MicrosoftExchangeMonitoring or

win2k8\MicrosoftExchangeMonitoring • Click Save Changes.

Recommended Best Practices

The following procedure is a best practice that is recommended for optimal performance.

Disable Automatic Updates on Foglight Management Server

Do NOT allow Microsoft’s automatic update feature to force an update of the server hosting the Foglight Management Server. This automatic update feature does not allow enough time for the Foglight Management Server to shutdown gracefully, which may leave your agents in a broken state.

Symptoms

• Cartridge agents will appear to be deactivated on the Agent Status dashboard. Resolution

• Using the Agent Status dashboard, select the deactivated agent and select the Activate button.

(28)

Index

A

activate agents

using Agent Setup wizard 12 using Agent Status dashboard 15

agent components requirements 8 Agent Setup wizard 12

alternate method for creating and activating agents 14

B

Best Practices

disable automatic updates on FMS 27 installation 9

C

cluster metrics

permissions required 18

compatibility 8

configure agent properties 11 create agents

D

deploy agent package

using Agent Status dashboard 14

using Exchange Agent Management dashboard 11

diagnostic tests

disable automatic updates on FMS 27

E

enable the cartridge 10

Exchange Agent Management dashboard 12 Exchange Server Discovery feature 25

F

Foglight Management Server compatibility 8

I

install cartridge 10 install Foglight 9 install vFoglight 9

installation best practices 9 installation procedure 9

Integration with Active Directory cartridge 25

M

Microsoft Exchange Monitoring Service 27

P

permissions 17

Active Directory account 17 Exchange agent 18

Exchange cluster monitoring 18 Exchange diagnostic tests 18 Exchange role feature states 18

prerequisites 17

Agent must be able to reach target host 18

PowerShell configurations required for feature state queries 24

register WMI classes 21

Remote Registry Service must be running 20 remote scripting must be enabled 19 Windows 2008 R2 20

R

register WMI classes 21 Remote Registry Service 20 Remote scripting 19 requirements 8 role feature states

RPCs Failed (Server Too Busy) performance metric 26

S

(29)

Installing the Microsoft Exchange Management Capabilities: Installation Guide Revision 1 29 Index

support 6

T

technical support 6 troubleshooting tips 25

U

upgrade procedure 16

V

vFoglight compatibility 8

W

Windows 2008 R2 prerequisite 20 WMI classes queried 21

Installing the Microsoft Exchange Management Capabilities Revision 1

5.5.8

Foglight

®