Software Deployment is the execution engine for your App Hub catalogue. A guided wizard takes a package from selection to a tracked, retryable job across your fleet.
Try DemoA New Deployment moves through four clear stages — no scripting required.
Pick App Hub apps flagged available for deployment and choose an action for each — install, uninstall, or update.
Target devices directly or by group, location, or tenant. A dynamic-membership flag keeps group targets live as devices come and go.
Set the run mode, schedule, expiry, retry behaviour, and failure handling for the job.
Confirm the packages, targets, and configuration, then submit the deployment job.
Step 3 exposes the knobs that decide how — and how forgivingly — a deployment runs.
Run interactively with real-time Console feedback, or in bulk in the background.
Submit now or schedule the deployment to begin at a chosen time.
Set a point after which the deployment will no longer attempt new devices.
Cap how many times a failed device is retried before the job gives up on it.
Set the minutes to wait between retry attempts.
Reinstall a package even where the device reports it already present.
Stop the whole deployment the moment any device fails.
Every deployment keeps a per-device record so failures are diagnosable, not mysterious.
Each device records its attempts with exit codes and stdout/stderr tails for fast diagnosis.
Retry re-queues only the devices that failed — successful targets are left untouched.
A deployment carries a clear status from pending through to completed, errors, or cancelled.
App Hub curates what can be installed; Software Deployment is how it actually reaches your devices. Build the catalogue once, then deploy from it as often as you need.
A guided wizard, flexible targeting, and retry handling that does the chasing for you.
View Pricing