Components

A component is a packaged job for a device: install an application, deploy a security agent, or run a script that fixes something. You build it once and then run it wherever it is needed.

Open RMM → Components.

Built-in components

More than 80 components are ready to use:

• Applications, installed silently with winget: browsers, productivity tools, communication apps, developer tools, runtimes, remote access tools, VPN clients, cloud storage, media and utilities.
• Security agents: ESET, SentinelOne, CrowdStrike Falcon, Sophos Endpoint, Huntress, Bitdefender GravityZone and Webroot SecureAnywhere. You supply your own installer link and licence key or site token.
• Printers: add a network printer with its driver, remove a printer, set the default printer and clear stuck print jobs.
• Maintenance: clear temporary files, restart a service, restart the computer, rename the computer, set the time zone, sync the clock, set the power plan, refresh Group Policy, repair Windows system files and reset Windows Update.
• Security hardening: turn on Windows Firewall, disable the Guest account, turn Remote Desktop on or off, block or allow USB storage, and update, scan with or add an exclusion to Microsoft Defender.
• Software: uninstall an app by name and remove built-in Windows apps.
• Linux and macOS: install updates, install a package, restart a service, flush the DNS cache and report disk space.

Built-in components are read-only. Choose Copy to edit to make your own version.

Three kinds of component

• Package. An application from the winget catalogue. Plenix installs it for every user on the device.
• Installer. An MSI or EXE file. You can upload the file to Plenix, or give the vendor's download link together with the file's SHA-256 checksum. Plenix checks the checksum on the device before it runs the installer, so a changed or tampered file is never run.
• Script. PowerShell on Windows, or a shell script on Linux and macOS.

Variables and secrets

A component can ask for values when it runs, such as a printer address, a service name or a licence key. Variable types are text, number, yes/no, a list of choices, a link and a secret.

Secrets are stored encrypted, are never shown again after you save them, and are removed from the output kept in the run history. Use a secret for anything like a licence key, a site token or a password.

Skip devices that are already done

Set a Skip when check so a component does nothing on a device that does not need it. The check can look for installed software, a file, a registry value, a service, or the result of a short check script.

Restarts

Each component says what happens after it runs: never restart, restart only if the install asks for it, or always restart. You can override this each time you run it.

Running a component

Choose Run, pick the devices (all devices, customers, groups and filters, or chosen devices), fill in any variables and confirm. A component only runs on devices with the right operating system; the others are skipped and listed as skipped.

The Runs tab shows every run with its result, output and the person or rule that started it. Filter it by component, status or batch.

Running a component automatically

• From a monitoring policy, when a monitor raises an alert. See Monitoring Policies.
• From an automation, when a trigger fires. See Scripts, Policies and Automation.