Extended Protection for LDAP Authentication (Domain Controllers only) (DEPRECATED)
Explanation
Beginning with the Windows 10 and Windows Server v2004 security baseline this setting has been moved to Security Options\Domain controller: LDAP server channel binding token requirements.
Use cases
Requires channel binding for LDAP authentications on domain controllers to counter relay attacks over LDAP over TLS. It goes along with the LDAP signing requirement described in advisory ADV190023.
Test with the "when supported" mode and monitor Directory Service log events before enforcing the strict value, since older clients may fail. Note that this ADMX setting is marked deprecated in the baseline.
Microsoft source: 2020, 2023, and 2024 LDAP channel binding and LDAP signing requirements for Windows (KB4520412)
Registry
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters- Value name
LdapEnforceChannelBinding
| State | Value written |
|---|---|
| Enabled | not defined in the ADMX (see the options below) |
| Disabled | not defined in the ADMX (see the options below) |
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
The ADMX does not specify the value written when enabled; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled). The commands below use 1/0 as an assumption.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Enable
# Enable: SecGuide/Pol_SecGuide_0100_LdapEnforceChannelBinding
$k = 'HKLM:\System\CurrentControlSet\Services\NTDS\Parameters'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'LdapEnforceChannelBinding' -Value 1 -Type DWord # assumed value (not defined in the ADMX)
# Configure LdapEnforceChannelBinding
# Possible options:
# Enabled, always (recommended) = 2
# Enabled, when supported = 1
# Disabled = 0
Set-ItemProperty -Path $k -Name 'LdapEnforceChannelBinding' -Value 2 -Type DWordDisable
# Disable: SecGuide/Pol_SecGuide_0100_LdapEnforceChannelBinding
$k = 'HKLM:\System\CurrentControlSet\Services\NTDS\Parameters'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'LdapEnforceChannelBinding' -Value 0 -Type DWord # assumed value (not defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": SecGuide/Pol_SecGuide_0100_LdapEnforceChannelBinding
$k = 'HKLM:\System\CurrentControlSet\Services\NTDS\Parameters'
Remove-ItemProperty -Path $k -Name 'LdapEnforceChannelBinding' -ErrorAction SilentlyContinueOptions (1)
| Label | Control | Registry value | REG type | Constraints / details | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Configure LdapEnforceChannelBindingPol_SecGuide_LdapEnforceChannelBinding | Drop-down listenum | LdapEnforceChannelBinding | REG_DWORD | Default choice (UI): #0
|
Application
Microsoft Security Baseline (MSS, SecGuide) (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.