Tchater maintenant avec le support
Tchattez avec un ingénieur du support

MessageStats 7.7.2 - Quick Start Guide

About This Guide Requirements for Installing the MessageStats Components Prerequisites for Gathering from Microsoft Exchange Planning a MessageStats Installation Appendix A: IIS Configuration Issues

Sources of Exchange Information

MessageStats gathers two types of Exchange information:

 
Table 3. MessageStats Sources of Information.
Type
Description

Tracking logs

Log files generated by Microsoft Exchange that track message-related events occurring on or between Exchange servers.

Exchange Object information

Exchange objects that are provided by an Exchange server.

These objects include:

•
Mailbox and user information
•
Mailbox-enabled objects
•
Mail-enabled groups in Active Directory
•
Simple Mail Transfer Protocol (SMTP) domains and address templates for SMTP
•
Internal Namespaces
•
Public Folders
•
Mail Contacts

The information processed from the tracking logs and the Exchange objects provides information about the flow and volume of email over user-defined periods. Report consumers can then view or create a report using MessageStats Reports through a web interface.

MessageStats Architecture

MessageStats is comprised of three main components, and three secondary components, as described in the following sections.

You can install all MessageStats components on a single computer, or you can distribute components on multiple computers, for the purpose of spreading the processing load and locating the gathering function closer to the data sources.

MessageStats Server

MessageStats collects and processes Microsoft Exchange tracking logs and Exchange object usage information from Active Directory, and from a list of Exchange servers, administrative groups, routing groups, and user-defined regions.

The MessageStats Server consists of the following three components:

•
MMC client console: The MessageStats console is a Microsoft Management Console (MMC) snap-in that is used administer MessageStats.
•
MessageStats Scheduler service: In a distributed gathering model, the MessageStats Scheduler Service coordinates all the gathering servers (Task Execution Servers). There can only be one MessageStats Scheduler Service per MessageStats database.
•
Task Execution Server: A server on which you install the task processors is called a Task Execution Server. To optimize information gathering, you can deploy multiple Task Execution Servers across your organization.

The MessageStats Server allows you to:

•
Connect to and enumerate the Exchange organizations.
•
Select the administrative groups, routing groups, regions, or servers that you want to include in your gatherings.
•
Create and schedule gathering tasks for the automated gathering of tracking logs and mailbox statistics.

MessageStats Database

The MessageStats Database is an SQL database that is the main repository for the gathered information. When the database is properly tuned, information can be efficiently stored, and MessageStats Reports can quickly access the required data.

To manage your MessageStats Database, you can use the Database Management functionality from the console to selectively delete obsolete data and to tune the database for optimal performance.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation