Get-CASMailbox uses wrong LDAP filter for ECPEnabled in Exchange Server 2019 and 2016

Applies to: Exchange Server 2019Exchange Server 2016

Symptoms


In Microsoft Exchange Server 2019 or Exchange Server 2016, consider the following scenario:
  • For any user, change the ECPEnabled parameter value to $false by using the following Set-CASMailbox cmdlet:
Set-CASMailbox NoEcp01 -ECPEnabled $false
  • You use the following Get-CASMailbox cmdlet to view the change that you made:
Get-CASMailbox -Filter ECPEnabled -eq $false'
In this situation, the output should be:

Name    ECPEnabled
----    ----------
NoECP01      False

However, the Get-CASMailbox cmdlet doesn't return any results even if the ECPEnabled parameter is set to $false.

Cause


This issue occurs because a wrong Lightweight Directory Access Protocol (LDAP) filter is used when you run the Get-CASMailbox cmdlet for the ECPEnabled parameter.

Resolution


To fix this issue, install one of the following updates:

References


Learn about the terminology that Microsoft uses to describe software updates.