No, not really. They said that it's an Apple issue and Apple is
investigating and have it already fixed in 13.5 Beta 3. They suggested
to unscope configuration profile for now and open Apple Care case if
more information is needed.
Yeah, we just got a few tickets for this as well. We have a similar
configuration profile for deferrals and some machines are updating fine
when others, all M2 for now, are failing to update with the same error.
I opened a case with Jamf support.
Yes, that worked for us too :-) Thank you @daniel_ross for reminding
about that 'unnecessary' necessity! Funny thing I didn't remember about
this at all even though it was well covered during my last certification
and I had a case open with jamf supp...
