+7Hi 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
Best answer by andrew_nicholas
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.
+13If 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.
+7If 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.
Hi @andrew_nicholas,
Also thought on this and working on it already.
Thank you for this idea, will update when tested.
BR
Daniel
+7If 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.
Hi @andrew_nicholas,
Recreating all notification managed conf profiles at least fixed it for now.
Thanks again for the input
BR
Daniel
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.