[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 635
  • Last Modified:

Exchange 2013 Certificate "Not Valid"

i have a fresh installed exchange 2013 server.

installed a 3rd party certificate, add services to it.

in the ECP manager it says "not valid"

but when i do an exchange connectivity test all seems ok.

also all clients can connect with no problem. what can this be?
0
Rik Van Lier
Asked:
Rik Van Lier
1 Solution
 
David CarrCommented:
Make sure the certifcate is not a wildcard certificate. Also make sure a self signed certificate is not being used. It will not be trusted by Exchange. What is the specific error message?
0
 
9l1vesCommented:
http://exchangeserverpro.com/exchange-server-2013-ssl-certificates/ a good site for reference of what Exchange 2013 requires from a certificate point of view. Verify that all of the Heading sections are correct in your certificate.
0
 
Adam BrownSr Solutions ArchitectCommented:
What is possible is that you have an Internal Host Name (mail.company.local, for instance) for the server that is not listed on the certificate. This is perfectly fine and Exchange will work properly without certificate errors as long as users don't attempt to access the server using a name that isn't on the certificate. You can get rid of the error by modifying your Exchange Virtual Directory internalURLs to reflect the names listed on your SSL cert. http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/ has a good guide and script that will help you do that.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now