Already a NinjaOne customer? Log in to view more guides and the latest updates.

Raspberry Pi ARM Support

Topic

This article discusses the NinjaOne functions supported by Raspberry Pi (Raspbian) OS devices and explains how to add them to the platform.

Environment

  • NinjaOne Endpoint Management
  • NinjaOne Linux Agent

Description

Raspberry Pi devices fill important roles as affordable, lightweight sensors and controllers for industries that require constant monitoring and display capabilities, such as manufacturing, agriculture, and warehousing. The NinjaOne platform can provide comprehensive status updates about the health of these devices, just like it does for Windows, Mac, and other Linux devices. You can apply policies to your Raspberry Pi endpoints and deploy automation scripts to them, enhancing their functionality.

Select a topic to continue.

Compatibility

NinjaOne supports the following Raspberry Pi models:

  • Pi2 (B)
  • Pi3 (A, B, A+, B+)
  • Pi4

Supported Features

The following table lists the NinjaOne features supported by the Raspberry Pi (Raspbian) OS.

NinjaOne does not display antivirus indicators, labels, or configuration options for Raspberry Pi OS devices, as the antivirus feature is not currently supported for ARM (Advanced RISC Machine) devices.
FeatureSupported?
Hardware MonitoringYes
Software InventoryYes
ScriptingYes
Remote Tools, including CLI & TerminalYes
Remote Access (ConnectWise Control/ScreenConnect)Yes
PatchingYes
Systray IconNo
Integrated AntivirusNo
Remote Access (TeamViewer, Splashtop)No
Remote Access (Cloud RDP)No
Ninja BackupNo

Adding a Raspberry Pi OS Device to NinjaOne

To add a Raspberry Pi OS device to NinjaOne, follow the process described in our NinjaOne Agent Installation: Add Device (Linux) article. When prompted, select Raspberry Pi from the Architecture drop-down menu.

Raspberry Pi devices use the Linux role for agent policies. 

addAComputer.png

Figure 1: Selecting architecture (click to enlarge)

The Software Inventory may not reflect the correct date if the Debian Agent's installation date is missing. Instead, it will reflect the Linux default date of 12:00 A.M. on January 1, 1970.

FAQ

Next Steps