-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task 1.2.4 - Failed to import secedit.ini #107
Comments
@kpi-nourman please provide as well what version of Windows you are using and how you are running it. For example We are working through a number of issues around this and we have only been able to test locally and on Azure. There have been ways with the order of controls that have been causing issues between local and cloud based, but I fear there is more logic we will have to build in. |
running using Windows Server 2019 Standard run on VM using VMware vSphere with Windows Version 1809, 10.0.17763 Build 17763 |
Ok seems that the common issue I am seeing now is that it is VSphere. In this case the order of how it is being applied is the issue. We saw that this is the case of azure vs local. Is it possible to get additional information for me using Ansible facts. I am wondering how Ansible is recognizing vsphere. The facts I am interested in are ansible_virtualization_type After this we will need to figure out the proper order of applying things. Also I need to know if the order it is running is the standard section 1 or it's trying to apply the cloud section one yaml. There are two unique orders depending on the type of system. Also check this link out as well we are seeing a similar issue in 2022 |
gather_facts for 2019, 2022, 2025 for vSphere nodes |
@kpi-nourman @animatco also do Cloud style 1.2.2 | PATCH | Ensure Account lockout threshold is set to 5 or fewer invalid logon attempt(s), but not 0. Or Local based System CONTROL 1.2.2, CONTROL 1.2.4, CONTROL 1.2.1, CONTROL 1.2.3 |
Also feel Free to msg me on discord if you are in there. |
hi @MrSteve81
|
Yes, in my output, run control 1.2.2 the task is ok, after that run control 1.2.4 the task fatal then playbook stopped.
|
I have pushed a update to dec24_updates repo could you please test this and let me know if it works. I am also going to push it to 2022 shortly. @animatco |
So we tested again on both a 2019 and 2022 Windows Server on vSphere. They failed at the 1.2.1 section, when we manually modified the prelim.
to be:
doing that allowed the code to continue. |
additional information from gather facts: Google: vSphere: Hyper-V: |
Just to let you know the latest update resolved the issue. |
Describe the Issue
Task 1.2.4 | PATCH | Ensure Reset account lockout counter after is set to 15 or more minutes. | Set Variable.]
fatal failed in below:
\tProcess Security Policy area\nThe parameter is incorrect.\n\nThe task has completed with an error.
"msg": "Failed to import secedit.ini file from C:\Users\nourman\AppData\Local\Temp\tmpE9FC.tmp",
Expected Behavior
pass that task
Actual Behavior
Ansible Failed to import secedit.ini file
Control(s) Affected
Rule 1.2.4
Environment (please complete the following information):
Additional Notes
Anything additional goes here
Possible Solution
resolution to solved this
The text was updated successfully, but these errors were encountered: