Closed ntruden closed 2 years ago
We currently think this is a bug in Jamf Pro's API during the upload process. I am working with others within Jamf to get this sorted out. PI-009068 is the bug number.
This occurs only when "Big Sur Compatibility" is enabled in PPPC Utility, and will be fixed in an upcoming release of Jamf Pro.
@ntruden Jamf Pro v10.39 shipped today with the fix for this bug. From the release notes:
[PI103169] [PI-009068] Jamf Pro now respects key-values in uploaded configuration profiles that are created with the PPPC utility and correctly deploys the profiles to computers with macOS 11 or later.
When the PPPC is uploaded to Jamf Pro, access gets set to 'Allow Standard Users to Allow Access'. You have to "Edit" each privacy setting so Jamf will change it to just "Allow". If this is not done the profile fail when trying to deploy.