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

Selecting a Server for Mailbox MAPI Gathering

The Mailbox MAPI property tab allows you to specify how the mailbox information is to be gathered for a specific Exchange 2010 or Exchange 2013 server. This property page is not used by Exchange 2016.

Normally, the mailbox gathering tasks use the default gathering server that is defined for the organization. This information is displayed on the property tab. For more information about defining a gathering server for the organization, see Selecting a Separate Gathering Server .

In some situations, you may want to gather the Exchange 2010 or 2013 mailbox information using an server other than the specified Exchange gathering server that is defined for the organization.

Use this property page to specify a different Exchange server than the gathering server that was defined for the organization. This may be an Exchange server that is located geographically closer to this server.

1
Select the Mailbox MAPI tab.
2
Select the option titled I want to use the following server for mailbox gathering tasks.

For an Exchange 2010 mailbox server

Select the Exchange Client Access Server (CAS) that should be used for mailbox gatherings for this server.

Specify a mailbox in one of the following formats:

The mailbox is used for MAPI logon to collect mailbox information. The task credentials must have full access rights to this mailbox. Also, the mailbox must not be hidden from Exchange address lists.

For an Exchange 2013 mailbox server

Selecting a Server for Legacy Public Folder MAPI gathering

The Legacy Public Folder MAPI property tab allows you to specify how public folder information is to be gathered for a specific Exchange 2010 server. This property page is used only to collect from Exchange 2010 public folders.

Normally, the public folder gathering tasks use the default gathering server that is defined for the organization. This information is displayed on the property tab. For more information about defining a gathering server for the organization, see Selecting a Separate Gathering Server .

In some situations, you may want to gather Exchange 2010 public folder information using an Exchange server other than the specified Exchange gathering server that is defined for the organization. This may be a server that is closer to this server.

2
Select the Legacy Public Folder MAPI tab.
3
Select the option titled I want to use the following server for public folder gathering tasks.
6
Click Apply and click OK.

Viewing General Information for a Server

The General tab displays basic information about the selected server, including the following information:

You can use the General property tab to specify the LDAP port that is used for a server.

All other fields are populated with information that is collected by a gathering task and are read-only.

The LDAP Port field indicates the default LDAP port used by the server. If you have an incorrect LDAP port specified in the Server Properties dialog box, MessageStats cannot connect to the server.

MessageStats communicates with Active Directory using a standard protocol called LDAP (Lightweight Directory Access Protocol). The standard communications port number for LDAP is 389.

If you have changed the port for security reasons, you might need to change LDAP port number. When you connect to your initial Exchange server, you can specify an alternate LDAP port by adding the port number to the end of the server name, separated by a colon.

For example, EXCHN:390 indicates that the server EXCHN is using port 390. If you do not specify a port, MessageStats uses port 389. If you have specified an incorrect LDAP port, MessageStats cannot connect to the server and a log entry is created to indicate that it could not connect to the server.

Viewing the Task Membership for a Server

The Task Membership tab shows the Exchange server-level gathering tasks to which the server belongs. You can use this tab to determine if you are gathering enough information for this server.

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).

Documentos relacionados