Exchange 2016 SSL Cert binding

PaulH 41 Reputation points
2022-02-10T18:54:32.29+00:00

Recently added a public SSL Cert to an Exchange 2016 server however the server doesn't want to let go of the self assigned cert for SMTP.

Via EMC I've assigned the new cert to SMTP and IIS. Now there are checks in the boxes however the boxes are grayed out. Not a big deal since that's what I want.
However, also in EMC the default self assigned cert has grayed out check boxes for SMTP, IMAP, POP, and IIS. I don't care about IMAP and POP but I want this removed from SMTP and IIS but I can't uncheck them in EMC.

In EMS I list the certs to get their thumbprints with "Get-ExchangeCertificate" then run the following command:

Enable-ExchangeCertificate -Services None -Thumbprint <SSL Cert Thumbprint>

It appears to execute properly, there are no errors however when I refresh or even reload EMC the self assigned cert is still bound to those services.

When I use the Digicert tool to see what's being presented IIS shows the public cert but SMTP is still using the self assigned cert.

Do I have to completely remove (delete) the self assigned cert to get this working properly or is there something else that I am missing?

Exchange Exchange Server Management
{count} votes

2 answers

Sort by: Most helpful
  1. Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator
    2022-02-10T20:23:03.613+00:00

    Yea, thats normal. The Backend "Exchange Server" certificate ( I think thats the one you are referring to), is bound to the backed IIS site so you dont want to remove and its ok if its set for SMTP as well. If things are working as expected, then you should be good to go!

    That command , well, it does nothing really :) Enable-ExchangeCertificate -Services None -Thumbprint <SSL Cert Thumbprint>

    More from my blog post:
    https://ehloergosum.com/2020/01/25/renewing-that-pesky-microsoft-exchange-certificate/

    1 person found this answer helpful.

  2. Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator
    2022-02-11T22:23:38.457+00:00

    So when you enter the host name in the checker, it connects to the receive connector and then Exchange looks for a cert that matches the FQDN, thats why you are seeing this.
    Old doc, but still applies:
    https://learn.microsoft.com/en-us/previous-versions/office/exchange-server-2007/bb430748(v=exchg.80)

    And, thats ok! Opportunistic TLS isnt looking to trust the cert, its only to see if you have a cert.

    With hybrid SMTP inbound connections, when you run the wizard, you will ask what cert to use ( choose the 3rd party one) and the wizard will bind that to the right connector with the Tls Subject and Issuer

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.