Rollouts
Rollouts enable safe, gradual deployment of configuration changes across your device fleet.
Why Use Rollouts?
Deploying to hundreds of devices simultaneously risks:
- Network congestion from simultaneous downloads
- Widespread failures if the configuration has issues
- Difficulty identifying which devices failed
Rollouts solve this through controlled, batched deployments.
Creating a Rollout
- Go to Rollouts > New Rollout
- Select target fleets
- Choose configuration and version
- Set batch size
- Review impact analysis
- Execute
Batch Size
Define how many devices update simultaneously:
Total devices: 500
Batch size: 50
Result: 10 batches of 50 devices each
Smaller batches: Safer, slower, less network impact Larger batches: Faster, higher risk, more network usage
Recommended: Start with 5-10% of fleet, increase as confidence grows.
Impact Analysis
Before executing, Admiral shows:
- Total devices affected
- Estimated bandwidth required
- Potential compatibility issues
- Offline devices (will update when reconnected)
Monitoring Progress
Track rollout status in real-time:
- Pending: Waiting for their batch
- In Progress: Downloading/applying update
- Completed: Successfully updated
- Failed: Encountered errors
Handling Failures
If devices fail:
- Pause the rollout
- Investigate failed devices (check logs)
- Fix the issue
- Resume or retry
Automatic Rollback
Configure rollback thresholds:
- "Rollback if >10% fail"
- Failed devices revert to previous version
- Successful devices remain on new version
Rollout Strategies
Canary Deployment
- Deploy to small "canary" fleet (5-10 devices)
- Monitor for 24-48 hours
- If stable, proceed with full rollout
Phased Rollout
Phase 1: 10 devices (2%)
Phase 2: 50 devices (10%)
Phase 3: 100 devices (20%)
Phase 4: Remaining devices
Geographic Rollout
Week 1: Asia-Pacific fleet
Week 2: European fleet
Week 3: North American fleet
Version Management
- Version History: Track all changes
- Pinning: Lock devices to specific versions
- Rollback: Revert to any previous version