AppManager ResponseTime for Windows (Windows-RT) allows you to monitor your organization’s Windows infrastructure to ensure the availability and performance of critical applications and services on a Microsoft Windows computer. Using the Windows-RT Designer, you create custom Knowledge Scripts you can use with AppManager to identify problems a user might encounter when accessing an application.
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, bn logs, 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 provides the following enhancements:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager ResponseTime for Windows provides support for TLS 1.2.
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 Windows 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 Windows has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
AppManager installed on the AppManager repository (QDB) computers, on the 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:
NOTE:Support for Windows Server 2008 on AppManager 7.x requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes page. |
|
Microsoft .NET Framework on the agent computer |
4.0 or later for Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2. NOTE:For Windows 8, Windows 2012, Windows 2012 R2, and Windows 10, the .Net Framework 4.0 or later is in-built feature. |
|
Visual Studio 2010 C++ runtime support file |
2010 NOTE:
|
|
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. |
You need Local Administrator Rights on the computer where you install Windows-RT.
For more information on hardware requirements and supported operating systems and browsers, see the AppManager ResponseTime for Windows 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 ResponseTime for Windows includes a managed object, qWinRT7.dll, and Knowledge Scripts to discover and monitor Windows resources. The download package includes a release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-Win-RT7-7.7.165.0.msi, the module installer.
AM70-Win-RT7-7.7.165.0.ini, a configuration file used with the AppManager setup program.
AM70-Win-RT7-7.7.165.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-Win-RT7-7.7.165.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckWin-RT7.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 Windows 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.
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.
NOTE:
After installing the module on your Windows-RT Designer computers, regenerate your custom Knowledge Scripts from your existing Windows-RT project files and check these Knowledge Scripts into the AppManager repository.
After installing the module or upgrading from a previous version of this module, you must restart the agent computer so that the Win-RT auto logon feature works properly.
For more information about installing this module, see the AppManager ResponseTime for Windows 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.
During the playback of scripts on Windows 8, Windows 2012, Windows 2012 R2, and Windows 10 computers, the desktop icons and the taskbar icons are not visible. When you playback scripts on Windows Server 8, Windows Server 2012, Windows 2012 R2, and Windows 10 (32-bit and 64-bit) computers, the scripts run but the desktop icons and the taskbar icons are not visible on the screen. To work around this issue, select the Run on default desktop option within Script Parameters of Win-RT Designer. (ENG331186 and DOC341833)
Player.exe does not update properly. If you do the remote deployment and the Player session is running during installation, the player.exe does not update properly. To work around this issue, before installing the module, stop any Player sessions that are running. (ENG287212)
Module script parameter with Is Input behavior does not display in AppManager. If you create a new module script parameter, designate the behavior as Is Input, and export this script as an AppManager Knowledge Script, the newly created parameter does not show up in the Knowledge Script parameters. To work around this issue, create the parameter within the main Win-RT7 Knowledge Script and the parameter shows up in the Knowledge Script parameters. (ENG274933)
Script that launches a non-existent process does not generate events. If you create a script that has a step to launch a non-existent process and run the script as a job, the script runs without errors and AppManager does not generate any error events for the non-existent process. (ENG318727)
Auto Layout button not available for 64-bit Windows computers. The Auto Layout button on the Start tab of the Ribbon only works for computers running 32-bit Windows operating systems and is not available for 64-bit Windows operating systems. (ENG295344)
Running Windows-RT in Conjunction with Web-RT. You can install AppManager ResponseTime for Windows and AppManager ResponseTime for Web, version 6.3 (and later), on a single computer. However, you cannot run Windows-RT Knowledge Scripts and Web Transaction scripts generated by the Web-RT Web Recorder extension simultaneously, because only one module can take ownership of the desktop at any given time. For more information on how to manage this situation, see the "Installation and Getting Started" chapter in the AppManager ResponseTime for Windows Management Guide. (ENG187738)
Failure to Import Security Manager Login Credentials. If the installation process fails to import login credentials into AppManager Security Manager, you must manually configure the information in Security Manager. For more information, see the "Post-Installation Configuration" topic in the AppManager ResponseTime for Windows Management Guide. (ENG221644)
Modified Windows Messages. Avoid products that modify the default behavior of Windows messages. Custom modifications of these message boxes may cause errors in the recording or playback of mouse actions and keystrokes.
Selecting My Computer in the Smart Recording Wizard results in an empty list. When browsing for an application during the Smart Recording Wizard, if you navigate to the My Computer directory, an empty list is displayed. You cannot select an application in this directory. To work around this issue, click the Look in list, the Up One Level button, or one of the other icons on the left-hand navigation menu to select another directory. (ENG246801)
This release of AppManager ResponseTime for Windows includes enhancements added in previous releases.
This release provided the following enhancements:
Support for Microsoft Windows 10 and Windows Server 2012 R2. This release supports Windows 10 and Windows Server 2012 R2. For more information, see the System Requirements.
Availability and Measurement data are not collected when you deselect the parameters in the Knowledge Script. With this release, when you deselect the create data options for the Availability and the Measurement parameters in the customized Knowledge Script, the data points are not collected.
Improved text recognition. With this release, the OCR capability of Windows-RT7 has improved significantly.
Create Analysis Center Data is merged with Data. With this release, the Create Analysis Center Data parameter for the customized Knowledge Script is removed and its functionality is merged with the Data parameters for generating the AC or NRC report.
Microsoft Visual C++ 2010 runtime support files are installed with the module. In the previous version, Microsoft Visual C++ 2010 runtime support files were pre-requisite for the module installation and required to be installed manually. With this release, the Microsoft Visual C++ 2010 runtime support files are provided with the module and installed automatically with the module.
This release resolved the following issues:
Win-RT OCR tools fail to recognize texts in Internet Explorer 11. The OCR Scanning tools were not able to recognize texts on a web page in Internet Explorer 11. With this release, the OCR tools recognize the texts in Internet Explorer 11. (ENG336862)
Win-RT auto logon feature does not work on a 64-bit operating system. The Win-RT auto logon failed on a 64-bit operating system. With this release, the auto logon works successfully on a 64-bit operating system. (ENG325043 and ENG319477)
Win-RT service stops when you open a screen shot. The Win-RT service crashed while trying to access a screen shot. With this release, you can open a screen shot without the service crashing. (ENG337170 and ENG336516)
Win-RT auto logon feature does not work after reboot. The Win-RT auto logon failed after reboot because the Legal Notice and the CTRL + ALT + DELETE screens were enabled. With this release, you can use the TakeDesktopOwnership Knowledge Script to disable the Legal Notice and the CTRL + ALT + DELETE screens so that the Win-RT auto logon works properly. (ENG325699)
Win-RT OCR features do not work on Citrix XenServer. The Win-RT OCR features did not work on Citrix XenServer. With this release, the Win-RT OCR features work properly on Citrix XenServer. (ENG341807)
This release provided the following enhancement:
Support for Microsoft Windows versions 2012, Windows 8, and Windows Vista with SP2 (32-bit and 64-bit). This release now supports Microsoft Windows 2012, Windows 8, and Windows Vista with SP2 (32-bit and 64-bit).
This release provided the following enhancement:
Support for Microsoft Windows versions 2008, 2008 R2 and Windows 7. This release now supports Microsoft Windows Server 2008, Windows Server 2008 R2, and Windows 7.
This release resolved the following issue:
Wait for Window scriptstep corrupts the Window Caption value if the target window has special characters in the caption. This release resolves an issue in which the Target Window parameter displayed a corrupted value in the Window Caption if you used the Wait for Window step while recording a Win-RT7 transition and the script was then run. The script displayed the corrupted caption only when the window selected in the Target Window field had a special character, such as "@" in the Window Caption. With this release, Window Captions that contain special characters display properly after the Wait for Window scriptstep. (ENG250996)
Win-RT7 script is not able to compare a numeric value beyond 1000. This release resolves an issue in which a Win-RT7 script could not compare the Screen Resolution parameter in the System Information step from the Windows Category with a constant value in the decision step from the Script Flow category. The maximum Constant Value that you could specify was 1000. With this release, you can specify a Constant Value beyond 1000. (ENG274039)
Module script is not able to collect all metrics. This release resolves an issue where a module script exported from the Win-RT7 Designer and run as AppManager job did not collect all the metrics if the data stream names for availability and response time were identical. With this release, the script collects the data streams even when the names are identical. (ENG271400)
Win-RT7 Designer playback fails to display the "{" character inserted by using the Keys scriptstep. This release resolves an issue where the Win-RT7 Designer playback failed if the Input Text inserted using the Keys script step contained the "{" character and the remaining text following that character was truncated. With this release, the Input Text containing the "{" character is handled properly during playback. (ENG274041)
The Decision scriptstep does not compare the value from the Output Text parameter of the OCR scriptstep correctly. This release resolves an issue where the Decision scriptstep displayed incorrect results during the numeric comparison of a value when compared with the output of the Output Text parameter of OCR scriptstep because the datatype of output of the OCR is a string. With this release, the output of the Output Text parameter is handled properly and the Decision scriptstep compares the numeric value correctly. (ENG287682)
Win-RT7 Knowledge Scripts sometimes collect negative values. This release resolves an issue where a Win-RT7 script sometimes collected negative values if you ran the scripts run on an Agent with multi-core processors. With this release, Win-RT7 scripts do not collect negative values even when run on an agent with multi-core processors. (ENG316624)
Win-RT auto logon feature does not use the modified credentials to unlock a computer. This release resolves an issue where the Win-RT auto logon feature used the previous credentials to log on to a computer when the credentials were modified in Security Manager. With this release, you specify that the module caches the Security Manager credentials, or you can trigger the resolution of the credentials each time the script is executed. You can configure this feature by selecting either True or False for the CacheCredentials field in Win-RT configuration file. (ENG323675)
Win-RT7 script, when run as AppManager job, fails if the script involves launching the Citrix ICA Client. This release resolves an issue where a Win-RT7 script, when run as an AppManager job, failed to launch the Citrix ICA Client because the script tried to playback on a new desktop. With this release, the Win-RT Designer includes an option to play back the Win-RT7 script on the default desktop or session, successfully launching the Citrix Client when you run the script as an AppManager job. (ENG315141 and ENG317440)
This release resolved the following issue:
Selecting and moving multiple objects causes console to fail. Before you install this release, the Designer console fails when the zoom-out option is selected and you attempt to select, and then move, multiple scriptsteps at one time. After you install this release, you can select and move multiple scriptsteps while in zoom-out mode without causing the console to fail. (ENG275287)
Citrix Network Neighborhood icon remains in system tray after playback transaction. Before you install this release, the Citrix Network Neighborhood icon remains in the system tray after the playback transaction function. With each playback transaction, another application icon remains in the system tray. After you install this release, the application icon is removed from the system tray during each playback transaction function. (ENG276748)
Script execution fails. Before you install this release, Win-RT7 Knowledge Script jobs fail and block subsequent iterations of the jobs. The failure event contains the following message: Error (-2146233087): Error executing worker Iteration 3. Waiting for script execution finished failed. The failures occur when a Knowledge Script job completes its execution but remains running, even if the job is scheduled to run only once. After you install this release, a code change allows the Knowledge Scripts jobs to end correctly. (ENG278641)
Player installed with incorrect lock parameter. Before you install this release, the Windows-RT7 Player is installed with a -locking parameter, which is supposed to launch the Player in lock mode, but does not because the parameter uses incorrect syntax. After you install this release, the Player is installed in unlocked mode. For information about methods of changing the Player to locked mode, see the "Locking the Windows-RT Player" topic in the AppManager ResponseTime for Windows Management Guide, included in the download package. (ENG280793)
Script will not run on a Windows XP computer that has been locked. Before you install this release, Win-RT7 Knowledge Script jobs will not run on computers that have been locked, even though the appropriate account login information is configured in AppManager Security Manager. This problem occurs if the script attempts to access and unlock a target computer using Microsoft Remote Desktop Protocol (RDP). A description of the workaround for this problem has been added to the “Troubleshooting Windows-RT” topic in the AppManager ResponseTime for Windows Management Guide, included in the download package. (ENG279886, DOC283735)
This release resolved the following issues:
Windows-RT Knowledge Script events do not launch associated actions. Before you install this release, Windows-RT events do not launch associated Action scripts. After you install this release, a correction to the Windows-RT template and to the included Knowledge Scripts allows associated actions to be launched when Windows-RT events are raised. (ENG260389)
No Help for Discovery_Win-RT7 Knowledge Script. Before you install this release, no online Help is available for the Discovery_Win-RT7 Knowledge Script when you click Help or press F1. After you install this release, Help is available by both methods. (DOC262915)
This release resolved the following issues:
Unintentional memory consumption when using the Windows-RT Designer. Before you install this release, the Windows-RT Designer might consume too much memory, a situation also known as a “memory leak,” which could lead to the Designer closing prematurely. After you install this release, you will not experience excessive memory consumption when using the Designer. (ENG254420)
Running a script a second time might cause the script to fail if the Use Windows Explorer option is not selected. Before you install this release, if a script does not have the Use Windows Explorer option selected, and you already have a Windows Explorer window open, the script fails the next time you run it. After you install this release, the script no longer fails in this situation. (ENG251907)
Windows-RT Designer becomes unavailable when defining a relative location or using a relational rectangle. Before you install this release, you might encounter a locked screen if you are defining a screen position or screen region parameter using the relative location option or the relational rectangle. Your screen might lock up if you move the point square (the square at the tip of the arrow) to the edge of the screen and change the size of the root square (the square at the base of the arrow). After you install this release, the Designer no longer stops functioning, and you can return to the Designer after defining your relative location parameters. (ENG244821)
An exported script or module script title is lost when you import the script later. Before you install this release, if you export a script or module script using the Win-RT Designer, and then import that script with the Designer on a different computer, the Designer does not include the title of the script. After you install this release, the title of an exported script is retained by the Designer when you import that script later. (ENG257842)
The umlaut character is lost when a saved project is reopened. Before you install this release, if you type a letter with an umlaut, such as ä, in a scriptstep parameter in the Windows-RT Designer, the umlaut character is replaced with a strange character after you save and close the project. After you install this release, the umlaut displays properly in the Designer even after you close and reopen the project. (ENG256274)
This release also included the following enhancements:
A new descriptive parameter was added to three scriptsteps. In the Windows-RT Designer, the Availability, Measurement, and Start Timer scriptsteps include a new, required parameter entitled Parameter Description. The text of this scriptstep parameter will display in AppManager on the Properties tab of the Knowledge Script that you generated from this Windows-RT script. If you use one of these three scriptsteps, you must complete the Parameter Description value on the Parameters pane to make the scriptstep valid. (ENG257655)
The WebServerPort value is now 8080. The value for the port used for the Web server was 80 in previous releases, but in this release, the value is now 8080 to avoid interference with other services and applications.
This release provided the following enhancements:
Windows-RT helps you monitor your organization’s Windows infrastructure to ensure the availability and performance of critical applications and services on a Microsoft Windows computer.
Using the Windows-RT Designer, you create custom Knowledge Scripts that can be used with AppManager to identify problems a user might encounter when accessing an application.
You can measure the response time and availability of your Windows applications, which you can use to manage the performance of a particular Windows computer.
The results you get from response-time testing with Windows-RT are extremely accurate, because AppManager is timing a transaction that acts just like a real transaction from the monitored computer.
This release also provided support for AppManager licensing. Windows-RT licenses are counted based on the number of installed Windows-RT Player or service components, or per discovered Windows-RT managed objects.
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.