+x+xThanks Tamas,
After completing hte configurations - specifying the powershell URL; Exchange URL; Recipient plus ensuring that the service account has the relevant permissions on Exchange, i am still not able to view audit events on Logbinder for exchange.
where would one get logs to help troubleshoot what the issue might be? NB: none of the errors documented in Appendix 5 have been experienced.
First,check under the input properties if there are any entries under Transactions. If there are entries, it means that LOGbinder is sending out audit log requests to the Exchange server. Once the File Name and Completed fields are filled out, it means that LOGbinder has received and processed the results.
It might take a considerable time between LOGbinder requesting the audit logs and receiving them back from Exchange. For Exchange 2010, it might be 30 minutes on average, while with Exchange 2013, it can take an entire day. You can speed this up by
changing the Exchange audit search poll interval to a smaller value, such as 10 or 15 minutes.
Further to my previous post more log info:
Test 1:[PS] C:\>Test-PowerShellConnectivity -ConnectionUri
https://xxxxxxx.yyyyyy.net/Powershell -TestCredential $yyyyyy.net\zzzzzzzz -Authentication Basic
Cannot validate argument on parameter 'TestCredential'. The argument is null. Supply a non-null argument and try the co
mmand again.
+ CategoryInfo : InvalidData: (

[Test-PowerShellConnectivity], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Test-PowerShellConnectivity
[PS] C:\>Test-PowerShellConnectivity -ConnectionUri
https://xxxxxxx.yyyyyy.net/PowershellWindows PowerShell Credential Request : cmdlet Test-PowerShellConnectivity at command pipeline position 1
Warning: This credential is being requested by a script or application on the xxxxxxx.yyyyyy.net remote
computer. Enter your credentials only if you trust the remote computer and the application or script requesting it.
Supply values for the following parameters:
TestCredential
Logon to the virtual directory 'xxxxxxx.yyyyyy.net/Powershell' failed with the following error: '
Connect
ing to remote server failed with the following error message : The server certificate on the destination computer (xxxxxxx.yyyyyy.net:443) has the following errors:
The SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable.The SSL certificate contains a common name (CN) that does not match the hostname. For more information, see the about_Remote_Troubleshooting Help topic.'. For more information, see the application event log.
+ CategoryInfo : NotSpecified: (

[Test-PowerShellConnectivity], LocalizedException
+ FullyQualifiedErrorId : F5C85988,Microsoft.Exchange.Monitoring.TestRemotePowerShellConnectivity
Test 2: (Trust any ssl certificate)[PS] C:\>Test-PowerShellConnectivity -ConnectionUri xxxxxxx.yyyyyy.net/Powershell
-TrustAnySSLCertificateWindows PowerShell Credential Request : cmdlet Test-PowerShellConnectivity at command pipeline position 1
Warning: This credential is being requested by a script or application on the Sxxxxxxx.yyyyyy.net remote
computer. Enter your credentials only if you trust the remote computer and the application or script requesting it.
Supply values for the following parameters:
TestCredential
Logon to the virtual directory 'xxxxxxx.yyyyyy.net/Powershell' failed with the following error: 'Connect
ing to remote server failed with the following error message : T
he WinRM client cannot process the request. The WinRM c
lient tried to use Negotiate authentication mechanism, but the destination computer (xxxxxxx.yyyyyy.net:443) ret
urned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or spec
ify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as t
he remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use
Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name a
nd password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubles
hooting Help topic.'. For more information, see the application event log.
+ CategoryInfo : NotSpecified: (

[Test-PowerShellConnectivity], LocalizedException
+ FullyQualifiedErrorId : BC25E3C,Microsoft.Exchange.Monitoring.TestRemotePowerShellConnectivity
CasServer LocalSite Scenario Result Latency(MS) Error
--------- --------- -------- ------ ----------- -----
Default-Fi... Logon User Failure Connecting to remote ...
Default-Fi... Logon User Failure Connecting to remote ...
[PS] C:\>
Question: How do we go about resolving the two issues above? - certificate trust issue and WinRm issue.