Addigy Priority Deployments allow you to modify the priority order in which MDM Profiles and Smart Software items reach a device. This means you can guarantee that essential software and settings are deployed to a device before anything else.
Priority Deployments unlock the ability to deploy items in the Pre-Enrollment stage of Automated Device Enrollment. With this, any items set to install in this stage will be configured before the user can finish setting up the device. Please be cognizant of what you are adding as large-sized pre-enrollment deployments can cause a delay in enrollment.
Pre-Enrollment Deployments works with Apple's Automated Device Enrollment to allow you to hold a device in a pre-enrollment state until specific software or MDM profiles are installed on the device. Once those essential items are successfully deployed, the device will continue into setup assistant where the user can continue onboarding. This allows Admins to guarantee that specific workflows will be available to users before they start their enrollment experience.
Directory
Policy Priorities
Before we can really harness the power of asset prioritization, we need to understand how the policy prioritizes deployment items today. Upon deployment, a policy will sort all the items that are to be deployed based on their priority ranking. The priority ranking can be a number from 0.1 to 19.9. Here's a look at the default priority for some catalog items:
Setting a Priority for Smart Software and/or MDM Profiles
To set a priority for Smart Software and/or MDM Profiles, we will need to go to the Catalog page, and press edit on an existing catalog item.
For Smart Software, the Installation Priority box will be located below the Installation Command.
For MDM Profiles. the box will be located at the footer.
You can modify the priority number to place this software item to be deployed within a specific stage of the policy deployment.
For example, we know that all Facts deploy with a priority of 2, which means if we wanted to have our software item deployed before Facts, we would assign it a number between 0-1.9. Alternatively, if we wanted this software to deploy at the very end of the policy we should assign it 19.9.
Pre-Enrollment Deployments
To configure Pre-Enrollment Deployment we need to set up a few items.
- Automated Device Enrollment must be configured with the Await Device Configured flag enabled.
- The specified software items or MDM profiles must have a priority value of 0-1
Await Device Configured
To start adding Software and MDM Profiles into the pre-enrollment state, you'll have to configure Automated Device Enrollment. What's important is that we enable Supervised Mode and Await Device Configured. These are key for holding the device in pre-enrollment while our policies deploy.
Once this is configured, we can now select which software and MDM profiles we want to deploy
Determining Items for Pre-Enrollment Deployment
Software and MDM Profiles can be prioritized within their policy deployments by setting a priority value. For them to be part of the Pre-enrollment Deployments group, we need to set the priority values anywhere between 0.1 and 1 (0.1, 0.22, 0.333, etc)
Once you have Automated Device Enrollment configured with the await device configuration flag and a few software and MDM Profiles set with priority values between 0.1 and 1. Any new device enrollment will now deploy those specific software and MDM profiles before the user reaches the setup assistant screen, allowing for a more tailored onboarding experience.