Before installing MessageStats, ensure your system meets the following minimum hardware and software requirements. The system requirements are divided into two sections:
- Requirements for the core MessageStats components.
- Requirements for Microsoft Exchange.
MessageStats Core Requirements
Before installing MessageStats, ensure your system meets the following minimum hardware and software requirements for the core MessageStats components:
| MessageStats Minimum Hardware Requirements |
| Processor | Pentium 4, running at a minimum speed of 2.4 GHz |
| Memory | 3 GB |
| Hard Disk Space | 250 MB of free disk space for installing the application.
This space should exist on a local disk drive rather than a network drive. The space requirement varies depending on the size of the database.
Note: If you are migrating an existing database, the free disk space requirement is larger than 250 MB. The space requirement varies, depending on the size of the database. If you are upgrading an existing database, the free disk space must be larger than for a new database. Space requirements also depend on the amount of information you write to the database and the length of time you retain the records.
Note: For help in assessing the amount of space sufficient for your implementation, contact Quest Support to acquire a database size estimation tool. To tune your MessageStats database and maximize performance, contact Quest Software Professional Services. You can contact Professional Services through your Quest sales representative.
|
| Other | Sufficient space for the temporary tracking log cache, application logs, and task documents. The size of this cache depends on the number of servers, the number of tracking logs on each server, and the size of each tracking log. The space should exist on a local disk drive rather than a network drive.
Monitor supporting a resolution of 1024x768 pixels.
Pointing device. You must have a pointing device installed on your computer to access all MessageStats features.
|
| MessageStats Minimum Software Requirements |
| Operating System | One of the following: - Windows Server 2008 R2
- Windows Server 2008 (SP 2)
- Windows Server 2003 R2 (SP 2)
- Windows Server 2003 (SP 2)
Note: MessageStats supports full installation on Microsoft Vista SP1 or Windows 7 only for evaluation scenarios. Microsoft Vista and Windows 7 require the same configuration as for Windows Server 2008. You can install only the MessageStats client console on Windows Vista or Windows 7 in production environments.
Note: If you are hosting reports that contain Chinese, Japanese, or Korean characters, you must install the East Asian language pack if the computer that hosts MessageStats Reports is installed on Windows Server 2003. You must also install the language pack on any computer to be used to view these reports.
|
| MessageStats Database Server | One of the following: - SQL Server 2012
- SQL Server 2008 R2 (Service Pack 1)
- SQL Server 2008 (Service Pack 3)
- SQL Server 2005 (Service Pack 4)
MessageStats supports SQL Server Express 2005 or later in test or evaluation scenarios only.
Note: SQL Server Agent must be running to use the Database Management tasks: database reindexing, defragmenting, or database aging. SQL Express does not include the SQL Server Agent. Database Maintenance tasks are not available when running on SQL Express. |
| MMC Console | For SQL Server 2008, SQL Distributed Management Objects (SQL-DMO) must be installed on the server that hosts the MessageStats MMC console. The SQL-DMO component is part of the Microsoft SQL Server 2005 Backward Compatibility package. You can download the SQL Server 2005 Backward Compatibility package from the Microsoft SQL Server 2005 or the SQL Server 2008 Feature Packs: SQL Server 2005 Feature Pack (December 2008) and SQL Server 2008 Feature Pack (August 2008). -OR- SQL 2005 Client Tools For SQL Server 2005, SQL 2005 Client Tools are needed for the MessageStats Database Management feature to function in a distributed installation environment. |
| MessageStats Reports Server | IIS 6.0 or later.
For Windows Server 2008, IIS 7.0 is required. There are also certain IIS role services that must be enabled. See the section titled "IIS Role Services on Windows Server 2008" in the MessageStats Quick Start Guide for more information. |
| .NET | Microsoft .NET Framework 3.5. For information about resolving common ASP.NET configuration problems, see “Appendix A: Microsoft ASP.NET Configuration Issues” in the MessageStats Administrator Guide. Note: If you have Microsoft .NET Framework 4.0 installed, you must also have .NET 3.5 installed side-by-side. |
| Browser | Internet Explorer 7.0 or later. |
| Documentation | Acrobat Reader 7.0 or higher is required to access the Administrator Guide, Reports User Guide, and Quick Start Guide PDF documents. |
Exchange-Specific Requirements for MessageStats Components
The following requirements must be met to use MessageStats in a Microsoft Exchange environment. You must install the prerequisites on the server which hosts the specified MessageStats component:
| Microsoft Exchange Minimum Requirements |
Task Execution Server (task processors) | MAPI For Exchange 2003 and earlier, MAPI is available with Microsoft Exchange Systems Manager (ESM) 2000 Service Pack 3 or Exchange Systems Manager (ESM) 2003 Service Pack 2.
For Exchange 2007 or 2010, you can install the Microsoft MAPI & CDO software download: (http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en) as their MAPI subsystem provider. This software must be installed wherever ESM would have been installed.
For Exchange 2010, ensure that you are using MAPI & CDO version 6.5.8211.0 or later. If you already have a version of the MAPI Download installed, you must remove it before installing the 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. Microsoft PowerShell 2.0 For Exchange 2010, you must also install Microsoft PowerShell 2.0 on the servers that host the MessageStats task processors. You can download the Windows Management Framework (which includes PowerShell 2.0) from http://support.microsoft.com/kb/968929. |
| Reports Client | To see the presence status information in Exchange mailbox-specific reports, the person viewing the reports must have Office Communicator 2005 or later installed, configured, and running. Microsoft Office Outlook 2003 or later must be installed. The Exchange organization must have Microsoft Live Communication Server 2005 or later configured and running. |
| Exchange Server Versions | - Exchange 2000 Service Pack 3
- Exchange 2003 Service Pack 2
- Exchange 2007 Service Pack 3
- Exchange 2010 Service Pack 2
Must have tracking logs enabled and the tracking log folder shared. |
Exchange-Specific Rights and Permissions
For information about the rights and permissions that are required to install MessageStats, to access the MessageStats database, to gather information from the Microsoft Exchange messaging environment, and to run the MessageStats service, see the MessageStats Quick Start Guide.
Requirements for Exchange 2010
To connect to an organization that contains at least one Exchange 2010 mailbox server, you select an Exchange 2010 server that has the Client Access Server (CAS) role installed. In addition, there must be an Exchange 2010 mailbox to which the account used to run gathering tasks has full access. This mailbox is specified as the Logon Mailbox (for MAPI logon) and is used when gathering mailbox data. For example, you can add a mailbox for the MessageStats service account.
Note: Quest has provided a PowerShell script that allows you to set a user account with full access rights to a specific mailbox. You can find the script in the MessageStats installation directory (by default this is C:\Program Files\Quest Software\MessageStats) in a folder called Scripts.
Exchange Server Configuration
For information about any configuration that must be done on the Exchange server to allow MessageStats to gather information from it (such as sharing the tracking log folder), see the MessageStats Quick Start Guide.