Exchange / Outlook - There is a problem with the proxy server's security certificate

Issue

After replacing a wildcard SSL certificate (*.domain.com) with a basic single-server certificate (webmail.domain.com) remote clients using Microsoft Outlook can no longer connect to their email accounts on an Exchange server using HTTP Proxy Method. Outlook displays below error and then repeatedly prompts for a password:

There is a problem with the proxy server's security certificate.
The name on the security certificate is invalid or does not match the name of the target site webmail.domain.com.
Outlook is unable to connect to the proxy Server. (Error Code 0)

Microsoft Exchange - Uninstall Anti-spam agents

If you don't use anti-spam feature on Microsoft Exchange server you can uninstall anti-spam agents completely:

Event 12014 - Microsoft Exchange could not find a certificate...

Issue

Microsoft Exchange 2007 regularly logs following errors in Windows Application Logs:

Event ID: 12014
Source: MSExchangeTransport
Level: Error
Description:
Microsoft Exchange could not find a certificate that contains the domain name <server-name.domain.local> in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default Send Connector with a FQDN parameter of <server-name.domain.local>. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

 

Terminal Services Gateway stops working after removing SharePoint 3.0

Issue

After removing SharePoint 3.0 from Windows Small Business Server (SBS) 2008, Terminal Services Gateway stops working. This in turns causes issues with Remote Web Workplace (RWW). The Terminal Services Gateway service fails to start with following error:

Windows could not start the Terminal Services Gateway service on Local Computer.
Error 1068: The dependency service or group failed to start.

Newsletter

Subscribe to receive occasional updates on new posts.
Your email will not be used for any other purpose and you can unsubscribe at any time.
Please wait