Hi everyone,
We’re managing a set of iOS devices and noticed the Software Update Preferences using DDM in Hexnode. I understand it works differently from the usual update methods, but I’m not very clear on what actually makes it better or when it should be used in a real setup.
If anyone has used this or can explain it with a practical example, that would really help.
19 Views
Using DDM for OS updates, and honestly, it’s a game changer for us. Instead of the server constantly polling the device to see if it updated, the device itself autonomously works to get to that state and reports back.
It is really useful when rolling out updates gradually. For example, updates can be delayed for a few days so they can be tested first, and only then made available across all devices. This helps avoid issues with apps that the organization depends on.
What about beta updates and notifications? We have had cases where users install unstable beta versions, and at the same time, too many update prompts end up annoying users.
Hi @margaret,
Beta updates can be fully restricted to prevent users from installing unstable versions, or selectively allowed for specific groups such as testing teams. This way, pilot users can evaluate upcoming releases while the rest of the devices remain on stable versions.
Notification behavior can also be adjusted. Update prompts can either be shown as usual or disabled. This helps reduce unnecessary interruptions for users while still ensuring that required updates are completed.
Regards,
Sienna Carter
Hexnode UEM
Don't have an account? Sign up
