Exchange 2013 certificate errors

I have the following error on my new exchange 2013 box, Microsoft Exchange could not find a certificate that contains the domain name servername.domain.local in the personal store on the local computer.

Its stops me sending and receiving mail and stops me adding accounts on the desktop clients.
Daniel ForresterDirectorAsked:
Who is Participating?
 
Cliff GaliherCommented:
You are tying two unrelated issues together. That error is common and DOES prevent mail from being sent and received via TLS. However TLS is seldom used and all major SMTP servers will fall back to unencrypted gracefully. If you cannot send and receive email, ibis VERY likely there is something else not set up properly. Use the mail flow tools built into exchange to troubleshoot.

This also would not impact desktop clients.
0
 
Daniel ForresterDirectorAuthor Commented:
When I try and connect to the server I get the following error.

There is a problem with the proxy server security certificate.
The name on the security certificate is invalid or does not match the name of the target site servername.domain.local

I have installed a authorised certificate from a provider.
0
 
Cliff GaliherCommented:
That error is pretty straightforward. The information you are entering (or that Autodiscover is handing out) doesnt match the certificate's name. You have to set up DNS with the name on the certificate, and if you are using Autodiscover, you have to tell the Autodiscover server what URLs to send out so they match as well. Exchange has a series of powershell commands to do that and setting up Autodiscover is documented on Technet.
0
 
Daniel ForresterDirectorAuthor Commented:
Can you point me in the direction of any documentation?
0
All Courses

From novice to tech pro — start learning today.