Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

MessageStats 7.8 - Administrator Guide

Table of Contents

What is MessageStats?

What is MessageStats?

The MessageStats Components

MessageStats Process Overview Example: Creating an Initial Task for an Exchange Environment

MessageStats Information Sources

How Does MessageStats Gather Information?

Gathering Microsoft Exchange Data Gathering Exchange Tracking Logs Sources of Exchange Object Information

Storing Data in the Database Reporting on Data Where to Go from Here

Using the Console Interface

Introducing the MessageStats Console MessageStats Node MessageStats Server Node Database Management Node Exchange Organizations Node

Servers Node

MessageStats Reports Node Support Node Regions Node

Creating Regions Editing Regions Deleting Regions

Task Execution Servers Node

Available Options for Task Execution Servers

Available Options for Tasks Expanding Tasks in the Task Activity View

Cancelling Tasks Reviewing and Saving Task Activity Logs Status Icons

Where to Go from Here

Creating a Connection to Exchange

Connecting to an Exchange Organization Viewing Connected Exchange Organizations

Renaming an Exchange Organization

Creating Gathering Tasks

About the Create Task Wizard

Intelligent Gathering for Exchange Creating a Default Gathering Task

Creating Additional Gathering Tasks Configuring Tasks to Run on a Regular Schedule Forcing an Update on Demand for Exchange

Default Gatherings

About the Exchange Default Gathering Task Creating an Initial Task for Exchange

Setting a Default Gathering to Run on a Schedule

Exchange Default Gathering Task Template Details

Selecting the Task Template Setting the Date Range for Tracking Logs Specifying the Task Execution Server Scheduling the Task Enabling Task Logging for Support Specifying Credentials for a Task Selecting a Gathering Server Selecting a Server for Collecting Mailbox Data

Observing Task Progress

Extending Gathering Tasks

Beyond the Default Gathering Defining Financial Chargeback Gathering Exchange Public Folders

Troubleshooting a public folder gathering

Gathering Content and Attachment Information

Gathering Mailbox Content and Attachments

Selecting Mailbox Items Applying Content Filters Applying Attachment Filters

Gathering Public Folder Content and Attachments

Selecting Public Folder Items Applying Content Filters Applying Attachment Filters

Regathering Exchange Tracking Logs

Setting the Tracking Log Date Range

Configuring Audits

Transport-Level Audits Storage-Level Audits

Managing Audited Information

Considerations for Performing Audits

Setting MessageStats Server Properties

Configuring the MessageStats Server

Specifying the MessageStats Database Settings Configuring Service Logging Setting Up Archiving for Service Logs Specifying Reports IIS Settings Updating Security Credentials for the Scheduler Service

Setting Configuration Properties

Setting General Configuration

Creating Server Roles for Exchange

Setting Exchange Organization Properties

Introducing Exchange Organization Properties Setting General Organization Properties

Selecting a Tracking Log Archive Location

Setting Properties for a Specific Exchange Organization

Identifying Internal SMTP Namespaces Identifying Internal IP Addresses Identifying Mailboxes for Mailbox Auditing Auditing Subject Text in Messages Configuring Internet Domain Auditing Excluding Mailboxes from Gatherings Setting a Threshold for Delivery Time Audits Changing the Exchange Connection Server Selecting a Separate Gathering Server Selecting a Server for Legacy Public Folder Gathering Viewing Task Membership for an Organization Gathering Distribution Group Membership Information Selecting Servers for Tracking Log Archiving

Setting Exchange Server Properties

Setting Properties for an Exchange Server

Assigning a Server Role for Reports Setting Server Thresholds for Reports Selecting a Server for Mailbox MAPI Gathering Selecting a Server for Legacy Public Folder MAPI gathering Viewing General Information for a Server Viewing the Task Membership for a Server Setting an Exchange Server to Archive Tracking Logs

Setting Task Execution Server Properties

Configuring Task Execution Servers

Viewing the Default Task Execution Server Specifying Paths for Task Log Files Setting Up Archiving for Task Logs Configuring Task Processors Modifying Task Processor DCOM Credentials

Setting Task Default Properties

Introducing Task Default Properties

Changing Task Credentials Changing the Schedule for a Task Enabling Task Logging Setting Task Retry Attempts Setting Financial Chargeback Amounts Setting Delivery Time Thresholds Configuring the Tracking Log Cache Using the Default Configuration

Compressing Tracking Log Files

About Compressing Exchange Tracking Logs

Using the MessageStats Compression Tool Files Included in the Compression Tool

Installing and Configuring the Compression Tool

What Happens When You Run QMSDeployment.exe?

Using the MessageStats Reports Console

Introducing MessageStats Reports

Types of Reports

Accessing the Reports

MessageStats Reports Features

Setting Security for Reports

Role-based Security File-System Based Security

Performance Considerations for MessageStats Reports Best Practices for Report Performance

Database Management

About the MessageStats Database Managing your MessageStats Database Using Database Management

Database Management Statistics Deleting Historical Data

Configuring a Data Aging Task

Database Maintenance—Reindexing and Defragmenting the Database

Reindexing the Database Tables Defragmenting the Database

Deleting Object or Report Data

Deleting Report Data Deleting Object Data

Clearing the Database

Appendix A:Microsoft ASP.NET Configuration Issues

Repairing IIS Mappings for ASP.NET

Appendix B: Gathering Task Dependencies

MessageStats Gathering Tasks for Exchange

Appendix C:Troubleshooting Permission Problems

What are the Symptoms of a Permissions Problem? Updating Scheduler Service Permissions

Updating the Scheduler Service Security Context Updating the Scheduler Service DCOM Credentials

Updating MessageStats Tasks Permissions

Updating the Task Processor DCOM Credentials Updating Default Credentials for Tasks

Setting MessageStats Server Properties

•

Configuring the MessageStats Server

•

Specifying the MessageStats Database Settings

•

Configuring Service Logging

•

Setting Up Archiving for Service Logs

•

Specifying Reports IIS Settings

•

Updating Security Credentials for the Scheduler Service

Configuring the MessageStats Server

The server on which you installed the MessageStats Scheduler Service is called the MessageStats Server. You might also install the MMC-based client console and task processors on the same server. In the treeview, the MessageStats Server is the child node of the root.

The properties tabs associated with the MessageStats Server contain the settings for the MessageStats database, the service (application) logs, and the IIS server on which the MessageStats web-based reports are installed.

To access the MessageStats Server property tabs

1

Select the MessageStats Server in the treeview.

2

Right-click and select Properties.

3

Select the tab for the properties tab that you want.

The following MessageStats Server properties tabs are available:

•

Database. See Specifying the MessageStats Database Settings .

•

Service Logging. See Configuring Service Logging .

•

Service Logging Archive. See Setting Up Archiving for Service Logs .

•

Reports. See Specifying Reports IIS Settings .

•

Scheduler Service Credentials. See Updating Security Credentials for the Scheduler Service .

Specifying the MessageStats Database Settings

The Database tab displays the MessageStats database location, the timeout settings, and the maximum number of database records per database update.

Table 1. MessageStats database settings.
Option	Definition
Locate the database on the following SQL server	Defines the location of the MessageStats database. By default, the Database tab contains the name of the database server that you specified during installation. You can edit the location if required.
Long command timeout (in seconds)	Defines the amount of time after which the task processors will time out for the gathering commands. For a long command (such as most of the gathering tasks), the default is 3600 seconds (or one hour).
Short command timeout (in seconds)	For short commands (such as read or write tasks), the default is 60 seconds.
Use the long command timeout when connecting to the database	Used only if you want to use only the long command timeout value.
Maximum number of records per update	Sets the maximum number of database records for a database update.

Configuring Service Logging

MessageStats creates log entries during several processes. You can set scheduler service logging to record the activity of the scheduler service on the MessageStats server.

These logs can help diagnose problems. If you contact Quest Support for assistance, you may be asked to enable or change the logging level of these logs to assist in resolving your problem.

Table 2. Setting logging for the MessageStats scheduler service.
Option	Definition
Enable service logging	Select this option to identify the location and detail level of the logs. The Enable service logging check box is cleared by default.
Store service logs in	Specify the path location in which the log files should be stored.
Log detail level	Set the level of detail that should be included in the log files. For information about the different levels of details, see About Logging Levels .
Record errors in the Windows Application Event Log	Select this option and MessageStats also records errors in Windows Application Event logs.

You can also set logging at the task level, using the Task Logging tab.

About Logging Levels

You can define the logging level for your service logs. The following log levels are available, from the most detailed to the least detailed:

Table 3. Logging levels for the MessageStats scheduler service.
Log Level	Detail
Trace	Trace level logging is extremely detailed logging that includes errors, warnings, and status messages, and also low-level event details. Trace logging is only used with custom components provided by MessageStats development for diagnostic purposes. This level of logging can generate large log file and can affect system performance.
Debug	Debug level logging includes errors, warnings, and status messages, and also low-level event details. Quest Support might ask you to set logging to the debug level to identify and resolve an issue. Use debug-level logging only at the request of Quest Support, since the log files can grow rapidly and can affect system performance. These logs contain very detailed entries.
Status	Status level logging includes warnings and errors, as well as the regular flow of major events within MessageStats. Use the Status level for a new installation to include more detailed logs.
Warning	Warning level logging includes errors that appear at the Errors level. The Warning level also includes errors that occurred but from which MessageStats recovered and continued gathering. Use this level for established and stable implementations.
Errors	Errors level logging includes errors that caused a gathering task to terminate.

It is recommended that you periodically remove obsolete logs. In general, retaining one month of service logs should be sufficient for most enterprises.

The configuration for service logs does not apply to the QMSCompress.log files. The compression logs are external to the MessageStats product. The Gathering Status report includes Errors and Warning details regardless of the detail level that you selected on the General tab.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center