Quest® MessageStats
Version 6.1.1 (build 877)

Release Notes

September 2007

2007 © Quest Software, Inc.
ALL RIGHTS RESERVED

Contents

Welcome to Quest MessageStats
What's New
Issues and Limitations
System Requirements
List of Updates to Existing Functionality
Global Operations
For More Information

Welcome to Quest MessageStats

Quest MessageStats is an MMC-based data collection and reporting application that facilitates the gathering and analysis of usage statistics for large Microsoft Exchange enterprises. MessageStats collects and processes Microsoft Exchange tracking logs and mailbox statistics from a list of Exchange servers, sites, routing groups, and user-definable regions. Through additional report packs, MessageStats also collects and processes data gathered from messaging components including BlackBerry® Enterprise Servers, SendMail and PostFix servers, Quest Archive Manager servers, and OWA (Outlook Web Access) servers.

MessageStats stores the contents in a database for web-based access by report consumers. MessageStats Reports provide summary and detailed information concerning critical metrics for resource usage, capacity, storage use, quotas, audited mailboxes or domains, delivery times, distribution lists, public folders, and migration preparedness.

Back to Top

What's New

This section describes the new features that can be found in Quest MessageStats release 6.1.1.

New Internet Domain Reports

Two new MessageStats reports are added in the Internet folder: Top Internet Domain Users by Messages and Top Internet Domain Users by Volume. The first report shows the mailboxes that send the most messages to and receive the most messages from Internet domains. The second report shows the mailboxes that send the largest volume of messages to and receive the largest volume from Internet domains. You can select the period of time and select users in a specific organization, Exchange server, or organizational unit (OU).

Additional Detail Available for Server Activity and Mailbox Activity Reports

To provide more detail about where delivered messages originate, new insertable fields are added to the reports in the Servers | Server Activity node and in the Mailboxes | Mailbox Activity node. In the Server Activity reports, you can now insert fields that classify whether messages come from an originator in the local store or a non-local store; from the local server or from a different server; and from within the organization or from an outside organization. In the Mailbox Activity reports, you can now insert fields that show the number of messages delivered whose originator is on the same store or a different store (on the same server), and on the same server or a different server.

New data sources are added to the MessageStats database to support the additional reporting. For existing customers, these fields contain data only for new mailbox gatherings that occurred after MessageStats 6.1.1 is installed. To include historical data, you can use the MessageStats database maintenance function to regather mailbox data from older tracking logs.

New Task Execution Server Node

Quest MessageStats 6.1.1 includes changes to the MessageStats console including a new Task Execution Server node in the treeview. A task execution server is a server on which you have installed the MessageStats task processors. Through the Task Execution Servers node, you can now set properties for a specific task execution server. You can change the default task execution server and set the number of task processors that can run concurrently.

Archiving Options Available for Task Log Files

Though the Task Execution Server property pages, you can identify a path location to which the task log files are written, and specify parameters for task log files and for log file archival.

Archiving Options Available for Service Log Files

Also new properties pages are added for the MessageStats (scheduler service) server that allow you to manage the service log files. You can change the location to which the log files are written, and you can set and manage archiving for the log files.

New Option to Select "Connect-To" Exchange Server

At the Exchange organization level, new properties are added that allow you to change the "connect-to" Exchange server that MessageStats uses as the access point to enumerate an Exchange organization.

New Option to Select Exchange Server for Organization-Level Tasks

For organization-level gathering tasks, you now have the option of selecting an Exchange server from which to collect information for organization-level gathering tasks. For example, you might want to run organization-level tasks on an Exchange server other than the defined Exchange connection server.

New Option to Rename an Organization Within MessageStats

If you right-click an Exchange organization in the MessageStats treeview, you now have the option to rename the organization. This only affects the organization as it is displayed in the MessageStats console and in MessageStats reports.

Mount Point Support for MessageStats Storage Reports

MessageStats now supports gathering storage metrics from mounted volumes that host Exchange databases, and reporting on those mounted volumes in the Storage reports.

Resolved Issues in MessageStats 6.1.1

MessageStats 6.1.1 also includes a number of important fixes. For more information about the fixes, see the List of Updates to Existing Functionality section.

Back to Top

Issues and Limitations

 

The following issues and limitations are known to exist in MessageStats 6.1.1:

Installation Issues:

  • Customers that are using Exchange 2007, but who do not have Exchange System Manager (ESM) for Exchange 2000 or Exchange 2003, should use 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.
  • MessageStats Reports can be installed on 64-bit operating systems, but IIS must be reconfigured for MessageStats Reports to operate correctly. On 64-bit operating systems, you must reconfigure IIS to run in 32-bit mode. For instructions on how to do configure IIS to run either the 32-bit version of ASP.NET 1.1 or ASP.NET 2.0, see the Microsoft Knowledgebase Article 894435 (http://support.microsoft.com/?id=894435). This procedure can cause compatibility issues with other web applications on the same IIS Web Server so it is recommended that MessageStats Reports be run only on servers without other web applications.
  • During installation, if the installation and service accounts are different, the MessageStats installer requests a reboot. This reboot is required to ensure that the Service Account has the appropriate rights to run the service. Note: On x64 implementations, a reboot is requested and the MessageStats installer does not resume the installation. In this case, you must rerun MessageStats_Setup to continue the installation. (CR0179216)
  • SQL Server Agent must be running to use the Database Management tasks: database reindexing, defragmenting, or database aging. Note: SQL Express (the personal edition of SQL 2005) does not include the SQL Server Agent. Database Maintenance tasks are not available when running on SQL Express; use either MSDE or full SQL Server.
  • The Distribution List Membership recurrence setting in previous versions of MessageStats is not migrated to this version. As a result, you must explicitly set the Distribution List Membership check box on the applicable organization property page.
  • There is a known issue in which the MessageStats installer does not verify the server name that is entered for the scheduler service.  As a result, an incorrect server name causes an error to occur later in the installation process.  To correct this problem, uninstall MessageStats and re-install with the correct name for the scheduler service.
  • When upgrading from Quest MessageStats 5.x to the current version of MessageStats, you must re-enter your SMTP gateway and From address in order for Report Subscriptions to function properly.
  • If you install MessageStats on Windows Server 2003, ASP (Active Server Pages) support is turned off by default. You must enable ASP support in order for MessageStats to install properly.
    Note:     You must have IIS installed and ASP support enabled before installing the .NET Framework version 1.1 or version 2.0.
  • MessageStats does not support case sensitivity on SQL Server. Some non-Latin database collations can cause SQL Server to observe case sensitivity.
  • Quest Software does not support installation of MessageStats for scenarios where the installation files have been encrypted.
  • Quest Software does not support the installation of MessageStats on domain controllers or Exchange servers.

Gathering Issues:

  • If you run an information store gathering, a mailbox gathering, or a public folder gathering against an Exchange organization, an administrative group, or a routing group that contains one or more Exchange 2007 servers that do not have the mailbox role installed, the gathering for those Exchange 2007 servers will fail. The gathering fails because there is no information store from which to gather data from on those Exchange 2007 servers. (CR0224526)
  • Inherited mailbox permissions are retrieved only if ESM is used as the MAPI subsystem provider. If the Microsoft MAPI+CDO download or Outlook 2007 is used, only non-inherited mailbox permissions can be retrieved.
  • There is a known issue with the Connectors gathering task when run it is against organizations that contain Exchange 2007 servers. If these organizations contain connectors of the type ‘msExchRoutingSMTPConnector’ that do not have a legacyExchangeDN attribute set, a warning is generated. You can safely ignore this warning. (CR0201951)
  • MessageStats cannot connect through MAPI to an Exchange server that does not have both a public and a private information store. If a task generates the error MAPI_E_FAILONEPROVIDER (0x8004011D), ensure that the server to which the task is connecting has both a public and a private information store. (CR0215952)
  • MessageStats cannot gather mailbox security for Exchange 2007 System Mailboxes. For each Exchange 2007 System Mailbox a warning will be logged to the log file for the Exchange Mailboxes gathering. (CR0201551)
  • There is a known issue with the MOM gathering if the gathering is run twice for the same day. If the MOM gathering fails, do not re-run the gathering. For information, go to the Quest web site and see the SupportLink solution 18734. (CR0178106)
  • MAPI-based gatherings (mailbox, public folder, and content and attachment gatherings) can unexpectedly fail if run on a machine that has both Outlook and Exchange System Manager (ESM) installed. Running Outlook and Exchange System Manager on the same machine is not supported by Quest Software due to conflicts in the underlying MAPI components. Please refer to the following Microsoft Knowledgebase article 266418: http://support.microsoft.com/default.aspx?scid=kb;en-us;q266418.
  • You may receive an error using the MessageStats Database Management tools from the Console when the database is on a remote server and you are using SQL 2005. To resolve the issue, you must install SQL Server Management Studio or SQL Server Client Tools (that ship with SQL 2005) on the MessageStats Console.
  • For all Public Folder gatherings to be successful from Exchange 2003 servers, you must be running ESM 2003 SP 2 on the Scheduler Server.
  • MessageStats requires all public folders to have the Folder Visible permission. MessageStats may generate warnings during public folder gatherings while attempting to open public folders and child folders of public folders without this permission. For more information, see the Microsoft knowledge base article 203646.
  • MessageStats does not support directory objects containing both a forward slash ( / ) and an equals sign ( = ) in their common name, regardless of their position or order in the name. ADSI cannot bind to objects containing both these characters in their common name, which prevents MessageStats from gathering all of the required information from the object.
  • There is a known issue with the Mailbox gathering for Exchange servers with multiple Mailbox Stores. If not all the Mailbox Stores are available on an Exchange server, the gathering task is completed for the available stores and the status for the task is Successful. However, the information for the mailboxes in the unavailable stores is not added to the database.
  • When connecting to a multi-domain organization that contains NT domains with Exchange 5.5 servers, an Exchange 2000/2003 server should be used as the Connect To server for MessageStats to properly gather data.

Reporting Issues:

  • MessageStats Reports subscriptions that contain reports with the "Local Time" enabled will use the daylight savings time settings that were in effect at the time the subscription was created or saved. When the daylight savings time change goes into effect in the US in 2007, the data in these reports can be off by one hour during the three week period affected by the change. To correct the problem, load the subscription, view the filter settings panel for each affected report, and resave the subscription. Before you perform this operation, you must apply the Windows time zone update patch (KB933360) on the machine on which Internet Explorer is running. Interactive reports and other features of MessageStats Reports are not affected by this problem.
  • MessageStats Reports cannot run on IIS servers on which the Microsoft Media Server has been installed in the root web directory. An error message appears stating, "Microsoft .Net Framework version 1.1 or version 2.0 must be installed on the IIS server that hosts this application." This error occurs because the Microsoft Media Server applies configuration options that affect all applications running on the server.

    The recommended solution is to create a second virtual IIS server on the machine that is to host MessageStats Reports, and install MessageStats Reports on the virtual server that is not hosting Windows Media Server.
  • If you are producing reports containing Chinese, Japanese, or Korean characters, you must install the East Asian language pack on the computer hosting MessageStats Reports. You must also install the language pack on any computer to be used to view these reports.
  • If you attempt to run MessageStats Reports on an IIS server on which SharePoint has been installed, an error message appears, stating, "Microsoft .Net Framework version 1.1 or version 2.0 must be installed on the IIS server that hosts this application." This error occurs because the Microsoft SharePoint installer implements tighter security on the IIS server which prevents MessageStats Reports from operating correctly.

    The recommended solution is to create a second virtual IIS server on the machine that hosts MessageStats Reports, and install MessageStats Reports on a virtual server other than the server that is hosting SharePoint. MessageStats Reports can also be installed on the same virtual server by following the instructions given in Microsoft Knowledge Base Article 828810: How to enable an ASP.Net application to run on a SharePoint virtual server.
  • When you try to access the Subscription dialog box on Windows 2000 servers where SP 4 and .NET Framework has been installed, you receive an Access Denied error. This error occurs because the account is not granted the rights to impersonate users for ASP.NET 1.1 or 2.0. This is a known issue with Microsoft. Please refer to the following knowledge base article:
    Knowledge Base Article 824308: http://support.microsoft.com/default.aspx?scid=kb;en-us;824308
  • If you are accessing a long-running report on a Windows 2003 Server, you may be prompted to log in due to a time-out. After you enter the user credentials, the Internet Explorer 401.2 error page displays. This problem occurs on servers with a heavy server load. The workaround is to set the IIS ConnectionTimeout parameter to a longer time such as 15 minutes. For more information about this parameter, see the Microsoft article on ConnectionTimeout.
  • By default, times are not displayed in Excel. When exporting reports that contain date/time fields to Microsoft Excel, load the exported file into Excel, select the column containing date/time information, and apply an appropriate Excel format string using the Format | Cells menu command.
  • MessageStats may differ by 1 KB on values reported in either Microsoft Exchange Administrator or Microsoft Exchange System Manager due to the nature of rounding implemented by Microsoft.
  • If two identical mailbox display names appear on a report that contains a graph, the graph groups the mailboxes together.

Back to Top

System Requirements

Quest MessageStats is an enterprise scale product and therefore requires appropriate sizing and planning activities prior to deployment. Do not upgrade your existing production MessageStats without first understanding the impacts and planning appropriately. For help in assessing the amount of space sufficient for your implementation, please contact Quest Software Technical Support for assistance or to acquire a database size estimation tool. In order to tune your MessageStats Database and maximize performance, please contact Quest Software Professional Services for further assistance. You can contact Professional Services through your Quest sales representative.

You should verify that your system meets the following minimum requirements before attempting to install and run MessageStats:

Hardware

Type Minimum Recommended
Processor

Note: If you install the MessageStats Database and the MessageStats Reports components on the same server, it is recommended that the server speed is a minimum of 2.4 GigaHertz.

Pentium 4, running at a minimum speed of 1 GigaHertz Pentium 4 running at a minimum speed of 2.4 GigaHertz.
RAM 1 GB 2 GB or more
Disk 250 MB of free disk space for 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 intend to write to the database and the length of time you intend to retain the records.

Note: For help in assessing the amount of space sufficient for your implementation, please contact Quest Software Technical Support to acquire a database size estimation tool. In order to tune your MessageStats database and maximize performance, please 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 PC to access all MessageStats features.
Software
Type Minimum
Operating System Microsoft Windows 2000 (Server or Advanced Server) SP4, Windows Server 2003 SP 1, or Windows Server 2003 R2. If you plan to install MessageStats Report Packs such as the Sendmail and Postfix Report Pack, Windows Server 2003 is the minimum requirement.

Note: MessageStats only supports installation on Microsoft Windows XP Professional SP 2 in evaluation scenarios. If you intend to use Windows XP SP 2, you must open port 80 so that Quest MessageStats can provide access to subscription links.

Note: If you are producing reports that contain Chinese, Japanese, or Korean characters, you must install the East Asian language pack on the computer that hosts MessageStats Reports. You must also install the language pack on any computer to be used to view these reports.
MAPI.DLL Exchange Systems Manager (ESM) 2000 SP 3 or ESM 2003 SP 2 is required.

Customers that are using Exchange 2007, but who do not have ESM for Exchange 2000 or Exchange 2003, should use 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.

Note: For non-Exchange environments, you must have Microsoft Outlook installed. For Exchange environments, it is recommended that you have ESM installed. Microsoft does not support ESM and Outlook installed on the same computer. If you have Outlook installed, it is recommended that you uninstall Outlook before you install ESM. If you are running MessageStats 5.x, you may need to stop of the MessageStats Scheduler Service before you uninstall Outlook and install ESM. For more information, contact Quest Support.
MessageStats Reports Server IIS 5.0 or IIS 6.0

When you install Windows 2000 Server, IIS 5.0 is automatically installed. If you use Windows 2000 Professional, or Windows XP Professional, you must manually add IIS 5.0 using the Add/Remove Programs facility.
Database Server Microsoft SQL Server 2000, SP4 or SQL Server 2005.

Note: MessageStats supports MSDE 2000 in test or evaluation scenarios.

Browser Internet Explorer 6.0 or Internet Explorer 7.0

Note: For the online help and F1 Help to function, you must have at least Internet Explorer 6.0 SP 1.
Other Microsoft .NET Framework version 1.1 or version 2.0

Note: For more information about resolving common ASP.NET configuration problems, see Appendix A: Microsoft .NET Configuration Issues in the MessageStats Quick Start Guide.

MDAC (Microsoft Data Access Components) 2.7. It is recommended that you use MDAC 2.7 SP 2 Refresh. For a distributed install, MDAC must be installed on the IIS Server and console; however, it is not required for the database components.

LDAP (Lightweight Data Access Protocol)

At least one server running Microsoft Exchange 5.5, Exchange 2000/2003, or Exchange 2007 with tracking logs enabled.

Note: For more information about installation and operational rights, please refer to the Quest MessageStats Quick Start Guide.

Back to Top

 

Updates to Existing Functionality

For the latest information about the issues addressed and enhancements implemented in this release see the following list:

CR0211790

Gathering by region does not retrieve data from old tracking logs.

CR0214529

Completed task that is missing finish time causes duration to continue to update.

CR0214120

If a task fails and goes into retry mode, the task duration shows a negative value.

CR0214068

Tasks reach 100% before they are actually complete.

CR0214118

Tasks created from a routing group do not expand properly in all cases.

CR0204912

Mailbox account gathering fails if there are duplicate domain names in different organizations.

CR0216660

MessageStats Server Uptime gathering does not support localized counter names.

CR0206218

MessageStats Reports: Windows 2003 error messages do not give clear directions on how to correct Web Service Extension issues.

CR0224079

Source expansion hangs during the organization enumeration if the only source for the task is an empty region.

CR0223779

Increase performance of the mailbox gathering by using the GC directly to look up security information.

CR0215174

F1 help is broken for Server Properties - disabled mailboxes.

CR0215173

Server Thresholds allow negative integers to be entered.

CR0215172

There should be the ability to add a routing group to a region.

CR0215170

When opening the MessageStats node in an unlicenced state, there should be a Contact Support menu item in the list.

CR0215169

MessageStats Console: F1 Help is missing on Connect to: Scheduler Service.

CR0223546

Tasks that are older than 7 days do not automatically move to the Older Than 7 Days node unless you refresh the display.

CR0223411

Inconsistent sorting in the Task Status View for the Sources Column.

CR0223194

MessageStats Data Aging configuration: After Deploy is selected, updated properties are not shown until user clicks Refresh.

CR0221880

Organization Public Folder Tree Analysis task performance improvement.

CR0221530

Site traffic processor does not store the correct delivery time threshold values.

CR0215967

Virtual Servers is a server-level task and should be creatable from a routing group, yet it is missing from the task wizard.

CR0219839

If you change the database location and create task, the task occurrence in the treeview does not refresh unless you force it.

CR0224242

Installer: Database creation shows garbage characters.

CR0224931

Database migration on SQL 2005 and above fails to kill all connections.

CR0224780

Installer does not update credentials in QMSSystemConfig.dat file when upgrading with a different user account.

CR0224713

MessageStats "run once" tasks that are scheduled in the past run immediately.

CR0224643

QMSDeployment asks for language but does not provide it.

CR0224513

In Autorun, the SupportLink web addresses do not go to localized pages.

CR0207781

Exchange Tracking Log processing performance improvements.

CR0224521

Benign warning is generated during the Servers gathering for Exchange 2007 servers that do not have the mailbox role installed.

CR0224444

Data Aging configuration adds Sunday on its own.

CR0218960

MessageStats Server Activity reports are showing negative numbers in some cases

CR0185548

If you use Delete Object Data to delete object data for an organization's connect-to server, the connection to the organization becomes invalid and existing tasks fail unexpectedly.

CR0217861

MessageStats subscription issue with Excel attachments due to incomplete gathering.

CR0216394

Failed Connect-To operations can go into retry mode and appear to be hung.

CR0216291

Content and Attachment gatherings generates warnings for messages that don't have a PR_MESSAGE_SUBMISSION_ID or PR_INTERNET_MESSAGE_ID property.

CR0216171

Issue when information regarding some mailboxes disappeared in some MessageStats reports.

CR0205625

Scheduler Service: No service logs created after changing the application log directory.

CR0205322

Gatherings can be rerun after an upgrade.

CR0215657

Content and Attachment gatherings do not support public folders and mailbox folders with size > 2 GB.

CR0215534

Current Content and Attachment gathering logic generates benign errors that are misleading and cause unnecessary concern.

CR0214897

Memory leak found in MessageStats logging.

CR0214370

Console Financials: Do not allow the input of decimals such as $0.02 per MB of storage.

CR0212977

Having the Exchange Store database files, edb and stm, on separate volumes causes incorrect mailbox count in the store summary.

CR0211160

MessageStatsConsole: Database Management memory leaks.

CR0210786

Using the Clear Database feature does not clear the lookup tables.

CR0210785

Departmental Mailbox Sizes report is empty in certain scenario.

CR0210656

Console: Task Log viewer improvements.

CR0209599

Console: Report pack nodes are not sorted properly when the new localizable display name format replaced the old format for the node definition in the MessageStats schema.

CR0224642

QMSCompress utility not working with Exchange 2007 logs in all cases.

CR0224095

Console: Cannot drag and drop regions onto 'source' node within tasks.

CR0222101

Scheduler Service: Service hangs if shut down while executing tasks and the SQL database is stopped.

CR0218844

Regathering of Exchange 2003 tracking logs results in duplication of some data.

CR0218547

Task Sources gathering fails for second organization with the same name.

CR0216513

Need to include the effective date range in reports.

CR0215832

MessageStats Service: Possible deadlock in MessageStats logging.

CR0221198

Console: Cannot view the log file for a failed explicit credentials connection.

CR0221081

Log file viewer is not opening for failed validation of connection server.

CR0220294

Task logging cannot be turned off.

CR0220279

Exchange Mail Enable Gathering does not properly respond to the cancel action.

CR0220274

Database views that are modified in code must have open permissions.

CR0218991

Organization gathering server list can contain deleted servers.

CR0218807

Duplicate insertable fields appearing in the Server Activity custom data sources.

CR0219279

MessageStats Console: Add to Task - Should not be able to add an Organization source to a server-level task (Content and Attachment).

CR0215143

Error in handling of the database connection in Database Management node (Data Aging).

CR0214344

Have the installer prompt to create a task execution server share.

CR0207372

Server Uptime report is showing incorrect down times for server.

CR0195542

Indicate on the Connect to Exchange Organization dialog that Messagestats only supports connection with a NetBios name.

CR0173242

Log Viewer window does not remember previous settings.

CR0189852

Connecting to multiple organizations with the same directory name does not work in MessageStats 6.0.1

CR0178978

MessageStats Console: Mailbox auditing list is not always sorted in correct order.

CR0183809

Log Viewer: Log events IDs are not resolved into log messages in an efficient manner.

CR0224623

When using the MAPI+CDO download, the mailbox security gathering fails completely.

CR0218857

MessageStats Console: Error can occur when adding mailboxes for auditing in some cases.

CR0208884

MessageStats Console: Task Node display for Last 7 Seven Days actually displays last 8 days.

CR0207088

Public Folder Content and Attachment Gathering: Empty display name property causes non-fatal errors to be logged.

CR0200094

Virtual server gathering can only be created from Organization node. Need to create at Exchange server node.

CR0211280

Review the implementation of how the realized state of mailboxes is determined.

CR0153385

Organization structure at time of connection does not allow the user to specify a specific task processor to run a task.

CR0225716

Installation: DCOM identity configuration is incorrect with unicode characters.

CR0209619

Statistics data aging is not functional; it is missing the date calculation.

CR0224241

MessageStats Console: Upgrade from 5.7 to 6.1.1 upgrade migrates task schedules from interactive to "once only" (and then runs them).

CR0224011

Apply Missing-graph-points-are-zero changes to web reports graph control.

CR0225454

Multiple tasks executing at the same time can cause Exchange servers to be marked as deleted.

CR0224779

Installer does not store passwords correctly in QMSSystemConfig.dat file.

Back to Top

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Japan.

The release is localized to the following languages: Japanese, French, German, Korean.

Back to Top

For More Information

Other Document Sources

The MessageStats documentation suite for MessageStats 6.1.1 includes the following:

MessageStats Online Community

Get the latest product information, find helpful resources, and join a discussion with the Quest MessageStats team and other community members. Join the MessageStats community at http://messagestats.inside.quest.com/

Contact Quest Software:

Email info@quest.com
Mail: Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site: http://www.quest.com/

Refer to our Web site for regional and international office information.

Contact Quest Support:

Quest Software’s world-class support team is dedicated to ensuring successful product installation and use for all Quest Software solutions. If you have questions, please contact our technical support staff. Please include the version number and, if your question is about an error message, include the error text as well.

SupportLink: http://support.quest.com
Email: support@quest.com

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. From SupportLink, you can do the following:

  • Quickly find thousands of solutions (Knowledgebase articles/documents).
  • Download patches and upgrades
  • Seek help from a Support engineer.
  • Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Back to Top