How to Install the Agent on Many Machines with One Installer
Generate one agent installer and run the same file on every machine. Each machine enrols by itself and appears as its own device.
Overview
You only need one installer file. Run the same file on every machine you want to manage. The first time the agent starts on a machine, it enrols that machine with Plenix and the machine appears as its own device.
This needs agent 3.79.2 or newer. Installers you generate now always contain the newest agent.
Install on several machines
- Go to RMM and choose Generate Agent Installer.
- If the machines belong to one of your customers, pick the company. Every machine installed from this file is added to that company.
- Download the installer for Windows, or copy the one-line command for Linux and macOS.
- Run the same file, or the same command, on each machine.
- Each machine appears in RMM as its own device within about a minute.
The download link stops working after 7 days. Machines that are already installed are not affected. Generate a new installer when you need to download the file again.
What happens on each machine
- The agent works out a private id for the machine from the id the operating system already keeps for itself. Only a scrambled form of it is sent to Plenix.
- Plenix gives that machine its own identity. The agent saves it next to the program and uses it from then on.
- If the machine has no internet connection on first start, the agent waits and enrols as soon as the connection is back.
Reinstalling and replacing machines
| Situation | What happens |
|---|---|
| You run the same installer again on the same machine | The machine keeps its device record and its history. No duplicate is made. |
| You set up machines from one disk image | Prepare the image the normal way (for Windows, with Sysprep) so that each machine gets its own id. Machines copied from a disk without that step look like one machine and share one device record. |
| You reinstall the operating system | The machine enrols again. If it has the same name and network address, it takes over its earlier device record. |
Stop an installer being used
Revoke the installer from the company's Monitoring tab, or ask your Plenix administrator. Revoking an installer also cuts off every machine that enrolled from it, so only revoke one when you want all of those machines to stop reporting.
Machines installed before this change
Machines you already manage keep their device record. You do not need to reinstall anything: the agent updates itself and enrols the machine during the update.
If you had run one installer on two machines before this change, they shared one device record and took turns showing as online. After both have updated to 3.79.2 they appear as two devices.
Related
← Previous
Agent Updates and Self-Repair
Next →
Remote Sessions: Seeing Which Machine and User You Are On
Was this article helpful?