Changes

Based on this forum post http://forums.contribs.org/index.php/topic,46752.0.html

Based on this forum post http://forums.contribs.org/index.php/topic,46752.0.html

This example refers to migrating a free StartCom SSL certificate on a Windows SBS2008 Server to SME.

This example refers to migrating a free StartCom SSL certificate from a Windows SBS 2008 Server to a SME server.

StartCom give out free SSL only certificates compatible with IE and Firefox which are only good for HTTPS.

StartCom give out free SSL certificates compatible with IE and Firefox which are only good for HTTPS.

To migrate the SSL certificate they already have (rather than buy a new one) follow these instructions: http://rackerhacker.com/2007/03/23/exporting-ssl-certificates-from-windows-to-linux/

To migrate the SSL certificate (rather than buying & installing a new one) follow these instructions: http://rackerhacker.com/2007/03/23/exporting-ssl-certificates-from-windows-to-linux/

The end result is you have the two files, .key and .crt. Do not implement the last three steps re importing the certificate to Apache, follow the instructiosn here: http://wiki.contribs.org/Certificates_Concepts#Commercial_certificates

The end result is you have the two files, .key and .crt. Do not implement the last three steps re importing the certificate to Apache, instead follow the instructions here: http://wiki.contribs.org/Certificates_Concepts#Commercial_certificates

=====Testing the migration before final deployment=====

=====Testing the migration before final deployment=====

Once the server is restarted, you can test the certificates, without disrupting the customers site, from a Windows workstation by doing:

Once the SME server is restarted, you can test the certificate from a Windows workstation (without disrupting the customers site) by doing:

Add the FQDN and internal IP Address of the SME server to the file c:\windows\system32\drivers\etc\hosts in the same format as the sample in the file.

1. Add the FQDN and internal IP Address of the SME server to the file  

Ping the FQDN of the SME server (the public FQDN, not the local one) to test it resolves correctly to the new SME server's internal IP address.

 

 

2. Ping the FQDN of the SME server (the public FQDN, not the local one) to test it resolves correctly to the new SME server's internal IP address.

Then open a web browser to the SME server using HTTPS.

Then open a web browser to the SME server using HTTPS.