Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > Create a WinRM HTTPS listener

Create a WinRM HTTPS listener

Table of contents
Created by William Muhle, last modified by Rodim Suarez on Aug 26, 2016

Views: 1,205 Votes: 0 Revisions: 5


This article describes how to create a WinRM HTTPS listener for Powershell on a remote server.


  • Windows
  • All SAM versions
  • All NPM versions


  1. Open a Command Prompt as an administrator from the Start menu, (right-click and select run as admin):
    The following command should be executed on the Remoting Server computer (the computer that you are polling from the Orion server). This is the target node which will be used with the SAM PowerShell monitor. It is also the computer where a self-signed certificate has been created.
  2. Enter the following command with the parameters replaced with actual values, as explained below:
    winrm create winrm/config/Listener?Address=<IP ADDRESS OF REMOTE SERVER>+Transport=HTTPS @{Hostname=”<NAME OR IP ADDRESS OF REMOTE SERVERr>”;CertificateThumbprint=”<CERTIFICATE THUMBPRINT WITHOUT SPACES>”;Port=”<PORT NUMBER>”}
    <IP ADDRESS OF REMOTE SERVER> - To bind the certificate to the Listener, specify the Remoting Server's local IP address (this is the ip address of the server you are going to be monitoring by Orion, not the Orion server itself). You can use the wildcard, (*), symbol to allow listening on all available local addresses;
    <NAME OR IP ADDRESS OF REMOTE SERVER> - The Remoting Server's node name or IP address;
    <CERTIFICATE THUMBPRINT WITHOUT SPACES> - Paste the self-signed certificate thumbprint created in steps 13-14 of the previous section;
    <PORT NUMBER> - This is the port number for the Listener. You can specify the default WinRM HTTPS port of 5986.
    For example:
    winrm create winrm/config/Listener?Address=IP: @{Hostname="";CertificateThumbprint="6aa47ed7356fb0f1e3b434850a7bb51ed40b0d3a";Port="5986"}
  3. Once the command has been successfully executed, the output will look similar to the following illustration:


For more help on this, please see the Configuring and Integrating PowerShell document.



Last modified