Hello everyone, we've been dealing with a strange bug that creates a locked "Library" folder, and a "private" folder when we push a policy that drops a file or folder onto a computer. They don't seen to cause any issues, but they do look messy. Has anyone else seen this? We are running MacOS 10.14, and Jamf Pro 10.22. Thanks in advance!
Hi there, I get the same issue since creating the last few packages. I only put one file into the composer and create a pkg to enroll this file to a specific directory. While the rollout runs, the two directories where created automatically . My workaround is at this time, to delete them with a script. At this time, I am playing around with the settings of the composer app. I think the cause for this behavior is somewhere there.