Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.6.1 Administrator Guide > Additional SAM technology requirements > AppInsight for IIS requirements and permissions

AppInsight for IIS requirements and permissions

Updated July 26, 2018

Review the requirements and permissions for configuring AppInsight for IIS nodes in your environment. AppInsight for IIS data is collected at the same default five-minute polling interval as traditional application templates.

Use the free Remote Execution Enabler for PowerShell tool to configure secure WinRM across one or more nodes. See this THWACK article for details.

Following are AppInsight for IIS requirements:

  • PowerShell 2.0 or later must be installed on the IIS server.
  • Administrator rights or equivalent credentials to the IIS server being monitored are needed for configuration. Non-administrative permissions for polling and monitoring is only achievable using the optional Orion Agent.
  • Ensure the WinRM service is running and the Startup Type is set to Automatic. 
  • IIS 7.0 or higher must be installed.
  • AppInsight for IIS supports the following operating systems and IIS versions:


Microsoft OS Supported IIS version

Microsoft Server 2008

IIS 7.0

Microsoft Server 2008 R2 and Vista

IIS 7.5

Microsoft Server 2012 and Windows 8

IIS 8.0

Microsoft Server 2012 R2 and Windows 8.1 IIS 8.5
Microsoft Server 2016 and Windows 10 IIS 10


If any prerequisite is missing, the application goes into an Unknown state.

AppInsight for IIS technologies and ports


The IIS server must have the ports open on the managed nodes.

Technology Port Notes
RPC Endpoint Mapper TCP port 135 SAM uses this port to establish WMI/RPC connections to the remote computer. RPC is required to gather performance counter data via the ASP.NET resource.
WMI TCP ports 1025 - 5000 or TCP ports 49152 - 65535 By default, Windows uses a random port from this range for WMI communications. The default port range differs based on the OS so you'll need to create a firewall exception on the remote computer.
PowerShell TCP port 5986 A secure listener hosted in the WinRM service.
HTTP TCP, At least one port mentioned in the bindings of a site. If the connection is not allowed, the HTTP Monitor is hidden.
HTTPS TCP. At least one port mentioned in the secure bindings of a site. If the connection is not allowed, the HTTPS Monitor will be hidden.
SSL TCP. At least one port mentioned in the secure bindings of a site. If the connection is not allowed, the SSL Certificate Expiration Date Monitor is hidden.
SMB (Windows Shares) TCP port 445 Used for Site Directory Information and Log Directory Information.
Last modified