I found the following workaround which allows me to continue using my own SSL certificate. Before running running the OME CLI commands, execute the following Powershell command to disable server certificate validation: PS> [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true} When done with my OME commands, I can re-enable validation with: PS> [System.Net.ServicePointManager]::ServerCertificateValidationCallback = $null
Hi, I'm trying to use the OME 1.3 CLI tools, but I receive the following error: PS> Set-ModifyDiscoveryRangeGroup -GroupName Test -AddRangeList "C:\Temp\TestRangeList.xml"  I found the following post in which the first reply asks if something has changed with the OME certificate: [URL] In my case, yes, I have changed the SSL certificate in IIS from the default one which comes installed with OME to one that I generated with my certificate provider.  I did this because we access OME via the FQDN and not the server.domain.local format and using my own certificate avoids the browser certificate security warning that is presented each time. As a test, I switched the SSL certificate back to the default OME version and then the above command works properly.  How can I resolve this trust relationship error while using my own certificate? Thanks, Ryan
OME Could not establish trust relationship