We’re deploying the Certify SSL Manager on a few Servers running Microsoft Exchange. Automated certificate renewal is working fine and the certificate is added to the IIS pool.
But: the certificate is not bound to the Exchange services (SMTP, POP3, IMAP), so even after requesting and installing the new certificate, Exchange will still identify with the previous certificate.
Is there a way to automate the service bindings?
@MEwald for advanced deployment of certificates you need to use post-request scripting (powershell). You can get to this by checking ‘Show Advanced Options’ and opening the Scripting tab. We have a few example scripts but you need to really copy and adapt as required, you can find the examples under C:\Program Files\CertifyTheWeb\Scripts\Common
I’m working on an update with a new feature called Deployment Tasks and intend to include an Exchange specific UI so you can select which Exchange services to apply the certificate to and also the option to defer some tasks until a maintenance window etc.
Also here’s a link to more info about scripting support: https://docs.certifytheweb.com/docs/script-hooks.html#example-enable-certificate-for-exchange-2013-2016-services-on-same-server
The above link is now at: https://docs.certifytheweb.com/docs/script-hooks#example-enable-certificate-for-exchange-2013--2016-services-on-local-server
Note that v5.x onwards has a basic Exchange deployment task which can be selected from the Tasks tab, or you can use your own powershell script as a powershell script task.