iis (IIS Server Monitoring) Release Notes

The probe allows you to perform the following activities on the IIS server:
The IIS Server Monitoring (iis) probe monitors the health and status of Microsoft IIS servers. The probe performs HTTP GET queries to the selected Microsoft IIS servers. These values are then used to generate QoS and alarms. You can use this probe for both local and remote monitoring.
The probe allows you to perform the following activities on the IIS server:
  • Monitor IIS http response times
  • Support a DLL add-on for server-side monitoring of individual requested resources, and displays running and statistical data
  • Display non-responsive IIS scripts
  • Deliver system-related and server-related performance data
  • Support custom OS monitoring objects
  • Deliver server-side status data when installed to the IIS server
  • Monitor application pools
Revision History
This section describes the history of the revisions for this probe.
Support case(s) may not be viewable to all customers.
What's New
  • (May 2021) Provided support for Windows 2019.
  • (October 2018) New MCS template (iis_mcs_template v1.91) with support for profile migration from legacy (non-enhanced) MCS templates to enhanced profiles. For more information, see Migrating and converting existing profiles.
  • Added the log size feature.
  • Enhanced documentation about the IIS server configuration.
  • (June 2018)
    New MCS template (iis_mcs_template 1.91) with:
    • Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile. For more information, see Configuring Alarm Thresholds in MCS.
  • (April 2019)
    The iis MCS (version 1.92 onwards) has been updated as part of addressing the common vulnerabilities and exposures by updating the jackson-databind libraries. For more information and CVE numbers, see Addressing Jackson Vulnerabilities.
Fixed Defect:
  • (September 2018)
    The probe reported incorrect Total CPU metric when compared with the Total CPU metric reported by the cdm probe running on the same robot.
    Support Case: 01148104
    To resolve this issue, follow these steps:
    1. Navigate to the
      Raw Configure
      interface >
    2. Add a new key
      and specify its value as
    3. Save the configuration and restart the iis probe.
October 2017
What's New:
  • Added support to monitor the SSL verification status of the host.
  • Added support to include $profilename in the suppression key for the following counters and alarm:
    • Counters:
      • HTTP Response Time
      • HTTP Response Value
      • IIS max Request Time
      • SSL Host Verification Status
    • Alarm
      • Host Availability
    For more information, see
    Upgrade Considerations
July 2016
Fixed Defects:
  • The probe now displays the correct website status under
    Default Website
    , on the probe GUI.
  • The probe displayed 0 values for the
    Application Pool Memory
    Application Pool CPU
    counters. You must upgrade the perfmon probe to version 1.63 to fix the issue.
    Support case number 299212
  • When opening the
    profile, the probe displayed an incorrect dialog.
    Support case number 293849
May 2016
Fixed Defect:
  • The
    IIS Status value
    monitor displayed the default website state (as listed on IIS server), instead of the service state of the IIS Server.
April 2016
What's New:
  • Added new counters for ASP and webservices monitors.
  • Added support for IIS Server version 8.5.
  • Added support for HTTPS.
March 2016
What's New
  • The probe can be migrated to standard static thresholds using the threshold_migrator probe.
  • Added a new device ID key (useRobotDevIDForLocalhost). This key can be set as
    to migrate the probe to standard static thresholds. This option is available only through Raw Configuration GUI to monitor local IIS servers. The value of this key is
    by default.
    Refer to Set Device ID Key Using Raw Configure section in v1.7 iis AC Configuration for the impact of setting this key value.
June 2015
What's New
  • Added support for monitoring application pools. Perfmon 1.53 or later is required for this functionality.
    The Application Pool monitoring feature is applicable for IIS 7.0 or later.
June 2014
  • Added 64 bit support.
November 2013
  • Added Probe Defaults for remote servers also.
June 2013
  • Implemented Probe defaults, which works only when the probe is deployed on IIS server machine.
  • Updated copyright information.
February 2013
  • Fixed issue of run time GUI crash while uncheck monitoring of checkpoint.
January 2013
  • SOC Support Added
December 2011
  • Added support for "IIS Status Value"; having multiple IPs on the host
August 2011
  • Added support of filterport on per-host basis
  • Added support to define the severity of alerts
  • Added support for IIS7.5
  • Removed printing password from log file
  • Added support for reading alarm tokens from cfg
December 2010
  • Added support for internationalization
October 2010
  • Fixed memory management issue
October 2010
  • Changes to libraries with respect to configuration locking.
October 2010
  • Made changes to libraries with respect to configuration locking.
June 2010
  • Added support for extended NIS database information.
March 2010
  • Fixed Server data (requests) not shown after adding ISAPI Filter
  • Fixed potential probe crashing issues
  • Fixed initialization of curl library
  • Fixed initialization of variables
September 2009
  • Collect data also when perfmon is not available.
  • Updated status of host in GUI when IIS server is not reachable.
  • Updated logging.
  • Removed limitation on portnumber in the isapi filter.
September 2008
  • QoS and Alarm source for 'localhost' profiles changed to actual host name.
  • Monitoring interval defaults to profile interval instead of global probe interval.
  • Changed QoS series name for disk and memory usage because of inconsistencies with QoS data supplied by the 'cdm' probe.
  • Server side DLL add on now available for 64 bits versions of Windows. IIS6 no longer need to be run in IIS 5.0 isolation mode.
  • The DLL is now available for 32 and 64 bits versions of Windows Vista, with IIS7.
January 2008
  • Added keyword 'localhost' for hostname, will cause performance collection without authentication.
  • Added possibility of setting IIS filter port number in cfg file.
  • Added support for all custom performance objects
  • Changed key separator from . to ,
  • Feature: Http server authentication added.
  • Fix: Removed ptPerfmonInstances call.
  • QoS definition fix (IIS)
July 2007
Initial version
October 2006
Threshold Configuration Migration
The probe (version 1.71 and later) threshold configurations can be migrated to standard static alarm thresholds using the threshold_migrator 2.10 version or later with CA UIM 8.31 or later.
The changes in the probe after migration are:
  • The Infrastructure Manager (IM) GUI of the probe will not be available and the probe can be configured using Admin Console (AC).
  • Probe specific alarm configurations in the probe monitors is replaced by Static alarm, Time To Threshold, and Time Over Threshold configurations.
  • The variable syntax changes from
  • The baseline_engine probe sends the alarms.
To migrate the probe to standard static thresholds for local IIS servers using the threshold_migrator
probe, you must set the device ID key, useRobotDevIDForLocalhost to yes from the Raw Configuration interface.
Probe Specific Hardware Requirements
The iis probe must be installed on systems with the following minimum resources:
  • Memory: 2-4 GB of RAM. The OOB configuration of the probe requires 256 MB of RAM.
  • CPU: 3 GHz dual-core processor, 32-bit or 64-bit.
Probe Specific Software Requirements
The iis probe requires the following software environment:
  • CA Unified Infrastructure Management 8.0 or later
  • Robot 7.62 or later (recommended)
  • Java JRE 6 or later (required for Admin Console)
  • Performance Collector probe (perfmon) 1.18 or later
    : To monitor application pool counters, you must use perfmon probe version 1.53 or later.
  • IIS 7.x (Windows 2008 R2), IIS 8.x (Windows 2012 R2), IIS V 1.90 (Windows 2016)
The iis probe requires the following software environment to migrate with threshold migrator probe:
  • CA Unified Infrastructure Management 8.3 or later
  • Robot 7.62 or later (recommended)
  • Java JRE version 7 or later (required for Admin Console)
  • Probe Provisioning Manager (PPM) probe version 3.21 or later
  • baseline_engine (Baseline Engine) version 2.60 or later
Installation Notes
Consider the following points to install the probe:
  • Provide administrator access to the probe in Admin Console by using the
    Settings > Probe Security
    Alternatively, use the
    Security > Probe Administration
    option in the Infrastructure Manager.
  • Restart the perfmon probe after installing or upgrading the iis probe.
  • Use the 'localhost' as the hostname to monitor the local IIS server to skip the performance authentication.
  • Ensure that remote registry is enabled on the IIS server for remote monitoring.
Installation Notes for IISRequest.dll
The IISRequest.dll is an ISAPI filter add-on for the IIS server and used by the probe. This add-on supports several versions of the IIS server and operating systems. You can go through the readme.txt file at the
<CA UIM Installation Directory>/Nimsoft/Applications/iis
location for supported versions and additional information about how to add this functionality.
Install ISAPI filter on a 64-bit OS
If the IIS server is running on a 64-bit version of Windows, the IISRequestNM64.dll or IISRequest64.dll library file is used. You must have the Microsoft Visual C++ 2005 Redistributable Package on the system with the IIS server. You can download this Microsoft Visual C++ 2005 Redistributable Package from the following link:
To execute the dll files, disable the following setting on the IIS server available in Advanced Settings for the Application Pool:
Enable 32-bit Applications
Activate the ASP Counters on IIS 7 or above
To use the
element, you must install the ISAPI Filters module on version 7 and later. For more information about installing the component, see http://www.iis.net/ConfigReference/system.webServer/isapiFilters
Install Metabase Compatibility Component on IIS 7 or above
The probe displays a wrong status when monitoring local IIS 7 server. To display correct status, the probe requires the Metabase Compatibility component, which is not available on IIS 7, by default. For more information about installing this component, see http://www.iis.net/learn/manage/managing-your-configuration-settings/metabase-compatibility-with-iis-7-and-above.
Installation Procedure
Perform the following steps for installing the probe:
  1. Deploy the iis probe.
  2. Restart the perfmon probe if you are upgrading the iis probe.
  3. To resolve the authentication problems for the iis probe that runs locally on the IIS server system, you can use 'localhost' as the profile hostname to skip performance authentication.
  4. For remote monitoring, ensure that the remote registry is enabled on the IIS server.
Configure IISRequest.cfg
Follow these steps:
  1. Navigate to
    folder and edit the IISRequest.cfg file.
  2. Ensure the following:
    • The first line is the host name of the computer where the IIS Server Monitoring probe is running (probe machine).
    • The second line is the host name of the IIS server computer (IIS server machine).
      The host name that you define must match with the host name or IP address that you provide while creating the probe profile.
    • The port number is in the last line, by default it is 999. This port number is used for communication between the IIS Request filter on the IIS Server and the probe.
  3. Save and close the file.
  4. Restart the IIS server.
Upgrade Considerations
Upgrade to Version 1.90 or later
To add the $profilename variable in the suppression key of the following components, set the
key to
in in the
Raw Configure
interface >
section. By default, the key value is
  • Counters
    • HTTP Response Time
    • HTTP Response Value
    • IIS max Request Time
    • SSL Host Verification Status
  • Alarm
    • Host Availability
If you enable this key, the probe also appends
to the
in the QoS target. Format:
. This enables the probe to display data of two profiles of same $hostname, separately on Unified Service Management (USM).
Upgrade to Version 1.71 or later
To monitor local Microsoft IIS servers, and make the probe Device ID same as the robot Device ID, set the
key to
in the Raw Configure interface >
section. By default, the key value is
The following table lists upgrade scenarios with the key value:
Probe Version
Key Value
Prior to version 1.71
Upgrade to version 1.71
No impact
Upgrade to version 1.71
Previously, all QoS and alarms for the local host profile were generated on the old Device ID. Now, the probe generates all the QoS and alarms for local host profiles on the new Device ID, that is, Robot Device ID. This breaks the old data continuity on the USM portal.
To execute the dll files, disable the following setting on the IIS server available in Advanced Settings for the Application Pool:
Enable 32-bit Applications