Hi,

Please refer to the following article:

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=12014&EvtSrc=MSExchangeTransport

To resolve this warning, perform the following steps:

1. Examine the configuration of the certificates installed on the Exchange server and the configuration of all Receive connectors and Send connectors installed on the server. The following commands are used to view the configuration:

   Get-ExchangeCertificate | FL *

   Get-ReceiveConnector | FL name, fqdn, objectClass

   Get-SendConnector | FL name, fqdn, objectClass

   Note   To display the services that are enabled for the installed certificate, you must use the asterisk (*) when you run the FL argument on the Get-ExchangeCertificate cmdlet. The Services values will not display if the * is not specified in the task parameters.

   Run the commands and compare the FQDN that is returned with the Warning event with the FQDN that is defined on each of the connectors and with the CertificateDomains values that are defined on each of the certificates. The CertificateDomains value is a concatenation of the Subject and Subject Alternative Name fields on the certificate.

   The goal is to verify that each connector that is using TLS has a corresponding certificate that includes the connector's FQDN in the CertificateDomains values of the certificate. Note any connectors that are enabled for TLS but do not have a corresponding certificate where the connector FQDN is in the CertificateDomains values of the certificate.

   Inspect the Services value on each certificate. If you are using a certificate for TLS, it must be enabled for the SMTP service with a Services value of SMTP.

2. If the FQDN is not listed on the CertificateDomains parameter, you must create a new certificate and specify the FQDN of the connector that is returned in this warning message. You can create the certificate by using the New-ExchangeCertificate cmdlet. Or you may prefer to use a third-party or custom certificate. You can use the New-ExchangeCertificate cmdlet to generate the certificate request. For more information, see Creating a Certificate or Certificate Request for TLS.

3. If a third-party or custom certificate has been installed on the server and it contains a matching FQDN but the certificate is not enabled for the SMTP service, the certificate must be enabled for the SMTP service. For more information, see Enable-ExchangeCertificate.

Thanks.

No, please read my original post. "A UC certificate is installed and linked to the IIS service only".

So, when I link the cert to SMTP, wont the Outlook clients all get a certificate error? as they are looking for servername.domain.local not mail.domain.com.

see these article to help you understand

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=12014&EvtSrc=MSExchangeTransport

http://social.technet.microsoft.com/Forums/en-US/b9ec2ab2-3e01-4c24-a066-a67fdd72d425/event-id-12014?forum=exchangesvrsecuremessaginglegacy

Those are no help. Send connector already has mail.domain.com as the FQDN.

I realize to fix the 12014 error I should add SMTP service to my certificate, but I don't want to break all the Outlook clients as they are looking for servername.domain.local still.

Hi user....

Please check the configuration of the authentication that are introduced on the Exchange Server & the setup of all the send connectors & receiver connectors which are introduced on Exchange Server......for this write the command shown in this blog....

https://mailsolutions.wordpress.com/2015/03/26/event-id-12014-starttls-certificate-error-troubleshooting/

Also, don't forget to use asterisk in the command shown in the blog....

Hope this will help you