Added the Exchange 2010 Database Availability Group application monitor to couple of our Exchange 2010 servers and got the following error –
Clicking “More” gives the following –
This is because Solarwinds is trying to run a PowerShell script on the remote server and the script is unable to run due to authentication errors. That’s because Solarwinds is trying to connect to the server using its IP address, and so instead of using Kerberos authentication it resorts to Negotiate authentication (which is disabled). The error message too says the same but you can verify it for yourself from the Solarwinds server too. Try the following command –
|
1 |
New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<yourexchsvr>/PowerShell -Authentication Negotiate -Credential (get-credential) |
This is what’s happening behind the scenes and as you will see it fails. Now replace “Negotiate” with “Kerberos” and it succeeds –
|
1 |
New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<yourexchsvr>/PowerShell -Authentication Kerberos -Credential (get-credential) |
So, how to fix this? Logon to the remote server and launch IIS Manager. It’s under “Administrative Tools” and may not be there by default (my server only had “Internet Information Services (IIS) 6.0 Manager”), in which case add it via Server Manager/ PowerShell –
|
1 2 |
> Import-Module ServerManager > Add-WindowsFeature -Name RSAT-Web-Server |
Then open IIS Manager, go to Sites > PowerShell and double click “Authentication”.
Select “Windows Authentication” and click “Enable”.
Now Solarwinds will work.