Self-service installation
Windows / IIS
Choose: IIS / modern Windows — encrypted PFX
Prefer automatic replacement? Set up automatic renewal for supported Windows / IIS configurations. These written steps and videos remain the manual-installation fallback.
Before you start
- Confirm you administer this server and can restore its current configuration.
- Check the certificate is production-issued, unexpired and covers every intended hostname.
- Check DNS points to the intended server, including any IPv6, proxy or CDN path. A certificate does not change DNS.
- Download the matching package; store it outside the web root and keep its password separately.
These steps target modern Windows IIS with Server Certificates and site Bindings available. Older Windows versions may not import the AES-protected PFX. Check your version before making changes.
Watch a recorded installation
Recorded scripted PowerShell session on an isolated demo server. Every displayed operation was executed. Silent, with English captions. Pause or use full screen to read commands. Disposable .test certificates are not publicly trusted; use your own hostnames and normal public trust in production. Passwords and MFA are supplied privately and are not shown.
Read the recorded transcript · Watch the quick slide overview
Jump to a chapter
Chapters are ready when video metadata loads.
Install step by step
Sign in, open the issued production request and download the IIS PFX using a fresh second factor and a new package password. Keep the password separately; staging certificates are not publicly trusted.
Back up your existing IIS configuration and note the site's current bindings and certificate. Transfer the encrypted PFX securely to the correct server, outside its website folder.
Open IIS Manager, select the server, open Server Certificates and choose Import. Select the PFX and enter its password locally. Confirm the imported certificate has the expected names, expiry and fingerprint. The import must include its private key.
Select only the intended website and open Bindings. Add or edit its HTTPS binding on port 443 with the exact hostname and the imported certificate. On a shared IP, require Server Name Indication. Configure apex and www separately when needed; do not replace other sites' bindings.
Open each HTTPS hostname from another device. Check normal browser trust, the served certificate fingerprint and the intended page. A wildcard covers one subdomain level; the apex needs its own SAN. DNS caching may still direct visitors to an old server.
For renewal, import the replacement and update each intended binding. Keep the previous working configuration for rollback until checks pass. Remove temporary transfer copies securely, preserving your protected recovery copy. If you need hands-on help, request a separate quote.
Illustrative configuration
Use your own paths and hostnames. Preserve the rest of your existing configuration.
IIS Manager → server → Server Certificates → Import IIS Manager → intended site → Bindings → https / 443 / exact hostname / SNI Choose the matching certificate, then verify every hostname over HTTPS.
Verify before calling it done
- Use another device to open every intended HTTPS hostname without bypassing certificate warnings.
- Check the correct website loads and the served certificate has the expected names, expiry and SHA-256 fingerprint.
- Check apex and www independently. A wildcard does not automatically include the apex.
- Confirm unrelated sites still work. Keep rollback material protected until checks pass.
Troubleshooting
The import worked, but IIS still serves the old certificate
Check the exact site's HTTPS binding, hostname, port and selected certificate. With a shared IP, verify SNI. Repeat for each hostname. A reverse proxy or another DNS destination may serve a different certificate.
The PFX will not import or its private key is missing
Use the full PFX package and its exact package password, not the public PEM. Confirm your Windows version supports the package encryption. Do not replace existing certificates or weaken protection to force an import.
The browser reports a name or chain error
Check the exact hostname, production status and DNS destination. For PEM servers, use fullchain.pem with the matching private key. Check any reverse proxy/CDN separately. Do not ignore the warning; restore the working configuration if verification fails.
Replacing an expiring certificate? Use the renewal checklist. Need assistance? Request a separate quote.