Learn how to a build a cloud-first strategyRegister Now

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

Exchange 2013 CAS server certificate problem

I have 4 exchange 2013 servers 2 Mailbox and 2 CAS running in win 2008 r2. When I check the certificates using power shell in the CAS02 it is shown the certificate of mailbox01.

But in ECP showing correctly. Also when I tried to import the third part certificate in cas02 I am getting an error certificate with this thump is already there.
Cas02-Certi.jpg
Certilist.jpg
0
jobby1
Asked:
jobby1
  • 2
  • 2
4 Solutions
 
pcmghouseCommented:
Please run command "get-exchangecertificate -server yourservername".
Have you assigned any services to the certificate?
0
 
MASTechnical Department HeadCommented:
As suggested above check the certificates in CAS02
And enable services using the command below
Enable-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -Services POP,IIS,SMTP. etc

http://technet.microsoft.com/en-us/library/aa997231(v=exchg.150).aspx
0
 
jobby1Author Commented:
Do I need to remove default certificate.

Do I need to remove the services for the default certificates.
0
 
pcmghouseCommented:
Were you able to import the certificate.
Do not remove the default ones. SMTP will work fine with the self-signed ones.

You can assign IIS services. But you have to make sure that your third party certificate is a SAN or wild card. And it is valid.

Provide output for get-exchangecertificate -server yourcasservername.

This IIS cert will be used in OWA, Outlook connectivity.
0
 
MASTechnical Department HeadCommented:
As suggested by pcmghouse let the SMTP enabled on self signed certificate and enable IIS on the new one
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

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