Posted on 10-08-2021 12:56 AM
Hi Jamf nation,
Since we updated to 10.32 (from 10.26) all configuration profiles are failing with "This profile no longer exists or contains invalid payload data" (already enrolled Device) or "The profile is either missing some required information or contains information in an invalid format." (newly enrolled Device)
Any suggestion?
Thank you
BR
Daniel
Solved! Go to Solution.
Posted on 10-08-2021 03:17 AM
If memory serves this was something to do with unsigned profiles not being saved after the upgrade. The quickest solution we had was to just rebuild the notification payload and redistribute.
Posted on 10-08-2021 03:17 AM
If memory serves this was something to do with unsigned profiles not being saved after the upgrade. The quickest solution we had was to just rebuild the notification payload and redistribute.
Posted on 10-08-2021 05:28 AM
Hi @andrew_nicholas,
Also thought on this and working on it already.
Thank you for this idea, will update when tested.
BR
Daniel
Posted on 10-11-2021 06:33 AM
Hi @andrew_nicholas,
Recreating all notification managed conf profiles at least fixed it for now.
Thanks again for the input
BR
Daniel