We have already demonstrated the installation of Exchange Server 2007 SP1 in the Step-by-Step Screencast:
How to Install Exchange 2007 SP1 on Windows Server 2008

The installation process generates and installs a temporary Self Signed Certificate which allows you to start and use Exchange Server 2007 immediately. Again, this certificate is provided as a temporary solution and Microsoft recommends that it is replaced with a Commercial Certificate. Using a SelfSigned certificate poses a security risk to your users. Also, you can not use ActiveSync and Outlook Anywhere with this certificate. In addition, the remote users get a Pop-Up window, warning them about the certificate when opening Outlook Web Access.

Ideally, you should be purchasing and installing a Multiple Domain (UCC) SSL certificate and we are publishing a Step-by-Step Screencast about this too.

There are cases when you want to use a Single Name SSL certificate – like the GoDaddy Turbo SSL certificate. The reason for this decision could be that you already have purchased such a certificate, the price of the UCC certificates, or simply because you are running a pilot project for testing purposes.
We have already demonstrated the installation of a Single Name GoDaddy SSL certificate in IIS6 – How to Install GoDaddy SSL Certificate in IIS6, and in IIS7 – How to Install GoDaddy SSL Certificate in IIS7

The steps outlined in the above Screencasts are still valid, though you should be aware of the following when installing a Single Name SSL Certificate on Exchange Server 2007:

● You can not use such a certificate, if you have the Unified Communications role installed
● You have to perform additional configuration steps when you are replacing the Self Signed certificate generated during the Exchange 2007 installation with a Single Name Certificate – in short, this requires modifying the SCP (Service Connection Point) and adjusting the Exchange Web Services URL. If you skip these steps, you will experience problems with Outlook 2007 clients.

● Configuring and using Outlook Anywhere requires additional and extra steps too. To keep things simple and straightforward, we will demonstrate the configuration of Outlook Anywhere with a Single Name SSL certificate in a separate Screencast.

In the following Screencast, we will demonstrate the installation and configuration of a GoDaddy Single Name SSL Certificate in Exchange Server 2007. We start by generating and submitting a CSR (Certificate Signing Request), then we download and install the certificate, perform the necessary extra steps to make this certificate work fine in Exchange 2007 environment, and finally, we test the certificate.
In our demo, we are using a Single Exchange Server 2007 scenario. You can download the text file with Exchange Management Shell commands, used in Step3 here.

Step 1 In this step, we take a look at the Self Signed certificate, generated by the Exchange 2007 installation, which is about to be replaced. Then, we generate a CSR (Certificate Signing Request), activate the Certificate credit at GoDaddy.com, and finally, submit the CSR.

Step 2 Next, we demonstrate how to download and extract the ZIP file with GoDaddy Intermediate Certificates and our Single Name SSL certificate. We proceed with importing GoDaddy Intermediate Certificates, and then our SSL certificate in the computer Certificates Store. It is important to follow the same order – first import the Intermediate certificates, then – the Exchange certificate. Finally, we check that our Certificate is successfully placed in the Certificates Store and confirm its Validity, Issuer, Common Name, and Certification Path.

Step 3 We haven’t enabled yet the new SSL certificate for the available Exchange Services. Before we proceed with this task, we configure split DNS, modify the SCP and adjust the Exchange Web Services URL. Once we confirm the result, we proceed enabling the SSL certificate for IMAP, POP, IIS and SMTP Services in Exchange Management Shell, and perform some final adjustments in Exchange Management Console.

Step 4 In the last step, we test the new certificate from clients on the local network and at a remote location.