Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for Exchange: WinRM test was successful. The SSL connection cannot be established

AppInsight for Exchange: WinRM test was successful. The SSL connection cannot be established

Updated February 24, 2017

Overview

The following error occurs when attempting to automatically configure or test AppInsight for Exchange:

WinRM test was successful. PowerShell Exchange web site testing failed with the following
error:Connecting to remote server x.x.x.x failed with the following error message:
The SSL connection cannot be established. Verify that the service on the remote host is
properly configured to listen for HTTPS requests. Consult the logs and documentation for
the WS-Management service running on the destination, most commonly IIS or WinRM.
If the destination is the WinRM service, run the following command on the destination to
analyze and configure the WinRM service: "winrm quickconfig -transport:https".
For more information, see the about_Remote_Troubleshooting Help topic.

Environment

SAM version 6.1 or later

Cause 

There is no SSL Certificate associated with the HTTPS binding on the default website on the Exchange server or an expired SSL certificate is assigned.

Resolution

Assign an SSL certificate to the default website on the Exchange Mailbox:

  1. Open a Remote Desktop Session to the Exchange Mailbox.
  2. Run > inetmgr.
  3. Expand Server > expand Sites.
  4. Right click Default Web Site > Edit Bindings.
  5. Edit the HTTPS binding.
  6. Assign a Valid Certificate to the binding.
  7. Re-run the Test/Configuration from the SAM Web Console.

See also the AppInsight for Exchange: Remote configuration was unsuccessful due to the following: "WinRM test was successful..." article for related information.

 

Last modified
21:02, 26 Mar 2017

Tags

Classifications

Public