You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?The text was updated successfully, but these errors were encountered: