Blog Post

Exchange Team Blog
4 MIN READ

Released: February 2023 Exchange Server Security Updates

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Feb 14, 2023
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
announcements
Exchange 2013
exchange 2016
exchange 2019
security
setup
Apie77's avatar
Apie77
Copper Contributor
Feb 17, 2023

I finally got my EWS in our DAG working again. Thank you yvess2355 for your excellent tip!

 

So basically I used these cmdlets, servernames are simple, not FQDN:

New-SettingOverride -Name "Adding learning location ClientExtensionCollectionFormatter" -Server SERVER1 -Component Data -Section DeserializationBinderSettings -Parameters @("LearningLocations=ClientExtensionCollectionFormatter") -Reason "Deserialization failed"

Get-SettingOverride -Identity "Adding learning location ClientExtensionCollectionFormatter" | Set-SettingOverride -Server SERVER1,SERVER2,SERVER3,SERVER4

 

And then:

Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

On each individual Server, followed by a IISRESET.