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

MessageStats 7.8.1 - 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:

•
All MessageStats Server minimum requirements are met. For information about requirements, see MessageStats Server Minimum Requirements .
•
The MessageStats Database, MessageStats Reports, and MessageStats Scheduler Service are already installed on their respective computers.
To install the MMC Client Console
1
Log on to the computer using local administration privileges.
2
Double-click the setup.exe.
3
In the Install wizard welcome page, click Next.
4
Read the license agreement and select the I accept the terms in the license agreement check box and click Next.
You must select the check box to activate the Next button.
5
Click Next to accept the default installation folder.
6
Select Custom install type.
7
Click on the individual features to set the following:
•
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.
8
Click Next.
9
Enter the computer names on which you previously installed the MessageStats Reports.
Enter the computer name on which you previously installed the MessageStats Scheduler service.
Click Next.
10
Enter your domain username and password.
11
Click Install.
12
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:

•
The number of Task Execution Servers that are needed is relative to the number of Exchange servers from which you want to collect data.
•
The Task Execution Servers must have good connectivity to the MessageStats SQL database and to the Exchange servers.
•
Collections must complete within a 24-hour cycle so that MessageStats does not continually get backlogged in Exchange tracking log processing.
•
Too many Task Execution Servers trying to connect to the SQL database at the same time can cause deadlocks and time-outs on data storage.

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:

•
MessageStats Database
•
MessageStats Reports
•
MessageStats Scheduler Service
To install the task processor
1
Add the MessageStats service account to the local administrators group on the new server.
2
Log on to the computer using the MessageStats service account.
3
Double-click the setup.exe.
4
In the Install wizard welcome page, click Next.
5
Read the license agreement and select the I accept the terms in the license agreement check box and click Next.
You must select the check box to activate the Next button.
6
Click Next to accept the default installation folder.
7
Select Custom install type.
8
Click on the individual features to set the following:
•
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.
9
Click Next.
10
Enter the computer names on which you previously installed the MessageStats Reports.
Enter the computer name on which you previously installed the MessageStats Scheduler service.
Select the Share the Application Log folder option to create a share in which the MessageStats log files are copied.
You must create a share to be able to view the log files from a remote console.
11
Click Next.
12
Enter the MessageStats service account name and password.
13
Click Install.
14
Click Finish.
15
Open the MessageStats console, right-click Task Execution Servers and select Refresh.
At this point, you can optionally set a limit on the number of months that you retain task log files. For example, you might decide to only keep task logs for one month.
16
Expand the Task Execution Servers node, right-click the name of the new Task Execution server and select Properties.
17
Select the Task Logging Archive tab
18
Enable archiving and set the Number of Months to Keep to 1.
19
Click OK.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택