Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2010 Certificates

Posted on 2014-04-11
8
Medium Priority
?
320 Views
Last Modified: 2014-04-11
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?
0
Comment
Question by:SECC_IT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 29

Accepted Solution

by:
becraig earned 2000 total points
ID: 39994565
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
 

Author Comment

by:SECC_IT
ID: 39994643
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
 
LVL 29

Expert Comment

by:becraig
ID: 39994660
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
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:SECC_IT
ID: 39994669
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
 
LVL 29

Expert Comment

by:becraig
ID: 39994684
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
 

Author Comment

by:SECC_IT
ID: 39994687
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
 

Author Comment

by:SECC_IT
ID: 39994874
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
 

Author Closing Comment

by:SECC_IT
ID: 39994875
It is a workaround, but it will have to do. Thank you!
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
how to add IIS SMTP to handle application/Scanner relays into office 365.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question