Let’s Encrypt→IIS
From issuance to renewal.
A Windows service automatically obtains, installs and renews free Let’s Encrypt certificates for your IIS sites.
WINDOWS SERVER · IIS · LET’S ENCRYPT
Your servers’ SSL certificates
renew themselves.
Technoera Server Assistant obtains, installs and renews Let’s Encrypt certificates automatically, with checks and automatic rollback if something goes wrong. It runs on Windows Server with IIS and is designed to manage Linux servers too, from a single console.
Automation on your server.
Let’s Encrypt certificatesPrivate keys stay on the serverAutomatic verification and rollback
WHY NOW
Shorter lifetimes.
Less room for surprises.
The maximum lifetime of public TLS certificates is shrinking. Manual renewal becomes a recurring task: a missed expiry means a browser security warning for your visitors.
Automated renewal becomes part of everyday website operations.
- Before 15 March 2026398 days
- From 15 March 2026200 days
- From 15 March 2027100 days
- From 15 March 202947 days
Limits apply according to issuance date. They do not represent the specific lifetime of Let’s Encrypt certificates.
Source: CA/Browser Forum, Baseline Requirements 6.3.2 (ballot SC-081v3)
HOW IT WORKS
From setup to renewal.
- Windows Server + IIS
Install.
Install the service on your Windows Server with IIS.
- www · api · *Your domains
Assign your sites.
Configure the sites to manage and their domain validation. For wildcards, set up the initial DNS delegation.
- Automatic renewal
Let it handle renewals.
The service obtains, installs and renews certificates. If approval is enabled, it asks before replacing a certificate.
THE WINDOWS CLIENT
Let the service handle
the recurring work.
From individual domains to wildcards, with the tools you use every day on Windows Server.
*.domain.extDNS → delegation
Set up DNS once.
For wildcard certificates such as *.domain.ext, you set up a DNS delegation record once. Renewals then continue without further DNS changes.
HTTP :80→SSL/TLS
Individual domains. No DNS changes.
Individual domains are validated automatically over port 80. No DNS validation records to add at each renewal.
One IP addressMultiple domains · SNI
More domains. One IP.
Use different certificates and custom domains for sites on the same IP address, without buying additional IP addresses.
Action neededApproval · Renewal · Expiry
Know when you need to act.
A pending approval, a blocked renewal or an approaching expiry: receive an email alert when human action is needed.
Desktop+CLI
Work your way.
A modern desktop application with a Windows 11-style interface, plus a command line. All operations are logged, including in Windows Event Viewer.
BUILT FOR PRODUCTION
Automatic.
With the right checks.
Replacing a certificate goes beyond installation. Server Assistant checks beforehand, verifies afterwards and rolls back if something goes wrong.
Your keys stay with you.
Private keys stay on your server. For issuance and validation, it communicates only with Let’s Encrypt and, for delegation, your chosen DNS service.
Check the names.
Before replacement, it checks that the new certificate covers every name used by the sites.
Ask for approval, if enabled.
You can require human approval before an active certificate is replaced.
Verify the result.
After replacement, it checks that each site serves the new certificate.
Roll back when needed.
If something goes wrong, it automatically restores the previous certificate.
THE PLATFORM
Multiple servers.
One place to manage them.
Server Assistant is designed as a platform: a service on every Windows server with IIS, a connector for Linux servers (where renewal clients already exist) and a central console (administration website) from which to follow the renewals of all servers.
The service for Windows Server with IIS is the part you can already try on your servers.
Windows + IISConsoleLinux · connector
ON THE SERVER
Windows Server + IIS
Local service · automatic renewal
AT THE CENTRE
Console
Renewals of all servers, Windows and Linux
WHO IT IS FOR
For those keeping client websites online.
And their own business websites.
IT partners and web agencies
Manage certificates for client IIS websites without turning every renewal into a manual task.
System administrators
Keep control of replacements with verification, rollback and operation logs.
Small and medium businesses
Reduce recurring certificate work and the risk of missing an expiry.
FAQ
Questions,
before you start.
How can I try it?
Contact Technoera to try the service for Windows Server with IIS on your servers.
Do I need to change DNS?
Individual domains are validated over port 80, without DNS changes for validation; the domain must already reach the server. Wildcards require an initial DNS delegation record. After setup, renewals are automatic.
Does port 80 need to be reachable?
For HTTP-01 validation of individual domains, Let’s Encrypt must be able to reach the challenge path on port 80. Normal HTTP requests can be redirected to HTTPS by IIS: the service itself answers the validation requests on port 80, before IIS.
Can I approve replacements on production sites?
Yes. The application can request approval before replacing an active certificate. It checks name coverage, verifies the certificate actually served after replacement and restores the previous one if something goes wrong.
Where do private keys stay?
Private keys stay on the server. For issuance and validation, the application communicates only with Let’s Encrypt and, when delegation is used, your chosen DNS service.
What about Linux servers?
On Linux servers, several clients already handle automatic renewal: the platform is designed to connect them to the console through a connector, so that the renewals of all servers can be followed from one place. The service you can already try on your servers is the one for Windows Server with IIS.
LET’S TALK
Try it on your servers.
Contact Technoera to learn about Server Assistant and try it in your environment.
Contact us on Technoera
Continue to the Technoera website for the contact form.