We have a third party certificate for our OWA site which we got from Thawte.
We put that on the IIS site and owa works just fine, no warning etc. I
connected to Exchange via Outlook 2007 today and I'm getting 2 warnings
about the name not being the same.

I've read that SSL is enabled by default for outlook 2007, but not so in
2003. How do I stop it in 2007?



Or

If i decided to use SSL would I just set up another certificate with my own
CA and set it on the EWS site (I didn't think this was related but it's what
shows up when I do a test email auto configuration test?) I'm assuming I'm
getting this error because when we registered we registered out external url
for owa and our internal that outlook is trying to look at it is different
and most 3rd party certs don't allow you to add internal dns to certs.

Sorry! I had the WRONG newsgroup selected in outlook express!

-John


"John W" <whitesj@xxxxxx> wrote in message
news:ePM37oDBIHA.1208@xxxxxx

> We have a third party certificate for our OWA site which we got from
> Thawte. We put that on the IIS site and owa works just fine, no warning
> etc. I connected to Exchange via Outlook 2007 today and I'm getting 2
> warnings about the name not being the same.
>
> I've read that SSL is enabled by default for outlook 2007, but not so in
> 2003. How do I stop it in 2007?
>
> Or
>
> If i decided to use SSL would I just set up another certificate with my
> own CA and set it on the EWS site (I didn't think this was related but
> it's what shows up when I do a test email auto configuration test?) I'm
> assuming I'm getting this error because when we registered we registered
> out external url for owa and our internal that outlook is trying to look
> at it is different and most 3rd party certs don't allow you to add
> internal dns to certs.
>