Not sure how many MS exchange gurus we have here but this is bugging me.

 

our SAN SSL cert expires next week so we have bought a new one from the same trusted authority as the current one.

 

I've got the new cert, loaded it onto exchange with no problems and assigned all the services to the new cert. However if I go https://servername/ I am still seeing the old cert.

 

So I went into  IIS and checked, and the default website is assigned the correct cert.

 

I've now removed the old certificate from exchange, its not listed in the console but still IIS seems to present the old one.

 

If I logon to the server and fire up IE and go https://127.0.0.1 I get a certificate error as the FQDN does not match, but clicking ignore I get the new cert. If I go https://servername/owa on the server I get the old one again.

 

Now really puzzled as the old certificate is not showing anywhere but IIS is still serving it up.

 

I've taken the same new cert and loaded onto the public reverse proxy and it works just fine.

 

Annoyingly this is an old server that is being retired in the next few months, but not everything has been migrated to the new Exchange 2013 box yet.

Edited 8 September, 20169 yr by mannyo

Just to update, I fixed it today. 

 

Not really sure what I did that was different to yesterday, anyway the certificate took and all is well. Even managed to apply it to ADFS for the Office365 hybrid install that we also disposing of in the coming weeks.