You can verify this by going to the MMC certificate list and hitting F5 -- if successful, your certificate will now have a small key in its icon.
You will then be able to select your certificate from IIS.
Oh and btw, why don't my empty lines show up in the final post once I've posted it?
How can you fix this issue without doing a new request or contacting someone for the key (if, for instance, it's the day before a launch? Due to the timeframe and some other issues, getting the key from the provider was not possible.
I found the following solution here (under pixelloa's comment) and thought it would be good to have the answer on Stack Overflow as well.
(Running IIS10 on Server 20R2) When I Created a Certificate Request, gone through the process of Re-keying and gone through the process of "Complete Certificate Request" I was able to sucessfuly configure "Bindings..." without the certificate disappearing.
You can export a pfx from IIS on another server, if you have a server with the cert successfully installed.
MOSS 2007 should always use the certificate specified in IIS.
I tried removing the old certificate from the local computer's personal certificate store. The secure site still uses the old certificate despite the removal. I'm starting to consider rebooting the server, which I'm very reluctant to do.
If this fails, your private key is no longer available and you need to send a new certificate signing request to the signing authority.
This happens when the installed certificate does not contain your private key.
I identified the server where I had generated the Certificate Request and successfully installed the new cert there. You need to ensure you are installing on the same server as the one you created the "CSR" file from. If you got your cert, just ask to re-key, it will ask for a new CSR file. Go Daddy allows you to re-key, just find the cert, and hit "manage" I am not expert at this stuff, but this managed to work. Now, your certificate does not disappear anymore and you can bind Website over SSL.
From that server I was able to export a pfx and then import the pfx version on the rest of the servers. A great resource: https://blog.lextudio.com/the-whole-story-of-server-certificate-disappears-in-iis-7-7-5-8-8-5-10-0-after-installing-it-why-b66e802baa38 certificate request, and hence when you import the (now signed) certificate associated with your first request, it will not have a private key associated with it.
Thanks Paul, that SSL Diagnostic utility shed some light on the situation. What I've looked up, it seems that all configuration should be done from IIS, and not from MOSS itself.