Tchater maintenant avec le support
Tchattez avec un ingénieur du support

MessageStats 7.8 - Deployment Guide

MessageStats Architecture Overview Planning for Deployment Deployment Recommendations and Solutions

Deployment Recommendations and Solutions

•
Deploying MessageStats in Small or Large Installations
•
Recommendations for Large Installations
•
Deploying a Distributed Installation Using Windows Authentication
•
Deploying MessageStats Across Forests
•
Manually Creating the MessageStats Database in a Distributed Installation

Deploying MessageStats in Small or Large Installations

Depending on the size of your Exchange deployment and whether it is situated in one geographic location or in several locations, you must determine whether to install MessageStats on a single server or on several servers.

Single Geographic Location

For a small-to-medium business that has its messaging system in a single location, the number of report consumers, either direct or indirect, is usually low. In this case, you can install all the MessageStats components on a single server. If the gatherings take longer than 24 hours, then you can install additional Task Execution Servers on other computers to reduce gathering times.

If your Exchange environment is in a single geographic location, you can install MessageStats on a single server or distribute MessageStats components on more than one server, depending on the number of mailboxes.

•
If you have 10,000 mailboxes in your organization, you can use single server deployment.
•
If you have more than 10,000 but less than 50,000 mailboxes, you should consider a distributed installation. You can place the MessageStats Server (which includes the scheduler service and the task processors) and the MessageStats database on different computers.
•
For 50,000+ mailboxes, you should have a MessageStats Server, MessageStats Database, and additional MessageStats task processors on separate computers.
Distributed Task Processors

This scenario applies to distributed locations where the locations are connected through internal networks with no firewalls between them. The largest location is considered the central location. You can install the MessageStats Scheduler Service, the MessageStats Database, at least one Task Execution Server, and MessageStats Reports on this computer.

For smaller locations, identify the locations that share similar connectivity. If some locations share a common pipe back to the central location, install an additional Task Execution Server to improve gathering performance. Locations must have a reasonable connection to the MessageStats database. If the database connection is poor, you can install multiple Task Execution Servers in that location.

Multiple Geographic Locations

You can distribute your task processors on different servers if your Exchange environment is distributed across more than one geographic location. A server on which task processors are installed is known as a task execution server.

It is recommended that you run the Tracking Log Gathering task on the task execution server that is closest to the MessageStats database server. Tracking logs should be compressed. Run all other gatherings on the task execution server closest to the Exchange environment.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation