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

MessageStats 7.8 - Quick Start Guide

About This Guide Requirements for Installing the MessageStats Components Prerequisites for Gathering from Microsoft Exchange Planning a MessageStats Installation Appendix A: IIS Configuration Issues

Installing MMC Client Consoles

The MMC Client Console is a thin application that can be installed on a MessageStats administrator’s laptop computer or workstation. The administrator can create tasks and view logs, but the task scheduling and gathering can be performed at another location with more robust resources. Several consoles can be deployed in your network.

Before you install an MMC Client Console, ensure that the following requirements are met:

2
Double-click the autorun.exe file and select Install.
3
Click the Install button under Quest MessageStats.
5
Read the license agreement and select the I accept the terms in the license agreement check box and click Next.
6
Click Next to accept the default installation folder.
7
Select Custom install type.
Set MessageStats Server to Will be installed on local hard drive.
Set MMC Client Console to Will be installed on local hard drive.
Set Scheduler Service to Entire feature will be unavailable.
Set Task Processors to Entire feature will be unavailable.
Set Database to Entire feature will be unavailable.
Set MessageStats Reports to Entire feature will be unavailable.
9
Click Next.
Click Next.
12
Click Install.
13
Click Finish.

Deploying Additional Task Execution Servers (Task Processors)

While you may install a single Task Execution Server on the same computer as other MessageStats components, some situations require that you deploy additional Task Execution Servers on separate computers.

Gathering tasks such as Public Folder Gathering, Distribution Group Membership Gathering, and Content and Attachment Gatherings require more system resources. For example, if you run the Public Folder Gathering on the same MessageStats Server that gathers the core data every night, resources could be consumed to the point that the Default Gathering task is delayed. Installing an additional task processor to run the Public Folder Gathering removes this risk.

When you are planning to install additional Task Execution Servers, consider the following:

To determine your specific need, see the Planning section of the MessageStats Deployment Guide.

Compression of Tracking Log Files

To optimize performance in collecting Tracking Logs, you should run the Tracking Logs gathering on a Task Execution Server that is close to the MessageStats Database server, and compress your Exchange Tracking Log and copy it over the network using the QMSCompress.exe utility, which is shipped with MessageStats. For more information, see the section “Compressing Tracking Log Files” in the MessageStats Administrator Guide.

Installing the Task Execution Server

The servers on which you intend to install the MessageStats task processors (Task Execution Servers) must meet the prerequisites specified in the section titled Task Processor Specific Requirements .

Before you install the task processor components, ensure that the following MessageStats components are already installed on their respective servers:

3
Double-click the autorun.exe file and select Install.
4
Click the Install button under Quest MessageStats.
6
Read the license agreement and select the I accept the terms in the license agreement check box and click Next.
7
Click Next to accept the default installation folder.
8
Select Custom install type.
Set MessageStats Server to Will be installed on local hard drive.
Set MMC Client Console to Entire feature will be unavailable.
Set Scheduler Service to Entire feature will be unavailable.
Set Task Processors to Will be installed on local hard drive.
Set Database to Entire feature will be unavailable.
Set MessageStats Reports to Entire feature will be unavailable.
10
Click Next.
Select the Share the Application Log folder option to create a share in which the MessageStats log files are copied.
12
Click Next.
14
Click Install.
15
Click Finish.
16
Open the MessageStats console, right-click Task Execution Servers and select Refresh.
18
Select the Task Logging Archive tab
20
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択