With DDM (and forgive this barely unnuanced layman’s articulation), the device is instructed to upgrade and can then be required to accomplish that by a selected time. Then, fairly than polling the device to nag it to conduct the upgrade, the device itself is forced to commonly report back on whether it has achieved the specified upgraded state. On this model, the device is made aware that it should upgrade and can upgrade itself at the primary possible opportunity.
There are several benefits — management is more practical, network demands are reduced, and IT has a a lot better overview across the state of the company fleet. DDM can also be safer, because the onus of reporting turns to the device, which, along side improvements in identity and zero-trust, means IT enjoys a much more accurate picture of events, and devices turn out to be less prone to turn out to be attack vectors.
What difference does it make?
Apple’s growing cohort of device management partners (Jamf to Kandji, Mosyle, Fleet, Hexnode, Addigy and beyond) already understood Apple’s intention to maneuver toward DDM, which implies they’re already introducing support for the improved DDM features Apple plans.