I've installed a GoDaddy wildcard certificate on my Win2003/IIS6 Server. It shows up in the Intermediate Certificate Authorities area of the MMC Certicates. All looks fine: Issued to: *.mydomain.com; Issued By: Go Daddy…;Expiration Date 11/2/2012; Intended Purposes: Server Authentication, Client Authentication
But, when I go to assign it to a website in IIS, it doesn't show up in the Available Certificates box.
I mostly followed these instructions from GoDaddy. I did just now realize that rather than choosing the .p7b file in step 12, I chose the .crt file. I tried re-following the steps and chose the .p7b file this time but it didn't make a difference.
What am I missing?
I've looked at this similar thread: IIS 6 Available certificates list
But his problem was his cert wasn't valid for Server Authentication, mine is.
Update
I deleted the ceertificate from the Intermediate store and installed it using the .p7b in the Personal store and then I can see the Certificate and it seems to link up properly but when I try to browse to the site using https, I get "The connection was interupted". So something still isn't right.
I ran SSLDiag and it states "You DON'T have a private key that corresponds to this certificate".
I tried running: certutil -repairstore my "mythumbprint" in the command line but that failed.
Best Answer
It's installed in Intermediate Certificates, not Personal Certificates; it's not installed correctly.
As David said, you can import with a private key if you have a bundle; if you did the full certificate request process from this system then something went wrong.
Can you provide additional detail about what steps to you to request and import this certificate?