Not alternatives so much as tools for different jobs.
Golden image The complete software state. For any fleet you want built identically. | Configuration file Settings only. For devices that already run the right software. | By hand, or by script Whatever you install. For a handful of devices, and the reference unit. |
Remote management (RCMS) None of your software. Manages Robustel firmware, apps and settings afterwards. |
Getting a device from its box into production means putting your software, your settings and your credentials onto it. RobustOS Pro gives you four ways to do that. They are not alternatives to one another so much as tools for different jobs, and most deployments use two or three together.
The four routes
| Route | What it puts on the device | Best for |
|---|---|---|
| Golden image (clone package) | The device's complete software state — your settings, packages, apps, containers and data, plus the Robustel system software on the reference unit | Any fleet you want built identically |
| Configuration file | Settings only | Devices that already run the right software but need different settings |
| By hand, or by script | Whatever you install | A handful of devices — and building the reference unit for a golden image |
| Remote management (RCMS) | None of your software — it manages Robustel firmware, Robustel-built apps and device settings afterwards | Any deployment you will manage remotely |
Set one device up, take a clone package off it, put that package on every other device.
Build the reference unit Then create the package on the command line. | → | Clone package Your software and settings plus the Robustel system software. | → | Onto the fleet Pre-installed at the factory, or per device by USB. |
Becomes the factory baseline A reset returns to your image, credentials included. | Shared identity Decide which credentials must be unique; issue them after restore. | Exact hardware match Same model and hardware variant, memory included. |
Set one device up exactly as you want it, take a clone package off it, and put that package on every other device. The package holds the device's complete software state — your configuration, the packages and apps you installed, container images and data, and your user data, together with the Robustel system software (the Linux kernel included) that was on the reference device. Restoring it replaces the whole of the target device's software, so every unit built from the package ends up on the same Robustel software version as the reference device — even if it left the factory on a different one, or has been updated since.
Building the package. Creation is a command-line step (rbt-system-mgmt clone create) — there is no button for it in the web interface. Before you build: clear the package cache (apt-get clean), make sure the writable layer has at least 50% free space, and use an ext4-formatted USB stick. Check the finished package with rbt-system-mgmt clone info before you rely on it.
Getting it onto the fleet — two routes:
Step-by-step instructions are published in the Robustel knowledge base: How to Bulk Copy EG Device Configurations & Applications.
Three things to know before you commit to this route:
Settings without the software. Export from one device, import on another through the web interface.
Settings only Not packages, apps, containers or data. | Applies on reboot The device restarts to use it. | Check after importing An unreadable file leaves the device on its default configuration. |
If your devices already run the software you want and differ only in how they are configured, you can export the configuration from one device and import it to another through the web interface. This is a super-admin operation.
Useful for per-site variation on top of a common build: one golden image everywhere, then the site's own configuration file on each.
Your side is a Debian machine: SSH, sudo and apt. Anything you can script, you can provision.
A RobustOS Pro device is a Debian system, and your side of it behaves like any Debian machine: you can reach it over SSH, use sudo, and install software with apt — so anything you can script, you can provision. Between your software and the Debian base sits Robustel's own system software, the Linux kernel included; that part is Robustel's to replace through firmware releases (see What an Update Changes).
Sensible for a handful of devices, for pilots, and for teams who already provision Linux estates with their own tooling. It does not scale on its own — but a scripted build feeding a golden image scales very well.
How you operate devices after deployment, alongside whichever route you use.
Manages Firmware updates, Robustel-built apps, device configuration. Robustel software and settings | Does not carry Your Debian packages or containers. Full-image installs stay on site. Your own software |
RCMS is how you operate devices after they are deployed rather than how you first set them up. For a 2.4.x fleet it manages Robustel's software and your device settings: firmware updates, distribution of Robustel-built apps, and device configuration.
What it does not do is put your own software on a device. Debian packages you install, and containers you run, have no RCMS delivery path on 2.4.x. Full-image installation is not an RCMS operation either; that stays a physical, on-site task.
| If you have | Use |
|---|---|
| More than a handful of identical devices | Golden image, pre-installed at the factory if the volume justifies it |
| Same software, different settings per site | Golden image for the build, configuration file for the site |
| A few devices, a pilot, the reference unit | By hand or by script |
| Any deployment you will not revisit | Enrol in remote management as well |
Decide this before you deploy. RCMS covers Robustel software and settings, not software you installed.
| Layer | Who and how |
|---|---|
| Firmware, kernel, Robustel apps | Robustel publishes; you install, per device or from RCMS |
| Device settings | You: web interface, command line or RCMS |
| Your packages, applications, containers, data | You, over SSH with apt |
Provisioning puts software on a device. Keeping it current afterwards divides along a line worth understanding before you deploy, not after.
| Layer | Who updates it | How |
|---|---|---|
| RobustOS Pro firmware, the Linux kernel, Robustel's own applications | Robustel | We publish releases; you install them — per device, or across a fleet from RCMS |
| Device settings | You | Web interface, command line, or RCMS |
| Your own Debian packages, your applications, your containers, your data | You | The device is a Debian 11 machine — you reach it over SSH and use apt |
RCMS covers the first two rows. It is not a delivery channel for software you wrote or installed yourself.
So plan your own update route before you deploy. On a fleet you cannot physically revisit, the practical shape is the one you would use for any Debian estate: publish your packages to your own signed repository, point the devices at it, and run the upgrade with the tooling you already use over SSH. See Updating Your Device → Shipping a new version of your own software.
Whatever state the reference unit is in propagates to the fleet.
1 Factory baseline Stays clean, or becomes your image? | 2 Unique credentials Which ones, per device? | 3 Automatic USB updates On or off in your image? |
4 Remote management Enabled in your image? |
| 1 | Does your factory baseline stay clean, or become your image? Choosing a golden image changes what every future factory reset on those units returns to. |
| 2 | Which credentials must be unique per device? Decide before you build the image, not after the fleet is deployed. |
| 3 | Are automatic USB updates on or off in your image? It ships off — but the image carries your configuration, so if you switch it on while building the reference unit, every device built from that image has it on too. |
| 4 | Is remote management enabled in your image? Same principle — whatever state the reference unit is in propagates to the fleet. |
What an Update Changes What updates and resets do to a provisioned device. | Securing Your Device Hardening a device once it is set up. | Updating Your Device Updating devices already in service. |
| Next · step 5 of 13Securing your device →The hardening checklist for putting a device into production. |