Deployment with SCCM
Microsoft Configuration Manager (MCM) lets you deploy SenseOn to many devices. A common name for MCM is its old name, Microsoft System Center Configuration Manager (SCCM). This guide gives the suggested steps to deploy the SenseOn endpoint agent with SCCM.
Recommended: Deploy via the SenseOn Install Command
The simplest procedure is to deploy a small PowerShell script that runs the SenseOn install command. When the script runs, it downloads and installs the latest published version of the Universal Sensor. Thus it is not necessary to package or update an MSI.
Step 1: Copy your install command
- Log in to SenseOn.
- Go to Settings > Universal Sensor.
- Copy the Windows install command.
Optional: Verify the install script checksum
If your security policy makes checksum verification mandatory before you run remote scripts, do this procedure. Do a check of the script on your admin workstation before you create 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 SHA256If the hash matches, the script is genuine. In Step 2, replace the
Invoke-WebRequest ... | Invoke-Expressionline with the contents of the verifiedSenseOn-Install.ps1. Keep the$env:SENSEON_INSTALLER_KEYline.
Step 2: Save the install command as a PowerShell script
Save the script that follows as SenseOn-Install.ps1 in your shared SCCM source location. Replace the tenant hostname and the installer key with your values:
$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
- In Configuration Manager, go to Software Library > Application Management > Packages > Create Package.
- Set the package source folder to the location that contains
SenseOn-Install.ps1. - Create a Standard Program with this command line:
powershell.exe -ExecutionPolicy Bypass -File SenseOn-Install.ps1
- Set the program to run with administrative rights. Also set the program to run whether or not a user is signed in.
- Distribute the package to your distribution points.
- Deploy the package to the target device collection.
Detecting an existing installation: A Standard Program has no detection rule. But if you deploy the script as an Application, use a registry detection method for the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\senseon-bootstrapper. This key exists when the SenseOn bootstrapper service is installed. The install command installs the bootstrapper. The bootstrapper then downloads and installs the Universal Sensor. Thus, if you detect the bootstrapper, Configuration Manager is responsible only for the software that it deploys.
Step 4: Verify
The target hosts appear in Assets > Devices in a few minutes after the script runs. For diagnostics, refer to Troubleshooting.
Removing SenseOn
Remove the agent as Uninstalling SenseOn tells you. On Windows, when you uninstall the bootstrapper MSI, the services of the Universal Sensor stop immediately. But the uninstall operation only schedules the removal of the sensor package for the next time an administrator logs on. Thus a device that no one logs on to keeps the sensor package until then.
To remove the two packages in one run, deploy the uninstall script as an alternative. The script removes the sensor and clears the scheduled removal. If you remove only the sensor, the bootstrapper stays. The bootstrapper then installs the sensor again in approximately ten minutes.