Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

PowerShell Remoting by FQDN instead of IP

$
0
0

I'm trying to use the  Windows PowerShell Monitor component (actually as part of the "SolarWinds Web Performance Monitor (WPM) Player" template) in the Remote Host Execution Mode.  The component attempts to connect using an IP instead of an FQDN, so this error is generated:

 

PowerShell script error. Connecting to remote server 172.10.10.31 failed with the following error message : The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TrustedHosts run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

 

If I specify HTTPS instead, then this error is returned:

 

PowerShell script error. Connecting to remote server 172.10.10.31 failed with the following error message : The server certificate on the destination computer (172.10.10.31:5986) has the following errors: The SSL certificate contains a common name (CN) that does not match the hostname.

 

Is there some tricky way to tell the component monitor to access via some Fully Qualified Domain Name instead, or is this a feature request that needs to be made?  I realize that could go about modifying the TrustedHosts setting on all of my different pollers, but we'd prefer the ability to not to and to be able to use HTTPS as it's available for all of our connections.


Viewing all articles
Browse latest Browse all 20396

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>