Solved

Match local server name to certificate name in Exchange 2013

Posted on 2016-11-21
6
51 Views
Last Modified: 2016-11-30
Hi I have a secure certificate for exchange.mydomain.com from GoDaddy for my Exchange 2013 server.  It's installed and  works fine for OWA and other Outlook connections, but when internal Outlook clients connect they get a certificate challenge saying that the server name does not match.  When they connect, the server name is resolved by Outlook to server.localdomain.local.  There is a record on the local DNS server resolving exchange.mydomain.com to the local IP of the Exchange server.
How can I make the internal Outlook clients resolve to exchange.mydomain.com so the certificate works for internal clients?
Thanks
0
Comment
Question by:PlexioUK
[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
  • 3
  • 2
6 Comments
 
LVL 15

Expert Comment

by:Jason Crawford
ID: 41895874
Follow this guide to set the internal URL of all vDirs and set the autodiscover internal URI for your CAS servers:

http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
0
 

Author Comment

by:PlexioUK
ID: 41895910
Thanks Jason

I looked at this article earlier - specifically which part of the process alters the name the internal Outlook clients resolve to?
0
 
LVL 3

Expert Comment

by:Pune Tech
ID: 41895958
You need to check autodiscover part , only autodiscover internal Uri.
0
Does Powershell have you tied up in knots?

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

 
LVL 15

Assisted Solution

by:Jason Crawford
Jason Crawford earned 500 total points
ID: 41895962
Just run this:

Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri mail.domain.com

Open in new window


Because .local SSL support was deprecated a few years back, you will also want to set the internal URL for all vDirs.
0
 

Accepted Solution

by:
PlexioUK earned 0 total points
ID: 41901713
0
 

Author Closing Comment

by:PlexioUK
ID: 41907012
This was the only article that solved the problem in it's entirety
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

In-place Upgrading Dirsync to Azure AD Connect
Outlook for dependable use in a very small business   This article is about using the Outlook application (part of Microsoft Office) in a very small business, or for homeowners where dependability and reliability are critical requirements. This …
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
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…
Suggested Courses

635 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