configuring apple configurator 2.5 for jamf now

#Configuring apple configurator 2.5 for jamf now for mac
#Configuring apple configurator 2.5 for jamf now manual

You can alternatively use Apple Configurator for Mac in the following workflow, which requires iOS 11 or later. So I assume this untrusted cert is the root of the error, have now removed accordingly. To enroll an iPad or iPhone, Jamf recommends using Apple Configurator for iPhone, which requires iPadOS 16.1 or later, or iOS 16 or later. > Click edit and assign the iPads that has the modified date: 'added less than a minute ago'. > Click on the existing PreStage enrolment or create a new PreStage enrolment. Date ranges are valid on both, as to why the older org profile is untrusted, I can only guess. In Jamf Pro, go to Mobile Devices and then PreStage Enrolment. So I head on over to Configurator 2 Preferences, Orgs, and then look for the one that has the older certificate date when you click on 'Show Supervision Identity.' - this is where I find that the older idendity appears to have an untrusted cert, and the newer one is trusted. This is to prevent those situations in BYOD and it gets enrolled buy maybe you dont agree with it being locked down as it is your device.

#Configuring apple configurator 2.5 for jamf now manual

In the Prepare with field, choose Manual Configuration and select. CoreyThomas the new configurator enrollment has a 30 day grace period by which a device enrolled can still be unenrolled with in 30 days by the user. However, I now have two items in my Org list have exactly the same string, which isn't brilliant. With Apple Configurator 2. A USB hub can be used to configure New In Apple Configurator 2.5 and iOS 11. It revalidated with the ABM apple ID and then the prepare went through on the iPad without error. So last thing to try was to choose the 'New Organization' option on the 'Assign to Organisation' option. I'm testing MDM differences, so have two MDMs setup (Jamf and the other both had this same error). The fix (for me) was to re-create the Organization profile as part of the Prepare steps. I just had this exact error in my new development environment.