T The Triage ManualTechnical Guides for IT Emergencies
P1 · PKI & Certificate Management

Expired SSL/TLS Certificate Causing Service Outage — IIS, RDS, Exchange or ADFS

An SSL/TLS certificate has passed its NotAfter date causing browsers to block access, RDS clients to refuse connection, Exchange to stop processing mail, or ADFS federation to fail. Emergency path is renew, import to machine store, and rebind to the affected service.

Indicators

Likely causes

Diagnostic steps

  1. Confirm expiry: openssl s_client -connect hostname:443 2>/dev/null | openssl x509 -noout -dates; or PowerShell: Get-ChildItem Cert:\LocalMachine\My | Where-Object {$_.NotAfter -lt (Get-Date).AddDays(30)}
  2. Identify all services using the expired cert: IIS bindings, RDS deployment properties, Exchange certificate assignments, ADFS token-signing/decrypting certs
  3. Obtain replacement certificate from CA (commercial CA, internal AD CS, or Let's Encrypt) — ensure all SANs match previous certificate
  4. IIS: Import PFX to certlm.msc (Local Machine > Personal); IIS Manager > Site > Bindings > edit HTTPS binding > select new certificate
  5. Exchange: Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path cert.pfx -Encoding byte -ReadCount 0)) -Password (ConvertTo-SecureString -String 'pass' -AsPlainText -Force); then Enable-ExchangeCertificate -Thumbprint <new> -Services SMTP,IIS,POP,IMAP
  6. RDS: Server Manager > Remote Desktop Services > Deployment Properties > Certificates — reassign per role (Gateway, Broker, Web Access, Licensing)

Resolution path

Prevention

Tools

ssltlscertificateexpirediisexchangerdsadfspkirenewal