Skip to content

IIS Discovery

Mat Davis edited this page Nov 20, 2019 · 1 revision

Enabling WMI-based IIsWebServiceSensor for IIS 7 discovery on Windows 2008 and 2012

TADDM 7.3 introduced a new script-based sensor for IIS 7 discovery that launches when IIS is found on Windows 2008 or 2012. This script-based sensor is named IISServerSensor. However, if your Windows environment is not configured for script-based discovery (e.g. admin shares are disabled making it impossible to copy script files) then what will happen is the new sensor will launch and fail and the old IIsWebServiceSensor won't launch at all. There is a work-around for this so that you can still discovery IIS 7 on Windows 2008 and 2012.

I should start by stating that this is not officially supported. If you implement this work-around, do not open service requests for discovery issues of IIS 7 on Windows 2008 and 2012.

First back up your existing templates by running the following command.

api.sh -u <user> -p <password> find -d 5 com.collation.platform.model.discovery.template.Template > templates-backup.xml

Download the attached iis-templates.xml file and copy it to a discovery server. Then issue the following command to load the templates.

api.sh -u <user> -p <password> import iis-templates.xml

You should see a message stating "Import completed successfully."

Important, make sure that you disable the IISServerSensor in your discovery profiles. It will still launch, even with the new templates loaded.

If you want to revert back to default you will need to delete the additional IIS templates that were added. This can be done by querying the templates again and issuing an api.sh delete against the existing GUIDs or editing iis-templates.xml, setting them to disabled, and importing the file again.

Long Storage Times During IIS Discovery (7.3.0.2 or later)

If you are experiencing long storage times during IIS discovery, see the applicable section on the performance Tips and Hints page.

Clone this wiki locally