AppManager for Windows Terminal Server allows you to manage and monitor the various sessions hosted by the Windows Terminal Server and to monitor the CPU and memory usage for those sessions.
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 for Windows Terminal Server provides the following enhancement:
Support for Microsoft Windows Server 2012 R2. This release supports Windows Server 2012 R2. For more information, see the System Requirements.
This release of AppManager for Windows Terminal 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 Windows Terminal Server has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Windows terminal servers you want to monitor (agents), and on all console computers |
7.0 or later 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 Windows operating system on the agent computers |
One of the following:
NOTE: On Windows Server 2008 R2 and later, Windows Terminal Server is known as Remote Desktop Server. |
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the Windows terminal servers computers you want to monitor (agents), and on all console computers |
7.6.170.0 or later |
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Windows Terminal Server Management Guide, included in the download package.
AppManager for Windows Terminal Server includes a managed object, qwtsa4.dll, and Knowledge Scripts to discover and monitor Windows Terminal Server resources. The download package includes these release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-WTS-7.1.36.0.msi, the module installer.
AM70-WTS-7.1.36.0.ini, a configuration file used with the AppManager setup program.
AM70-WTS-7.1.36.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-WTS-7.1.36.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckWTS.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 terminal 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.
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 Windows Terminal Server 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.
Few Knowledge Scripts are not supported on Windows Server 2012 and Windows Server 2012 R2. On Windows Server 2012 and Windows Server 2012 R2, the following Knowledge Scripts are not supported because the associated object counters are not available: (ENG341161)
SessionsTotalBytes
SessionsTotalErrors
SessionsTotalFrames
SessionsTotalProtocolHitRatio
Remote deployment fails on Microsoft Windows Server 2012 computers. When you remotely deploy this module to a computer running Windows Server 2012, AppManager displays the following error: Unknown operating system detected for machine IPAddress. To work around this issue, install this module manually. (ENG319069)
The WTS_Messenger Knowledge Script generates a "Send message failed" error when you run it on a Windows Server 2012 computer. The WTS_Messenger script is not supported on Windows Server 2012. (ENG323271)
Some Knowledge Scripts always return data points with values of zero (0) for Windows 2008 Service Pack 1 and later. Computers with Windows Server 2008 Service Pack 1 and later always provides zero (0) for the associated performance counters for the following Knowledge Scripts: (ENG290957)
SessionsTimeout
SessionsTotalErrors
SessionsTotalProtocolHitRatio
The SessionsReset Knowledge Script does not work with 64-bit Windows Server 2003. Running the SessionsReset Knowledge Script on a 64-bit Windows Server 2003 computer results in an error message stating that the commands associated with the SessionsReset job are not recognized. (ENG265210)
This release of AppManager for Windows Terminal Server includes enhancements added in previous releases.
This release provided the following enhancement:
Support for the most recent Microsoft Windows operating systems. This release now supports the following versions of Windows:
Windows Server 2012
Windows 8 (32-bit and 64-bit)
Windows Server 2008 R2
Windows Server 2008 (32-bit and 64-bit)
Windows Server 2003 (32-bit and 64-bit)
This release added support for Windows Server 2003 Service Pack 1 Terminal Services.
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.