Help with Self-Signed Exchange 2007 Certificate:

Hi all.
Here's the situation.
We have a domain named "MyDomain" and already have a self-signed certificate on the Exchange 2007 server.  We'll call the Exchange server "MyExchangeServer".
The domain has a netbios name of "DomainNB" and the FQDN is known as "Domain.Local".
The self-signed certificate on the Exchange server reads "MyExchangeServer" but when accessing OWA you get a certificate warning stating that the name is mismatched.  This is because the OWA address is "".
I'd like to add this OWA address into the current certificate or create a new one which includes the info from the current cert along with the OWA address.
I found a very helpful article which explains how to do just through the Exchange Management Shell:
The issue is the example they give is a little confusing to me and I was hoping someone can give me instructions in plain english, using my domain info above so I can accomplish this.
FYI - the whole reason I'm doing this is because I have a demo Windows 7 phone I'm trying to connect to the Exchange server and it won't connect because of the certificate name mismatch.  I'm assuming once this new certificate is created and placed in the Exchange server's Trusted Root Certification Authorities folder I'll be able to connect with the phone successfully.

One more thing is that when I browse the "local computer" certificates on the Exchange server, I find the self-signed certificate.  It is not currently in the "Trusted Root Certification Authorities" folder.  Is this going to be an issue?

Any help would be appreciated.
Who is Participating?
AmonPereiraConnect With a Mentor Commented:

To me there is only 2 options to solve this.

1 - Add certificate to Mobile device;
2 - Issue a valid SAN certificate.

I know SAN cert can be very expensive, but there is some options quite cheap.

Please check this one:

Using this one, you might bypass this issue with no worry.

Let me know if it helped you.

First you need to enable Windows CA to issue SAN certificates (certs with multiple names). By default Windows CA only issues single certs.

There a link below which explains it better.

Let me know if it helped you.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

homerslmpsonAuthor Commented:
OK so here's what happened.
I went ahead and followed the original link's instructions like a dope.
The certificate was created.
I verified OWA is still accessible from outside the network and it is.
The problem is you still get a certificate warning, this time stating that the certificate wasn't issued by a trusted certificate authority.
Of course the Windows phone still won't let me connect to Outlook.
To make matters worse, an Outlook 2010 user is now getting prompted to accept a certificate every time he opens Outlook.
I tried "installing" the certificate onto his machine but it doesn't seem to matter.
There are only 3 Outlook 2010 users and I'm going to assume this will only affect them but of course, we'll have more eventually and I'd like to get past this.
What the hell did I do?
homerslmpsonAuthor Commented:
Well I already emailed myself the certificate and installed it on the phone which apparently installed no problem but something is off.

For a price of $30 a year, this is definitely something to consider but this was kind of done without my managers knowledge and I don't want to have to ask for approval to get the cert, etc if I can help it.

I'm noticing that there are 2 certificates in the "Trusted Root Certification Authorities" folder on the Exchange serer that look identical.  They both have the name "MyExchangeServer.domain.local" and were "issued by" that same name name (MyExchangeServer.domain.local).

In the "Personal" certificates folder on the Exchange server there are 2 certificates that caught my attention.  The first one is named "MyExchangeServer" and there is no domain in the name.  This was the one that was here the whole time.
There is also the new one I created which states it's issued to "" and was issued by "MyExchangeServer.domain.local".

I feel like this is a very simple fix for someone that has a strong understanding of what I'm trying to do and knows enough about certificates to help.
Please provide more information about your mobile OS.

Once i was in project which i had to disable mobile cert signing to make it works.

Im waiting...

homerslmpsonAuthor Commented:
Very sorry for the delay.

I explained to my manager the situation and I got approval to go ahead and by the $30 SSL cert on the site you mentioned.

Is there anything I need to know about getting / applying this cert?  Perhaps I need to remove all of the previous created self-signed certs or move them elsewhere?

The mobile OS is Windows Phone 7 (Verizon HTC Trophy).

I've been reading nothing but horror stories when it comes to getting these phones to connect to Exchange.
homerslmpsonAuthor Commented:
Of course the $30 SSL cert is the wrong one.
It needs to be the $60 per year USS SSL cert which I didn't get approval for.

There is a way of using Exchange 2010 with a Single SSL Cert.

I found an article that might help you out.

Let me know if it helps.
homerslmpsonAuthor Commented:
That seems a bit more advanced than I'd like to get.
It's talking about modifying DNS, etc.
I can't believe this is so tricky.
I'm waiting on approval from my manager to spend the $60 as opposed to the $30 I already got approved for but in the mean time I'm trying to see if there is a free solution that actually works.
None i have know of.

But its possible and it works, i have done this once for a customer and it worked quite well.

If you are not going do it, please close the question.

Any more help, you can count on us.

homerslmpsonAuthor Commented:
I went ahead and purchased a certificate from the link you provided but the $30 one wasn't the right one.  I needed to get the $60 one.  I just submitted the request for the certificate and am waiting to get it.
Assuming this takes care of the issue, this question can be closed.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.