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
usuthAsked:
Who is Participating?
 
MAS (MVE)EE Solution GuideCommented:
Please check these articles
EE
Technet
0
 
Ganesh Kumar ASr Infrastructure SpecialistCommented:
There is a similar thread discussed about this internal certificate error : http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28128848.html
0
 
Simon Butler (Sembee)ConsultantCommented:
Enabling Outlook Anywhere on its own shouldn't have caused this error.
All you need to do is setup a split DNS, then reconfigure Exchange to use the external host name internally.
http://semb.ee/hostnames2010

Takes about 15 minutes to do and then you are set.

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
usuthAuthor Commented:
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.
0
 
Simon Butler (Sembee)ConsultantCommented:
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.
0
 
usuthAuthor Commented:
let me check them out (They all are in french)

Thanks
0
 
usuthAuthor Commented:
It had worked perfectly. Thanks a lot
0
 
usuthAuthor Commented:
Sorry, the accepted Solution was Simon Butler's and I checked the wrong one as the solution. Can you please correct it
0
 
DJNafeyCommented:
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 :-)
0
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.