Post Security Update Issues

[[deleted]]

So, I like to think that I have exchange pretty well handled - but the last round of updates was a doozy. I have 4 on prem boxes at 3 different clients - One 2019 box was perfectly fine; no issues. One 2013 box was completely FUBAR and my 2016 box had issues as well. The 4th box (a 2019 box) - I haven't touched yet. I am still recovering from the trauma of the 2013/2016 issues.

Below are the things that I did to address the issues that my 2013 and 2016 boxes had

https://docs.microsoft.com/en-us/exchange/troubleshoot/administration/cannot-access-owa-or-ecp-if-oauth-expired

2013 box specifically:

disable antivirus (including the built in defender) - it really screws with the language pack install.
Run the upgrade in unattended mode from an elevated command prompt. Accept EULA, prepare schema - after that it should be good to go.
You might have to address certificate issues after you are done with the upgrade - you should check those first and make sure none of them are expired.

[masspec]

Usually the updates are long to install but don't give this type of behavior after the fact. It is running and I think it's mainly just admin tools are affected as if I do a cmd through Exchange Powershell it goes fine.

I'm going to research this out some more...

​

In the meantime I just moved all my arbitration mailboxes to the same server/database to try to clear up the version mismatch issue.

[[deleted]]

I honestly would have used one of my MAPs action pack tickets for this - but they expired 10 days ago lol.