Have you checked ReadtheDocs?:
Yes
Describe the Issue
When executing the Ansible task: "PRELIM | Obtain Then Load Default And User Hives | Pull all username and SIDs"
which is located on the prelim.yml file. When I try to execute the section 19 , the playbook hangs indefinitely. on this task, probably because the VM is already domain joined and trying to fetch all the users from organization.
Expected Behavior
The task should complete successfully or fail gracefully (e.g. with helpful output), but it should not hang indefinitely.
Actual Behavior
The task hangs on this specific step when running on a domain-joined VM
Control(s) Affected
PRELIM Step - User hives collection and SID enumeration
Potential impact on downstream CIS controls relying on local accounts
Environment (please complete the following information):
- branch being used: main
- Ansible Version: core 2.14.4
- Host Python Version: Python 3.9.16
- Ansible Server Python Version: Python 3.9.16
- Additional Details: VM receives domain membership during provisioning before the CIS role runs
Additional Notes
The issue has been consistently reproducible only on domain-joined machines
Possible Solution
Add handling to detect if the host is domain-joined and skip or adjust the task accordingly
Have you checked ReadtheDocs?:
Yes
Describe the Issue
When executing the Ansible task: "PRELIM | Obtain Then Load Default And User Hives | Pull all username and SIDs"
which is located on the prelim.yml file. When I try to execute the section 19 , the playbook hangs indefinitely. on this task, probably because the VM is already domain joined and trying to fetch all the users from organization.
Expected Behavior
The task should complete successfully or fail gracefully (e.g. with helpful output), but it should not hang indefinitely.
Actual Behavior
The task hangs on this specific step when running on a domain-joined VM
Control(s) Affected
PRELIM Step - User hives collection and SID enumeration
Potential impact on downstream CIS controls relying on local accounts
Environment (please complete the following information):
Additional Notes
The issue has been consistently reproducible only on domain-joined machines
Possible Solution
Add handling to detect if the host is domain-joined and skip or adjust the task accordingly