Some certificates were originally created with the option to not run an installer. How can I change this so that renewals use an installer? Also how can I tell which certificates will use an installer next and which will not?
My web server is (include version): IIS 10
The operating system my web server runs on is (include version): Windows server 2016 Datacentre
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):v1.9.11.2
When I use LetsEncrypt on my server, using the Win-acme interface, I get an option to run an installer script after the certificate has been created. Some of my domains were originally set up to not use an installer - I originally set up bindings manually. This continues when the certificate is renewed - I have to set up bindings manually each time. I would like to change this so that the bindings are automatically set up. I can do this when I set up a new domain, but can’t find a way of changing the way the renewal of old domains works.
Your question strikes me as pretty specific to WinACME. Someone in the forum may know the answer but if you don’t get a reply I’d suggest trying to open an issue with the maintainers of WinACME seeing if they know the answer.