Applications Systems

AppInsight for Exchange: Remote configuration was unsuccessful due to the following: "WinRM test was successful..."

You receive the following error message: Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error: Connecting to remote server..."

First published date

10/15/2018 8:49 PM

Last published date

6/26/2020 3:01 AM

Overview

You receive the following error message:

Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error: Connecting to remote server <ip address> failed with the following error message: The WinRM Client set a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic".

Product section

Server Application Monitor

Cause

There are no default HTTPS bindings for all unassigned ports, (i.e. “HTTPS 443 *”).

Resolution

Establish the missing default HTTPS binding with an Exchange certificate.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.