Configure Windows CA & IIS SSL
Budget: $30 – $250 USD
I already have a small lab in place—a Windows-based DNS server, a standalone root CA on its own Windows box, an IIS web server, and a Windows client. Despite that, any browser that reaches the site still flashes a certificate warning.
I want an experienced Windows PKI specialist to walk me through (or remotely carry out) the full certificate life-cycle so the site loads over HTTPS with a clean-green padlock:
• Issue a proper server certificate from my existing root CA, using the site’s DNS name.
• Import the root certificate into the correct stores so every Windows client trusts it.
• Bind the new certificate in IIS and confirm TLS 1.2+ is negotiated.
• Prove the result—no warnings in Edge, Chrome, or Firefox.
Please stick to native Windows tools—Certification Authority snap-in, certreq / certutil, and IIS Manager—so I can repeat the process later. A short step-by-step write-up or recorded session at the end will count as acceptance criteria.
I want an experienced Windows PKI specialist to walk me through (or remotely carry out) the full certificate life-cycle so the site loads over HTTPS with a clean-green padlock:
• Issue a proper server certificate from my existing root CA, using the site’s DNS name.
• Import the root certificate into the correct stores so every Windows client trusts it.
• Bind the new certificate in IIS and confirm TLS 1.2+ is negotiated.
• Prove the result—no warnings in Edge, Chrome, or Firefox.
Please stick to native Windows tools—Certification Authority snap-in, certreq / certutil, and IIS Manager—so I can repeat the process later. A short step-by-step write-up or recorded session at the end will count as acceptance criteria.
Related categories:
System Admin
Web Security
Active Directory
DNS
Microsoft
Windows Server
Network Security
SSL