When you install Exchange Server, a self-signed certificate that's created and signed by the Exchange server itself is automatically installed on the server. However, you can also create additional self-signed certificates that you can use.
- The private key however is stored on the machine that generated the CSR (presumably the server requiring the cert, but not necessarily) and is NOT included in the contents of the CSR, and may not be derived from the CSR. It is kept private. In general terms, the server generating the CSR generates a key pair (public and private).
- Category: Create CSR Key – Step by Step Guide. How to Generate a CSR on Node.js; How to Generate CSR on Plesk Onyx (Version 17) How to Generate Private Key and CSR in cPanel? Create CSR on Microsoft Lync Server 2013; Generate CSR in Microsoft Exchange Server 2013 / 2016; Create CSR for FileZilla Server Using OpenSSL.
- When you create a certificate request you actually create two things: A private key, which remains safe on your server, and a Certificate Signing Request (CSR), which is a data file that contains the information a Certificate Authority like DigiCert® needs to create a public key to match your private key without compromising the private key.
You can create self-signed certificates certificate in the Exchange admin center (EAC) or in the Exchange Management Shell.
What do you need to know before you begin?
Estimated time to complete: 5 minutes.
Exchange self-signed certificates work well for encrypting communication between internal Exchange servers, but not so well for encrypting external connections, because clients, servers, and services don't automatically trust Exchange self-signed certificates. To create a certificate request (also known as a certificate signing request or CSR) for a commercial certification authority that's automatically trusted by all clients, servers, and services, see Create an Exchange Server certificate request for a certification authority.
When you create a new self-signed certificate by using the New-ExchangeCertificate cmdlet, you can assign the certificate to Exchange services during the creation of the certificate. For more information about the Exchange services, see Assign certificates to Exchange Server services.
To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the 'Client Access services security' entry in the Clients and mobile devices permissions topic.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.
Using Microsoft IIS to generate CSR and Private Key. IIS to generate a Private Key and CSR. Information Exchange. To convert it to RSA Private Key format.
Use the EAC to create a new Exchange self-signed certificate
Open the EAC and navigate to Servers > Certificates.
In the Select server list, select the Exchange server where you want to install the certificate, and then click Add .
The New Exchange certificate wizard opens. On the This wizard will create a new certificate or a certificate request file page, select Create a self-signed certificate, and then click Next.
Note: To create a new certificate request for a certificate authority, see Create an Exchange Server certificate request for a certification authority.
On the Friendly name for this certificate page, enter a friendly name for the certificate, and then click Next.
In the Specify the servers you want to apply this certificate to page, click Add
On the Select a server page that opens, select the Exchange server where you want to install the certificate, and click Add - >. Repeat this step as many times as necessary. When you're finished selecting servers, click OK.
When you're finished, click Next.
The Specify the domains you want to be included in your certificate page is basically a worksheet that helps you determine the internal and external host names that are required in the certificate for the following Exchange services:
Outlook on the web
Offline address book generation (OAB)
Exchange Web Services
If you enter a value for each service based on the location (internal or external), the wizard determines the host names that are required in the certificate, and the information is displayed on the next page. To modify a value for a service, click Edit () and enter the host name value that you want to use (or delete the value). When you're finished, click Next.
If you've already determined the host name values that you need in the certificate, you don't need to fill out the information on this page. Instead, click Next to manually enter the host names on the next page.
The Based on your selections, the following domains will be included in your certificate page lists the host names that will be included in the self-signed certificate. The host name that's used in the certificate's Subject field is bold, which can be hard to see if that host name is selected. You can verify the host name entries that are required in the certificate based on the selections that you made on the previous page. Or, you can ignore the values from the last page and add, edit, or remove host name values.
If you want a SAN certificate, the Subject field still requires one common name (CN) value. To select the host name for the certificate's Subject field, select the value and click Set as common name (check mark). The value should now appear bold.
If you want a certificate for a single host name, select the other values one at a time and click Remove ().
When you're finished on this page, click Finish.
You can't delete the bold host name value that will be used for the certificate's Subject field. First, you need to select or add a different host name, and then click Set as common name (check mark).
The changes that you make on this page might be lost if you click the Back button.
Use the Exchange Management Shell to create a new Exchange self-signed certificate
To create a new Exchange self-signed certificate, use the following syntax:
This example creates a self-signed certificate on the local Exchange server with the following properties:
Subject: <ServerName>. For example, if you run the command on the server named Mailbox01, the value is
Subject alternative names: <ServerName>, <Server FQDN>. For example,
Friendly name: Microsoft Exchange
Services: POP, IMAP, SMTP.
This example creates a creates a self-signed certificate on the local Exchange server with the following properties:
Subject: Exchange01, which requires the value
CN=Exchange01. Note that this value is automatically included in the DomainName parameter (the Subject Alternative Name field).
Additional subject alternative names:
Services: SMTP, IIS
Friendly name: Contoso Exchange Certificate
The private key is exportable. This allows you to export the certificate from the server (and import it on other servers).
The only required part of the X.500 SubjectName parameter value (the certificate's Subject field) is
Some Services parameter values generate warning or confirmation messages. For more information, see Assign certificates to Exchange Server services.
For more information, see New-ExchangeCertificate.
How do you know this worked?
To verify that you have successfully created an Exchange self-signed certificate, perform either of the following steps:
In the EAC at Servers > Certificates, verify the server where you created the self-signed certificate is selected. The certificate should be in the list of certificates with the Status value Valid.
In the Exchange Management Shell on the server where you created the self-signed certificate, run the following command and verify the properties:
The new version Microsoft Exchange, Exchange Server 2007, adds a wealth of new features and makes many things easier to do. Unfortunately, installing SSL Certificates isn't really one of them. Installing an SSL Certificate in Exchange 2007 requires you to run several commands in the Exchange Management Shell. Don't fret yet! If you carefully following these instructions, you'll have your Exchange 2007 server secured in no time!
Determine Your NeedsCopying and Pasting in the Exchange Management Shell
Unfortunately, you can't just use Ctrl+C and Ctrl+V to copy and paste in the Exchange Management Console. To copy something (like a thumbprint), right-click the shell window and Click Mark. You can then highlight the text that you want to copy and press Enter to copy it. To paste, just right-click and select Paste.
Powershell Generate Csr
There are several methods of securing your Exchange 2007 server. This article will walk you through the process of ordering a Unified Communications SSL Certificate with multiple domains from a commericial certificate authority and installing it on your Exchange server. Exchange 2007 includes some new features, like Autodiscover, that require multiple names to be secured. There are other methods of securing the additional Exchange 2007 names but the recommended method is to use a Unified Communications Certificate so you only have to worry about one certificate and one IP address.
What names do you need to include? It depends on what services and features you plan to use. At a minimun, you need to include the external name that people use to send and receive mail (mail.yourdomain.com) and the base domain and local name (yourdomain.com and yourdomain.local). You will also want to include the name for Autodiscover (autodiscover.yourdomain.com) so that Outlook 2007 users can use the Autodiscover feature without receiving errors. If you would like to use OWA internally, you will also want to include two NetBIOS names (Server01.yourdomain.local and Server01). So, in a typical scenario, you would include the following names in your UC Certificate:
Exchange 2007 Generate Csr Private Keyboard
Generate Csr Exchange 2013
For more information about which names to include see the resources in the Links section below. Once you have determined which names you need to secure you are ready to create a Certificate Signing Request and order the certificate.
Can I use a Wildcard certificate?
A Wildcard certificate (*.yourdomain.com) will secure all first-level subdomains of a particular domain. This could work to secure your Exchange 2007 server, but it is not reccomened for these reasons:
- You wouldn't be able to access the server using the internal server name (Server01) because it is not covered by the certificate and you would receive a 'name mismatch' error.
- A wildcard certificate is incompatible with POP3 and IMAP4 on Exchange 2007. See Microsoft's explanation of what certificates to use with Exchange 2007 for more information.
Create the Certificate Signing Request
Before you can order an SSL certificate for Exchange 2007, you need to create a Certificate Signing Request using the instructions below:
- Click on the Start menu, go to All Programs, then Microsoft Exchange Server 2007 and click on Exchange Management Shell.
Run the New-ExchangeCertificate command below replacing the appropriate values with your own. We recommend using DigiCert's New-ExchangeCertificate Command Generator to get a command that you can just paste in.
New-ExchangeCertificate -domainname mail.google.com, google.com, google.local, autodiscover.google.com, server01.google.com, server01 -Friendlyname google.com -generaterequest:$true -keysize 2048 -path c:certrequest.txt -privatekeyexportable:$true -subjectname 'c=US, o=Google Inc., cn=server01.google.com, s=California, l=Mountain View, ou=IT'
Name Explanation Examples -domainname Enter all of the names that you determined you needed to secure in the step above.
-Friendlyname Any name you want to use to keep track of the certificate on this server. my google certificate -keysize The size of the key that is generated. Bigger numbers are more secure but can be slower. 2048 is recommended 2048 -path The location where you want to save the CSR. c:certrequest.txt Common Name (cn=) Enter the first name in your list above. This is the most visible name in the certificate (the other names are listed as Subject Alternative Names and they aren't displayed as clearly)
Organization (o=) The legal name of your organization. This should not be abbreviated and should include suffixes such as Inc, Corp, or LLC. Do not include commas or the command won't work. Google Inc. Organizational Unit (ou=) The division of your organization handling the certificate. Information Technology
City/Locality (l=) The city where your organization is located. Mountain View State/province (s=) The state/region where your organization is located. This shouldn't be abbreviated. California Country/Region (c=) The two-letter ISO code for the country where your organization is location. US
Once you have generated a CSR you can use it to order the certificate from a certificate authority. Not all providers offer Unified Communications Certificates, but you can pick one from our list of Unified Communications SSL Certificates or you can compare SSL UC certificates using the SSL Wizard to find one. Once you find the provider that you want to buy from, click the Buy Now button and go through the order process. You will paste in the CSR and provide information about your company so it can be validated. Once the SSL provider validates your order, you will receive your new UC certificate file.
Install the Certificate
To install your newly acquired SSL certificate in Exchange 2007, first copy the certificate file somewhere on the server and then follow these instructions:
- Click on the Start menu, go to All Programs, then Microsoft Exchange Server 2007 and click on Exchange Management Shell.
- Run the Import-ExchangeCertificatecommand below. Make sure to specify the path to the certificate file you downloaded and remove any services that you will not be using.
Import-ExchangeCertificate -path c:google.p7b Enable-ExchangeCertificate -Services IMAP, POP, UM, IIS, SMTP
- If you didn't receive any errors, then it should have installed correctly. Run the Get-ExchangeCertificatecommand to verify that the certificate is enabled for the correct services. If you aren't sure which thumprint it is, you can view the thumbprint of the certificate you just installed by double-clicking it and looking for the thumbprint on the details tab.
- If the certificate isn't enabled for the correct services (S=SMTP, I=IMAP, P=POP, U=Unified Messaging, W=Web/IIS) you need to run the Enable-ExchangeCertificatecommand below. You can copy the thumbprint from the output of the Get-ExchangeCertificate command that you just ran.
Enable-ExchangeCertificate -Services IMAP, POP, UM, IIS, SMTP -thumbprint 896B74B25F7EBF330C93E56DA2A76CFC6A7
- After running the Enable-ExchangeCertificate command, run the Get-ExchangeCertificate command again to verify that the certificate is enabled for the correct services.
Install any Intermediate Certificates
This step is not necessary if you received a .p7b certificate file from your SSL provider because this file contains all the Intermediate certificates and they are automatically installed. If you received an individual .crt certificate file you may need to follow the instructions in this step.
Most SSL providers issue server certificates off of an Intermediate certificate so you will need to install this Intermediate certificate to the server as well or your visitors will receive a Certificate Not Trusted Error. You can install each Intermediate certificate (sometimes there is more than one) using these instructions:
- Download the intermediate certificate to a folder on the server.
- Double click the certificate to open the certificate details.
- At the bottom of the General tab, click the Install Certificate button to start the certificate import wizard. Click Next.
- Select Place all certificates in the following store and click Browse.
- Check the Show physical stores checkbox, then expand the Intermediate Certification Authorities folder, select the Local Computer folder beneath it. Click OK. Click Next, then Finishto finish installing the intermediate certificate.
You can verify that the certificate is installed correctly by visiting the site in your web browser using https instead of http or using our SSL Checker.
Exchange 2007 SSL Certificate Videos
Originally posted on Tue Jul 3, 2007