Skip to content

Setting Overrides


Setting Overrides can be configured via New-SettingOverride cmdlet and in certain cases with the help of registry values. They can be created to change default values for common Exchange services and features (e.g., the default run cycle of the Managed Folder Assistant).

Sometimes they are used to enable new features like the recently introduced Serialized Data Signing for PowerShell payload.

In very rare cases, Microsoft recommends to disable a feature or component by the help of an override (e.g., EWS web application pool stops after the February 2023 Security Update is installed) to work around known issues.

HealthChecker checks for known overrides which should be removed as a solution for to a particular problem is available.


Incorrect usage of the setting override cmdlets can cause serious damage to your Exchange organization. This damage could require you to reinstall Exchange. Only use these cmdlets as instructed by product documentation or under the direction of Microsoft Customer Service and Support.

Setting Overrides

Feature Exchange Version(s) Controlled via Recommended setting
BaseTypeCheckForDeserialization 2013, 2016, 2019 Registry Value Disabled


New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\Diagnostics -Name "DisableBaseTypeCheckForDeserialization" -Value 1 -Type String


Remove-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\Diagnostics -Name "DisableBaseTypeCheckForDeserialization"

Feature Exchange Version(s) Controlled via Recommended setting
Strict Mode for ClientExtensionCollectionFormatter 2016, 2019 New-SettingOverride Enabled


Get-SettingOverride | Where-Object {$_.ComponentName -eq "Data" -and $_.SectionName -eq "DeserializationBinderSettings" -and $_.Parameters -eq "LearningLocations=ClientExtensionCollectionFormatter"} | Remove-SettingOverride


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

Included in HTML Report?


Additional resources