An IIS certificate renewal is complete only when the intended site presents the new certificate. Obtaining a certificate and installing it are separate responsibilities, even when one client automates both. Keeping that distinction visible makes failures much easier to diagnose.
win-acme can handle the Windows renewal and IIS installation workflow. SimpleACME supplies delegated DNS-01 updates, which are useful when a site is private or when HTTP challenge routing is not the simplest validation path.
Start with the site's real names
Inventory the hostnames and IIS bindings clients actually use. A certificate for one name does not cover an unrelated name simply because both bindings point to the same server. A wildcard matches a specific level of subdomains, not every possible descendant.
Choose single-domain or wildcard coverage deliberately. For a public website whose existing HTTP validation already works, the native HTTP-01 path may remain appropriate. For internal IIS applications, delegated DNS-01 can remove the inbound challenge requirement.
Configure DNS validation independently
Create the domain registration in SimpleACME, add its challenge CNAME and verify it publicly. Store the issued update credentials where the win-acme renewal identity can read them securely.
Use the client's supported DNS script validation workflow with reviewed PowerShell code. The create hook sends the supplied authorization value, handles update failures and waits for DNS visibility. Keep its output useful for diagnosis without exposing authentication headers.
Use an installation step that knows IIS
Where it fits the deployment, prefer win-acme's IIS installation integration to a custom script that guesses at certificate bindings. Review which site and binding will be updated, including SNI behavior and the intended certificate store.
If you need custom deployment, make the target explicit. Importing a PFX and selecting a thumbprint should not silently replace every binding on the server or delete the old certificate before validation.
Verify unattended behavior
- Test the workflow in staging with a clearly separate test certificate.
- Confirm the scheduled-task identity and credential-file permissions.
- Inspect the target binding after installation.
- Connect using the real hostname and verify the certificate and chain.
- Confirm that future renewal uses the saved validation and installation settings.
SimpleACME's timeline can confirm a TXT change, while win-acme and IIS provide issuance and deployment evidence. Use all three views when investigating a failure.
The result is a repeatable Windows workflow without a DNS-provider zone token on the renewal host. Start with the win-acme integration guide and the protected subscriber examples, then adapt the installation stage to the exact sites you operate.