Skip to content

Deployment via NinjaOne

This guide covers deploying the SenseOn Universal Sensor to Windows, Linux, and macOS devices using NinjaOne (formerly NinjaRMM).

NinjaOne deploys SenseOn by running the SenseOn install command as an Automation (custom script) against target devices. The automation installs the latest published Universal Sensor on each device it runs on. On macOS you also need to deploy a Full Disk Access configuration profile so the agent can read the required system events.

💡 NinjaOne agent required: Every target device must already have the NinjaOne agent installed and be enrolled in your NinjaOne tenant. The SenseOn install runs through the NinjaOne agent, so a device that is not enrolled cannot be targeted.

Windows

Step 1: Copy your install command

  1. Log in to SenseOn.
  2. Navigate to Settings > Universal Sensor.
  3. Copy the Windows install command.

Step 2: Create the NinjaOne automation

  1. In NinjaOne, navigate to Administration > Library > Automation.
  2. Click Add > New Script.
  3. Configure the script:
    • Name: SenseOn Install (Windows)
    • Description: Installs the SenseOn Universal Sensor via the SenseOn install command.
    • Language: PowerShell
    • Operating System: Windows
    • Run As: System

  4. Paste the following into the Script Content area, substituting your tenant hostname and installer key from Step 1:

    $ErrorActionPreference = "Stop"
$env:SENSEON_INSTALLER_KEY = "<your-installer-key>"
Invoke-WebRequest -UseBasicParsing -Uri "https://<your-tenant>.senseon.io/install.ps1" |
    Invoke-Expression

  5. Click Save.

🛡 Optional: Verify the install script checksum

If your security policy requires checksum verification before executing remote scripts, download the script on your admin workstation first and verify the SHA-256 checksum against the value shown in Settings > Universal Sensor.

To use the verified script in the NinjaOne automation, replace only the Invoke-WebRequest ... | Invoke-Expression line with the contents of the verified install.ps1. Keep the $ErrorActionPreference and $env:SENSEON_INSTALLER_KEY lines in place — the installer will fail without the installer-key environment variable.

Step 3: Deploy to Windows devices

You can either run the automation on demand or attach it to a policy so it runs on every in-scope device automatically.

Ad-hoc run:

  1. In NinjaOne, navigate to Groups or Organizations and select your target Windows devices.
  2. Right-click the selection and choose Run automation.
  3. Select the SenseOn Install (Windows) automation and click Run.

Via a policy (recommended for larger fleets):

  1. Navigate to Administration > Policies > Agent Policies.
  2. Open the policy applied to your Windows devices (typically the Windows workstation or server role).
  3. Under Scheduled Automations, add the SenseOn Install (Windows) automation.
  4. Set the schedule to Run once so it does not re-run on every check-in.
  5. Save the policy.

Target hosts will appear in Digital Estate > Devices within a few minutes of the script completing.

Linux

Step 1: Copy your install command

  1. Log in to SenseOn.
  2. Navigate to Settings > Universal Sensor.
  3. Copy the Linux install command.

Step 2: Create the NinjaOne automation

  1. In NinjaOne, navigate to Administration > Library > Automation.
  2. Click Add > New Script.
  3. Configure the script:
    • Name: SenseOn Install (Linux)
    • Description: Installs the SenseOn Universal Sensor via the SenseOn install command.
    • Language: Bash / Shell
    • Operating System: Linux
    • Run As: Root

  4. Paste the following into the Script Content area, substituting your tenant hostname and installer key:

    #!/bin/bash
set -e
curl -fsSL https://<your-tenant>.senseon.io/install.sh \
  | SENSEON_INSTALLER_KEY="<your-installer-key>" bash

  5. Click Save.

Step 3: Deploy to Linux devices

Ad-hoc run:

  1. In NinjaOne, navigate to Groups or Organizations and select your target Linux devices.
  2. Right-click the selection and choose Run automation.
  3. Select the SenseOn Install (Linux) automation and click Run.

Via a policy:

  1. Navigate to Administration > Policies > Agent Policies.
  2. Open the policy applied to your Linux devices.
  3. Under Scheduled Automations, add the SenseOn Install (Linux) automation and schedule it to run once.
  4. Save the policy.

The installer detects whether the host uses apt or rpm and installs the appropriate package. Target hosts will appear in Digital Estate > Devices within a few minutes.

macOS

macOS deployment is a two-part process:

  1. Push a Full Disk Access configuration profile so the SenseOn agent can access the system events it needs.
  2. Run the SenseOn install command as an automation.

Both steps must be completed. If the install runs before the configuration profile is applied, the agent will install but will be unable to collect telemetry until Full Disk Access is granted.

Step 1: Deploy the Full Disk Access configuration profile

The SenseOn endpoint agent requires Full Disk Access to operate on macOS. NinjaOne can push the SenseOn Full Disk Access configuration profile through its built-in MDM.

💡 MDM enrolment required: Devices must be enrolled in NinjaOne's MDM (or a linked third-party MDM) for configuration profiles to apply. If your macOS devices are managed by the NinjaOne agent alone without MDM enrolment, the FDA profile cannot be pushed automatically and users will be prompted to grant Full Disk Access manually in System Settings > Privacy & Security > Full Disk Access.

  1. Download the SenseOn Full Disk Access profile: SEE-FDA.mobileconfig.
  2. In NinjaOne, navigate to Administration > Apps > MDM > Configuration Profiles.
  3. Click Add > Upload Profile.
  4. Give the profile a name such as SenseOn Full Disk Access and upload the SEE-FDA.mobileconfig file.
  5. Set the Scope to the macOS device group(s) you wish to deploy SenseOn to.
  6. Save and enable the profile.

Verify the profile has been applied to a target device before proceeding:

  1. On the macOS device, open System Settings > Privacy & Security > Profiles.
  2. Confirm SenseOn Full Disk Access is listed and shows as Verified.

💡 Using a linked MDM instead? If your macOS estate is managed by Jamf Pro or Kandji rather than NinjaOne MDM, deploy the configuration profile through that MDM first. See Deployment via Jamf Pro and Deployment with Kandji for the profile-upload steps in those tools, then return here for the install-command step.

Step 2: Copy your install command

  1. Log in to SenseOn.
  2. Navigate to Settings > Universal Sensor.
  3. Copy the macOS install command.

Step 3: Create the NinjaOne automation

  1. In NinjaOne, navigate to Administration > Library > Automation.
  2. Click Add > New Script.
  3. Configure the script:
    • Name: SenseOn Install (macOS)
    • Description: Installs the SenseOn Universal Sensor via the SenseOn install command.
    • Language: Bash / Shell
    • Operating System: macOS
    • Run As: Root

  4. Paste the following into the Script Content area, substituting your tenant hostname and installer key:

    #!/bin/bash
set -e
curl -fsSL https://<your-tenant>.senseon.io/install.sh \
  | SENSEON_INSTALLER_KEY="<your-installer-key>" bash

  5. Click Save.

Step 4: Deploy to macOS devices

Ad-hoc run:

  1. In NinjaOne, navigate to Groups or Organizations and select your target macOS devices.
  2. Right-click the selection and choose Run automation.
  3. Select the SenseOn Install (macOS) automation and click Run.

Via a policy:

  1. Navigate to Administration > Policies > Agent Policies.
  2. Open the policy applied to your macOS devices.
  3. Under Scheduled Automations, add the SenseOn Install (macOS) automation and schedule it to run once.
  4. Save the policy.

Verifying deployment

Once NinjaOne reports the automation as complete on a device:

  1. Log in to SenseOn.
  2. Navigate to Digital Estate > Devices.
  3. Confirm the device appears with its expected hostname and a recent Last Seen timestamp.

To check per-device rollout progress in NinjaOne:

  1. Navigate to Administration > Library > Automation.
  2. Open the automation you created.
  3. Review the Run History tab — each device is listed with its exit status and any script output.

📝 Note: Devices that have not checked in with NinjaOne since the automation was scheduled will show as Pending. Devices that have run the script show as Completed with an exit code — 0 is success, anything else indicates a failure.

For diagnostics if a host does not appear in SenseOn, see Troubleshooting.

❓ Need help? If the installation has not been successful, please confirm that TLS interception is not taking place. If it is, you will need to allow-list *.snson.net and *.senseon.io. Then contact our support team for additional help.