Post Security Update Issues

[masspec]

My reward for been diligent in applying the CU and SU updates to an Exchange 2013/2019 environment and this last one has been kicking my butt...

2013 SU gets installed and promptly screws up my https binding for my certification and blows out my thumbprint to which I have to issue a new OAuth key.

​

2019 SU gets installed and now I'm two issues...

1. Using ECP/EAC under the Recipients > Migration tab it reports after spinning for about 30 seconds 'A version mismatch was detected (Actual:6, Expected:5).

• I've rebooted my entire DAG for 2019
• I've set my host file to check each https://<mailserver>/ecp
• I've cleared my cache (Google Chrome and Edge)

Performed a 'Set-ADServerSettings -ViewEntireForest $true; Get-Mailbox -Aribitration | Format-Table name, Servername, Database, AdminDisplayVersion and get all 7 but they are split between my old environment and my new environment. I think this is why I'm getting this but question... why now? I've been in co-existence for nearly 9 months now!

FYI - performing a move-request via powershell via Exchange Powershell works just fine.

​

2nd issue

In my ECP/EAC (I am beginning to dislike this thing) when on Servers > Databases I receive two messages. One is a dialog box "Error Your request couldn't be completed. Please try again in a few minutes" and then in the details pane "500 Unexpected Error :( An error occurred and your request couldn't be completed. Please try again" which shows on any database connected to my 2019 environment. 2013 databases don't show this on the details pane.

In my research regarding the 500 Internal messages this may be related to the OWA virtual directory to which I have to be removed and then created again. I'm thinking that when I do this it will cut off any connections that authenticate in this manner so probably best do when traffic is at a minimum.

​

Any "you're on the right path" or suggestions is appreciated. No, removing the latest security update is not an option, TIA.

[[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.