Open aydeisen opened 4 years ago
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.
Out of curiosity: what's would be the use case for me to use the
UserAccountControl
resource in theComputerManagementDsc
module instead of the setting theUser_Account_Control*
keys for theSecurityOption
resource in theSecurityPolicyDsc
module?