Skip to content
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

UserAccountControl: ComputerManagementDsc vs SecurityPolicyDsc #344

Open
aydeisen opened this issue Jul 9, 2020 · 1 comment
Open

UserAccountControl: ComputerManagementDsc vs SecurityPolicyDsc #344

aydeisen opened this issue Jul 9, 2020 · 1 comment
Labels
question The issue is a question.

Comments

@aydeisen
Copy link

aydeisen commented Jul 9, 2020

Out of curiosity: what's would be the use case for me to use the UserAccountControl resource in the ComputerManagementDsc module instead of the setting the User_Account_Control* keys for the SecurityOption resource in the SecurityPolicyDsc module?

@PlagueHO PlagueHO added the question The issue is a question. label Dec 3, 2020
@PlagueHO
Copy link
Member

PlagueHO commented Dec 3, 2020

Hi @aydeisen - there does seem to be some cross over with both resources. This does happen from time-to-time - especially when there are multiple ways of achieving something using PowerShell. In this case the UserAccountControl resource has a less granular option for setting parameters.

But from an implementation perspective, UserAccountControl sets values in the registry directly where as SecurityOption uses secedit.exe to set the options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue is a question.
Projects
None yet
Development

No branches or pull requests

2 participants