Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for Exchange: Remote configuration was unsuccessful due to the following: "WinRM test was successful..."

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

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".

Environment

All SAM versions

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.

 

Last modified

Tags

Classifications

Public