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

MessageStats 7.8.1 - Administrator Guide

What is MessageStats? MessageStats Information Sources Using the Console Interface Creating a Connection to Exchange Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting MessageStats Server Properties Setting Configuration Properties Setting Exchange Organization Properties Setting Exchange Server Properties Setting Task Execution Server Properties Setting Task Default Properties Compressing Tracking Log Files Using the MessageStats Reports Console Database Management Appendix A:Microsoft ASP.NET Configuration Issues Appendix B: Gathering Task Dependencies Appendix C:Troubleshooting Permission Problems

Setting an Exchange Server to Archive Tracking Logs

Tracking log archiving is a feature that compresses and archives Exchange tracking log files. Using the Tracking Logs tab, you can enable the selected Exchange server for archiving. If you are archiving the tracking logs, the tracking logs are archived in the location that was specified using the Tracking Log Archive property tab. For information, see Selecting a Tracking Log Archive Location .

Expand the Exchange Organizations node in the treeview, select and expand an Exchange organization.
Select the Tracking Logs tab.

Tracking log share

Specifies the location where MessageStats looks for new tracking logs.

You can edit this field to specify a UNC path to a different location. This option may be relevant if you have configured your Exchange server to store the tracking log files to member/file servers or in a non-default directory. If you edit the default path to a remote share, you must precede the share name with “\\”.

Alternate tracking log share

Specifies any alternate location where tracking log files reside. This share does not indicate where you want to place archived logs; instead, it indicates where tracking log files already exist.

Select the Archive Tracking Logs check box and click Apply.

For information about the steps that MessageStats performs for archiving, see What is the Workflow for Archiving? .

Setting Task Execution Server Properties

Configuring Task Execution Servers

Task execution servers are servers on which you have installed MessageStats task processors. In a complete installation, the task processors are installed on the same server as the MessageStats Scheduler Service and the MMC console.

In a distributed installation, the task processors might be installed on several additional computers. For each MessageStats instance, there is one MessageStats Scheduler Service that launches the task processors, regardless of where the task processors are located.

Using the properties tabs, you can select a different default task execution server, change the location to which task log files are written, configure archiving for task log files, or set the maximum number of task processors that can run on the task execution server.

The task execution servers are displayed under the Task Execution Servers node in the treeview.

Select Properties.

The following Task Execution Server properties tabs are available:

Viewing the Default Task Execution Server

In a MessageStats implementation with several task execution servers, you can use the Summary tab to view whether this server is the default task execution server. This server is used as the default server when you create new tasks.


Server Name

Shows the name of the selected Task Execution Server.

Is Default Task Execution Server

If the displayed server is the default task execution server for new tasks, this option is selected.

To set the default task execution server, you must right-click on a Task Execution Server in the treeview (or in the list) and select Set As Default.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation