• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 82
  • Last Modified:

Exchange 2013 - Certificate Errors

I have server 2012 R2 installed with Hyper-V; one VM "2012 R2" with essential experience as the DC; one VM with Exchange 2013.
Mail is working well with OWA and Outlook.  But I have two issues:

On outlook, after connecting, we get a certificate error "The name on the security certificate is invalid or does not match the name of the site" on all clients (except one).
    What do I need to check, verify etc. ?

I cannot get "Anywhere Access" to complete on the DC server.  I am trying to use the SSL certificate issued for the Exchange which it accepts.
    Should the intermediate certificate be installed on this server ?
    Is it correct to use this SSL certificate on the DC server ?
0
Eur0star1
Asked:
Eur0star1
  • 4
  • 4
1 Solution
 
MAS EE MVETechnical Department HeadCommented:
Hi,
Please check my article
https://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html

Please let me know if it doesnt help.
0
 
Scott CSenior Systems EnginerCommented:
Use this to look at the specifics on your certificates.

Get-ExchangeCertificate | fl

Did you get your cert from a CA like Godaddy?

Make sure it hasn't expired.
0
 
Eur0star1Author Commented:
Spent some time this morning cross checking all settings using -MAS-'s article as guidance.

Current situation:  The SSL certificate is from Godaddy and has over 18 months to run.  It is assigned to services IMAP, POP, SMTP and IIS and the hosts   remote.   autodiscover.    mail.   and  servername.   are assigned.

We get certificate errors on all  'Outlook 2013'  clients  but,  the  'Outlook 2016'  client works correctly.

We also get a certificate error on using the ECP interface.

Hope the  'Outlook 2016'  gives you a clue !

Regards
Brian
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
MAS EE MVETechnical Department HeadCommented:
Please post the error.
0
 
Eur0star1Author Commented:
It's the Certificate Security Warning

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

displayed about 2 minutes after opening Outlook
0
 
MAS EE MVETechnical Department HeadCommented:
Please post the output of these commands
Get-clientAccessServer | fl Name,AutoDiscoverServiceInternalUri

Open in new window

Get-ExchangeCertificate | fl Issuer,CertificateDomains,services

Open in new window

0
 
Eur0star1Author Commented:
Sorry about delay;  long weekend !

As requested:

Get-clientAccessServer
Name                                                : SIKORSKY
AutoDiscoverServiceInternalUri   : https://mail.reprotec-ltd.co.uk/autodiscover/autodiscover.xml

Get-ExchangeCertificate
Issuer                        : CN=Go Daddy Secure Certificate Authority - G2,
                                     OU=http://certs.godaddy.com/repository/,
                                     O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
CertificateDomains : {remote.reprotec-ltd.co.uk,  www.remote.reprotec-ltd.co.uk,
                                      mail.reprotec-ltd.co.uk, sikorsky.reprotec-ltd.co.uk,
                                      autodiscover.reprotec-ltd.co.uk}
Services                     : IMAP, POP, IIS, SMTP

Issuer                         : CN=sikorsky.reprotec-ltd.co.uk
CertificateDomains : {sikorsky.reprotec-ltd.co.uk, autodiscover.reprotec-ltd.co.uk,
                                      remote.reprotec-ltd.co.uk,  mail.reprotec-ltd.co.uk}
Services                     : IMAP, POP, SMTP

Issuer                         : CN=sikorsky.reprotec.local
CertificateDomains : {sikorsky.reprotec.local}
Services                     : SMTP

Issuer                        : CN=sikorsky.reprotec.local
CertificateDomains : {sikorsky.reprotec.local}
Services                     : None

Issuer                        : CN=Microsoft Exchange Server Auth Certificate
CertificateDomains : {}
Services                     : SMTP

Issuer                         : CN=Sikorsky
CertificateDomains : {Sikorsky, Sikorsky.REPROTEC.local}
Services                     : IIS, SMTP

Issuer                         : CN=WMSvc-SIKORSKY
CertificateDomains : {WMSvc-SIKORSKY}
Services                     : None

Regards
Brian
0
 
MAS EE MVETechnical Department HeadCommented:
Your config seems fine.
Please try to create a new outlook profile and let me know.

Thanks
MAS
0
 
Eur0star1Author Commented:
After checking various settings -MAS- the long standing issue was resolved after rebuilding the profiles.

Thanks

Brian
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now