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)
Read more: Exchange / Outlook - There is a problem with the proxy server's security certificate
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:
- Open Exchange Management Shell
- Navigate to C:\Program Files\Microsoft\Exchange Server\Scripts
- Run .\uninstall-AntispamAgents.ps1 cmdlet
- Confirm uninstall for each agent
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.
Read more: Event 12014 - Microsoft Exchange could not find a certificate...
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.
Read more: Terminal Services Gateway stops working after removing SharePoint 3.0
- WSUS 3.2 on 2008R2 fails to download Windows 10 Anniversary Update (1607)
- Updating Group Policy .admx template files with Windows 10 (1607) specific settings
- Symantec Backup Exec agent install error - Microsoft VC++ Redistributables
- Cannot start IIS website - Exception from HRESULT: 0X80070020
- WindowsUpdate.admx on Server 2012 (Windows 10 upgrade pop-ups on domain PCs)
- Renew MS Exchange Trusted Certificate
- Configure DELL SonicWALL SSL-VPN (NetExtender)
- Files disappearing from redirected folders in Windows 10 (DFS gone crazy)...
- Find out if your domain SYSVOL replication is run by FRS or DFS-R
- Pervasive SQL services don't start after server reboot