asked on

Exchange 2010 internal outlook client certificate warning

We have an exchange 2010 server (all services are in server) named close to -Ex2010.bec.ca . I have enabled outlook anywhere with SSL SAN certificate (OWA and autodiscover) - mailbec.com. Our internal outlook clients getting security warning. How will I avoid the warnings. How will I setup DNS to forward the internal clients to use the same SSL certificate mailbec.com to access the exchange server. How will I make outlook clients to not to get the warning errors.

Thanks

Ganesh Anand

There is a similar thread discussed about this internal certificate error : https://www.experts-exchange.com/questions/28128848/Exchange-2013-certificate-warning-for-local-outlook-clients.html

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

usuth

ASKER

I did complete the steps in Simon's link. The lap desktop worked perfectly (no cert error displayed) but not other desktops. The system is still showing the certificate error. Certificate error shows up whenever start outlook first time in the morning.

ASKER CERTIFIED SOLUTION

M A

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Simon Butler (Sembee)

The first thing I would do is look at the SSL certificate that is coming up. Ensure that it is your certificate and not a remote one.
Check the clients are resolving the host name correctly, to the correct IP address.

Simon.

usuth

ASKER

let me check them out (They all are in french)

Thanks

usuth

ASKER

It had worked perfectly. Thanks a lot

usuth

ASKER

Sorry, the accepted Solution was Simon Butler's and I checked the wrong one as the solution. Can you please correct it

DJNafey

Simon (Sembee),

Thanks very much. We have had this as a niggling problem for ages on a couple of networks and have been under a lot of pressure for a few weeks to get it fixed. My colleague spent most of yesterday trying to work it out but was going down the wrong route.

Your article was one of the clearest I have ever come across - I came in early this morning and used it to fix two networks before any of the users had even turned on their PCs.

I also bookmarked your contact details :-)