Skip to content

Deployment via SCCM

Microsoft Configuration Manager (MCM) commonly referred to by its old name Microsoft System Center Configuration Manager (SCCM) is a way to support the mass deployment of SenseOn. This guide outlines the suggested steps for using SCCM to deploy the SenseOn endpoint agent.

The simplest approach is to deploy a small PowerShell script that invokes the SenseOn install command. The script downloads and installs the latest published version of the Universal Sensor at run time, so you do not need to package or update an MSI.

Step 1: Copy your install command

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

🛡 Optional: Verify the install script checksum

If your security policy requires checksum verification before executing remote scripts, verify the script on your admin workstation before creating the package:

# Step 1: Download the script
Invoke-WebRequest -UseBasicParsing -Uri "https://<your-tenant>.senseon.io/install.ps1" -OutFile SenseOn-Install.ps1
# Step 2: Verify the checksum (compare against the value shown in Settings > Universal Sensor)
Get-FileHash SenseOn-Install.ps1 -Algorithm SHA256

If the hash matches, the script is genuine. In Step 2 below, replace the Invoke-WebRequest ... | Invoke-Expression line with the contents of the verified SenseOn-Install.ps1, keeping the $env:SENSEON_INSTALLER_KEY line in place.

Step 2: Save the install command as a PowerShell script

Save the following as SenseOn-Install.ps1 on your shared SCCM source location. Substitute your tenant hostname and installer key:

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

Step 3: Create the SCCM package

  1. In Configuration Manager, go to Software Library > Application Management > Packages > Create Package.
  2. Point the package source folder at the location containing SenseOn-Install.ps1.
  3. Create a Standard Program with the command line:
powershell.exe -ExecutionPolicy Bypass -File SenseOn-Install.ps1
  1. Set the program to run with administrative rights and whether or not a user is signed in.
  2. Distribute the package to your distribution points.
  3. Deploy the package to the target device collection.

Step 4: Verify

Target hosts will appear in Digital Estate > Devices within a few minutes of the script running. For diagnostics, see Troubleshooting.