Posted on 09-19-2024 07:59 AM
Since Jamf Pro was upgraded to 11.9.1 we are getting Profile installation failed message when configuring brand new iPads and also existing devices after erasing them.
Screenshot of the error attached below
No change on our environment
Any help would be appreciated.
Thank you
Posted on 09-19-2024 08:22 AM
Have you accepted the new agreement in ABM/ASM?
Posted on 09-19-2024 08:24 AM
yes already agreed the new agreement on ABM.
Thank you
Posted on 09-19-2024 08:47 AM
There is a thread on slack that talks about this
Are you by a chance pushing out settings to manage wallpaper?
Posted on 09-19-2024 10:23 AM
Yes we have a automated wallpaper deployment to the prestage devices
Do you have a link for that slack?
Thank you
Posted on 09-19-2024 01:19 PM
Mac Admins Slack
#jamfnation channel
Posted on 09-19-2024 01:08 PM
We have a ticket opened with JAMF support and they told me the same thing about the Wallpapers and Automated management in the smartgroup. We use this for all of our devices and are running into the same issues with SCEP errors during provisioning.
Posted on 09-19-2024 02:01 PM
Yes, this a known Jamf PI with v11.9.1, apparently a hotfix is in the works and is tentatively scheduled to update cloud deployments on 9/27/24 if I heard correctly. In the interim, you can remove the device record from Jamf and enroll the device if re-enrolling existing devices. You may have to remove the Automated Wallpaper as well, although I didn't when re-enrolling. Not sure what your options are for new devices where you cannot remove the Jamf record other than trying to remove the Automated Wallpaper for the time being.
Posted on 09-20-2024 12:10 PM
Thank you for the information
We are also seeing sign in and sign out issue as of today on shared devices
only change we did was we not deploying automated wallpaper yesterday
Anyone seen this in their environment?
Posted on 09-20-2024 12:13 PM
To be clear its giving 403 error on jamf setup app
Posted on 09-23-2024 08:53 AM
Apparently JAMF deleted the record of our jamf setup and reset app so had to restore our jamf server database which did resolve the issue