SSL Exchange Help (ipsca)

[pritchardavid]

Yep got three certs to install in total

 

SSL Certificate Authority low-cost, fully-validated 38$ SSL and 276$ Wildcard Certificates (Plus of course our one made for our server)

 

 

The weird thing is, if I was to go to the owa site actually on the Mail Server it works fine with the Certs, its got the correct Cert path too

 

It any other computer lol

 

Believe they are installed in the correct location

 

 

Under Cert mmc these are the ipsCA Certs I can see that are installed on the Mail Server

 

 

 

Personal >>>> Certificates >>>> mail.theockedonacademy.com Cert Issued By ipsCA Level 1 CA

 

Trusted Root Certification Authorities >>>> Certificates >>>> ipsCA Global CA Root Cert Issued By ipsCA Global CA Root

 

Intermediate Certification Authorities >>>> Certificates >>>> ipsCA Level 1 CA Issued By ipsCA Global CA Root

 

Third-Party Root Certification Authorities >>>> Certificates >>>> ipsCA Global CA Root Issued By ipsCA Root

[sukh]

perform a iisrest on the exch server

[pritchardavid]

I did restart the whole iis service before, would have tried a reboot now, but the remote server id down

[pritchardavid]

All Sorted!

 

Just a reboot of the server resolved this!

[JonWPS]

Just sorted out a IPSCA cert for our exchange server yesterday. No problems at all. Shame Firefox still don't support the certs though.

[RobBaxter]

I use GoDaddy too. https://kingshott.herts.sch.uk/owa/

 

They have full instructions on how to install it. The only "minor" issue, is that if you sign the certificate on a external domain. Outlook will report that the certificate for dc02.kingshott.local in my case is valid, verified but working on the wrong domain.

 

In order to stop this, you need to add your external domain to your local domain as a alias and import the certificate as trusted... "hums... very poor explain there!", I'm english but my dyslexia getting the best of me this morning :S

[sukh]

1. FYI, iisrest is not a restart of the IIS services in windows, it's different, this is specific to IIS and would have reset IIS, althoguh the reboot would have done the same.