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

MessageStats 7.8.1 - Reports User Guide

Upgrading MessageStats Overview Typical MessageStats Upgrade Scenarios Moving the MessageStats Database Moving and Upgrading MessageStats Moving Custom Reports and Report Subscriptions Viewing, Creating, and Editing MessageStats Reports My Reports and Corporate Reports Exchange Executive Summaries Reports Exchange Organizations Reports Exchange Server Reports Exchange Content Analysis Reports Exchange Mailboxes Reports Exchange Mail Contacts Reports Exchange Distribution Groups Reports Exchange Public Folders Reports Exchange Storage Reports Exchange Internet Reports Exchange Inventory Reports Migration Reports MessageStats Gathering Reports Appendix A: How to Read the Reports Report Filter Definitions

Naming Subscriptions

You can specify a display name to identify the subscription.

To name the subscription
1
Enter a display name for the subscription in the Display Name box.
2
Click Finish.
This name is displayed in your list of current subscriptions.

Changing the SMTP Mail Server or From Display Name

When you install MessageStats Reports, you can specify the SMTP mail server to be used to send subscription notifications and the originator display name. If you did not enter this information during installation, you can use the Configure Subscriptions option on the main Subscriptions dialog. You can edit the mail server name or display name.

To change configuration settings for subscriptions
1
Select the MessageStats Reports node.
2
Click File | Subscriptions | Configure Subscriptions.
3
Edit the SMTP Server and SMTP From Address.

Performance Considerations for MessageStats Reports

The configured reports found in the MessageStats Reports treeview are optimized for performance against a number of standard usage scenarios and date periods. However, due to the volume of data in the MessageStats database and complexity of reports, report performance may slow in some scenarios.

To address slow running reports, there are a number of steps that report consumers and MessageStats administrators can undertake:

•
You can ensure fast-running reports by reducing the number of Parts in an At A Glance report or a custom report.
•
You can increase report rendering by using shorter date periods.

MessageStats administrators can ensure that MessageStats Reports run quickly by performing routine maintenance on the MessageStats database. Maintenance activities include reindexing and defragmenting the database on a regular basis. For information about reindexing and defragmenting data, see the MessageStats Administrator Guide.

When report consumers require long running and complex reports, you could set up report subscriptions that use a delivery method other than Send as Link. This method allows MessageStats Reports to process a report offline for delivery to a web site or within an email body. For information about report subscriptions, see Configuring Report Subscriptions .

Best Practices for reports

To ensure optimal performance, the following best practices are recommended:

•
Install MessageStats Reports on a separate computer to avoid the impact on memory and processor usage due to report rendering.
•
Use filter options to reduce dataset queries. Select specific filter options or a specific date range to ensure that a smaller result set is searched, resulting in quicker results.
•
Carefully define the mailboxes, Internet domains, message subjects and message delivery times that you audit. Performance is affected if you have extensive auditing information in the MessageStats database since the report queries must scan a larger dataset to produce audit reports. For information about auditing, see the MessageStats Administrator Guide.
•
Run statistical reports at the same frequency as the gathering recurrence for the report content. For example, if you configure MessageStats to collect distribution group information on the first day of each month but you create a report subscription for distribution groups to be sent every Friday, only the first Friday of the month contains new information. Each subsequent Friday of the month the report does not contain any new information. The memory and processor time used for subsequent reports could be better used by another process.
•
Create subscriptions only for reports that are useful to oversee and monitor your Exchange organizations. For example, set subscriptions for summary reports to identify anomalies and trends. Based on those the summary reports, create additional reports to investigate any unexpected results.
•
Select the report that best that best suits your needs. Several reports can present the same data organized in different ways (such as Top Senders by Messages and Top Senders by Volume). Determine if one report satisfies the reporting need instead of duplicating the effort.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation