Home/RMS Bulk Configuration

RMS Bulk Configuration

What bulk configuration does

RMS bulk configuration allows you to push configuration changes or firmware updates to multiple Teltonika devices simultaneously – by selecting individual devices or entire device groups. Configuration templates let you define a standard configuration and apply it across a fleet without touching each device individually.

Bulk configuration workflow

1

Create a configuration template

Export a working configuration from a reference device (or create one manually) and save it as a template in RMS. Templates can be parameterised to allow per-device variables like hostname or SIM APN.

2

Select target devices or groups

In the RMS dashboard, select the devices or groups to receive the configuration. Devices can be filtered by model, firmware version, or status to ensure you only push to compatible targets.

3

Schedule or apply immediately

Push the configuration immediately or schedule it for a maintenance window. Scheduling is important for production devices where a configuration change may cause a brief restart.

4

Monitor the rollout

RMS tracks the push status for each device – pending, in progress, success, or failed. Failed devices can be individually reviewed and retried.

Bulk firmware updates

Bulk firmware updates work on the same model. Select a firmware version compatible with the target device models, select the target devices or group, and schedule the update. RMS downloads the firmware to each device and applies it, reporting success or failure per device. Scheduling updates in groups (rather than all at once) is recommended for production fleets to limit simultaneous device restarts.

Practical application – initial deployment

Bulk configuration is particularly powerful for initial deployment of a large fleet. Devices can be shipped to site, connected to power and a SIM, and automatically pick up their configuration from RMS – without any local engineering. The workflow is: zero-touch provisioning on site, credit assigned, configuration template pushed remotely, firmware confirmed, device operational. Site visits become optional rather than required for software configuration.