Documentation forServer & Application Monitor

Create a WinRM listener for AppInsight for IIS

When AppInsight for IIS is configured for target servers, port 5968 is used as the WinRM HTTPS listening port, by default. If you receive an "HTTPS listener currently exists on port 5986" message, follow these steps to switch the listening port to an available port.

  1. To configure WinRM on an IIS server, open an elevated Windows PowerShell command prompt; run PowerShell as an administrator.
  2. Copy the following text to a text editor:
    winrm create winrm/config/listener?Address=*+Transport=HTTPS @{Port="5986";CertificateThumbprint="<Thumbprint value of certificate>";​Hostname="<IP Address of Server>_Solarwinds_Zero_Configuration"}

    This statement binds the certificate to the WinRM listener, using a wildcard symbol ("*") for Address to allow listening on all available local addresses. Syntax may vary based on usage inside of PowerShell or the Administrative Command prompt.

    Port is the port number for the listener. The default port for WinRM is 5986, but you can change it, if necessary.

    For <Thumbprint value of certificate>, paste the self-signed certificate thumbprint, without spaces. See Retrieve the Thumbprint of a Certificate (© 2020 Microsoft Corp, available at, obtained on October 29, 2020.)

    The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.

    Important: Quotation mark characters (") can change during copying and pasting. Using a text editor such as Notepad should prevent that from happening, but if you don't get the desired results, check the quotation marks to make sure they did not change.

  3. Copy the text, paste it into the PowerShell command line, and press Enter. Results should look something like this:

  1. To verify the configuration, type winrm get winrm/config/listener?Address=*+Transport=HTTPS.
  2. Press Enter.
  3. Results should look something like this:

The following log file contains information and errors related to the WinRM configuration process: C:\ProgramData\Solarwinds\Logs\APM\RunWinRMConfigurator.log

See also: