Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elev...
Updated Mar 03, 2023
Version 13.0
Blog Post
Nino_Bilic Perhaps I did something wrong but your workaround seemed pretty straight forward. I added the registry key on both Exchange servers. I then ran the following commands:
New-SettingOverride -Name "Adding learning location ClientExtensionCollectionFormatter" -Server CHAMB01 -Component Data -Section DeserializationBinderSettings -Parameters @("LearningLocations=ClientExtensionCollectionFormatter") -Reason "Deserialization failed"
Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
IISreset on both servers
When I go to Manage add-in OWA I get "There was a problem loading your options. Please try again". In the dev tools I see:
https://mail.domain.com/owa/service.svc?action=GetApp&EP=1&ID=-37&AC=1 ---- 500 (Internal server error)
The work around doesn't appear to address the add-ins issue.