AppManager for Microsoft Internet Information Services 7.4.0.1 Release Notes

Date Published: December 2018

AppManager for Microsoft Internet Information Services allows you to monitor the availability and performance of Microsoft Internet Information Services (IIS). AppManager for Microsoft IIS looks for IIS messages in event logs and monitors IIS resource consumption, including CPU and memory utilization, to ensure your Web server functions properly.

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 Web site 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 Web site.

1.0 What’s New?

This release of AppManager for Microsoft Internet Information Services provides the following enhancements:

  • Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft Internet Information Services provides support for TLS 1.2.

  • IIS deployment supports .NET Framework 4.5: This release of AppManager for Microsoft Internet Information Services changes the prerequisite logic to support deployment of IIS with .NET Framework 4.5. (ENG347605)

This release of AppManager for Microsoft Internet Information Services resolves the following issues:

  • CPU utilization of process crosses threshold limit: CPU utilization crosses the permitted threshold limits due to Knowledge Script logic not considering number of CPU processes. This release of Microsoft Internet Information Services resolves this issue. (ENG342381)

  • IIS_SSLCertMon: ReportAM_DetailData cannot report on data from this KS: This release of AppManager for Microsoft Internet Information Services does changes in ReportAM_DetailData KS, which resolves this issue. (ENG343944)

  • Deselected nodes show event for IIS_ApplicationPool jobs: This release of AppManager for Microsoft Internet Information Services resolves this issue by doing code changes in managed object. (ENG346636)

  • SSLCertMon KS is having constant severity which cannot be customized: This release of AppManager for Microsoft Internet Information Services includes changes in Knowledge Script to support customized severity information, which resolves the issue. (ENG342357)

  • IIS_HealthCheck: Job eventing on disabled aspnet_state service: HealthCheck generates events for IIS services, which have startup type as Manual and current status as not running. With this release of AppManager for Microsoft Internet Information Services, changes are made to generate events for IIS services if the startup type is Automatic or Automatic (Delayed start). (ENG343337)

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 Internet Information Services replaces all Previous Releases.

2.0 System Requirements

AppManager for Microsoft IIS has the following system requirements:

Software/Hardware

Version

NetIQ AppManager installed on the AppManager repository (QDB) computers, on the IIS 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:

  • AppManager agent 7.0.4 with hotfix 72616 or later

  • AppManager agent 8.0.3, 8.2, 9.1, 9.2, 9.5, or later

Combination of IIS and Microsoft Windows operating system on the agent computers

One of the following:

  • IIS 10.0 on Windows Server 2016

  • IIS 8.5 on Windows Server 2012 R2

  • IIS 8.0 on Windows Server 2012

  • IIS 7.5 on Windows 7 (32-bit or 64-bit)

  • IIS 7.5 on Windows Server 2008 R2

  • IIS 7.0 on Windows Server 2008 (32-bit or 64-bit)

  • IIS 6.0 on Windows Server 2003 R2 (32-bit or 64-bit)

Microsoft .NET Framework on the agent computers

One of the following:

  • Microsoft .NET Framework 4.5 with IIS 10.0

  • Microsoft .NET Framework 3.5 with IIS 8.5

  • Microsoft .NET Framework 3.5 with IIS 8.0

  • Microsoft .NET Framework 2.0, 3.0, or 3.5 with IIS 7.5

  • Microsoft .NET Framework 2.0, 3.0, or 3.5 with IIS 7.0

  • Microsoft .NET Framework 2.0, 3.0, or 3.5 with IIS 6.0

AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the IIS computers you want to monitor (agents), and on all console computers

Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page.

Microsoft Log Parser on the agent computers

2.2

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.

NOTE:

  • Because Microsoft removed NNTP features from IIS 8.0, IIS 7.5, and IIS 7.0, the IIS_NNTP Knowledge Scripts do not work in environments running those versions of IIS.

  • Because IIS 8.0, IIS 7.5, and IIS 7.0 use SMTP features from IIS 6.0, without IIS 6.0 compatibility enabled, the IIS_SMTP Knowledge Scripts does not work in environments running those versions of IIS.

  • Because IIS 7.0 uses UDDI features from IIS 6.0, without IIS 6.0 compatibility enabled, the IIS_UDDI Knowledge Scripts does not work in environments running those versions of IIS.

  • All Web applications must be properly registered with the correct version of .NET. If you encounter problems monitoring Web applications, use an IIS registration tool such as aspnet_regiis to ensure the applications are properly registered.

For more information on hardware requirements and supported operating systems and browsers, see the Microsoft Internet Information Services 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.

3.0 Contents of the Download Package

Microsoft Internet Information Services includes a managed object, qIISa4.dll, and Knowledge Scripts to discover and monitor Microsoft Internet Information Services resources. The download package includes this Release Notes, a Management Guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-IIS-7.4.72.0.msi, the module installer.

  • AM70-IIS-7.4.72.0.ini, a configuration file used with the AppManager setup program.

  • AM70-IIS-7.4.72.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-IIS-7.4.72.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

  • ckIIS.exe, the pre-installation check used with the AppManager setup program.

  • DefaultRule_IIS.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.

4.0 Installing This Module

Run the module installer to install the module components in the following locations:

  • On the Internet Information Services 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 Microsoft Internet Information Services Management Guide, included in the download package.

5.0 Known Issues

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.

  • 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 prevent this issue, install AppManager Hotfix 7011602 for Control Center, available at the AppManager Suite Hotfixes page. If you do not want to upgrade AppManager, you can work around this issue by installing this module manually. (ENG319069)

  • Running jobs do not upgrade properly. When you upgrade running Knowledge Script jobs, many jobs do not upgrade properly. Some HTTP-related jobs, some ASPNET-related jobs, and all IIS_ApplicationPools jobs fail and stop running completely. IIS_FTPfiles and IIS_HealthCheck report errors during their first and second iterations, but run correctly after the second iteration. (ENG316647)

  • Microsoft Log Parser no longer supported on Windows Server 2008. The CentralizedBinaryLogging Knowledge Script requires the use of Microsoft Log Parser, which Microsoft does not support for Windows Server 2008. Despite the lack of support by Microsoft, the CentralizedBinaryLogging script will still run properly on Windows Server 2008. (DOC258710)

  • Knowledge Scripts that depend on IIS 6.0 compatibility do not work properly when you turn off compatibility. Turning off IIS 6.0 compatibility affects all Knowledge Scripts with the IIS_SMTP prefix, as well as the UDDIConnections script. The jobs for the SMTP and UDDI scripts will then generate the Counter unavailable events. (ENG288210)

  • The set of IIS_NNTP Knowledge Scripts do not work with IIS 8.0, IIS 7.5, and IIS 7.0 environments. NNTP (Network News Transfer Protocol) is no longer part of Internet Information Services 8.0, 7.5, and 7.0, and it is not available in Windows Server 2008, Windows Server 2008 R2, Windows 7, and Windows Server 2012. As a result, the set of IIS_NNTP Knowledge Scripts in this module do not work on Windows Server 2008, Windows 7, and Windows Server 2012. (DOC257403)

  • The ASP Errors/Sec and Requests/Sec performance counters are not reset when the WWW Publishing Service restarts. This can cause the ASPRequestError and ASPThroughput Knowledge Scripts to return erroneous data and raise false events when you restart the WWW Publishing Service. (ENG133686)

  • AppManager for Microsoft IIS cannot monitor Web sites whose names contain commas (for example, NewYork,Main Site). Knowledge Scripts cannot distinguish commas that are part of an object name from commas that have been inserted by the infrastructure (that is, passed in as a Knowledge Script parameter) to delimit a list of object names. (ENG109326)

  • AppManager for Microsoft IIS sometimes returns a Counter unavailable error. Possible causes for the Counter unavailable error include:

    • The extensible performance DLL may be marked as disabled. You can re-enable the object by modifying the Disable Performance Counters registry value in the Performance subkey of the supported service for the extension. For more information, see Microsoft Knowledge Base Article KB24899.

    • On Windows Server 2003, sometimes any counters that follow the NNTP Service in an alphabetical listing cannot be accessed. Stopping the NNTP Service corrects this problem.

    • Counters accessed by the ASPNET set of Knowledge Scripts will not be available if:

      • the .NET Framework is not installed, or

      • there are no worker processes running.

6.0 Previous Releases

This release of AppManager for Microsoft Internet Information Services includes enhancements added in previous releases.

6.1 Release 7.4, November 2015

This release of AppManager for Microsoft Internet Information Services provided the following enhancements:

  • Support for IIS version 8.5. This release now supports the monitoring of computers running IIS version 8.5. For more information, see the System Requirements.

  • Support for Windows Server 2012 R2. This release now supports computers running Microsoft Windows Server 2012 R2. For more information, see the System Requirements.

  • IIS_HealthCheck monitors dynamic Web site activation threshold. With this release, the IIS_HealthCheck Knowledge Script raises an event if the number of configured Web sites are less than or equal to the dynamicRegistrationThreshold value.

  • Support for the RECOMMENDED_IIS Knowledge Script Group. This release now supports recommended Knowledge Script Group that includes:

    • IIS_ApplicationPools

    • IIS_ASPEventLog

    • IIS_ASPNETReqStat

    • IIS_ASPReqStat

    • IIS_ASPThroughput

    • IIS_CacheHitRatio

    • IIS_CpuHigh

    • IIS_FTPTransStat

    • IIS_HealthCheck

    • IIS_HTTPRequests

    • IIS_HTTPStatistics

    • IIS_HTTPTransStat

    • IIS_Log

    • IIS_MemoryHigh

This release of AppManager for Microsoft Internet Information Services resolved the following issues:

  • IIS 6.0 discovery fails on Windows Server 2003. This release resolves an issue in which IIS 6.0 failed to discover on Windows Server 2003 Service Pack 2 because of .NET Framework incompatibility. With this release, an update to the Pre-installer checks for the required version of .NET Framework and IIS discovery is successful if .NET Framework 2.0 or 3.5 is available. (ENG331590)

  • Unable to set the event severity in IIS_SSLCertMon for an unavailable valid SSL certificate. This release resolves an issue in which the event severity for an unavailable SSL certificate in the IIS_SSLCertMon Knowledge Script could not be set manually. With this release, a parameter is added that allows you to set the event severity when a valid SSL certificate is not available. (ENG334163)

  • IIS_HTTPStatistics fail to monitor total number of connections to a server. This release resolves an issue in which the IIS_HTTPStatistics Knowledge Script failed to monitor the total number of connection to a server. With this release, the Knowledge Script monitors the total number of Web site connections to a server from all anonymous and non-anonymous (user) accounts. (ENG299923)

6.2 Release 7.3.154.0, May 2013

This release of AppManager for Microsoft Internet Information Services resolved the following issue:

  • IIS_Log Knowledge Script job creates temporary files in the System directory and does not properly remove them. This release resolves an issue in which the IIS_Log job created .evt and .dat temporary files in the \Windows\System32 directory and never deleted these files, some of which had the potential to grow to over one GB in size. With this release, the .evt files are now saved as .log files to prevent confusion with the Microsoft Event Viewer files for Windows. The IIS_Log job stores the .log and .dat temporary files in the \NetIQ\Temp\ folder and deletes these files on a regular basis. (ENG327688)

6.3 Release 7.3.145.0, December 2012

This release of Microsoft Internet Information Services provided the following enhancement:

  • Support for Windows Server 2012. This release now supports computers running Microsoft Windows Server 2012. For more information, see the System Requirements.

This release also resolved the following issues:

  • Knowledge Script jobs consume too much memory. This release resolves memory leak issues in Knowledge Script jobs. With this release, the jobs use the appropriate amount of memory. (ENG304991, ENG292506, ENG313951)

  • Discovery fails in environments with numerous application pools. This release resolves an issue in which the Discovery_IIS Knowledge Script failed with the error Unable to bind IIS module in environments with many, usually more than 20, application pools. With this release, discovery completes successfully. (ENG309577)

6.4 Release 7.3.98.0, March 2011

This release of Microsoft Internet Information Services resolved the following issue:

  • The ApplicationPools Knowledge Script failed to raise an event if a monitored application pool is down or stopped. This release resolves an issue in which the ApplicationPools script reported that it is successfully retrieving data from a monitored application pool that is no longer running. With this release, the ApplicationPools Knowledge Script generates an event when the application pool being monitored is unavailable. (ENG301658)

6.5 Release 7.3.91.0, August 2010

This release of AppManager for Microsoft IIS provided the following enhancements:

  • Support for IIS version 7.5. This release provides support for the monitoring of computers running IIS version 7.5.

  • Support for IIS version 7.0 without 6.0 compatibility mode. This release provides support for the monitoring of computers running IIS version 7.0 without requiring IIS 6.0 compatibility mode.

  • Support for FTP 7.5. This module provides support for monitoring FTP 7.5 on computers running IIS version 7.0 or 7.5.

  • Knowledge Script updates to reflect changes in compatibility mode requirements. The following Knowledge Scripts were updated to support IIS 7.0 without requiring 6.0 compatibility mode:

    • IIS_ApplicationPools

    • IIS_CentralizedBinaryLogging

    • IIS_HealthCheck

    • IIS_IsolatedApps

    • IIS_Log

    • IIS_SSLCertMon

    • IIS_UnloadApps

    • IIS_WebServiceExtensions

    • Discovery_IIS

  • Knowledge Script updates to reflect changes to support the most recent releases of IIS. The following Knowledge Scripts were updated to support IIS 7.0 and IIS 7.5:

    • AMADMIN_IISRestartServer

    • AMADMIN_IISRestartSite

    • Action_IISRestartServer

    • Action_IISRestartSite

6.6 Release 7.2.53.0, October 2009

This release provided the following enhancements:

  • AppManager agent (NetIQmc) fails on Windows Server 2008. Before you install this release, the NetIQ AppManager Client Resource Monitor service, NetIQmc, fails during the auto-discovery portion of installing the AppManager for IIS module. After you install this release, a code change corrects a buffer problem and prevents the agent service from failing during auto-discovery. (ENG274362)

6.7 Release 7.2.47.0, January 2009

This release provided the following enhancements:

  • Support for IIS version 7.0 on Microsoft Windows Server 2008. This release supports the monitoring of computers running IIS version 7.0 on Microsoft Windows Server 2008, including computers running 64-bit operating systems.

  • Updated version of the CAPICOM.dll file. This release contains an updated version of the CAPICOM.dll file, which can be used to digitally sign data, sign code, verify digital signatures, envelop data for privacy, hash data, and encrypt or decrypt data.

6.8 Release 7.1, September 2008

This release provided the following updates:

  • Support for IIS version 6.0. This release adds support for IIS version 6.0 on 64-bit Microsoft Windows operating system.

  • Support for IPv6. This release adds support for Internet Protocol version 6 (IPv6). AppManager for Microsoft IIS recognizes and displays IPv6 addresses in the Operator Console and Control Center Console.

6.9 Release 6.3, December 2006

This release provided the following updates:

  • Support for IIS versions 5.0, 5.1, 6.0, and future versions, including service packs and patches.

  • Support for IIS 6.0 on 64-bit Microsoft Windows Server 2003 operating systems.

  • Introduction of new Secure Sockets Layer (SSL) Certificate Monitoring Knowledge Script to identify and monitor expiration dates of SSL certificates running on Web servers.

  • Introduction of new Application Pools Knowledge Script to monitor application pools that have their own set of server resources.

  • Introduction of new Enterprise UDDI (Universal Description, Discovery, and Integration) Knowledge Script to discover and reuse Web services and other programmatic resources, to build and deploy extensible and reliable applications.

  • Introduction of new Centralized Binary Logging Knowledge Script to scan the IIS centralized binary logging file for information based on a list of filter criteria.

  • Introduction of new Web Service Extensions Knowledge Script to extract the Web service extensions listed on the IIS servers and their status.

  • Consolidation of existing Knowledge Scripts with similar functionality into single scripts for ease of use and enhancements in the future. For example, ASPReqStat is a consolidation of the ASPRequestError, ASPRequestFailed, and ASPSessionTimeout Knowledge Scripts.

7.0 Contact Information

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 Web site.

For general corporate and product information, see the NetIQ Corporate Web site.

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.