Certificate status could not be determined because revocation check failed when importing third-party certificate
Original KB number: 979694
A valid third-party certificate is imported into an Exchange Server 2010 Client Access server (CAS). Then, the following status message is displayed in the Exchange Management Console:
The certificate status could not be determined because the revocation check failed.
If you run the
Get-ExchangeCertificate cmdlet in the Exchange Management Shell, you receive the following status for the third-party certificate:
However, if you click the Certificate Revocation List (CRL) link that is specified on the certificate, you can still access the third-party certificate through the Exchange server.
This issue occurs because Exchange Server 2010 uses Microsoft Windows HTTP Services (WinHTTP) to manage all HTTP and HTTPS traffic, and WinHTTP does not use the proxy settings that are configured for the Internet browser.
To view the WinHTTP proxy settings, at a command prompt, run the following command:
netsh winhttp show proxy
To resolve this issue, you must configure the WinHTTP proxy setting and the server FQDN in the WinHTTP bypass list.
If you do not configure both the proxy setting and the server FQDN in the WinHTTP bypass list, the Exchange Management Shell and the Exchange Management Console cannot contact the Remote PowerShell.
To resolve this issue, open a command prompt, type the following command, and then press ENTER:
netsh winhttp set proxy proxy-server="http=myproxy" bypass-list="*.host_name.com"
The myproxy placeholder represents the proxy server name, and host_name represents the Exchange Server 2010 host name.
For more information about WinHTTP and about how to set the proxy on the Exchange 2010 server, see:
- Netsh Commands for Windows Hypertext Transfer Protocol (WINHTTP)
- Configure Proxy Settings for WinHTTP
- WinHttpDetectAutoProxyConfigUrl function
For more information about the WinSock Proxy Auto Detect, see Description of WinSock Proxy Auto Detect support.