Article ID: 978253 - View products that this article applies to.
On a Microsoft Exchange Server 2007 server, you run the Test-SystemHealth command and then you run the Test-OwaConnectivity command in the same Exchange Management Shell window or through Exchange Server 2007 Management Pack for Operations Manager. In this situation, the Test-OwaConnectivity command operation fails and you receive the following certificate validation error message:
However, if you run the Test-OwaConnectivity command specifying the-TrustAnySSLCertificate:$true parameter, the operation still fails.
WARNING: The test was unable to log on to Outlook Web Access because the SSL certificate did not validate. You can force the command to proceed by re-running it and specifying the TrustAnySSLCertificate parameter.
Note This problem occurs when you run any Test-*connectivity command after you run the Test-SystemHealth command, not just the Test-OwaConnectivity command.
This problem occurs because the Test-SystemHealth command forces a specific certificate validation call that is not released. However, the later command, such as the Test-OwaConnectivity command, tries to use a different certificate validation call.
To resolve this problem, install the following update rollup:
(http://support.microsoft.com/kb/979784/ )Description of Update Rollup 3 for Exchange Server 2007 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Test-SystemHealth command, visit the following Microsoft Web site:
General information about the Test-SystemHealth command
Article ID: 978253 - Last Review: March 18, 2010 - Revision: 1.0