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

Unable to replace SSL cert

I have recently replaced an expiring certificate on my Exchange 2013 server running on Server 2012 R2.  OWA shows the correct, new SSL certificate; however, Outlook is generating a warning on startup related to an expired cert meaning somehow OWA and Outlook are using different certs.  I have replaced many expiring certificates over the years, and I've never run into this issue.  Here is the process I followed:

1. Generated CSR from EAC
2. Submit .req file to 3rd party CA (Comodo)
3. Complete pending cert request in EAC using .crt file supplied by Comodo
4. Assign the IIS and SMTP services to new cert
5. Restart IIS

As I said, when viewing the certificate presented by OWA, the new, unexpired certificate is used.  Outlook continues to revert to the expired certificate for some reason.  Here are the troubleshooting steps I've tried so far:

1. Delete the expired cert completely
2. Reinstall the unexpired cert
3. verify bindings for 'Default Web Site' in IIS on port 443 are set to use the new, unexpired cert
    - Subsequently there are two bindings for port 443 which I thought was odd.  One for All Unassigned IPs (*) and another for 127.0.0.1.  Is this normal?
4. Ran an ExRCA test and verified the Outlook Anywhere test did show the new, unexpired certificate meaning this is only affecting Outlook.

Any help here would be appreciated.
0
terminalb
Asked:
terminalb
  • 4
  • 2
1 Solution
 
nashiookaCommented:
Forgive me but after step 3 did you import the certificate from comodo back to the machine that generated the original CSR?  If you don't do that it will be missing the private key and cause all sorts of issues.

Also, do you have more than 1 CAS server, that Outlook could potentially be speaking to?  If so you would need to export the certificate from that first machine and re-import it to any additional CAS servers.  Personally I like to use the same certificate across the global environment, so this is usually a good thing.  Of course when you generated the CSR you would have had to use the -PrivateKeyExportable parameter.
0
 
terminalbAuthor Commented:
You're right, I should have clarified those points.  When I reinstalled the new cert I ensured to include the private key, and this is a single Exchange server environment with a Typical installation.
0
 
nashiookaCommented:
Run a connection test in outlook to make sure it's connecting to the correct CAS server for all the https based services.  I know you said you only have one server, but I think give that a shot.  It's possible the Autodiscover SCP isn't set to the FQDN or other namespace DNS resolving to the CAS server?
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
terminalbAuthor Commented:
Yea I thought of that also.  Everything is connecting to the correct servers and URLs.  I can't explain it.
0
 
terminalbAuthor Commented:
Closing as unresolved.
0
 
terminalbAuthor Commented:
No resolution
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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