Foglight ® for SQL Server

Release Notes

Developed and tested for Foglight Management Server 5.9.2 - 5.9.8 and 6.0.0

February 2022

These release notes provide information about the Foglight ® for SQL Server release.


Welcome to Foglight for SQL Server

Foglight ® for SQL Server allows database administrators (DBAs) to quickly and efficiently identify performance deviations, determine their root cause, perform comprehensive analyses, and resolve performance bottlenecks. This product provides web-enabled dashboards for centralized visibility, management and health checks for the SQL Server instances deployed in your environment, as well as proactive alerting and alarm workflows for tracking your responses to critical performance anomalies.

Foglight for SQL Server is an n-tier application, which leverages a web-based user interface to ensure having complete visibility into the SQL Server infrastructure wherever an Internet connection is available.

These Release Notes cover the resolved issues, known issues, workarounds and other important information about release of Foglight for SQL Server. Review all sections before starting installation.

New in this release

Version does not contain any new feature or update.

See also:

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Resolved issues

Issue ID

Resolved issue


upgrade log4j libraries to 2.17.1

Issues also resolved in version,, and

Issues resolved in version,, and

Issue ID

Resolved issue


Replace Data Direct JDBC Driver with Microsoft JDBC Driver for SQL Server Cartridge


SQL Server Error log retrieval issue


SQL Server User Defined Collection Not Showing Up


No data in DB Administration after upgrading FMS but not db cartridge


Failed to run DBSSFileProcessor processor of DBSS_File collection


Error message in Database Groups after upgrade from 5.9.5 to 6.0.0


Fixed an issue where Foglight Agent manager crashes frequently on Windows platform with SQL Server cartridge and


Added ASP parameter to control maximum Host disk queue length and the default value of the parameter is 5000.


Fixed an issue that it might fail to execute the callback: [BLOCKING_LIST] and display error on blocking (current).


Fixed an issue where the users could not change the “Connect as” sysdba/normal in Migration Dashboard.


Fixed an issue that the agent might log exception when the backup location is a virtual disk.


Fixed an issue where it might fail to create SQL PI database when the initialize size is smaller than that of the Model database.


Fixed an issue after migrating the PI from Infobright to SQL Server-based repository the PI engine might be paused.


Fixed an issue when the agent name contains '[]', the Jobs list might not show up in Administration > Alarms > DBSS - Job Failed > Rule Exceptions.


Fixed an issue where Database dashboard might not be able to sort by the size column.


Fixed an issue where SQL - Disk Space Usage Report PDF might miss detail rows if file_groups.files.virtual_file_statistics has no data.


Fixed an issue where the collection colMaxRows value is set too small for customer's environment, and customer might not get full Databases dashboard.


Fixed the missing metrics for SQL Server: Up Since and Availability.


Fixed an issue where showplan parsing might be wrong for operation: Clustered Index Seek.


Fixed an issue where data in Local Last Backup Date field might be incorrect after all backup information has been deleted.


Fixed an issue where data for Disk Space might miss when having a snapshot in the instance.


Fixed an issue after clicking inactive session wrong dialog might pop up.


Fixed an issue when the system have hundreds of agents, the table records grow very fast. And 'registry_registry_value' and 'registry_registry_variable' take more than 1TB.


Fixed an issue where the Blocking (Current) page in SQL Server cartridge is very slow to load when the number of rows is >10.


Fixed an issue when the locale is GERMAN, the Workload summary report always displays 0.00% for each resource breakdown.


Fixed an issue when users access Manage SQL PI Repository from Databases dashboard, the FMS console might hang.


Fixed an issue where the dashboard I/O by File might not display a period value.


Fixed an issue where the DB agent log might print password information as Pa$$word , even if the value has been encrypted.


Fixed an issue where on-demand data connections might fail unless more TCP ports are opened.


Fixed an issue when configuring Rule exceptions for rule DBSS - Hours Since Last Log Backup, it might not work.


Fixed an issue when the customer have many system events files, the current deadlock query might consume high CPU, and the query execution time might need several minutes.


Fixed an issue when the percentage of usage exceeds 100, there might be gaps in SQL Server Memory > Summary > Memory Used graph.

Known issues

The following is a list of issues known to exist at the time of release.

General issues


General issues

Issue ID

Known issue


PI engine didn't use new credential changed in Connection Details dashboard.

Workaround: Reactive the agent after changing the credential.


Cannot use cluster server or AlwaysOn listener to monitor AlwaysOn environment on FIPS-enabled FMS.

Workaround: Refer to KB 324797 for detailed information.


When there are many DB agents with PI enabled in FMS environment and you want to upgrade the cartridge to the latest version, the SQL PI component update might fail.

Workaround: Click Cancel on Update SQL PI Failed and click Update SQL PI Components to update again.


DB instance is still synchronized and displayed in FMS federation master even though it is stopped for some reason and not displayed in the FMS federation child.


After DB agent restarts, there will be a 5 minutes data gap in the SQL PI baseline view.


Incomprehensible error message is displayed when using local account without hostname prefix to setup PI Repository.

Workaround: Use hostname\username to setup PI Repository instead of only using username.


Enabling SQL PI is only supported when the SQL PI agent manager is installed on one of the following operating systems:




“Context infos” display null in the Comparison Parameter dashboard.


An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3.


If two SQL Server instances running in different hosts but these two hosts have the same short name, these two hosts shows same on the Home page.

Workaround: Contact Quest support to get the scripts for updating the loadGVData function.


Due to the metric collection interval, value of Data files, log files, and disk space metrics will be occasionally missing on the Databases > Temdb dashboard.

Workaround: Wait for 3 minutes, then you will see these metrics on the dashboard.


It fails to run DBSSSQLAgentErrorLogProcessor processor of DBSS_SQL_Agent_Error_Log collection if the SQL Server Agent Service is not started.

Workaround: Start the SQL Server Agent Service.


DBSS_Error_Log_List collection fails if SQL Server 2017 Agent is not running on Linux.


Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard.


Alarm is not triggered while the error has been collected on the DBSS - SQL Server Error Log page.


If AD authentication has been used to monitor SQL Server instance, the default option 'Log in to the host using the same account used for monitoring SQL Server' cannot be used to monitor Linux Operating System (OS).

Workaround: Switch to use the option 'Log in to the host using different login credentials', then choose either of the following Linux authentication types: input AD account info, input other Linux account info, or use 'Select from stored credentials...'.


When using IP address to create a SQL server agent, Disk metric and Host metric will be missing in the Global view.


Using CLI to create multiple SQL Server instances with OS monitoring might result in failure to activate some host agents.

Workaround: Either activate those host agents manually on the Agent Status dashboard or re-create those host agents.


When monitoring SQL Server 2017 on Linux, an error message will be shown in Logs > SQL Agent Error Logs page.


If you select either of DB_SQL_Server, DB_SQL_Server_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again.

Workaround: Do the following:

Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.
  1. Search for DBSS_Is_Fglams_Required_Upgrade.
  2. Change its value to -1.


Creating Infrastructure agent automatically after failover occurs on Linux-based SQL Server cluster may fail.


In the Master server of the federation environment, the values in Message of back up alarm are null.


When SQL Server cluster on Linux does fail-over, IC agent may not be auto created when the host name of the node is different with previous node.


Databases Replication Dashboard does not show all Subscriptions when using multiple distribution databases.


Failed to monitor SQL Server 2005 on premise while using no required permission DB credential.

Workaround: Download the DB_SQL_Server_Grant_Permission_Script from Components for Download, execute the script at SQL Server client to grant permission to the new user, then use the new user to monitor SQL Server 2005 Instance.


Databases on a secondary replica are read-only, so the grant script cannot create the user in the database. The Foglight user may still not be able to read data from these read-only replicas even if the users are synchronized.


  • When using new SQL Server Authentication and granting permission failed, do the following:

Re-monitor this instance again, and then it could be monitored successfully.

  • When using new AD (Active Directory) Authentication and granting permission failed, do the following:

1. Re-monitor this instance again.

2. A grant permission dialog pops up. Skip the permission granting step.

3. Continue monitoring the instance, and then it could be monitored successfully.


When the VMwarePerformance Agent exists, the Disk Latency in SQL Server Overview would always show “-” while enabling OS monitoring.


On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock.

Workaround: Implement trace flag -T1234.


When working with Global View while the screen resolution is set to 1024 by 768 pixels, it is advisable to switch to the browser's full view (F11 toggles between full and normal views in all browsers).


User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols.


The DBSS- Deadlock Details alarm is disabled by default.


Changes made in the Global Administrations > Alarms screen are saved when switching to another global administration screen, even if selecting “Yes” in the dialog box that asks whether to exit without saving changes.


Editing a user-defined collection results in periodic overlap of data.


Creating a user-defined collection with more than one SQL in it will not alert the user, however, only the first SQL in the collection will be executed.


When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > FglAM host property.

SSDB-8987, SSDB-7326

On Microsoft® Windows® 2008 R2, a SQL Server version 2012 instance with a name that contains inverted commas (''; (for example:'X641_ENT1') can encounter issues with the retrieval of WMI data. This is by design on the part of Microsoft.

Workaround: If WMI data is not retrieved, the instance name without the '' should be added in the field Service Name in the Agent Properties dashboard.


Cluster data can be collected only if the xp_cmdshell parameter is configured.

To configure this parameter, run the following commands:

EXEC sp_configure ‘show advanced options’,1


--To update the currently configured value for advanced options.



—- To enable the feature.

EXEC sp_configure ‘xp_cmdshell’, 1


—- To update the currently configured value for this feature.




In SQL Server® 2012, when a database is part of an availability group and is currently accessible for connections, when the application intent is set to read only, several collections will fail.


Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension.


In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility.


The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings:


SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration.


In case the privilege of OS monitoring is not set to the Local Administrator group on the host being monitored, see the Knowledge Article 215054 .


Performing an upgrade process on a large environment (more than 50 agents) takes time to complete.


When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows.


In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, the more recently created collection will not appear in the topology, nor will it be displayed on the User-defined Collections panel.


Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for SQL Server.


In environments configured to monitor SSAS agent only, when upgrading to version or later, the upgrade process will fail.

Workaround: In the Administration > Agents > Agent Status dashboard, click Deploy Agent Package, then follow on-screen instructions to deploy the SSAS package manually.


Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 installed.


If the WMI exception “Format specifier '%s' “ is entered in agent log the following workaround is recommended:


For Windows® Vista® and Windows Server 2008 or above:

According to , the default dynamic port range for TCP/IP has changed in both versions. The new default start port is 49152 and end port is 65535. Subsequently, monitoring instances that run under these operating systems can be carried out by setting a static (fixed) WMI port in Windows Server.

For more information, see the Knowledge Article 114559 .


When Foglight or the Agent Manager are installed on a VM, it is highly recommended to reserve the following:

  • CPU - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.
  • RAM- for a virtual machine the memory reservation is highly recommended for better performance.


Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article .

Execution plan

Execution plan related known issues

Issue ID

Known issue


Execution plan may not be resolved.


Sometimes, query_hash is changed by SQL Server and generating a plan using the Generate button fails. SQLhash isn't found in XML so the screen displays No operation was found and the execution plan changes are missing.


Time range changes are not affecting the execution plan dashboard.


In the Execution Plan comparison popup, the date of the selected plan is the insert time to the SQL PI repository and not the execution time.


In the Execution Plan Comparison popup for statement - the estimated plan appears only as the selected plan on the left side. It cannot be selected from the list.

Third party known issues

The following is a list of third party issues known to exist at the time of this release.

Third-party known issues

Issue ID

Known issue


No throughput data on dashboard for SSAS 2017 due to WMI class missing.


Download cumulative update package through .
  1. Install the package on the host where SSAS is installed.
  2. Restart the host.


Popup SQL Statement dialog cannot show all SQL text when accessing with Firefox browser using FMS version higher than 5.9.4.


Cannot import license into installer with license file name XXX.lic.


When importing license into installer, change license file name to XXX.license.
  1. Install xxx.lic after login FMS.
  2. Change license file name to XXX.license and put it into license folder before FMS start up.


The Foglight Agent Manager (FglAM) failed to restart when upgrading DB Cartridge, which is due to Could not obtain a deployment lock error.

Workaround: Perform the procedure described in the Knowledge Article 266110 .


In FIPS-compliant mode, it is required to use at least 2048 RSA and DSA key size to do OS monitoring via SSH connection in DB cartridge.

When FglAM version is lower than, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to or later.


WMI-related issue

Problem: WMI support is affected by the firewall

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

Open TCP port: 135.

WMI by default uses the port range 1024 to 5000.

  1. Open up a range of ports above port 5000.

Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.

  1. Add the registry key, including additional ports.
  2. Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
  3. Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista® and Windows Server 2008:

According to Microsoft® , the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.

Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

  • Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).
  • Limit the port range that is used in each monitored server.


As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions:

  • SQL Server 2012 Production version and later
  • SQL Server 2008 Service Pack 3 Cumulative Update 4
  • SQL Server 2008R2 Service Pack 1 Cumulative Update 6
  • SQL Server 2008R2 Service Pack 2


Third Party Limitations

Monitoring an SQL Server instance that resides on a Windows 2008R2 or higher requires a workaround as follows:

Browse to / and log in.
  1. Perform solution .


Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft site, .


Due to a known Microsoft issue , on SQL Server instances version 2014 the SQL text presented may be truncated.


SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug: “ The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014 "


The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. Refer to for more information.


The Windows System Center Endpoint Protection (SCEP) tool and Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight, Foglight Agent Manager, and the SQL PI repository.

To reduce resource consumption it is highly recommended that you exclude the following directory from being scanned by the protection tools:

  • <installation directory>:\Quest\<FoglightAgentManager>


Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software. For detailed information, refer to the “Configuring anti-virus exclusion settings” in Installing Foglight on Windows with an Embedded PostgreSQL Database .

Workaround for all missing WMI metric cases

In some cases, running the command: %windir%\system32\wbem\wmiadap.exe /f in Windows' command-line (CMD) may solve the problem of missing WMI classes. This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details, see

Upgrade and Compatibility

A direct upgrade to Foglight for SQL Server 5.9.7.x is only available from version 5.7.5.x or later. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 5.9.7.x. A direct upgrade to Foglight for SQL Server 5.7.x is only available from version 5.5.8 or later. Customers that are running earlier versions of the product must first upgrade to version 5.5.8 and then upgrade to version 5.7.x.

For example, if your Foglight for SQL Server is version 5.5.8 and you are going to upgrade to version 5.9.7.x, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.7.x.

To upgrade Foglight for SQL Server to version 5.9.7.x:

For cartridge installation instructions, see the Foglight for Databases Deployment Guide.

Once you have upgraded the cartridge, to deploy the agent package, navigate to the Global View dashboard and follow the upgrade wizard instructions. For a procedure describing how to deploy the agent package, see the Foglight for Databases Deployment Guide.


  • Foglight for SQL Server does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/ .
  • Starting from version, Infobright is no longer supported. It is necessary to move existing agents to the SQL Server-based PI repository. We have provided a data migration utility for customers who want to keep their historical performance data. For more information, refer to How to migrate database agents to a SQL Server-based PI repository.


  • If you are upgrading to the current version of Foglight for SQL Server in a Federation architecture, the upgrade should be applied first to the Federated Children and then to the Federation Master. If the Federation Master is upgraded first, it will display incorrect information regarding the number of instances being monitored in the Status Summary section.

The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version


Foglight Management Server

5.9.2 - 5.9.8

All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager

Note: The monitoring agents available in this version of Foglight for SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide.

5.9.2 - 5.9.8

All platforms supported by this version of the Foglight Agent Manager

System requirements

Before installing Foglight for SQL Server, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide.

Customers running large deployments (that is, with more than 20 agents) should consult the Foglight for Databases Deployment Guide.

Required privileges

For information on the required privileges, refer to the Foglight for Databases Deployment Guide.

Supported platforms

Foglight for SQL Server supports monitoring the following platforms:


  • Foglight for SQL Server also supports the Express and Developer editions of Microsoft ® SQL Server.
  • Virtualization monitoring requires installing the VMware tools service on the monitored VM.
  • SQL Server on AWS VM (IaaS) is supported and can be monitored as long as the Instance port is opened and the OS is configured as described in: Configuring Windows Remote Management (WinRM).
  • For the Amazon RDS for SQL Server, only Standard and Enterprise version are supported.

Final Browser Support Notice

Support for Microsoft® Internet Explorer® 8, 9, and 10 has been discontinued in this Foglight release.

Microsoft ended the support for these browsers on January 12, 2016. For more information, visit .


This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledge base:

Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.

Foglight for SQL Server is covered by the base Foglight license that allows cartridges to be installed. The SQL Performance Investigator extension requires a dedicated license.

To activate a trial or a purchased commercial license:

On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  1. Click Install.
  2. In the Install License dialog box, click Browse.
  3. In the file browser that appears, specify the location of the license file.
  4. In the Install License dialog box, click Install License.

Getting started with Foglight for SQL Server

Contents of the release package

The Foglight for SQL Server release package contains the following:

Installation instructions

For installation pre-requisites, permissions, information necessary to determine your environment’s hardware requirements, and for installation instructions, see the Foglight for Databases Deployment Guide.

Additional resources

Additional information is available from the following:


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, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The server will be enabled for Global Operation, but not localized to any particular locale.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit .

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at .

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

© 2022 Quest Software Inc.


This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software 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 Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE 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 SOFTWARE 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 SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software 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 Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.
Attn: LEGAL Dept.
4 Polaris Way
Aliso Viejo, CA 92656

Refer to our website ( ) for regional and international office information.


Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at .


Quest, the Quest logo, Foglight, and Where next meets now are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and “Amazon RDS” are trademarks of, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.




WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death.




CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.




IMPORTANT NOTE , NOTE , TIP , MOBILE , or VIDEO: An information icon indicates supporting information.