[BUG] Missing Domain Controller GPOs #62873
Labels
Bug
broken, incorrect, or confusing behavior
Confirmed
Salt engineer has confirmed bug/feature - often including a MCVE
Execution-Module
lgpo
Sulfur v3006.0
release code name and version
Windows
Milestone
Description
Salt lgpo module cannot find two of the "Domain controller" security settings policies: "Domain controller: Allow vulnerable Netlogon secure channel connection", and "Domain controller: LDAP server channel binding token requirements".
Setup
Salt 3005.1 installed on Windows Server 2016
This was tested and set up on a VMware virtual machine (VMware Fusion).
Steps to Reproduce the behavior
Log into the Windows Server 2016 UI. It doesn't need to be promoted to a domain controller. Launch gpedit.msc. Navigate to Local Computer Policy, Windows Settings, Security Settings, Local Policies, Security Options. Note the Policy names starting with "Domain controller:". In the UI, note that five policies are listed:
Run
salt-call --local lgpo.get machine return_full_policy_names=True
. Note that only three of the policies listed above are returned.These policies are missing:
Expected behavior
Policies showing up in the UI should also show in the list returned by
lgpo.get
.Screenshots
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
@twangboy asked me to include the reference to the backing registry keys.
"Domain controller: Allow vulnerable Netlogon secure channel connections" is backed by
"Domain controller: LDAP server channel binding token requirements" is backed by
CIS document added this note: This Group Policy path requires the installation of the March 2020 (or later) Windows security update. With that update, Microsoft added this setting to the built-in OS security template.
The text was updated successfully, but these errors were encountered: