지금 지원 담당자와 채팅
지원 담당자와 채팅

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 General Organization Properties

From the Exchange Organizations node in the treeview, you can set basic properties that are not specific to any one Exchange organization.

Specifically you can select the archive location for your tracking logs if you are using the MessageStats archiving feature.

For information about setting a custom location for archived tracking logs, see Selecting a Tracking Log Archive Location .

Selecting a Tracking Log Archive Location

If you are archiving the Exchange tracking logs, you can specify the location in which to archive the tracking logs using the Tracking Log Archive property tab.

1
Select the Exchange Organizations node in the treeview.
4
Click Apply.

You can select the servers for which the tracking logs are to be archived using the Tracking Logs tab in the properties for a specific Exchange organization. For more information, see Selecting Servers for Tracking Log Archiving .

Setting Properties for a Specific Exchange Organization

The parameters that you set for a specific organization are used as the default configuration for the organization-level tasks that you create for that organization.

SMTP namespaces—You can modify internal SMTP namespaces to ensure that, when the task processors are processing the tracking logs, traffic is correctly recorded as internal or external.
Internal subnets— Messages sent directly through SMTP to an Exchange server are usually counted as “external” in reports. You can identify the IP addresses used by your company so that internal messages submitted directly through SMTP are counted as “internal”.
Audits—Specify the mailboxes, email subjects, and Internet domains that you want to audit. The task processors collect the extra audit data when they process the Exchange tracking logs.
Mailbox exclusions—You can exclude certain mailboxes from mailbox statistics reporting (other than mailbox size).
Delivery time thresholds—Set delivery time thresholds to allow the MessageStats task processors to identify messages that exceed the threshold during the tracking log processing.
Exchange servers for gatherings and organization task membership—You can change the Exchange connection server for the organization or specify a gathering server for specific organization-level gathering tasks.
Distribution group membership—You can set whether distribution group membership information is gathered for the organization.
Tracking log archiving—You can select Exchange servers in the organization for which the tracking logs are to be archived.

By configuring properties for a specific Exchange organization, you apply them to all the servers within the organization.

1
Expand the Exchange Organizations node in the treeview and select a specific Exchange organization.

Identifying Internal SMTP Namespaces

MessageStats reports on your internal and external email traffic. Within the MessageStats task processors, a component enumerates the SMTP domains in the Recipient Policies and attempts to determine which namespaces are internal to an organization. The component also checks the domains in the primary and secondary SMTP addresses of mailboxes.

You can use the SMTP Namespaces tab to ensure that all internal SMTP namespaces are correctly identified and to ensure that MessageStats can accurately report internal and external email traffic.

For more information about how MessageStats report internal and external email traffic, see Appendix A in the MessageStats Reports User Guide.

Though MessageStats automatically populates the SMTP namespace list, if any internal SMTP namespaces are missing, you can add them. An SMTP namespace consists of two or more parts (technically labels), separated by dots. The top-level namespace is the right-most label and any children of the namespace are the labels to the left. MessageStats includes parent namespaces and child namespaces according to the level of namespace that you enter.

For example, if you entered Blackbox.com, MessageStats captures information for both Westland.Blackbox.com and Blackbox.com. However, if you explicitly enter Westland.Blackbox.com, MessageStats does not capture Blackbox.com in the Internal Namespace Distribution report.

1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the SMTP namespaces tab.
4
Click Add.
6
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the SMTP namespaces tab.
6
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
3
Select the SMTP namespaces tab.

To make changes to multiple namespaces, you can select a group of namespaces in the list, right-click and select the option you want.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택