AppManager for Microsoft SQL Server provides a comprehensive solution for monitoring the performance and availability of your Microsoft SQL Server environment. This module provides Knowledge Scripts that present a complete view of Microsoft SQL Server performance on your servers.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials website.
NOTE:This new module of AppManager for Microsoft SQL Server is not an upgrade to the previous versions (7.x) of the SQL module. This module has a new set of Knowledge Scripts and managed objects and it has a new approach to monitor SQL Server than earlier versions of the SQL module. This module requires you to configure different user specifications in Security Manager and does not use the user specifications configured for the earlier versions of the SQL module.
This release of AppManager for Microsoft SQL Server provides the following enhancements:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft SQL Server provides support for TLS 1.2.
This release of AppManager for Microsoft SQL Server resolves the following issues:
Arithmetic Overflow Error Converts Expression to Int Data Type: While converting database size into KB for database size more than 2.5 TB, the intermediate result exceeds the maximum size of SQL Int data type and causes arithmetic overflow exception. This release of AppManager for Microsoft SQL Server resolves this issue. (ENG348140)
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.
This release of AppManager for Microsoft SQL Server replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Microsoft SQL Server has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the SQL Server computers you want to monitor (agents), and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required:
|
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
Microsoft SQL Server on the agent computers |
One of the following:
|
|
Microsoft .NET Framework on the agent computer where you want to install the managed objects of AppManager for Microsoft SQL Server |
3.5 and 4.0 or later |
|
Microsoft .NET Framework on the computer where you want to install the repository, Knowledge Scripts, help files and console extensions of AppManager for Microsoft SQL Server |
3.5 |
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer and on all console computers |
7.6.170.0 or later NOTE:For clustered SQL Server monitoring on Windows Server 2012 and later, you must ensure that AppManager for Microsoft Windows 7.8 or later is installed on the agent and on all console computers. |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Microsoft SQL Server Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Microsoft SQL Server includes a managed object, qSQLServerMOa4.dll, and Knowledge Scripts to discover and monitor Microsoft SQL Server resources. The download package includes this release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-SQLServer-8.2.84.0.msi, the module installer.
AM70-SQLServer-8.2.84.0.ini, a configuration file used with the AppManager setup program.
AM70-SQLServer-8.2.84.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-SQLServer-8.2.84.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckSQLServer.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_SQLServer.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On the SQL Server computers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
NOTE:
Install Microsoft .NET Framework 3.5 and .NET Framework 4.0 or later on the agent computer where you want to install the managed objects of AppManager for Microsoft SQL Server. To install .NET 4.0 with the Add Roles and Features wizard in Windows Server Manager, refer the Microsoft article.
Install Microsoft .NET Framework 3.5 on the computer where you want to install the repository, Knowledge Scripts, help files and console extensions of AppManager for Microsoft SQL Server.
IMPORTANT:If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for Microsoft SQL Server Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. AppManager for Microsoft SQL Server had no known issues at the time of release. If you need further assistance with any issue, please contact Technical Support.
This release of Microsoft SQL Server includes enhancements added in previous releases.
This release of AppManager for Microsoft SQL Server provided the following enhancements:
Added SQLServer_AvailabilityGroupOwner: This Knowledge Script determines the node ownership of a SQL Server AlwaysOn Availability Group.
Added SQLServer_SQLClusterOwner: This Knowledge Script determines the node ownership of a SQL Server failover cluster instance.
SQLServer_RunSql can be run on AlwaysOn Availability Group. You can now use this Knowledge Script to run SQL statements or stored procedures on AlwaysOn Availability Group. (ENG346925)
SQLServer_MonitorJobs accepts the SQL wildcard characters (% and _). You can now use the SQL wildcard characters (% and _) in the Specify list of jobs to monitor (comma-separated) parameter. (ENG346732)
This release of AppManager for Microsoft SQL Server resolved the following issues:
SQLServer_BlockedProcesses fails to connect to DMS cluster machines. The error occurred when the SQL Server instance was configured at a non-default port. In this release, the issue is resolved. (ENG345848)
SQLServer_ClusterOwner fails to determine the node ownership in few scenarios. In this release, the SQLServer_ClusterOwner Knowledge Script is removed and two new Knowledge Scripts- SQLServer_AvailabilityGroupOwner and SQLServer_SQLClusterOwner are added that are used to determine the node ownership of AlwaysOn Availability Group and failover cluster instance respectively. (ENG344796)
SQLServer_ SQLClusterOwner and SQLServer_AvailabilityGroupOwner raise events on frequent basis. The Raise Event to show the owner node in first iteration? parameter was raising events on a frequent basis. In this release, this issue is resolved and now the parameter generates events for the first iteration only. (ENG347354)
This release of AppManager for Microsoft SQL Server provided the following enhancements:
Support for Microsoft SQL Server 2017: This release supports SQL Server 2017. For more information, see System Requirements.
SQLServer_Accessibility, SQLServer_DataSpace, SQLServer_DBStats, and SQLServer_LogSpace can now exclude the monitoring of loading or restoring databases: In this release, a parameter is added in these Knowledge Scripts that provides the functionality to exclude the monitoring of the SQL Server databases that are in loading or restoring state.
SQLServer_LogShipping can now exclude the monitoring of the backup errors: In this release, a parameter is added in the Knowledge Script that provides the functionality to exclude the monitoring of the backup related errors of the SQL Server databases.
This release of AppManager for Microsoft SQL Server resolved the following issues:
Fails to discover SQL Server resources on cluster nodes: In few scenarios, the SQL Server resources on cluster nodes were not discovered because of the inconsistent part component names. In this release, the issue is resolved. (ENG345060 and ENG344621)
Fails to discover a FQDN node on an Always On Availability Group cluster: The node that was named in the FQDN format on an Always On Availability Group cluster was not discovered. In this release, the issue is resolved. (ENG343424)
SQL Server objects in the FQDN format are duplicated and appear as the NetBIOS name format in the treeview after the discovery: The SQL Server objects that were named in the FQDN format were duplicated and appeared as the NetBIOS name format in the treeview. This behavior was seen when you selected the Display “AppManager Proxy Events” as objects in treeview parameter in the Operator Console and ran the Discovery_SQLServer Knowledge Script. In this release, this issue is resolved and you do not see the duplicated SQL Server objects in the treeview. (ENG343557)
SQLServer_LogShipping raises an event even though log shipping is not configured on a SQL Server: Even though log shipping was not configured on the SQL Server, the SQLServer_LogShipping Knowledge Script raised an event when the Raise event if number of failure log shipped records exceeds threshold? parameter was selected. This event was raised because of the backup errors. In this release, this issue is resolved and a parameter is added in the Knowledge Script to exclude monitoring of the backup errors. (ENG344707)
SQL Server databases that are in loading or restoring state are not monitored: The databases that were in loading or restoring state could not be accessed or opened when you ran any one of the Knowledge Scripts:
SQLServer_Accessibility
SQLServer_DataSpace
SQLServer_DBStats
SQLServer_LogSpace
In this release, the issue is resolved and a parameter is added in the above Knowledge Scripts to exclude monitoring of the databases that are in loading or restoring state. (ENG343731)
Fails to discover an Always On Availability Group on Windows Server 2008 R2: When you ran the Discovery_SQLServerAlwaysOnCluster Knowledge Script on Windows Server 2008 R2 to discover an Always On Availability Group, the discovery job failed in few scenarios. In this release, the issue is resolved. (ENG342921)
This release of AppManager for Microsoft SQL Server provided the following enhancements:
Support for Microsoft SQL Server 2016. This release supports SQL Server 2016.
Added new Knowledge Scripts: Following Knowledge Scripts are added:
SQLServer_ClusterOwner: Determines the node ownership of a SQL Server failover cluster instance or AlwaysOn Availability Group.
SQLServer_CPUUtil: Monitors the percentage of CPU used by SQL Server processes.
SQLServer_DBMirrorStatus: Monitors the status of each mirrored database.
SQLServer_LogShipping: Monitors log shipping status.
SQLServer_MemUtil: Monitors the amount of memory used by SQL Server processes.
Added new parameters for database space in the DBStats Knowledge Script: In this release, you can monitor the total used database space based on the threshold you specify.
SQLServer_MonitorJobs monitors failed jobs from the specified time prior to first iteration. In this release, you can specify the time prior to first iteration from which the SQLServer_MonitorJobs Knowledge Script will monitor the failed jobs.
Added new parameters for T-SQL statement in the BlockedProcesses Knowledge Script: In this release, you can view the T-SQL statement for each blocked process and also specify the timeout duration before a timeout exception is raised.
Added new parameters for most expensive queries in the TopResourceUsers Knowledge Script: In this release, you can view the most expensive queries for the CPU time, the elapsed time, and the IO operations using the TopResourceUsers Knowledge Script.
Added new parameters for timeout and retry mechanism in the RunSql Knowledge Script: In this release, you can specify the timeout duration and the retry attempts while establishing a SQL connection using the RunSql Knowledge Script.
Using non-default TCP port for SQL Server or Availability Group Listener: If SQL Server or Availability Group Listener uses a non-default TCP port, you can specify the TCP port in AppManager Security Manager.
Support for dynamic logging for jobs: In this release, you can enable dynamic logging for jobs while the jobs are running.
TopCPUUsers, TopIOUsers, and TopMemoryUsers Knowledge Scripts are removed from the module: In this release, the SQLServer_TopCPUUsers, SQLServer_TopIOUsers, and SQLServer_TopMemoryUsers Knowledge Scripts are removed. Instead, you can run the SQLServer_TopResourceUser Knowledge Script to use the functionalities similar to the Knowledge Scripts that are removed.
This release of AppManager for Microsoft SQL Server resolved the following issues:
SQLServer_ErrorLog does not display error log entries in Japanese language: The SQLServer_ErrorLog Knowledge Script failed to display the log entries that were written in Japanese. In this release, the SQLServer_ErrorLog Knowledge Script can handle Japanese strings. (ENG341680)
Discovery_SQLServer does not have the option to exclude the discovery of database size if auto growth is enabled: The Discovery_SQLServer Knowledge Script did not have the option to ignore the event that was raised when the database size was increasing if auto growth was enabled. In this release, a parameter is added to exclude the discovery of data space and log space if auto growth is enabled. (ENG341201)
Run time error associated to dictionary key: VBScript run time error This key is already associated with an element of this collection was observed in the following Knowledge Scripts:
SQLServer_DataSpace
SQLServer_DBLocks
SQLServer_DBStats
SQLServer_LogSpace
In this release, a check mechanism is added to prevent the run time error. (ENG343118)
This release of AppManager for Microsoft SQL Server provided the following enhancements:
Discovery and monitoring of SQL mirror database excluded from a witness machine. With this release, the SQL mirror database is excluded from discovery and monitoring on a witness machine. Only a principal machine can discover and monitor the SQL mirror database.
New parameters added for the Discovery_SQLServer Knowledge Script. With this release, you can exclude the list of databases from discovery while using the Discovery_SQLServer Knowledge Script.
New parameter added for the SQLServer_RunSql Knowledge Script. With this release, you can specify a description for the SQL query in the SQLServer_RunSql Knowledge Script.
This release of AppManager for Microsoft SQL Server resolved the following issues:
DataSpace and LogSpace display wrong values for large database. The DataSpace and LogSpace Knowledge Scripts displayed wrong values for large database and collected wrong results for the data point. With this release, the DataSpace and LogSpace Knowledge Scripts works properly for large database. (ENG339308)
SQLServer_RunSql performs threshold checking on rows only. The SQLServer_RunSql Knowledge Script performed threshold checking on the number of rows only regardless of the option chosen. With this release, the Knowledge Script performs threshold checking according to the selected option. Also the Knowledge Script truncates the SQL query string in the data legend if the string length exceeds 126 characters. (ENG341096)
SQLServer_DBStats returns wrong value for the total database size. The SQLServer_DBStats Knowledge Script returned wrong value for the total database size and the event message did not display the exact cause of the problem. With this release, the SQLServer_DBStats Knowledge Script returns the correct value for the total database size and the event message displays the cause of the problem properly. (ENG340363 and ENG340444)
This release of AppManager for Microsoft SQL Server included the following new Knowledge Scripts:
Discovery_SQLServerAlwaysOnCluster: Discovers the AlwaysOn availability group listeners on a cluster. An availability group listener is a virtual network name (VNN) to which clients can connect to access a database in a replica of an AlwaysOn availability group. This script only discovers the listener node. You must run the Discovery_SQLServer Knowledge Script on the discovered listener nodes to discover the availability group resources under the listener nodes.
AvailabilityGroupHealth: Monitors the AlwaysOn availability group health status, replica synchronization status, replica failover readiness, and operational status.
BackupJob: Monitors SQL Server backup jobs to track data backup activities optimally.
DBStats: Monitors the percentage of used space for data and log files.
NearMaxConnect: Monitors the number of user connections used compared to the maximum number of connections configured for the server.
NearMaxLocks: Monitors the current number of locks used compared to the maximum number of locks configured for the server.
RunSql: Runs T-SQL statements or stored procedures.
TopCPUUsers: Monitors the total CPU time (in milliseconds) used by SQL Server users.
TopIOUsers: Monitors the number of IO operations that is read and write operations performed by SQL Server users.
TopMemoryUsers: Monitors the total memory pages allocated to all the SQL Server users.
TopResourceUsers: Monitors the total CPU time used by SQL Server users, the number of IO operations performed, the total number of locks held by all SQL Server users, and the number of memory pages that can be allocated to all SQL Server users.
RECOMMENDED_SQLServer: This release supports new recommended Knowledge Script Group that includes the following Knowledge Scripts:
Accessibility
BlockedProcesses
CacheHitRatio
Connectivity
DBLocks
DBStats
MonitorJobs
ServerDown
TopResourceUsers
UserConnections
This release of AppManager for Microsoft SQL Server also included the following enhancements:
Support for AlwaysOn availability group. This release now supports AlwaysOn availability Group.
The Discovery_SQLServer is enhanced to support discovering availability group resources under the listener nodes.
The following Knowledge Scripts are enhanced to support monitoring the availability databases in availability group:
Accessibility
DataSpace
DBLocks
DBStats
LogSpace
This new release of AppManager for Microsoft SQL Server supports SQL Server version 2005 and later and included the following Knowledge Scripts:
Discovery_SQLServer: Discovers SQL Server configurations and resources.
Accessibility: Monitors SQL Server database accessibility and raises an event if a specified database is not accessible.
BlockedProcesses: Monitors the number of SQL Server processes that have been queued for longer than the period of time you specify.
CacheHitRatio: Monitors the percentage at which the requested data page is retrieved from the SQL Server cache without performing physical reads from disk.
Connectivity: Monitors SQL Server connectivity and raises an event if the server is not available during the monitoring interval.
DataSpace: Monitors the available data space and the percentage of data space used by each database.
DBLocks: Monitors the number of locks per SQL Server database and raises an event if the number of locks exceeds the threshold you specify.
ErrorLog: Monitors the SQL Server error logs and looks for any error log entries that have appeared since the last monitoring interval.
LogSpace: Monitors the available log space and used log space of a database and raises an event if the available log space falls below the threshold, or if the percentage of log space used exceeds the threshold you specify.
MonitorJobs: Reports on any scheduled jobs that have not completed successfully and raises an event only when new job failures occur since the last monitoring interval.
ServerDown: Monitors the up or down status of a SQL Server and also identifies the downtime of the SQL Server since the server was started.
UserConnections: Monitors the total number of user connections currently connected to a SQL Server and raises an event if the total number of user connections exceeds the threshold you specify.
The Microsoft SQL Server product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Apache License: Distributions of log4j, log4net, log4cxx Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
Definitions “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.” “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2018 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.