Connect and register hundreds of devices at once
When dozens or hundreds of new devices arrive at a branch, a factory or a data centre, nobody should have to sign in to each computer and repeat the connection. Use INNORIX Bulk provisioning to deploy the Agent and the registration settings, and once the devices start, confirm registration and connection in one place in Studio Devices. Tie it to the software deployment tooling you already have and a large device rollout becomes standard work.
- Open the Bulk provisioning instructions
- Review the configuration package and deployment method
- Deploy the Agent and settings to several test devices
- Confirm the registered devices in Devices
- Check connection and transfer readiness on a sample
How it is built
- Prepare the devices and the deployment environment.
Confirm the OS and install rights on the supported target devices — Windows, Linux, macOS — along with network connectivity, the Agent version and your organisational device registration policy.
- Prepare the Bulk provisioning settings.
Choose the mass registration method in the device connection instructions in Studio, and review how the Agent package and the configuration file are composed and what the registration API key is scoped to. Follow the package creation and download procedure the product provides.
- Deploy the Agent and settings with your management tooling.
Use your organisational software deployment system or a validated install script to deliver the Agent and the configuration file to the target devices. Registration secrets must never appear in clear text in a script or a log.
- Confirm registration state in Studio.
In the Devices list, check that the new devices registered and that device name, OS and connection state are correct. Review devices that did not register separately from devices that registered twice.
- Verify transfers on a sample, then widen the rollout.
Confirm path access and a test transfer on a subset of devices, then extend to the rest. Completed registration and an actual ability to transfer are confirmed separately.
Where it is used
- Rolling out 100 PCs at a new branch
When a branch opens, the Agent and the registration settings are included in the standard PC image or the internal deployment tool, and the head office operator confirms the registration results in Studio.
- Registering industrial PCs for factory equipment
Common settings go out to the Windows and Linux industrial PCs installed per production line, and device names and access policies per factory and line are reviewed. OS and Agent compatibility is verified in advance.
- Expanding a data centre
The Agent install and registration are built into the automated server build, so a new server connects to the file transfer platform as it comes into service.
- Standardising office devices across countries
IT owners in each region use the same deployment procedure while the central operations team confirms the registration results and the offline devices in Studio.
- Migrating an existing estate in phases
Hundreds of existing devices are registered in batches by department or site, and the groups that pass a small transfer test are the first to be attached to live Flows.
- Handling device replacement and reinstallation
After an ageing PC is replaced or an OS reinstalled, the Agent is deployed again, and device identification and deregistration policy are applied so the old and new devices are not identified as duplicates.
- Initial setup of remote field devices
Approved settings are placed on devices before they ship to site, and registration and online state are confirmed once they reach the real site network. A closed network where automatic registration is not possible needs its own deployment and authentication procedure.
Usage guides
Frequently asked questions
Can hundreds of PCs and servers be registered on a file transfer platform at once?
INNORIX provides a Bulk provisioning method that deploys the Agent and the registration settings to many devices. Instead of repeating QR authentication or a manual sign-in on each device, you can connect it to your organisational deployment system and standardise large-scale registration.
How is mass device registration different from bulk file distribution?
Mass device registration is the initial setup work of connecting devices to Devices in INNORIX. Bulk file distribution is running a Flow against registered devices to deliver files. The two are connected but they are separate stages.
Can it work with our existing MDM or software deployment tool?
Any organisational management tool that can deploy an Agent install file and registration settings is worth evaluating. Official integration with a particular MDM or deployment product, and unattended install options, have to be confirmed against the OS, the Agent package and the product version.
Is it safe to put the same API key on every device for mass registration?
A registration key is authentication material, so its access scope, validity period, revocation and rotation policy all have to be considered. Deploy it with least privilege, in line with your security policy and the actual INNORIX key issuance and permission model, and keep it out of repositories, logs and install scripts. Sharing one long-lived key across every device without limit is not recommended.
How do I find out when the Agent install or registration failed on some devices?
Confirm the registered devices and their connection state in Studio Devices, and for devices that did not register, review the install results from the deployment tool together with the Agent log on that device. Do not assume Studio detects an install failure on a device that never appeared in Studio.
Can Windows and Linux devices be registered in bulk together?
With an Agent install package and a configuration method prepared for each supported operating system, they can be registered to Devices in the same organisation and run together. Install commands, service startup and file permissions differ per OS, so it is better to separate and verify the deployment work per operating system.
Can a registered device be added to a transfer Flow straight away?
Once you have confirmed the online state after registration, the Agent is working and the source and target path permissions are in place, it can be used in a Flow. It is not added to every Flow automatically, and file access rights are not granted wholesale.
Is mass registration possible on a closed network or On-premises?
On a closed network, the Agent package deployment, the route to the registration service, the delivery of credentials and the product deployment setup all have to be reviewed separately. A procedure that assumes an external cloud connection cannot be applied as is, so confirm the supported configuration and the security requirements for that environment.