IMazing's blueprints can be configured to, in Apple Configurator lingo, prepare devices. The format is encrypted and secure, and you can choose to exclude your organization's certificate so that you don't expose secrets when sharing workflows with the community. IMazing's blueprints can be exported and shared in. You can also select a blueprint and put iMazing in Interactive mode, and connect devices one after the other: every new connected device will be automatically processed. You can limit the maximum number of devices processed at the same time, and let iMazing manage a queue. IMazing Configurator can handle bulks of devices simultaneously. The features listed below are unique to iMazing Configurator, or present substantial improvements. We've specifically developed iMazing Configurator to handle real world use cases where Apple Configurator is inadequate. How's that different from Apple Configurator? All these tasks and more can be automated via blueprints. Also available are a series of actions to perform on the target devices: update the OS, run a battery health check, erase, perform a backup or restore one. Here's the blueprints library:īlueprints encapsulate a wide array of settings and configuration options, including supervision, MDM enrollment, apps and app files, profiles, wallpapers, and setup assistant configuration. But that's just the surface the real power of iMazing Configurator resides within its advanced blueprint editor and format. Here's what the Devices library looks like:įrom here, simple tasks can be performed on bulks of devices: operations such as backing up, updating the OS, removing pairing or exporting device details can be launched in just a couple of clicks, with progress reported inline per device. IMazing Configurator is built from the ground up to enable easy processing of a single device or of dozens of devices simultaneously, using the same unified workflow. Today, we are glad to announce the availability of iMazing Configurator, a fully fledged app within the app dedicated to local configuration and provisioning of iOS, iPadOS and tvOS devices. They often face unique challenges which cannot be solved with Apple Configurator or MDM alone. So I assume this untrusted cert is the root of the error, have now removed accordingly.For years now, we've been interacting with IT professionals who are leveraging iMazing's capabilities to back up Apple mobile devices, migrate their data, or provision them with contacts, PDF documents and other files or media. Date ranges are valid on both, as to why the older org profile is untrusted, I can only guess. 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. However, I now have two items in my Org list have exactly the same string, which isn't brilliant. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |