I'm tryig to use the New-WebServiceProxy cmdlet to connect to the information service on 17778. It seems to connect, but the cert if self signed and not trusted. I added the cert to the trusted root certificate authorities but it still fails.
The certificate is issued to "SolarWinds-Orion" and since the cert isn't issued to "orion1" either by short name or FQDN, it is untrusted. I'm not really sure how to reissue a proper cert to the Information Service. I supposed I could trick it by creating a DNS entry for SolarWinds-Orion that resolves to the server, but there should be a nicer way of getting this to work.
New-WebServiceProxy -Uri 'https://orion1:17778/SolarWinds/InformationService?wsdl'
New-WebServiceProxy : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
At line:1 char:10
+ $Orion = New-WebServiceProxy -Uri 'https://orion1:17778/SolarWi ...
+ CategoryInfo : ObjectNotFound: (https://orion.c...ionService?wsdl:Uri) [New-WebServiceProxy], WebExcept
+ FullyQualifiedErrorId : WebException,Microsoft.PowerShell.Commands.NewWebServiceProxy
You can get New-WebServiceProxy to ignore SSL errors by following the instructions in this post: http://www.poshpete.com/powershell/new-webserviceproxy-and-ssl. But you are better off with the Connect-Swis cmdlet we provide. I'm guessing you turned to New-WebServiceProxy to work around the issue you described in Orion SDK Powershell and Windows 8.