Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
PUP 5.5.1
-
None
-
None
-
- As an administrator I should be able to interactively run puppet agent no matter the original installation method.
-
Windows
-
1
-
Windows 2018-07-18, Windows 2018-07-25
-
Normal
-
3 - 25-50% of Customers
-
3 - Serious
-
4 - $$$$$
-
-
34512
-
1
-
Not Needed
Description
This issue was created from the work in PUP-6729
—
In some instances when Puppet Agent is installed as SYSTEM, the local administrators are unable to run puppet agent interactively.
Attachments
Issue Links
- relates to
-
PA-1165 Windows - pxp-agent.conf & server.cfg can only be accessed by local system account
-
- Needs Information
-
-
PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System
-
- Resolved
-
-
BKR-1478 beaker-pe should not backup the client_data directory
-
- Resolved
-
-
PA-910 windows agent permission errors
-
- Closed
-
-
PA-2019 Privilege escalation via %ProgramData%\PuppetLabs on Windows
-
- Closed
-
-
PUP-7793 Puppet agent replacing transactionstore.yaml on first run after boot
-
- Closed
-
-
PUP-9106 Windows file system ACLs should always write SYSTEM: (F)
-
- Closed
-
-
PUP-8771 Write integration/acceptance tests for NTFS permissions for PUP-6729
-
- Closed
-
-
PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
-
- Closed
-
-
PUP-9068 Windows admin? check should consider group membership
-
- Closed
-
-
PUP-5491 The "client_data" Directory Permissions Incorrect After Installation
-
- Resolved
-
-
PUP-266 Allow puppet to manage owner & group file settings (Redmine 18342)
-
- Closed
-
-
PUP-4684 windows file resource doesn't grant group full permissions
-
- Closed
-