サポートと今すぐチャット
サポートとのチャット

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

Selecting a Server for Legacy Public Folder Gathering

If you are collecting public folder information from Exchange 2010 servers, you can select an Exchange 2010 server to be used to collect legacy public folder information using MAPI. You must also specify credentials that have access rights to an Exchange 2010 logon mailbox.

To select a specific server for legacy public folder gatherings
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
2
Right-click and select Properties.
3
Select the Legacy Public Folder Gathering Server tab.
4
Select the option titled I want to use the following Exchange server.
5
Select the Exchange 2010 client access server (CAS) to be used for legacy public folder gatherings for this organization.
6
Specify an Exchange 2010 mailbox in one of the following formats:
•
Display Name
•
Alias
•
SMTP Address
The mailbox is used for MAPI logon to collect public folder information. The task credentials must have full access rights to this mailbox. Also, the mailbox must not be hidden from Exchange address lists.
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.
 
* 
NOTE: The mailbox is not validated on this property tab. Ensure that it is a valid mailbox or the public folder tasks will fail
 

Viewing Task Membership for an Organization

The Task Membership tab shows the gathering tasks in which the organization is included. You can review this list to determine whether you are collecting all the information that you require to produce meaningful reports for that organization.

The Task Membership tab provides basic information about the task, such as the credentials that are used to run the task, the regular schedule for the task, and the next scheduled run of the task (in both local and UTC time).

Gathering Distribution Group Membership Information

Though the Default Gathering task includes distribution group gathering, you can determine whether to gather membership information for distribution groups. By default, the option to gather membership information is selected.

Gathering, processing, and storing distribution group membership can use significant server resources and storage. For large organizations, you may want to move the Distribution Group task to a different task execution server.

To change the distribution group membership option
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
2
Right-click and select Properties.
3
Select the Distribution Group Membership tab.
4
Select or clear the Gather membership information when gathering distribution groups. check box.

Selecting Servers for Tracking Log Archiving

Selecting Servers for Tracking Log Archiving

Tracking log archiving is a feature that compresses and archives Exchange tracking log files. Using the Tracking Logs tab, you can select the Exchange servers for which you want to enable archiving.

To select a server for archiving
1
Expand the Exchange Organizations node in the treeview and select an Exchange organization.
2
Right-click and select Properties.
3
Select the Tracking Logs tab.
4
Under the lower pane, click Configure.
5
Select the servers for which you want to enable archiving:
•
To select one server, click a server in the list and click .
•
To select all the servers, click .
6
Click OK.
Where are the Tracking Logs Archived?

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 .

What is the Workflow for Archiving?

In normal operation without archiving, the steps to handle the tracking logs for a server are performed in the following order:

1
Copy the tracking log to local cache.
2
Process the tracking log.
3
Clear the local cache.

If archiving is turned on, the steps to handle the tracking logs for a server are performed in the following order:

1
Copy the tracking log to the local cache.
2
Process the tracking log.
3
Compress the tracking log.
4
Move the tracking log to the archive location and clear the local cache.

If the tracking logs are already compressed, either through using the MessageStats Compression utility or through a third-party compression model, the step to compress the tracking log is not performed. MessageStats only compresses tracking logs if they are not compressed already.

The local cache that is used when processing the tracking logs is set in the properties tabs for a task. For more information, see Configuring the Tracking Log Cache .

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択