Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > IIS handler mapping requirements

IIS handler mapping requirements

Table of contents

Updated: May 4, 2018


This article lists the file extensions that IIS must allow in order for Orion Platform products to function.


NPM 12.2


For the Orion Web Console to function, the IIS handler mapping must allow the following file extensions:

  • Pages - .aspx, .html, .htm
  • Services - .asmx, .ashx
  • Resources - .js, .css
  • Images - .ico, .gif, .jpg, .png
  • Docs -  .pdf, .txt
  • Fonts -  .svg, .woff, .woff2, .ttf
  • Import samples - .csv, .xls
  • No extension - "." (files with no extension)


For Handler Mappings, the IAO must document and approve all allowable file extensions the website allows (whitelist) and denies (blacklist) by the website. The whitelist and blacklist will be compared to the Handler Mappings in IIS. Handler Mappings at the site level take precedence over Handler Mappings at the server level.


Last modified