Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


Resolution

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

↑ Back to the top


References

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

↑ Back to the top


Keywords: CI121912, kbHotfixAuto, get-casmailbox uses wrong ldap filter

↑ Back to the top

Article Info
Article ID : 4570248
Revision : 8
Created on : 9/15/2020
Published on : 9/15/2020
Exists online : False
Views : 222