Chat now with support
Chat with Support

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

MessageStats Server Minimum Requirements

The MessageStats Server consists of the following three components:

•
MMC client console
•
MessageStats Scheduler Service
•
Task processors

Minimum hardware requirements are given for the server and for each component, in the following table.

 
Table 4. MessageStats Server component hardware minimum requirements.
Type
Minimum
Hardware Requirements for any or all MessageStats Server components

Processor

Pentium 4, running at a minimum speed of 2.4 GHz

RAM

8 GB

Disk

90 MB of free disk space

SQL connectivity

For SQL database connectivity, you must install the new version of Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). You can find the download here: https://www.microsoft.com/en-us/download/details.aspx?id=56730.

Other

Sufficient space for the temporary MessageStats caches, application logs, and task documents. The size of the cache depends on the number of servers, the number of logs on each server, and the size of each log. The space should exist on a local drive rather than a network drive.

Monitor capable of supporting a resolution 1024 by 768

Pointing device must be installed on your server to access all MessageStats features.

The minimum software requirements are listed for each of the MessageStats server components. If you install more than one component on the same computer, you must meet the requirements for each component.

 
Table 5. Software requirements for MessageStats Server components.
Component
Minimum

Operating Systems

Windows Server 2012 or later

Full installation on Windows 10 is supported for evaluation purposes only.

NOTE: In a production environment, you can install only the MessageStats client console on Windows 10.
Task Processor Specific Requirements

MAPI

For Exchange 2010 or 2013 you can install the newest Microsoft MAPI & CDO software download (http://www.microsoft.com/en-us/download/details.aspx?id=39045) on the Task Execution Server.

•
For Exchange 2010, ensure that you are using MAPI & CDO version 6.5.8211.0 or later.
•
For Exchange 2013, ensure that you are using MAPI & CDO version 6.5.8320.0 (released 5/17/2013). This version of MAPI & CDO implements RPC over HTTPS (Outlook Anywhere) which requires that the proxy (CAS) server have an SSL certificate on it that is trusted by the Task Execution Server.

Configuring an SSL certificate on your Exchange 2013 CAS (proxy) server is part of the normal setup that is required for the Outlook 2013 client. For more information, see the Microsoft Exchange 2013 documentation for configuring mail flow and client access.

If you already have a version of the MAPI Download installed, you must remove it before installing a new version. The Microsoft MAPI installer does not upgrade, nor does it warn you if you try to install MAPI & CDO without removing the previous version.

.Net

Microsoft .Net Framework 4.7.2

Can be downloaded from https://dotnet.microsoft.com/download/dotnet-framework/net472

Microsoft PowerShell 2.0

For Exchange 2010, 2013, 2016, and 2019, you must also install Microsoft PowerShell 2.0.

You can download the Windows Management Framework (which includes PowerShell 2.0) from http://support.microsoft.com/kb/968929.

Report Client Specific Requirements

Microsoft Lync and Outlook

To see the presence status information in Exchange mailbox-specific reports, the person that is viewing the reports on the web site must have Lync Communicator 2010 or later and Outlook installed and running on their local computer.

For 64-bit computers, the 64-bit version of Microsoft Office 2010 or later must be installed. If a 32-bit version of Office, such as Office 2010 (x86) is installed, the presence icons will not appear since the 64-bit version of the required Name.dll will not be available.

NOTE: The Exchange organization must have Lync Server or later configured and running.

Rights and Permissions Required by MessageStats

The account that you use to install MessageStats should be the account that you use as the MessageStats service account. This account must have distinct rights and permissions to install MessageStats, to gather information, and to render reports. These requirements are described in the following sections:

Installation Rights
Operational Rights
MessageStats Reports Security Settings
Setting IIS Role Services for IIS
Trust Relationships
Miscellaneous Rights

Installation Rights

The account you use to install MessageStats must have the following rights and permissions:

•
Membership in the local Administrator group
Database Server Permissions

To install the MessageStats Database, the MessageStats service account must have database creation rights on the SQL Server. Specifically, the following SQL security roles must be assigned to the account used to install the database:

•
dbcreator
•
public
•
securityadmin

For information about the permissions that are required for different operational activities, see Operational Rights .

MessageStats roles and permissions created during installation

During installation, MessageStats automatically performs the following actions:

•
Adds the service account to the local administrator group.
•
Grants the following rights to the service account on the local MessageStats server:
•
Act as part of the operating system
•
Logon as a batch job
•
Replace a process level token

The MessageStats installer automatically creates the following roles and permissions on the server in which the specific component is installed:

 
Table 6. Permissions and roles created during installation.
Installed Component
Item
Name

MessageStats Database

Task Processor

MessageStats Scheduler service

MessageStats MMC console

Two local groups

MessageStats Admin

MessageStats Web

NOTE: For a server on which only the task processors are installed (a Task Execution Server), only the MessageStats Admin local group is created.

MessageStats Admin group rights

The MessageStats Admin local group is added to the following server Local Security Policies:

•
Access this computer from the network
•
Act as part of operating system
•
Allow log on locally
•
Impersonate a client after authentication
•
Log on as a batch job
•
Log on as a service
•
Replace a process level token

MessageStats Reports web site

Three local groups

Web Report Administrators

Web Report Authors

Web Report Users

MessageStats Database

Two database users (Server Logins)

These logins allow database read, write, and security admin rights on the MessageStats database.

MessageStats Admin

MessageStats Web

Two database roles on the SQL server that hosts the MessageStats database

MessageStats_Admin

MessageStats_Web

Operational Rights

After installation, the account that runs the MessageStats Scheduler Service requires db_owner rights on the MessageStats database.

To perform database maintenance activities, the account used to run the database maintenance tasks must have rights to re-index and defragment the MessageStats database (such as alter rights, and so on). To use the database management features in a distributed environment, one of the following accounts must have the sysadmin fixed server role on the SQL server that hosts the MessageStats database:

•
the MessageStats service account
- OR -
•
the account that is currently logged into the MessageStats console

The account (task credentials) used by MessageStats to gather from Microsoft Exchange servers must have the following permissions:

•
Membership in the MessageStats Admin local group on the SQL server that houses the MessageStats Database
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating