Question : Microsoft Exchange could not find a certifcate...

I found this message in application log.. and found a recommended solution in Microsoft site "http://support.microsoft.com/kb/555855", can anyone tell me would it affect the performance of my Exchange 2007 if I do not apply this solution to my server?  What is impact on server if I do not apply it?  I am using SSL cert for my webmail function and allow laptop computer user access to my Exchange 2007 via "RCP over HTTPS" while they are not in office.

Message in application log.
Microsoft Exchange couldn't find a certificate that contains the domain name webmail.company.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Outbound_Internet_Email with a FQDN parameter of webmail.cwalkergroup.com. 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.

Answer : Microsoft Exchange could not find a certifcate...

Exchange 2007 is designed to run securely and runs with a Self Signed SSL Certificate with an "Out of the Box" installation.

If you have replaced this certificate then you just need to enable it for use on SMTP. Not doing so will not have any bearings on the servers performance as long as it is enabled for IIS.

Only if the certificate is not enabled for IIS will you have issues with Webmail and Outloock Anywhere (RPC over HTTPS).

Fromt he Powershell run "get-exchangecertificate | fl" to see what certificates are in use, and take a note of the thumbprint for the Certificate that uses the FQDN of the server. (Or find the thumbprint on the certificate installed on a Web Client"

Then in power shell run "Enable-ExchangeCertificate -thumbrpint xxxxxxxxxxxxxxxxxxxx -Services SMTP" where xxxxxxxxxxxxxxxxxxxx is the Thumbprint.

THis should then clear the issue