Solution
This tutorial will be given in 3 parts. All parts must be completed, but you may find that either Part I and/or Part II may already be completed depending on your security settings and the version of your Windows Server. If the certificate installation is a renewal of an already existing QuoVadis certificate, you may not need to do Parts I and II as you should already have installed the certificates previously. The intermediate files (Part II) must also be installed to ensure that some browsers do not show a certificate error.
Part I - Installing the Root Certificate
Generally, your Windows Server should have the QuoVadis Root certificates installed, however there have been cases where they have not been. When you install the SSL certificate, if the root certificate is not present, the system will prompt you to trust it, which will also install it.
First you must open the Microsoft Management Console.
- Click on Start and then type MMC. This should display "mmc - Run command" as the best match. Click on it to open the Microsoft Management Console.
- The Console1 window will appear.
- Click on File at the top and then select Add/Remove Snap-in... Alternatively, you can press Ctrl + M.
- In the Add/Remove Snap-in window, click on the Add... button at the bottom. This will open a third window named Add Standalone Snap-in.
- Scroll down in the Add Standalone Snap-in window and find the Certificates component. Once found, highlight it and click on the Add button at the bottom. Alternatively, you can double-click on Certificates.
- In a new window, you will be given 3 options for which account you want the certificates snap-in to manage.
- Select the Computer account radio button and click on the Next button.
- At the next screen, click on the Finish button.
- Click on the ">" sign next to Certificates (Local Computer) to expand it (if it isn't already expanded).
- Locate and expand the Trusted Root Certification Authorities store and the click on the Certificates folder underneath it.
- In the right hand pane, you should see a list of certificates. Click on any certificate that you see and press the letter "Q" on your keyboard to fast-track to the QuoVadis root certificates. Verify that you have the correct Root CA certificate in this list of certificates in the right hand pane. The correct certificate is shown and available for download within the certificate download page within Trust/Link. If this certificate is in the Trusted Root Certification Authorities store, then you can skip to Part II to check for the Intermediate Certificate. If this certificate is not installed, then the next steps will guide you through the process of installing this file.
- Place the certificate in a directory where it can be accessed by the server.
- Right-click on the Certificates folder underneath the Trusted Root Certification Authorities folder and in the drop-down menu, select All Tasks and then click on Import.
- The Certificate Import Wizard will appear. At the welcome screen, click on the Next button.
- You must specify the file to import. Click on the Browse... button and find and select the Root CA certificate. Once selected, it should appear in the File name: field. Click on the Next button.
- On the next screen, the option for Place all certificates in the following store should be selected by default and in the Certificate store: field should be Trusted Root Certification Authorities. Click on the Next button.
- At the summary screen, click on the Finish button.
- You should get a message that reads, "The import was successful."
Part II - Installing the Intermediate (chaining) Certificate
Part II explains how to install the intermediate files that are required. QuoVadis uses an intermediate certificate that must be installed on the server to prevent errors in certain browsers. You may want to go through these steps and if the intermediate certificate is not installed, then please obtain it and follow through with the rest of Part II. Part II assumes that you currently have the Microsoft Management Console open. If you do not, you can find the instructions in Part I of this guide, steps 1-8.
- Click on the ">" sign next to Certificates (Local Computer) to expand it.
- Locate and expand the Intermediate Certification Authorities store and then click on the Certificates folder underneath it.
- In the right hand pane, you should see a list of certificates. Verify that you have the correct Intermediate CA certificate (Chain) in this list of certificate in the right hand pane. The correct certificate is shown and available for download within the certificate download page within Trust/Link. If this certificate is in the Intermediate Certification Authorities store, then you can skip to Part III. If you do not, then the next steps will guide you through the process of installing this file.
- Place the certificate in a directory where it can be accessed by the server.
- Right-click on the Certificates folder underneath the Intermediate Certification Authorities folder and in the drop-down menu, select All Tasks and then click on Import.
- The Certificate Import Wizard will appear. At the welcome screen, click on the Next button.
- You must specify the file to import. Click on the Browse... button and find and select the Intermediate CA (Chain) certificate. Once selected, it should appear in the File name: field. Click on the Next button.
- On the next screen, the option for Place all certificates in the following store should be selected by default and in the Certificate store: field should be Intermediate Certification Authorities. Click on the Next button.
- At the summary screen, click on the Finish button.
- You should get a message that reads, "The import was successful."
Part III - Installing the Certificate
Part III explains how to install the SSL certificate and bind (assign) it to a website.
- Click on Start. Go to Administrative Tools and then click on Internet Information Services (IIS) Manager.
- Click on the name of the server in the left Connections pane. This should be the same server that you previously created a CSR for.
- In the middle pane, double-click on Server Certificates icon.
- In the right Actions pane, click on Complete Certificate Request...
- In the Complete Certificate Request window that appears, click on the ellipses (...) button and navigate to the server certificate you received from QuoVadis.
Note: Trust/Link by default supplies its certificates in PEM format with the file extension *.crt. When you browse for a certificate, IIS initially looks for a file with the *.cer extension. You will need to specify *.* in the drop-down in order to select your *.crt file. Alternatively, you could also rename your certificate file extension to *.cer.
- Type in a name for this certificate in the Friendly name: field.
Note: The friendly name is a name given to the certificate which is used to help differentiate between certificates.
- Select Personal from the drop-down list and then click on the OK button.
You should see your newly installed certificate in a list.
- Go back into the left Connections pane and expand the Sites folder and select the website that you want to bind (install) the SSL certificate to.
- Once the Web Site is selected, click on the Bindings... link in the right Actions pane.
- The Site Bindings window appears. Click on the Add... button.
- In the Add Site Binding window, change the Type: field to "https" by selecting it from the drop-down menu.
- In the SSL certificate: field, select the friendly name of the certificate that you installed. Once you have selected this, click on the OK button.
- Note: In most cases, the IP Address: field will be kept to All Unassigned unless the website has a specific IP Address it needs to be assigned too.
- Back in the previous Site Bindings window, you should see the binding for port 443 in the list. Click on the Close button once completed.
OCSP Stapling Support
Although optional, it is highly recommended to enable OCSP Stapling which will improve the SSL handshake speed of your website.
Windows Server 2016 automatically utilizes OCSP Stapling by default. No additional configuration is required.
You can read up on more on OCSP Stapling at https://support.quovadisglobal.com/KB/a415/what-is-ocsp-stapling.aspx.