Skip to content

Export Exchange 2013 Certificate

Export Exchange 2013 Certificate using PowerShell

In this post, I will look at how to export an Exchange 2013 certificate with private key using PowerShell and how to verify if the certificate has the private key after export.

A certificate can be exported from the exchange server as a simple backup method or to import on any other devices. The Exchange admin console can also be used to export the certificate.

After the export, the certificate file will be password protected and will be a binary PKCS #12 file that contains the private key, and can be used on other servers.

To get started with the export process, the following cmdlet needs to be run in the Exchange Management Shell.

This cmdlet will give an output of the certificate thumbprint which we will use to export the needed certificate.

To continue and export the certificate, the following cmdlet can be executed.

The same export can be done from the Exchange admin console as well, to export from the Exchange admin console the following steps can be followed.

  1. Login to Exchange admin console
  2. Navigate to Servers then Certificates
  3. Select the server where you want to export the certificate from

  1. Select the certificate from the list of installed certificates and click on the more ( … ) options.
  2. Select Export Exchange Certificate from the list.

  1. Provide a valid unc path for the export and provide a password for the certificate file.

How do check if the certificate has the private key attached with it.

  1. Launch mmc using Run and open the certificate manager.

  1. Select the Local machine from the Certificate Manager.

  1. Open the certificate manager navigate to personal certificates and double click the exported certificate.

  1. On the general page at the bottom you will see a key and that means that the certificate was exported with the private key.

#ThatLazyAdmin

Sharing is caring!

Published inExchange 2013

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *