This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello everybody!
Recently installed a DAG cluster of 4 servers. Everything is configured, all certificates have been linked to IIS and SMTP services and to reception connectors for TLS connections - at the same time, a *.WildCard certificate with a certain fingerprint is used.
Now I see a notification in the logs that the certificate for the servers themselves (including the other three) initiates notifications 12018 that the certificate expires on May 4 (as well as the WildCard certificate itself) and everything would be fine, but for some reason the fingerprint of the WildCard certificate on the server itself is completely different.
The actual screen:
Question: Tell me what this might mean and will it affect the operation of any Exchange services if this certificate is not renewed to the server, or do I misunderstand this information? Or is it that in the event there is a ReceiveConnector TLS Certificate to which the WildCard certificate is attached?
Thanks!
Hi, not sure what you mean by completely differently? The wildcard cert thumbprint is the same as in the event log thumbprint, yes?
Thank you, the question is removed. This is a notification from the server itself - that the WildCard certificate, which is installed on this server, will expire on a certain date.
Ok, then yes, renew that cert before then, and then enable for SMTP and IIS.
You can do that following:
then assign to services:
If prompted to overwrite to existing SMTP Exchange default cert when assigning services, say no.
Thank you, the question is removed. This is a notification from the server itself - that the WildCard certificate, which is installed on this server, will expire on a certain date.