Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 68
  • Last Modified:

Certificate for Exchange 2010

I have a Exchange 2010 setup, mail1.abc.com (CAS / Hub) and mail2.abc.com (Mailbox).  For exchange webmail, it is mail.abc.com. In public DNS, abc.com and www.abc.com is pointed to our website.

For the certificate in Exchange, which name should I only include mail1.abc.com & mail.abc.com. Do I need to include my domain name abc.com in the certificates ?

Thx
0
AXISHK
Asked:
AXISHK
  • 2
  • 2
1 Solution
 
MASTechnical Department HeadCommented:
In your certificate you need only 2 names which is mail.abc.com (common name) and autodiscover.abc.com.
both the A records should be pointed to your CAS server.
Please check my article how to configure this and certificate requirements
https://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html

This article is for fixing errors. The same can be used in your case.
1
 
AXISHKAuthor Commented:
Try renew the certificate with mail.abc.com and autodiscover.abc.com. After binding it to Exchange and connect Outlook internally, it prompts for the following :
"There is a problem with the proxy server's security certificate"

I have already run those Exchange powershell mentioned and the name has been point to the mail.abc.com.

Any idea what's missing ? Do I really need to include mecmail1 in the certificate files as inside Outlook setting, it is referring both internal name (mail1) and public name (mail).

Thx

Thx
0
 
MASTechnical Department HeadCommented:
Please post the screenshot.
You dont need internal FQDN in the certificate.

Thanks
MAS
0
 
AXISHKAuthor Commented:
Apply wizard certificate and fix the problem, Thx
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

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