Deployment via Jamf Pro
This guide will cover the necessary steps to deploy the SenseOn Universal Sensor to macOS devices using Jamf Pro.
Compatibility: Deployment is fully supported via Jamf Pro but is not currently compatible with Jamf Now.
Step 1: Enable Full Disk Access
The SenseOn Endpoint agent requires Full Disk Access to operate. To give the agent full disk access upload the following configuration profile to the Jamf management device.
- Download the file named: SEE-FDA.mobileconfig. Click here to download SEE-FDA.mobileconfig
- Login to Jamf Pro and navigate to: Computers > Configuration Profiles
- Click: Upload > Select the SEE-FDA file > Click: Upload
- Set the Scope according to your requirements (this can be set to ‘All Computers and All Users’ to deploy to every device managed by Jamf). Leave all other settings as Default
Step 2: Setup the Distribution Point
If the Distribution Point is not yet configured follow these steps:
- Navigate to: Settings > Server Infrastructure > Cloud Distribution Point
- Select the dropdown for Content Delivery Network
- Choose Jamf Cloud
- Tick: 'Use as Principal Distribution Point'
- Click: Save
Step 3: Upload Package
Once the Distribution Point has been configured, add the package to Jamf pro using the following steps.
- Navigate to: Settings > Computer Management > Packages
- Click: New
- Click: Choose File and select the SenseOn Agent .pkg file. Note. If the choose file button is missing you need to complete Step 2: Setup the Distribution Point
- Click: Save
Step 4: Setup Install Key Script
To place the install key in the correct location create a script which places the key in /tmp:
- Download the install key file from the SenseOn Platform: Settings > Endpoint Agent Software
- Open the key in a text editor and Copy the contents to the clipboard
- In Jamf, navigate to Settings > Computer Management > Scripts
- Click: New
- Give the script a name e.g. install key
- Click the Script tab
-
Use the script below, pasting in the install key content where prompted
cat > /tmp/senseon_install.txt << 'EOF' <PASTE CONTENTS OF install_key.txt HERE> EOF
-
Click: Save
Step 5: Create a Policy
Once the package and install key is added to Jamf, create the policy to push the install key and package to the Jamf management device the next time it checks in.
Note: Due to a quirk in the way Jamf applies policies, the script must also be configured to update the inventory of the Jamf management device.
- Navigate to: Computers > Policies
- Click: Add
- Give the Policy a suitable name e.g. SEE
- Tick the following boxes if they are not already: Enabled Recurring Check-In
- In Execution Frequency, select: 'Once per computer'
- Configure the scope according to your requirements by clicking on the Scope tab (This can be set to All Computers and All Users to deploy to every device managed by Jamf).
- Click: Options tab
- Add the Package to the profile:
- Select Packages
- Click: Configure
- Click: Add on SenseOn agent uploaded earlier
- In Distribution Point select: Cloud Distribution Point (this may differ if you have configured other distribution points) Set Action to: Install
- Add the install key script:
- Select: Scripts
- Click: Configure
- Click: Add on the install key script created earlier
- Set Priority to ‘Before’
- Add the Update Inventory Script:
- Select Maintenance
- Click: Configure
- Tick Update Inventory
- Click: Save
- Once the policy is saved it should look like the below screenshot:
Step 6: Verify Rollout
Once the Policy has been saved it will start installing the Agent on Devices within scope when they next check in. To check which devices have had the policy applied follow these steps:
- Navigate to Computers > Policies
- Click on the policy created in the previous section
- Click Logs from the bottom right
- From here you can see each machine in scope and the status of the deployment.
Note: Devices which have not checked in yet will show ‘Pending’ and devices that have will show ‘Completed’.
Need help: If the installation has not been successful please confirm that TLS interception is no taking place, if it is you will need to allow list *.snson.net. Then contact our support team for additional help.