MULTI-DEVICE FILE DISTRIBUTION
One distribution job,
hundreds of devices delivered.
Distribute files and folders from a server to many devices at once. Choose connected devices or a group, pick the files and the destination, and INNORIX runs the per-device transfers and tracks overall progress.
One distribution job replaces creating a transfer for every device.
- One distribution jobNo separate transfer per device
- Group targetsConnected devices or a whole group
- Per-device progressOverall progress and per-device results
Factory A, Software distribution
Central Linux Server → Factory A, 100 devicesStudio / Runs
- Completed devices
- 100 / 100
| Target device | Progress | Status |
|---|---|---|
| factory-a-001 | 100% | Completed |
| factory-a-002 | 100% | Completed |
| factory-a-003 | 100% | Completed |
| factory-a-004 | 100% | Completed |
All 100 devices completed. Per-device results are being compiled.
SOURCE FILES & TARGET DEVICES
Choose the files to distribute, and pick the device group.
Select the files or folders prepared on the central server.
Target individual connected devices, or an entire group.
Delivering the same files to many devices is configured as a single Flow.
Source & targets
Source, Central Linux Server
/releases/2026.11/
application.bin2.4 GBconfig.json12 KBrelease-notes.txt24 KB
Target group
- Factory A 100
- Factory B 72
- Branch offices 64
- Targets
- Factory A, 100 devices
- Destination path
/opt/application/
3 files → Factory A, 100 devices, /opt/application/. The distribution job is set.
DISTRIBUTION RULES
Same location on every device, saved by the rules you set.
Set the destination path on target devices and how existing files are handled.
When a file already exists, apply the save rule you need, such as overwrite or automatic numbering.
Configure a destination that fits each device and preview the result before distributing.
Distribution preview
Central Linux Server, /releases/2026.11/
- application.bin
- config.json
- release-notes.txt
- Destination
/opt/application/ - If exists
Auto numbering
Target storage
| Device | Path | Result |
|---|---|---|
| factory-a-001 | /opt/application/ | 3 files |
| factory-a-002 | /opt/application/ | config_1.json |
| factory-a-003 | /opt/application/ | 3 files |
factory-a-002 already has a config.json, so the file is saved as config_1.json.
DISTRIBUTION EXECUTION & AUTOMATION
Distribute now, or automatically on a schedule or event.
Run a distribution job right away, or schedule it hourly, daily, weekly or monthly.
A distribution can also start on an event, such as new files becoming ready or a previous job completing.
Automate recurring software rollouts, configuration updates and device data distribution.
Factory A, Software distribution
Scheduled execution, Every day at 02:00
- MON 11/0902:00Completed
- TUE 11/1002:00Completed
- WED 11/1102:00Completed
- THU 11/1202:00Scheduled
- WED 02:00 run, devices
- 100 / 100
- Next execution
- THU 11/12 02:00
Event trigger
- New release, /releases/
2026.11.2 ready- Triggered distribution
- Completed, 100/100
Distributions run and are logged automatically, on schedule and when new files are ready.
DISTRIBUTION MONITORING
From the whole distribution down to each file on each device.
Follow overall distribution progress and the number of completed devices.
Drill into a single device and search its files for completed, failed and incomplete status.
On an interrupted device, see how far the files got and trace errors and recovery results.
Factory A, Software distribution
| Device | Progress | Status |
|---|---|---|
| factory-a-001 | 100% | Completed |
| factory-a-002 | 100% | Completed |
| factory-a-003 | 100% | Completed |
| factory-a-004 | 100% | Completed |
FAQ
File distribution setup & execution
Can I distribute files from one server to many devices?
Yes. A 1:N transfer distributes files from a single source server to many devices or device groups.
Can I choose which files and folders to distribute?
Yes. Select files and folders on the connected source server to build the distribution.
Can I distribute to an entire device group?
Yes. Device groups built in Studio can be selected as the distribution target.
Can each device have a different destination path?
Yes. Destination paths and save rules can be configured to fit each device's environment.
What happens when a file with the same name already exists?
It is handled by the configured save rule, such as overwrite or automatic numbering.
Can distribution run automatically at a set time?
Yes. Scheduled runs can be set hourly, daily, weekly or monthly.
Can distribution start automatically when new files are ready?
Yes. Supported event conditions start a distribution when a new file appears or a previous job completes.
Can I follow distribution progress per device?
Yes. Runs shows the overall distribution, per-device progress and per-file results.
What happens if some devices are offline?
The configured exception policy applies, such as wait, retry or skip.
If a distribution is interrupted, does it start over?
No. Depending on the recovery policy, completed files are kept and the transfer resumes with the incomplete files or from where it stopped.
GET STARTED