Chat now with support
Chat con el soporte

MessageStats 7.5.1 - Administrator Guide

What is MessageStats? MessageStats Information Sources Creating a Connection to Exchange Using the Console Interface Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting Configuration Properties Setting MessageStats Server 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

Excluding Mailboxes from Gatherings

You can exclude specific mailboxes from the gathering process. There might be mailboxes in your enterprise that generate a large volume of email, but you may not want to include these mailboxes as part of your usual email traffic.

For example, you might have an infrastructure monitoring application that generates notifications by email. The traffic generated by this application could be excluded from your overall analysis of messaging traffic generated by users.

To exclude mailboxes, MessageStats performs a text comparison between the originator and all recipients and the text that you enter in the Mailbox Exclusions tab. MessageStats does not recognize aliases or other distinguished names (DNs) when excluding mailboxes.

The Mailbox Exclusions tab contains a list of the excluded mailboxes and allows you to add, edit, or delete mailboxes.

Mailbox exclusions do not apply to reports that include structural properties, such as Mailbox Sizes and Mailbox Quotas. These reports include data for all mailboxes, regardless of the mailbox exclusion status. If you audit a mailbox that appears in the excluded mailbox list, no audit information is available. The following reports do not contain data for excluded mailboxes:

To identify the mailboxes that you do not want to include in message traffic reports, add mailboxes to the exclusion list. The dialog box lists all mailboxes that exist in the MessageStats database.

You can select more than one mailbox from the list or select a contiguous group of mailboxes from the list.

You can select a continuous group of mailboxes in the list, such as health mailboxes, specific mailboxes, or a single mailbox to be excluded.

1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Message Exclusions tab and click Add.
5
Hold down the SHIFT key, and click the down arrow to scroll down the list until you reach the last mailbox in the group.
6
Click Apply and click OK.
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Message Exclusions tab and click Add.
5
Hold down the CTRL key and select the mailbox you want.
7
Click Apply and click OK.
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Message Exclusions tab and click Add.
4
Click Select Mailbox to select mailboxes from the browser list.
Click Enter Mailbox Detail and enter the specific mailbox information in each field.

Select Mailbox

Select this option and select one or more mailboxes that are listed in the browser list.

Enter Mailbox Details

Select this option if you know the display name, mailbox distinguished name, and mailbox email for the mailbox. You can enter the information instead of browsing through the list of mailboxes. You cannot select multiple mailboxes that you entered manually.

Enter the mailbox display name.

Enter the mailbox distinguished name (DN).

Enter the mailbox email.

5
Click Apply and click OK.
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Message Exclusions tab.
6
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Message Exclusions tab.
5
Click Yes to confirm.
6

Setting a Threshold for Delivery Time Audits

You can audit messages that take an unusually long time to be delivered to the recipients. Using the Delivery Time Audit tab, you can enable message time auditing and set a threshold for message delivery times.

When a message takes longer to deliver than the audit threshold, it is reported in the Message Delivery Audit report in MessageStats Reports under the Servers | Delivery Times nodes.

1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Delivery Time Audit tab.
4
Select the Enable auditing for message delivery times box.

Threshold value for time to deliver a message (in seconds)

Indicates the number of seconds you want to use as the threshold for message delivery times. If you do not set a number, MessageStats sets a default of thirty seconds.

The Delivery Time reports show the average delivery time and the number and percentage of messages that are under this threshold. The threshold is displayed on the appropriate threshold report graphs.

6

Changing the Exchange Connection Server

Using the Connection Server tab, you can change the Exchange server that MessageStats uses as the access point to enumerate an Exchange organization.

The Connection Server property tab is used to set the root default connection server for the entire organization. Initially, this is the Exchange server that you selected when you created the connection to the Exchange organization.

This tab only allows you to change the connection server for the current organization. To connect to additional organizations, see Connecting to an Exchange Organization .

To select a different Exchange server from which to gather information, use the Gathering Server property tab. However, the server specified as the Connection Server is always used as the connection server for the Exchange Organization Structure gathering task.

The Exchange Organization Structure task runs automatically overnight to update the organization structure information in the database. You can also manually run the Exchange Organization Structure task, either using the Regather Structure option in the shortcut menu when you right-click an organization, or by selecting the task template in the Task Wizard at the organization level.

The following prerequisites apply when connecting to an Exchange server:

1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Connection Server tab.

At least one public folder or mailbox server that is running Exchange 2010:

If there is a child domain, you must enter the full email address instead of the display name or alias. For example, enter the mailbox as FirstName.Lastname@domain.com.

At least one public folder or mailbox server that is running Exchange 2013:

If there is a child domain, you must enter the full email address instead of the display name or alias. For example, enter the mailbox as FirstName.Lastname@domain.com.

At least one mailbox server that is running Exchange 2016:

3
Click Validate.
d
Click Accept.

Selecting a Separate Gathering Server

You have the option of selecting an Exchange server that is different from the specified Exchange connection server to run gathering tasks that are initiated at an organization level.

For example, you might want to run organization-level tasks, such as the Exchange Mail Contacts gathering task, on a different Exchange server, for performance reasons.

You can use the Gathering Server tab to specify an Exchange server that is used in the default configuration when you create an organization-level task using the Create Task wizard.

The following prerequisites apply when selecting an Exchange server that is used for gathering information at the organization level:

1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the Gathering Server tab.
4
Select the I want to use the following Exchange server.

At least one public folder or mailbox server that is running Exchange 2010:

At least one public folder or mailbox server that is running Exchange 2013:

At least one public folder or mailbox server that is running Exchange 2016:

3
Click Validate.
4
Click Apply.
Documentos relacionados