Deployment with baramundi
This guide covers deploying the SenseOn Universal Sensor to Windows devices using baramundi Management Suite (bMS).
The recommended approach is to wrap the SenseOn install command in a PowerShell step inside a baramundi software package. The package always installs the latest published version of the Universal Sensor at run time, so no MSI needs to be staged on a depot or refreshed when a new sensor version is released.
Step 1: Copy your install command
- Log in to SenseOn.
- Navigate to Settings > Universal Sensor.
- Copy the Windows install command. It has the structure:
$env:SENSEON_INSTALLER_KEY="<your-installer-key>"; iwr -useb https://<your-tenant>.senseon.io/install.ps1 | iex
Step 2: Create the install script
Save the command as SenseOn-Install.ps1 on the machine where you run the baramundi Deployment Studio (bDS):
$ErrorActionPreference = "Stop"
$env:SENSEON_INSTALLER_KEY = "<your-installer-key>"
Invoke-WebRequest -UseBasicParsing -Uri "https://<your-tenant>.senseon.io/install.ps1" | Invoke-Expression
Substitute your tenant hostname and installer key from Step 1.
Step 3: Create the baramundi Software Package
- Open the baramundi Deployment Studio (bDS).
- Create a new package and name it
SenseOn Universal Sensor. - Add a PowerShell action (or a Run command action that invokes
powershell.exe). -
Configure the action to run:
powershell.exe -ExecutionPolicy Bypass -File SenseOn-Install.ps1 -
Add
SenseOn-Install.ps1to the package's source files so it is delivered to the endpoint alongside the action. - Set the action to run as Local System so the install has the privileges it needs.
- Save the package and publish it to your baramundi depot.
Detection rule: Configure the package's "Installed" detection rule to check for the presence of
C:\Program Files\senseon-see\senseon-agent.exe. This allows baramundi to recognise that an endpoint already has SenseOn installed and avoid re-running the install.
Step 4: Create the baramundi Job
- In the baramundi Management Center, open Jobs and create a new job.
- Give the job a name such as
Install SenseOn Universal Sensor. - Add the
SenseOn Universal Sensorpackage as a job step with the Install action. - Under Targets, add the devices or device groups you want to deploy to (typically an OU, a baramundi group, or a dynamic group based on attributes).
- Set the Schedule to run on next check-in (or as appropriate for your environment).
- Save and enable the job.
Step 5: Verify
baramundi will run the job on each in-scope endpoint at its next check-in. Once the job completes successfully:
- Log in to SenseOn.
- Navigate to Digital Estate > Devices.
- Confirm the host appears with its expected hostname and a recent Last Seen timestamp.
The job log in the baramundi Management Center reports the per-device status of the deployment, including the exit code of the PowerShell action.
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. Then contact our support team for additional help.