Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
This workflow enrolls a server certificate, verifies its identity fields, and binds it to an IIS HTTPS endpoint.
Prerequisites
- Administrative access to the affected servers.
- A verified backup and approved maintenance window.
- A pilot system for testing before production rollout.
Step-by-step procedure
- Confirm the public hostname and DNS ownership.
- Generate a request with the approved template.
- Install the issued certificate in Local Computer Personal.
- Bind the thumbprint to the correct IIS site and hostname.
Commands
Get-Certificate -Template "WebServer2025" -DnsName "www.contoso.example" -CertStoreLocation Cert:\LocalMachine\My
Get-ChildItem Cert:\LocalMachine\My | Sort NotAfter -Descending
Get-WebBinding -Protocol httpsVerification
A remote TLS client receives the expected certificate chain, hostname, and valid dates.
Rollback
Restore the former IIS binding and certificate thumbprint, then remove the unused test certificate.
Security and operations
- Use least privilege and document all production changes.
- Replace example addresses and names with approved values.
- Review relevant Windows event logs after implementation.
A certificate request is only half of the IIS deployment
Choose the template your CA administrator actually published and authorized for the server. The WebServer2025 label in the sample is an example name; it does not guarantee that the template exists or is appropriate for every Windows Server version. Confirm the intended DNS names before requesting the certificate.
After enrollment, verify that the certificate includes the required private key, a suitable server-authentication purpose and every hostname clients use. Check the issuing chain and validity period. Selecting the certificate with the latest expiry date is not a reliable way to identify the right certificate when several services use the same machine store.
Create or update the IIS HTTPS binding using the intended hostname, port and SNI behaviour. Keep other sites’ bindings intact. Test externally with the production hostname, because a local IP-address request may select another site or trigger a name mismatch.
Record how renewal will occur and who will update the application binding if that does not happen automatically. Keep the existing working certificate available during the change window, and restore its binding if the replacement fails validation. Do not disable client trust checks as a substitute for repairing a chain or name problem.
Related resources
Canadian Windows VPS and RDS hosting is available from managed Windows VPS hosting. Also review the official Microsoft Windows Server documentation.