Exchange 2010 Certificates

Layout:
Domain:  eyecare.com
Exchange 2010 with all SPs and RUs.
Most clients use OWA, using https://mail.eyecare.com/owa (yes even internally)

Own a godaddy SSl certificate that covers eyecare.com, mail.eyecare.com, and autodiscover.eyecare.com. OWA users are covered under this.

ISSUE:
GoDaddy will not cover our internal addresses any longer. I recently had to rekey our certificate and lost coverage of my .local addresses.

Internal:  exchange.eyecare.local - I have a built-in Exchange certificate that does cover this internal address.

My OWA clients are fine - they do not get SSL errors because they are using mail.eyecare.com.

However, those that use Outlook 2010 are getting errors:

"The name on the security certificate is invalid or does not match the name of the site."

When you select "view certificate" on this error, it is pointing to the godaddy certificate for mail.eyecare.com.

When I configure Outlook 2010 to our server, it automatically inserts exchange.eyecare.local under mail server.

So, how do I tell Exchange to use the built-in exchange.eyecare.local certificate for the Outlook clients?
SECC_ITAsked:
Who is Participating?
 
becraigConnect With a Mentor Commented:
The simple no impact solution is to update your internal urls to match the external URLs:


You can get the external urls here :
Get-ActiveSyncVirtualDirectory   | ft server,*lur* -AutoSize
Get-AutodiscoverVirtualDirectory | ft server,*lur* -AutoSize
Get-ClientAccessServer           | ft name,  *lur* -AutoSize
Get-EcpVirtualDirectory          | ft server,*lur* -AutoSize
Get-OabVirtualDirectory          | ft server,*lur* -AutoSize
Get-OwaVirtualDirectory          | ft server,*lur* -AutoSize
Get-WebServicesVirtualDirectory  | ft server,*lur* –AutoSize


Then change your internal urls to match the external urls:

Set-ClientAccessServer -Identity HostName -AutodiscoverServiceInternalUri https://mail.yourdomain.com/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "HostName\EWS (Default Web Site)" -InternalUrl https://mail.yourdomain.com/ews/exchange.asmx

Set-OABVirtualDirectory -Identity "HostName\oab (Default Web Site)" -InternalUrl https://mail.yourdomain.com/oab
0
 
SECC_ITAuthor Commented:
My internal mail doesn't need an SSL certificate.

How do I tell Exchange to use the built-in exchange.eyecare.local certificate for the Outlook clients?
0
 
becraigCommented:
If you have not configured your internal url to require SSL why are your internal users going to SSL ?

The fact your internal users are getting SSL prompts indicate that it is configured to use SSL.

The option I outline above simply resolves an addition future problem you might have where users DO NOT trust your self signed certificate (without additional work).
It is also minimizes your workload in terms of certificates to manage.

If you want to proceed using a self signed certificate, simply go to the .local sites in IIS and update the bindings to your self-signed certificate you will create.

I do not suggest this however, as I know it might probably just lead to a question later of client NOT TRUSTING your new .local certificate.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
SECC_ITAuthor Commented:
Honestly, your solution was actually my first thought, and you saved me some Googling by listing exactly how to do it.

Is there a downside to your solution?
0
 
becraigCommented:
There is no downside to be honest, it is the path most folks will end up going as a result of the certificate vendors change from honoring requests with .local domains.
0
 
SECC_ITAuthor Commented:
Okay. I am going to try this. I will leave this ticket open in case I run into issues. Thank you! If it works, you'll get the points!
0
 
SECC_ITAuthor Commented:
I did everything you said. The commands ran without incident. I restarted the  Exchange Transport service and the IIS Admin service and, voila! - no more certificate errors!

Thank you for your help!
0
 
SECC_ITAuthor Commented:
It is a workaround, but it will have to do. Thank you!
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.