立即与支持人员聊天
与支持团队交流

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

Scheduling the Task

Use the Scheduling Tasks page to schedule gathering tasks. You can run a task once or create a regular scheduled task:

 
Table 5. Scheduling the task to run.
Option
Definition

Task Period

Select the time period (Daily, Weekly, Monthly, Once Only, Now) for the scheduled task. For recurring tasks, you can set the recurrence for different intervals:

Daily: By default, the Daily Task Period is configured to perform the gathering task every day. You can change the interval to every two days or at any other appropriate daily period.

Weekly: Using the Weekly period, you can set the following types of schedules: gather every second Tuesday; or gather every Monday, Wednesday, and Friday; or any other combination.

Monthly: Using the Monthly period, you can set the following types of schedules: gather on the first day of each month; gather on the last Friday of March, June, September, and December (each quarter); gather on the fifteenth day of every other month; or any other combination.

Start Time

Enter the start time for the scheduled task.

End Time

You do not need to set an End Time for the schedule. If you want to set an end time, click the check box to select it.

Start Date

Select a start date for the scheduled task.

Enabling Task Logging for Support

MessageStats creates log entries during several processes. If you contact Support for assistance, Support might request that you change your logging detail level to help troubleshoot technical issues. You use the Task Logging page to set logging at the task level.

For information about setting logging at the scheduler service level, see Configuring Service Logging .

 
Table 6. Setting task logging levels.
Option
Definition

Enable logging for the given Task Processor

Select the box to enable logging for this gathering task. You can identify the detail level the task logs.

Log detail level

Set the level of detail that should be included in the log files.

Record errors in the Windows Application Event Log

Select this option and MessageStats also records errors in Windows Application Event logs.

About Logging Levels

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

 
Table 7. Task logging levels.
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 a 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. If you want, you can set up task logging management for the task execution server. After specifying an expiry period, you can set task log files to be deleted, to be moved to a backup location, or to be compressed and moved to a backup location. For more information, see Setting Up Archiving for Task Logs .

Specifying Credentials for a Task

Using the Task Credential page, you set the security credentials for the task. By default, this page displays the credentials that you defined for the MessageStats Scheduler Service during installation. If you changed the Task Execution Server, this page automatically displays the credentials that you specified for that server.

Credentials are not verified in this page. Ensure that you enter a valid account or the gathering tasks will fail. Ensure that the credentials that are specified have the appropriate permissions to run the task against the selected Exchange servers. For more information, see the MessageStats Quick Start Guide.

Selecting a Gathering Server

Selecting a Gathering Server

For organization-level gathering tasks, the Exchange server that is defined as the default Connection server for the Exchange organization is used to gather information. The Connection server is the Exchange server that MessageStats uses as the access point to enumerate an Exchange organization.

On the Gathering Server dialog, you can select a different Exchange server in the organization from which to collect information when creating a Default gathering task. For performance reasons, you may want to gather Exchange information from an Exchange server other than the Connection server.

 
* 
IMPORTANT: You must enter a NETBIOS server name. Do not use the FQDN (Fully Qualified Domain Name) or the IP address for the server.
 
Table 8. Specifying a gathering server.
Option
Definition

Using the currently defined Connection server.

For organization-level gathering tasks, the Exchange server that is defined as the Connection server for the Exchange organization is used to gather information. The Connection server is the Exchange server that MessageStats uses as the access point to enumerate an Exchange organization.

I want to use the following Exchange server.

You can select a different Exchange server in the organization from which to collect information when creating a gathering task. For performance reasons, you may want to gather Exchange information from an Exchange server other than the Connection server.

For information about specifying the gathering server, see Selecting a Separate Gathering Server .

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级