cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 7

Exchange 2016 CU3 - Unknown status / Access Denied for one server

Jump to solution

Hello Twack.

I have Solarwinds with SAM 6.3.0 and I have 3 Exchange 2016 servers setup in DAG at CU3.

After updating to CU3 one of the servers is unable connect to the "AppInSight for Exchange" counters corretly.

The other servers are able to connect and display information on all mounted DB and users with no problem. All of the servers have the same service user credentials configured and all have an Agent installed.

No changes to Powershell Configuration were made during the update.

No changes to the firewall configuration, the windows firewall is off.

All of the machine reside on the same subnet.

When testing the connection to the server it displays:

"WinRM test was successful.

PowerShell Exchange web site testing failed with the following error:

Connecting to remote server (theipaddressishere) failed with the following error message : [ClientAccessServer=(theservernameishere),BackEndServer=,RequestId=2a248506-670e-406d-a15a-9759acf46d28,TimeStamp=20.1.2017 11:52:36] Access Denied For more information, see the about_Remote_Troubleshooting Help topic."

When trying to Configure the Server it displays:

"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 (theipaddressishere) failed with the following error message : [ClientAccessServer=(theservernameishere),BackEndServer=,RequestId=dac2df62-ec05-4381-848b-d332a7a3e680,TimeStamp=20.1.2017 11:56:16] Access Denied For more information, see the about_Remote_Troubleshooting Help topic.""

I've checked the following things.

1.  Check is IIS server certificate is set to "Secure Exchange" on all servers. Bindings are exactly the same for all servers.

2.  Deleting the node and re-adding it to Solarwinds.

3. Checking and adding the Service user credential to Powershell Configuration as suggested in AppInsight for Exchange: Access is Denied - SolarWinds Worldwide, LLC. Help and Support

4. Check the "ListeningOn" suggested by AppInsight for Exchange: WinRM testing failed - SolarWinds Worldwide, LLC. Help and Support with Listening On set to various IP's

Any Ideas?

0 Kudos
1 Solution
Level 9

Go into the assigned application monitor (Settings --> All Settings --> Sam Settings --> Manage Application Monitors)

In the left column Group By Application Monitor Template --> Click on AppInsight for Exchange --> Select the correct server in the right pane --> Edit Properties.

Under the two entries for PowerShell at the top of the screen replace the variable ${IP} with the FQDN. For instance:

instead of this entry: https://${IP}/powershell/ 

enter: https://mailserver.domain.com/powershell/

Then hit the configure server button.

Also, make sure the Exchange server is being polled with WMI and not the agent.

In my experience this will get you up and running, until something magically breaks this monitor again in the somewhat near future.

View solution in original post

1 Reply
Level 9

Go into the assigned application monitor (Settings --> All Settings --> Sam Settings --> Manage Application Monitors)

In the left column Group By Application Monitor Template --> Click on AppInsight for Exchange --> Select the correct server in the right pane --> Edit Properties.

Under the two entries for PowerShell at the top of the screen replace the variable ${IP} with the FQDN. For instance:

instead of this entry: https://${IP}/powershell/ 

enter: https://mailserver.domain.com/powershell/

Then hit the configure server button.

Also, make sure the Exchange server is being polled with WMI and not the agent.

In my experience this will get you up and running, until something magically breaks this monitor again in the somewhat near future.

View solution in original post