What Windows and IIS do on their own
IIS serves the certificate that each HTTPS binding references by thumbprint, from the Local Machine store (Personal or Web Hosting). A renewed certificate has a new thumbprint, so renewing is only half the job: the bindings have to move to it.
IIS 8.5 and later can do that for you. Certificate Rebind, enabled with Enable Automatic Rebind of Renewed Certificate under Server Certificates, creates a scheduled task that runs when Windows renews a certificate and moves the bindings from the old thumbprint to the new one.
Rebind only reacts to renewals made by Windows certificate enrolment, which in practice means certificates from your own Active Directory Certificate Services with autoenrolment. A certificate from a public CA that you import is a new certificate to Windows, so Rebind does nothing.
Public certificates on IIS
For publicly trusted certificates, IIS needs an ACME client on the server or an external tool that installs the certificate. Common Windows ACME clients include win-acme, Certify The Web and Posh-ACME. They request the certificate, import it into the store, update the bindings and schedule the next renewal.
Whichever you use, check three things after each renewal:
- The binding for each site and hostname points at the new thumbprint, including bindings that share one certificate.
- The private key is readable by the account the service runs as.
- The served certificate, checked from outside, is the new one with the full chain.
Where it gets hard
- Many servers. Each server renews alone, so a failure on one is easy to miss.
- Shared certificates. One certificate is often bound to several sites and IP bindings, and a tool that updates only one leaves the rest on the old certificate.
- Central Certificate Store. Farms that use the IIS Central Certificate Store read PFX files from a share, which needs a different process.
- Lifetimes. Public certificates are moving toward 47 days, explained in certificate lifetimes are falling to 200, 100 and 47 days. Planning for this is covered in how to stop certificate expiry outages.
How clm.mt handles IIS
The clm.mt Windows agent renews the certificate through ACME with DNS-01 or from AD CS, installs it in the My or Web Hosting store, moves the IIS bindings that use it, and checks the served certificate. It does not write to the IIS Central Certificate Store.
clm.mt status
Supported for Microsoft IIS. Native Windows Server 2022; My and WebHosting stores. IIS Central Certificate Store is refused. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AD CS certificate autoenrollment and auto renewal
- AWS load balancer certificate renewal with ACM
- Azure Key Vault certificate auto renewal, and when it does not happen
- F5 BIG-IP SSL certificate renewal automation
- FortiGate ACME certificates and automatic renewal
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation