Deploying app updatesSolved

Participant
Discussion
1 week ago Mar 26, 2026

We’re trying to get better at how we deploy app updates across devices.

Right now it’s basically “deploy to everyone and hope for the best,” which… hasn’t always gone well. Came across phased rollout strategies, how are you guys actually using this in practice?

Replies (6)

Marked SolutionPending Review
Participant
7 days ago Mar 26, 2026
Marked SolutionPending Review

If you’re deploying to everyone at once, that’s the first thing to fix.

Phased rollout is really about reducing impact. Instead of updating your entire device fleet in one go, you split it into smaller groups and move step by step.

Marked SolutionPending Review
Participant
7 days ago Mar 26, 2026
Marked SolutionPending Review

Yeah, but is anyone here actually doing this through Hexnode?

Marked SolutionPending Review
Hexnode Expert
7 days ago Mar 26, 2026
Marked SolutionPending Review

Hi @mo-chou,

In Hexnode, phased rollout for app patching is designed to give you controlled, step-by-step deployment rather than a one-time deployment across all devices.

You can configure multiple phases, each targeting a specific group of devices, using features such as Dynamic Groups, and Update Deferral. These dynamic groups can be based on your existing device segmentation, such as departments, locations, or test groups.

Each phase can be scheduled, allowing you to define when the update should be deployed to that group. This ensures that updates can be rolled out progressively without disrupting users during active hours.

Regards,
Sienna Carter
Hexnode UEM

Marked SolutionPending Review
Participant
6 days ago Mar 27, 2026
Marked SolutionPending Review

So it’s not just batch deployment, it’s more like structured stages?

Marked SolutionPending Review
Hexnode Expert
6 days ago Mar 28, 2026
Marked SolutionPending Review

Hi @ezekiel,

Each phase acts as a checkpoint. Once a phase is completed, you can monitor how the update behaves across that group, whether installations succeed, if there are failures, or if any unexpected behavior is observed.

Based on that, you can proceed to the next phase, delay it, or make adjustments if required.

Regards,
Sienna Carter
Hexnode UEM

Marked SolutionPending Review
Participant
4 days ago Mar 29, 2026
Marked SolutionPending Review

Got it. So the idea is to use each phase as a validation step, not just a deployment step.

Save