Solved

Outlook 2016 - the name on the security certificate is invalid

Posted on 2016-08-23
8
33 Views
Last Modified: 2016-10-01
Hello,

We have just installed a new windows 2012 server running 2 hyperv servers. One being our domain controller and the other being our exchange 2016 server.

We have this working OK apart from the SSL certificate integration. ie we were getting complaints on starting up outlook regarding an invalid or untrusted certificate. I presumed that once we obtained the correct SSL, this would just disappear.

Unfortunately, having just purchased our True ID SAN from geotrust, and installed it, we are still experiencing a warning on starting outlook. This is :-

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

I have spoken with geotrust and they tell me its because it is looking for the internal exchange 2016 name, which  I can confirm is the case.

the name of the local server is exch2016.domain.local

Our SSL is to secure remote.domainname.co.uk and autodiscover.domainname.co.uk

Geotrust say that we have to rename our local site to match??

Can anyone advise on what we need to do to resolve this problem?
0
Comment
Question by:nigelbeatson
  • 4
  • 3
8 Comments
 
LVL 17

Accepted Solution

by:
xtermie earned 400 total points (awarded by participants)
Comment Utility
It seems like the common name that you specified when you generated the certificate request for that Web site does not match the URL that is used to access the Web site. For example, if you access the site by typing an IP address or the server name, but the common name that is specified in the certificate request is remote.domainname.co.uk, so that is why you receive the security message.

To avoid this warning, make sure that the common name that is specified when you generate the certificate request matches the URL that will be used to access the site.

If the URL that will be used to access the site cannot be changed to match the common name on the certificate, follow these steps:
1.Create another certificate request. Make sure that the common name matches the URL that is used to access the Web site.
2.Have your certification authority generate a new certificate.
3.Use the new certificate for the Web site.
0
 
LVL 17

Assisted Solution

by:xtermie
xtermie earned 400 total points (awarded by participants)
Comment Utility
You can also check a related microsoft's article here:
https://support.microsoft.com/en-us/kb/2772058
0
 

Author Comment

by:nigelbeatson
Comment Utility
many thanks for your reply.

I think my situation must be a little different, as when I asked about adding the local site to my San, geotrust told me that this was no longer allowed.

it is not actually a site which is causing the problem, it is outlook 2016 that is looking for exch2016.domain.local , and our Ssl only covers remote.domainname.co.uk

I don't understand why the local copy of outlook 2016 does not trust its own local 2016 server, but as I can't add the local name to our Ssl, I presume that we have to somehow change the local name of the exchange server.

accessing exchange remotely works fine, so I am very frustrated that I am having this problem locally.

I will check out the additional link, to see if it helps.

many thanks
0
 
LVL 18

Assisted Solution

by:Peter Hutchison
Peter Hutchison earned 100 total points (awarded by participants)
Comment Utility
It is itrue that using .local in DNS for certificates is no longer allowed.

You need to configure exchange so that it will use public names d(omainname.co.uk) where possible instead of .local ones. So for owa it will be mail.domainname.co.uk, for autodisover it is autodiscover.domainname.co.uk, and so on.

https://blog.digicert.com/replace-your-internal-name-certificates/
https://www.digicert.com/ssl-support/redirect-internal-exchange-san-names.htm
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 

Author Comment

by:nigelbeatson
Comment Utility
sorry for the delay in updating this incident. I have been away on vacation, but now I'm back, will be addressing this issue.

will update you later today.

many thanks for your assistance
0
 

Author Comment

by:nigelbeatson
Comment Utility
I have now run the digicert tool which changed our local settings to autodiscover.domainname.co.uk.

I have ensured we have a Dns zone for domainname.co.uk
with an entry for autodiscover and remote (which we use externally) both pointing to the local IP address of our exchange server.

I can confirm that our current San covers both remote.domainname.co.uk and autodiscover.domainname.co.uk but the warning when starting out look still appears.

I am very frustrated, so if anyone can provide any further assistance, I would be much obliged.

it would seem that outlook is still trying to reach exch2016.domain.local. is there anything to do on outlook 2016 to stop this?

many thanks
0
 
LVL 17

Assisted Solution

by:xtermie
xtermie earned 400 total points (awarded by participants)
Comment Utility
One more thing to check as are likely to have these two registry settings:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover]
"domain.com"="c:\\auto\\autodiscover.xml"
"PreferLocalXML"=dword:00000001

With HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
for Outlook 2010

You must make this solution more robust by adding these registry entries:

"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
"ExcludeHttpRedirect"=dword:00000000
"ExcludeSrvRecord"=dword:00000001

The only lookup type that will be used now, is HTTP Redirect to the XML file. If this fails, there'll be no Autodiscover.
This is an excerpt from my documentation after having implemented this solution twice with different forests, not Office 365.

For more information see here:
Potential Autodiscover Issue During E-Mail Coexistence
http://social.technet.microsoft.com/Forums/en-US/onlineservicesmigrationandcoexistence/thread/d6c69c69-6524-493b-a0c6-21c79e146ce7/

Outlook 2007 unexpectedly connects to an on-premise Exchange Server 2007 server mailbox instead of an Exchange Online server mailbox
http://support.microsoft.com/kb/956297/en-us
0
 
LVL 17

Expert Comment

by:xtermie
Comment Utility
good comments and recommendations provided by experts
0

Featured Post

Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

772 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now