Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for Exchange error: Remote configuration failed

AppInsight for Exchange error: Remote configuration failed


The following error message appears when trying to configure AppInsight for Exchange:
Remote Configuration Failed
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
failed with the following error message : The WinRM client received an HTTP bad request status
(400), but the remote service did not include any other information about the cause of the failure.
For more information, see the about_Remote_Troubleshooting Help topic."



As a result of this error, when you edit the Site Bindings, the HTTPs binding is set to all unassigned address on port 443 with a valid SSL certificate as shown below.



SAM version 6.2


This issue is caused by a missing PowerShell https endpoint.


Note: The error on the component will still appear upon application of the resolution as the Server Mailboxes are polled once every day. The error should no longer appear the following day or during the next polling.

1. Create a wsMan listener by initializing $targetIP variable with the Exchange Server IP.
    Run the next query on the Exchange Server and give the output:
    $targetIP = "";
  $hostname = $targetIP + "_Solarwinds_Exchange_Zero_Configuration";
  $lifeTimeDays = 365 * 50; 
  # Get the thumbprints of the SSL certificates that match the hostname
  Write-Output "SSL certificates info:";
  Get-Childitem -path cert:\LocalMachine\My | Where-Object {$_.Subject -eq "CN=$hostname"};
  $thumbprints = Get-Childitem -path cert:\LocalMachine\My | Where-Object {$_.Subject -eq "CN=$hostname"} | Select-Object -Property Thumbprint; 
  # PowerShell magic to retrieve the first matching thumbprint (there'll probably only be one anyway) 
  $thumbprint = @($thumbprints)[0].Thumbprint;
  Write-Output "Retrieved thumbprint:";
  Write-Output $thumbprint; 
  # Create a WinRM listener, identifying the SSL certificate by the thumbprint
  New-WSManInstance WinRM/Config/Listener -SelectorSet @{Address = "*"; Transport = "HTTPS"} -ValueSet @{Hostname = $hostname; CertificateThumbprint = $thumbprint}; 
  } catch {
  Write-Output "Unable to create wsMan listener. ERROR: $($Error[0])";
2. Recycle the following application tools:

  •     MSExchangePowerShellFrontEndAppPool (Default Web Site\PowerShell app.pool)
  •     MSExchangePowerShellAppPool (Exchange Back End\PowerShell app.pool)
  •     MSExchangeOWAAppPool (Default Web Site app.pool)
  •     DefaultAppPool (Exchange Back End app.pool)
    Refer to the Recycle an Application Pool on Demand (IIS 7) for more information regarding recycling application pools.



Last modified
23:06, 30 Nov 2016