AppManager ResponseTime for Networks helps you monitor many features of your network, including response time, availability, throughput, and numerous application transactions that run over a network.
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.
This release of AppManager ResponseTime for Networks resolves the following issues:
Support for Microsoft Windows 10, Windows Server 2012 R2, and Windows Server 2012. This release supports Windows 10, Windows Server 2012 R2, and Windows Server 2012. For more information, see the System Requirements.
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 ResponseTime for Networks 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 ResponseTime for Networks has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
AppManager installed on the AppManager repository (QDB) computers, on the management server, on the computers you want to monitor (agents), and on all console computers |
8.0.3, 8.2, 9.1, or later One of the following AppManager agents are required:
|
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the computers you want to monitor (agents), and on all console computers
|
7.6.170.0 or later |
|
NetIQ Performance Endpoint installed on the computers you want to monitor |
Version 5.1.15905 of the Performance Endpoint is included with AppManager ResponseTime for Networks and is installed automatically on the managed client. See the AppManager ResponseTime for Networks Management Guide for specific information about endpoint versions and support for proxy monitoring on systems other than Windows. |
|
Microsoft .NET Framework on agent computers |
3.5 NOTE:Microsoft .NET Framework 3.5 is required for installing the Networks-RT Knowledge Scripts. |
|
Microsoft Internet Explorer installed on the agent computers |
7.0 or later |
IMPORTANT:Before installing the module on a 32-bit Windows 10 agent computer, ensure that the Windows NTVDM feature is enabled.
To enable the Windows NTVDM feature:
Go to Control Panel > Programs > Programs and Features > Turn Windows features on or off.
In Legacy Components, select NTVDM.
Click OK.
For more information on hardware requirements and supported operating systems and browsers, see the AppManager ResponseTime for Networks Management Guide, included in the download package.
AppManager ResponseTime for Networks includes a managed object, qNetMona4.dll, and Knowledge Scripts to discover and monitor ResponseTime for Networks resources. The download package includes these release notes, a Management Guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-Networks-RT-7.0.217.0.msi, the module installer.
AM70-Networks-RT-7.0.217.0.ini, a configuration file used with the AppManager setup program.
AM70-Networks-RT-7.0.217.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-Networks-RT-7.0.217.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckNetworks-RT.exe, the pre-installation check used with the AppManager setup program.
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 computers you want to monitor (agents) and all proxy agent computers 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.
IMPORTANT:This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.
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.
Module installation installs the latest endpoint. However, automatic installation of the Performance Endpoint might fail on computers where you have enabled User Account Control (UAC). If you have UAC enabled, disable UAC during installation or install the Performance Endpoint manually. You can download the free endpoint software from the Current Performance Endpoints Product Upgrades page.
For more information about installing this module, see the AppManager ResponseTime for Networks Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Jobs fail on computers with Dual NIC cards configured as Host only. When you run a Networks-RT Knowledge Script on a Performance Endpoint installed on a computer with dual NIC cards, and one of the cards has network settings of Host only, the job fails with this event: CHR0201: The address is in a TCP network that is unreachable.
Unable to use Add Jobs option on certain proxy computers. In our testing, we found that we could not select Endpoint 1 computers using the Add Jobs option if those computers were being proxied by the same computer. Normally, if you right-click a job in the Operator Console and select Add Jobs, the values of the job are copied and that job can then be started on a new object. However, AppManager ResponseTime for Networks will not allow you to start new jobs on remote computers that are using the same proxy as the original job.
Changes to Knowledge Scripts not automatically applied. Any changes you make to Knowledge Scripts that you have previously generated using the Knowledge Script Generator utility, or to Knowledge Scripts whose names have been changed, are not automatically applied. However, the template that is used by the Knowledge Script Generator is updated when you install the upgraded version of AppManager Networks-RT. Therefore, any Knowledge Scripts generated after the upgrade will contain the latest updates.
This release of ResponseTime for Networks includes enhancements added in previous releases.
This release resolved the following issue:
Networks-RT_Report_ResponseTimeSummary Knowledge Script reports an availability value that is ten times greater than the actual data. For example, in previous releases this script listed 100% availability as 1000% availability in the report. With this release, an update to the script prevents this reporting error. (ENG123456)
This release provided the following enhancements:
Support for Windows Server 2008 R2. This release provides support for monitoring in Microsoft Windows Server 2008 R2 environments.
Support for Windows 7. This release provides support for monitoring in Microsoft Windows 7 environments.
Support for 64-bit Windows 2003. This release provides support for monitoring in 64-bit Microsoft Windows 2003 environments.
This release provided support for AppManager version 7.0.
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) 2016 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.