Details
Description
What You Need From Engineering:
Help identifying a workaround / long-term fix for an issue setting ACLs with the "APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES" user.
Summary:
There seems to be an issue setting ACLs with this user no matter how you specify the name. I've attached a manifest using the strings:
- S-1-15-2-1
- APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES'
- ALL APPLICATION PACKAGES
..and these all fail
If applicable , did you do a run with --debug --trace?
Yes attaching output
OS & Version:
Windows 2012R2
PE Version on affected machine:
Puppet agent 1.10.1
ACL Module version
'puppetlabs-acl', '2.0.0'
Master Or Agent Affected:
Agent
Steps Taken To Reproduce:
With the attached manifest do a "puppet apply"
Files Acquired:
manifest acl.rtf
26132debug.rtf: Debug and trace output from the attached manifest
Attachments
Issue Links
- blocks
-
MODULES-5187 modsync for Puppet 5/Ruby 2.4
-
- Resolved
-
- relates to
-
MODULES-9215 ACL: Cannot update ACL if there is an existing unmanaged ACE for ALL RESTRICTED APPLICATION PACKAGES
-
- Open
-
-
PA-1374 Windows prop_file negative test failed "Expected ACL change event not detected!"
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
