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

Using the MessageStats Compression Tool

The MessageStats compression tool provides the following benefits:

Files Included in the Compression Tool

The compression tool consists of two executable files and a language file, if applicable:

QMSDeployment.exe

Used to install and configure the QMSCompress executable. This executable file has a wizard-type interface.

QMSCompress.exe

Compresses the log files on Exchange servers. This executable file does not have a user interface. To change the compression settings, run the QMSDeployment executable file.

QMSDeployment.deu

QMSDeployment.fra

QMSDeployment.jpn

QMSDeployment.kor

If you specified German, French, Japanese, or Korean as your operating language when you installed MessageStats, the corresponding language file is also included for the compression tool. The language file must also be copied to the server on which you deploy the two executable files.

The files are located in the MessageStats installation directory. For more information, see Installing and Configuring the Compression Tool .

You must copy these files to the Exchange servers on which you want to enable compression.

Installing and Configuring the Compression Tool

Before you install and configure the compression tool, you must copy the compression tool files to all Exchange servers on which you will be compressing the tracking log files. You run the QMSDeployment.exe file locally. You cannot remotely deploy the compression tool.

When you install and configure the compression tool, a compression task is created in the Windows Task Scheduler.

3
From the Exchange server, run the QMSDeployment.exe file.
4
Click Next.
7
Click Analyze Server.
9
Click the drop-down box and select Deployed to enable the compression tool.

Remove Orphans

Select this option to remove any compressed files that do not have an associated raw tracking log.

Catchup Enabled

Select this option to compress all the raw tracking logs instead of just the most recent logs.

Thread Priority

Set the desired thread priority.

Logging Level

Set to Normal.

Increased logging is generally used only when trouble shooting compression issues.

12
Click Next and review the summary of your compression options.
13
Click Start if the options are appropriate or click Back to change the configuration options.

What Happens When You Run QMSDeployment.exe?

When you install and configure compression using the Compression Deployment Wizard, the wizard performs the following actions.

Verifies the tracking log share name

Ensures that the tracking log share name that you selected exists on the server and can be accessed using the security account that you specified.

Creates a Compressed folder in the tracking log folder

Initially the folder contains the QMSCompress.exe file.

After you compress an Exchange tracking log, the Compressed folder contains:

Schedules the compression task to Run Now

Compresses the most recent tracking log on the Exchange server as soon as the deployment is enabled and configuration is complete.

Creates a cyclical schedule in the task scheduler

Compresses the existing log file every day. This schedule default is 12:05 UTC but you configure the time in the Compression Deployment Wizard.

If the tracking log file is unavailable when the compression is scheduled, the tool compresses the tracking log file at the next scheduled compression, along with any new tracking logs that may exist.

Documentos relacionados