OWA Certificate troubles


Here I go for SSL Certificate question nr 500...*sigh* :

-I've purchased a 3rd party UCC certificate.
-After some trouble I managed to install it on our HUB Exchange 2007 server called MAILSERV (the messaging server of our Essential Business 2008 Server). I enable IMAP POP SMTP WEB. All is well.
-I did NOT install it on the EDGE Exchange 2007 server called SECSERV (the security/forefront server of our Essentials Business 2008 Server and the gateway of our company)

When external users connect to OWA (mail.domain.com) they still receive the annoying certificate warning. When I use IE and check the certificate it still mentions a self-signed certificate instead of the commercial one.
To complicate things this self-signed certificate was installed previously on both MAILSERV & SECSERV. Because of that I don't even know what server is hosting the certificate seen in OWA (the HUB or the EDGE server ?).

So what I want to achieve is getting the 3rd party cert as the OWA certificate once and for all, instead of the self-signed certificate.

Who is Participating?
vindenConnect With a Mentor Author Commented:
Thanks Bikkelbink but apparently the certificate was already available in IIS on the messaging server.

This is what fixed the problem :

The messaging server of EBS 2008 is indeed the CAS server. On that server I had to open IIS and export the certificate. On the Security/forefront server I had to import the certificate in certificates mmc in the "personal" folder. After that I had to open forefront TMG and go to properties for the OWA Web listener. There's a tab called certificates. On that tab I simply had to change the certificate from the old one to the new one by selecting it.
BikkelbinkConnect With a Mentor Commented:
I can't tell you where you OWA is hosted. It is called the CAS server (most likely also on your HUB server).
When you figured out which server it is (see your Exchange console), open the IIS manager on that server. You have to change the certificate on the website used there.
After doing that, restart your IIS services (Start -> Run -> iisreset) and all should work fine...
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.