MessageStats reporting the following error gathering from Exchange 2010 Server
Failed to remotely gather the database copy status using Powershell. Failed to create PowerShell connection on remote server <ServerName>. Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: Negotiate For more information, see the about_Remote_Troubleshooting Help topic.
Some Basic Steps to troubleshoot remote powershell connections are listed below:
1. Verify the port bindings in IIS on the Exchange server. Ensure that there are no host headers required to connect to the server.
2. Verifiy if SSL is required on the default website / powershell virtual directory. If so try removing this requirement.
3. Attempt to login and establish a remote powershell session via powershell using the following commands(when prompted for credentials provide the MessageStats service account credentials):
$s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<NetbiosServerName>/PowerShell/ -Authentication Kerberos -Credential (Get-Credential)
4. On your Exchange Server you can try running " Winrm quickconfig" from an elevated command prompt window.
Once these items have been tested try the software again to ensure that is is able to run it's tasks using remote powershell against the server in question.
The Powershell Help Topic Referenced in the Error Message about_Remote_Troubleshooting can be found online at: