Discussion Locked

OWA 2007 Certificate Wrong Issuer

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have completed the our OWA setup and it works great but.... when I go to view my certificate it shows the issuer as being My server name. I want it to be a third party providor. EG: verisign

I have imported the thirdparty SSL into IIS and confirmed that it is there.

1 reply

by rechtepublic

Andre,

In order for all of the features of Exchange 2007 to work properly you must have a SSL certificate from a well known provider so you are on the right track.

However, Exchange 2007 handles its own certificate requests and imports so stay away from using IIS or the Certificates console for this task.

First, open Exchange Management Console and look up the part about creating your SSL certificate. There are instructions on how to use the Exchange's PowerShell interface to create your request and import the cert once it is created.

Now you need to purchase a multi-domain certificate from a known provider. I got a good deal on a 5-domain certificate from GoDaddy.com. Not only was it a good price but they had instructions for generating the cert request in Exchange 2007 and good phone support.

Why use a multi-domain cert? Well you need the Common Name (CN) to be your mail server's public FQDN and you need to have an alternate name to support your mail server's private FQDN. You wil also need two more alternate names for public and private autodiscover records if you want to use Autodiscovery. (See Autodiscovery in Exchange 2007 help for more info.)
(E.g. mail.abc.com, autodiscover.abc.com, mail.domain.local, autodiscover.domain.local)

Once I had successfully generated my cert request using Exchange PowerShell I copied and pasted the information into GoDaddy's web utility to create the certificate.

Here is where I discovered that GoDaddy requires the request to contain SUBJECT information. (There is nothing about including SUBJECT information in the Exchange 2007 SSL request instructions.) I revised my request to include the SUBJECT information and this time GoDaddy's web utility accepted my request and created my cert.

I downloaded the cert to my Exchange server and then followed the instructions to import the certificate using Exchange PowerShell.

The final challenge was importing the certificate. Apparently, Windows or Exchange had already created a certificate and I could not import my new certificate until I found and removed the old one(s).

I did this by opening MMC and adding the Certificates snap-in. Then I deleted all the certificates that referenced my private FQDN. After that I successfully imported my GoDaddy cert using Exchange PowerShell.

Now there is no warning when I go to OWA and Outlook Anywhere works perfectly.

I hope this helps.

This discussion is closed to new replies.