Comments on: Expired Certificates Cause Exchange Cumulative Updates to Fail

By: Seth

Seth — Fri, 21 Jun 2024 22:25:01 +0000

Thank you for this write up. It just saved me a lot of time.

By: Michael Wiskman

Michael Wiskman — Thu, 24 Aug 2023 21:25:12 +0000

Thank you Paul,
You saved my night.

By: kevinds

kevinds — Mon, 17 Oct 2022 18:13:40 +0000

>When you’ve successfully completed the cumulative update for your Exchange server, it’s time to do something about your certificate problems. There’ll be a cost involved, usually not more than a few hundred dollars, which hopefully by now you consider a bargain.

Or.. Lets Encrypt..

By: Fanus Swanepoel

Fanus Swanepoel — Tue, 02 Aug 2022 14:56:56 +0000

In reply to Frans. Hi Frans Did you manage to get an answer for this problem, I have the same issue, the Microsoft Exchange Server Certificate expired and I ran the Cumilative update, now I cant access EAC, EPS, only have access to Power shell and Command.

By: Tim

Tim — Wed, 16 Feb 2022 15:19:55 +0000

You’re a genuine lifesaver. Thanks for taking the time to write this post.

As you mentioned, this should be part of the prerequisite checks.

By: MMO

MMO — Mon, 22 Nov 2021 20:28:45 +0000

Thanks, saved my ass!

By: Joe Evangelista

Joe Evangelista — Tue, 08 Jun 2021 17:58:02 +0000

worked like a charm!

By: Arno

Arno — Fri, 30 Apr 2021 08:19:17 +0000

Thanks a lot again, Paul!
Your posts keep saving my day dealing with exchange CUs.

I’ll read one of your posts again soon I guess 😉

Best regards from Belgium!
Arno

By: Bubba

Bubba — Mon, 08 Mar 2021 01:17:00 +0000

Thanks for pointing me in the right direction. One binding was pointed to the current certificate, the other to the old expired one.

By: Svend

Svend — Sun, 07 Mar 2021 01:03:35 +0000

You saved my bacon.

Far out there are so many possible things that could go wrong with these Cumulative Updates.
I got this while installing CU19 on a Hybrid server that had not been touched since CU12.

At one point my update appeared to have stalled on “Copying Exchange Files 16%”. For that you just need to be patient, but when it did get to 100% it sat there and I left it for an hour and a half. There had been no CPU or Disk activity for the whole hour and I was about to reboot the server, instead I decided to see if I could exit the CMD window and upon hitting the enter key the results all of a sudden progressed to “Language Files 1%”
FAR OUT!! Was it waiting for some input but had failed to write the message to the screen??

Thanks to you I have now progressed… on to the next issue with this update, whatever that may be.

Thanks heaps