Maybe I'm spoiled. Maybe I'm just used to the efficiency and intelligence of Apache. Maybe I don't want to do 15 steps to replace an SSL certificate like it seems to be the case in IIS. Maybe I prefer the console way with vim... But some solutions need to be run on Windows and if one needs to renew a certificate/to replace an existing certificate with a new one, some more steps need to be done in order to import the certificate. Having done it today, and won't be using it for a while, I am sure I will forget these procedure soon again, so I made a HowTo of it: Import SSL Certificates in Windows Server 2003/2008 and configure IIS Maybe it'll be of service.
|