How to Issue a SAN Certificate to Exchange Server 2010 from a Private Certificate Authority

Exchange Server 2010 makes use of SSL certificates for securing network communications between servers and clients.  An example of this is Outlook Web App (OWA) which uses the HTTPS protocol for users connecting via their web browser (eg

In this article:

Introduction to SAN Certificates for Exchange Server 2010

Traditionally SSL certificates were issued for a single name (such as the webmail name above), however this is very limiting because once an SSL certificate is bound to an IP address that IP address is not able to accept connections addressed to different names over SSL, or at least not without the name mismatch causing a warning message to the connecting client.

This became an issue for Exchange Server 2007 and 2010 because, depending on the server roles installed, the server may need to accept SSL connections to several different names such as:

  • the server’s FQDN (eg
  • webmail and other published names (eg,,
  • multiple DNS namespaces (eg,

Configuring multiple IP addresses, DNS records, IIS instances, and SSL certificates for all of the possible names in an Exchange organization would be tedious and expensive.

The X.509 certificate standard has catered for this for a long time now with a feature known as Subject Alternative Names.  Basically this allows a single SSL certificate to be configured with a primary name and then multiple alternative names, making it valid for all of the required names that clients and other servers will be connecting to.

SAN certificates are available from most commercial providers however some organizations choose to issue them from their own private certificate authority.  Windows Server 2008 Certificate Services supports SAN certificates by default, however Windows Server 2003 requires the option to be manually enabled first.

Enabling SAN Certificate Support for Windows Server 2003 Certificate Services

You can check an existing Windows Server 2003 CA for SAN support by using the certutil utility from a command prompt.

C:\>certutil -getreg policy\EditFlags

  EditFlags REG_DWORD = 15014e (1376590)
    EDITF_ENABLECHASECLIENTDC -- 100000 (1048576)
CertUtil: -getreg command completed successfully.

If there is no EDITF_ATTRIBUTESUBJECTALTNAME2 flag then you can enable it by running the following command.

C:\>certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2

Old Value:
  EditFlags REG_DWORD = 11014e (1114446)
    EDITF_ENABLECHASECLIENTDC -- 100000 (1048576)

New Value:
  EditFlags REG_DWORD = 15014e (1376590)
    EDITF_ENABLECHASECLIENTDC -- 100000 (1048576)
CertUtil: -setreg command completed successfully.
The CertSvc service may need to be restarted for changes to take effect.

Next you must restart Certificate Services for the change to take effect.

C:\>net stop certsvc
The Certificate Services service is stopping.
The Certificate Services service was stopped successfully.

C:\>net start certsvc
The Certificate Services service is starting.
The Certificate Services service was started successfully.

The server is now ready to issue SAN certificates.

How to Request a SAN Certificate for Exchange 2010

The next step is to create a certificate request from the Exchange server.  You can perform this task from the Exchange Management Shell, or from the console.

For an example of the Exchange Management Console steps see the previous article here.

From the Exchange Management Shell use the New-ExchangeCertificate cmdlet to generate a certificate request.  In this example I am requesting a certificate with the following attributes:

  • A friendly name of “Exchange 2010 Certificate”
  • The server’s FQDN
  • The alternative names of,, and

I’m also using -GenerateRequest to create a certificate request rather than simply creating a self-signed certificate.

[PS] C:\>New-ExchangeCertificate -FriendlyName "Exchange 2010 Certificate" -IncludeServerFQDN -DomainName,, -GenerateRequest -PrivateKeyExportable $true

The command will output a certificate request that looks similar to this.



Copy the output to your clipboard for the next steps.

Open your web browser and navigate to the web enrollment URL of your Certificate Services server (eg http://ca-server/certsrv).  Click on Request a Certificate.  Note if you are running a Windows Server 2003 CA you may need an update to the web enrollment pages before you can proceed any further.

Choose Advanced Certificate Request.

Choose to Submit a Certificate request…, because we’ve already generated the request on the Exchange server earlier.

Paste the generated certificate request data into the form, and choose Web Server as the certificate template.  Click Submit to continue.

When the certificate has been issued download the certificate file to your Exchange server.

Completing a Pending Certificate Request for Exchange Server 2010

The certificate has been issued and downloaded, and now the pending certificate request needs to be completed for Exchange Server 2010.

Launch the Exchange Management Console, navigate to Server Management, and choose the server that you imported the certificate to.  Right-click the new certificate and choose Complete Pending Request.

Browse and select the certificate file that was downloaded, and the continue to complete the wizard.

The certificate has now been installed and is ready to be assigned to Exchange services.

If you encounter an error message stating that “The certificate is invalid for exchange server usage” then see this article for the solution.


  1. Raffaele Marmiroli says

    I was stuck with the Certification server policy. That worked also for Windows Server 2008 CertSrv.
    Thank you. I’ll reference this doc in my blog.

  2. Curtiss says

    i don’t get the “begin new certificate request”/”end new certificate” text output after i run the new-“exchangecertificate … -generaterequest” command. i just get a thumbprint.

    Thumbprint Services Subject
    ———- ——– ——-
    C527BEEE14788799C6C602AAF7D6DEBFDA8509D0 …… CN=sisexcp9.student.dom

    i ran the command on an exchange 2010 sp1 server running on 2008 r2.

  3. says

    Hi again, I’ve applied the new SAN certificate (created a new CA on the CAS with Windows Server 2008 R2 and issued a certificate) and assigned services (IMAP/POP/IIS/SMTP) , all worked fine for my domain joined PCs but a pc with Outklook 2010 says “the security certificate was issued by a company you have chosen not to trust “.
    Can you help with this? Thanks.

    • Curtiss says

      your machines or users with outlook 2010 have to trust the publisher of the certificate. you can use group policy to publish the CAS’s “root certificate” to the “trusted publishers” certifcate store. outlook 2007 did not throw this error for self-signed or untrusted certificates. if the problem pc is not a domain pc, you can manually put the root certificate into trusted publishers on that pc with the Certificates mmc console.

  4. Manjula says

    i have installed En root CA on my Additional AD (windows 2008 r2), do you recommend it?
    i just install Exchange 2010 sp1.
    And i failed to issue certificate by the CA console and Web enroll, in the web enroll i cant select “web server” in certificate template. only contain “user” and “basic EFS”.
    i had tried by issuing certificate request by Exchange 2010 EMC and EMS.

    What can i do to over come this?

    • says

      You can use your own CA if you like it just means non-domain members will not trust the CA until you deploy the root certificate to them.

      If you’re not seeing the web server template I’d say your account doesn’t have permissions to request that type of cert.

  5. Miroslav Gree says

    Hello, thanks for your articles about SAN certificates. I have a Q about SAN names. In the real world, SAN certificate for Ex 2010 must includes these names in cert : in the case of internal and external domain

    – server FQDN (
    – name for webaccess for external users (
    – name for autodiscover (
    – name for webaccess for internal users (webmail.mycompany.local)

    And netbios name of server (for example “server”) is needed too ? I have read many artciles, some says you do not have to include netbios name, some articles says you have to include the netbios name.

    So what about netbios name in the SAN ?

    Thanks for reply.

    • says

      Netbios would be needed if you plan to have your internal users hitting OWA (for example) by using the server’s Netbios name. As long as they’re hitting the FQDN then no need to include the Netbios name.

  6. uwedadmin says

    Hi, everybody! i need your help, Powershell show this error when runing with “certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2” command: Certutil: -setreg command failed: 0x8007000d, Certutil: The data is invalid

    How i can fix this?

      • uwedadmin says

        No, type it out myself…. but on command promt cetutil is runing without troubles, now, another problem, Exchange SA service is not running automatically and test -servicehealth command shows Mailbox Server Role: False, how i can fix this problem?

  7. Rick says

    Hello Paul;

    Just looked at this article which was great to learn how to make an exchange certificate. Just to add in the note for this article for how to find the output a certificate request that was made in the MMC exchange console is the following:

    1) Right-click the exchange certificate file which is the .reg extension.
    2) select open with or open
    3) open using notepad and there you will find all the information per example below:


    From: Rick.C

  8. says

    Hi paul.
    i bought a SSL certificate from verisign for my exchange 2010 and it working fine when i use owa but am having a certificate mismatch error every time i open my outlook 2010 form computer that is joined to the domain

  9. Amit says

    Hi Paul,
    Can you tell me how to generate and assign certificate for multiple CAS server exchange 2010. Further i would like to know if i generate certiifcate from private CA and assign it to CAS server is it ok

    CAS server name CAS1 & CAS2
    domain name which will be used for all the services is :

    • says

      Hi Amit, you can do it a few different ways. Either generate a separate cert for each server, or do one cert request that includes all of the CAS server FQDNs in it. You can then export the cert from the first server you install it on and import it into the other(s).

  10. fazlin says

    I successfully created a new Exchange 2010 SP2 certificate. Downloaded and installed the certificate as per GoDaddy kb. After I had successfully completed the “Complete Pending Request” I dont see the new certificate in EMC. The only certificate I can ses is the first “Microsoft Exchange” certificate which gets automaticly installed while installing MS Exchange. My Exchange 2010 SP2 runs on second 08 R2 Ent server.

      • Fazlin says

        thats correct, I can still see the first certificate “Microsoft Exchange” which is the self signed certificate but not the one which I had created and used it to purchase a Godaddy cert and later cant find in EMC after completing pending tasks.
        This is my fifth exchange 2010 deployment this year but first with SP2 and I had never had this issue in any version of exchange earlier

        • says


          Run MMC and add the Certificates snapin for Local Computer, and see if you can see the cert in the Personal/Certificates store there. If not, its possible it has somehow been deleted.

        • John says

          I just experienced the same problem as Fazlin. I looked here -> “Run MMC and add the Certificates snapin for Local Computer, and see if you can see the cert in the Personal/Certificates store there.”

          I have done this and can see the default Microsoft Exchange cert for Server Authentication, as well as my new cert for Server and Client Authentication. Any hints on what has happened here or how I can resolve this?

        • Kevin says

          Same problem here. I can’t believe it just disappeared!!! no error messages or anything. As John says it is in the Personal cert store along with the self signed original exchange one. I guess the only non standard thing about my set up is that I am in the process of migrating from exchange 2007 to 2010. Any ideas on how to get this cert back into exchange so I can assign services to it??

        • James says

          Hi, great article. Just in case it helps anyone, I had this exact problem. However it was my fault for not selecting ‘Web Server’ when I requested the certificate.

  11. fazlin says

    what can i do to start useing Outlook for remote users and other servides which require trusted certifficates

  12. Romain says

    Hi Paul, thank you or this very valuable article.
    Some users would like to access to Outlook Web Access from a computer ouside of the domain and dns.
    So they access by ipaddress, not by the fqdn: https:///owa.
    It works fine but they still have certificate error , even when i put the ipaddress as an Altrnative Name (SAN).
    But if they update their host file and access to OWA by he fqdn it works.
    What could be the problem? Is it possible to access to owa url by ipadress without having certificate issue?


    • says

      You should create a public DNS record for OWA and have your users use that.

      Note that recent changes in the rules governing how SSL certs are issued means you won’t be able to get certs for IP addresses or short names (eg “owa”) in the very near future.

      Better off doing it the right way right from the start :)

  13. Kiran says

    i have 2 physical separate sites as two child domains and the other as The user base is present in these two domains. The exchange is installed on the root domain ( i want to go with one single certificate for exchange 2010(not the wild card). I want to ensure that US users connect to the US Exchange(CAS+HT+MB) and India Users connect to the India EXchange(CAS+HT+MB). The question is should i have two separate autodiscover entry in the SAN or is it possible or necessary? And if it only requires one entry, i need to understand how the autodiscovery works for a user who sits externally to connect to the mail server. In the sense what mechanism takes place to ensure that the user connects to the right CAS server.

    • sharpwaves says

      I am in the same situation.
      Certificate MisMatch OR Outlook …. proxy server…Error 8, works fine when connect through VPN or internal LAN. IMAP & POP is working fine.
      Exchange Test says the same thing.
      The site has SBS 2011, Exchange 2010, Outlook 2010 external client and NO Public SSL yet.
      I realised there is no entry for Autodiscover.EXTERNALDOMAIN.NAME (e.g. on the certificate created by SBS. How would I add a domain to current certificate?
      I am unable to issue a new certificate as certsrv is not loading.
      Strangly, outlook is pulling all the information from Server externally.
      Any experience ?????

  14. Exchange User says

    i have two DCs and a domain wich my user’s trust :DC1, DC2 i found a CA on the DC2 but my exchange organisation is on a diffrent domain with two mailbox on DAG and CAS Hub and two DCs but no CA on this domain
    my problem is that when i tried to generate a certificat on my CAS as shown on steps and sign it on the CA that my user’s trust, the certificat request is always keeping peending and self signed.

    DC2 with CA on it


  15. Exchange User says

    hi Paul,
    thanks for your help, now the certificate is not self signed..that’s fine but it apears with in red meaning that the server coundn’t find the revocation list, wich i importe from my CA and install it on the server BANK certificat but still havin’ the problem

  16. Pavan Segal says

    I would like to follow the steps mentioned in the article above to issue a new certificate from my own server…
    My Exchange server is a member server. Can I install the AD Certificate Services on the Exchange Server (eg a member server) or is it better to install the Certificate server on the DC ?

  17. Mike Joseph says

    Hello, I followed this article because my client with Exchange 2007 has an internal domain name of but they do not own so I cannot get a UCC cert from GoDaddy to cover the FQDN of their exchange server. Consequently, users get an SSL error every time the open Outlook.

    I installed a Certificate Services server and followed your article. Now, users no longer get the SSL error when they launch Outook, but IE complains about the cert when they go to OWA:

    “The security certificate presented by this website was not issued by a trusted certificate authority.”

    Is there anyway around this? Once again, this is Exchange 2007 not 2010.


  18. David says

    I have a certificate issued by Verisign that will be expiring soon. Since I have no external facing services there doesn’t seem to be any point in paying for renewal. Is it safe to simply allow the existing cert to expire and issue one from my CA to “replace” it, following the above instructions?

    • says

      Don’t wait for it to expire. If it expires clients will begin showing certificate validation errors to your end users. You should replace it before it expires.

      Yes, if you choose to go with a private CA you can follow the instructions above to provision the cert, then make sure you also enable it for the services previously associated with the old cert.

  19. reda_boutbicha says

    I set up two CAS servers in NLB mode
    and the name of NLB: mail.domain.local
    Do I put the netbios name server if the certificate SAN, or I will just put the name of nlb: mail.domain.local
    thank you

    • says

      The intro section of this article explains which names to include. I’d recommend you read that.

      The NLB cluster name doesn’t need to be included. Neither does the CAS Array name (which is not necessarily the same as the NLB cluster name, though they can be the same). The names that need to be included are any that clients will be connecting to over HTTPS.

  20. Jamie says

    Thanks for this Paul!
    I was getting a bit confused as to why after completing the previous request I had (using a technet guide) my cert was disappearing from Exchange.
    However – Your guide was much clearer, and worked first go!

  21. Sandro Alves says

    Paul ,

    I have one just like it ( ) scenario . Using two Exchange , only one of them is accessed as a proxy .

    In Exchange that is facing internet , I use a digital certificate with the public domain ( ) and my OWA is configured to ( External: ) and (Internal : ) .

    You Exchange that are not face to internet , OWA is configured to ( External: empty) and ( Internal : servername.local ) . This Exchange user when connecting with Outlook client is generating validation error name ( servername.local ) , because as I’m using the same Exchange certificate that is facing internet . So the audience is trying to validate the certificate name that is not registered as an alternative name.

    question : the exchange that is not facing the internet, I need to use the same public certificate that is in exchange that is facing the internet? or can I just use an internal certificate?

    Thank you.

  22. Troy says

    Hey Paul,

    Quick question. Have you ever seen a situation where you issue an SSL cert from a CA server on MS Server 2008 with the SAN information, but then once you try to access the FQDN from a web browser you get an error. On the bad cert there is no more SAN field and the error message is “mismatched address?”

    Anything would help!!

Leave a Reply

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