This article serves as a guide to correctly install SentinelOne using Addigy.
SentinelOne requires a token file that is unique per oganization.
What do I need to start with SentinelOne?
In order to correctly install SentinelOne, you will need a token and the PKG file.
To create the token file, you will need to run:
echo "TOKEN_HERE" > "com.sentinelone.registration-token"
You would replace TOKEN_HERE with the actual token you get from SentinelOne.
This should create the token in your user's folder. Alternatively, you can search for the token in the finder app by searching for "com.sen" and it should pop up.
Creating the Custom Software
Once you have both the token and PKG files, upload them both into Addigy using our file manager in custom software.
The custom software should similar to this:
SentinelOne also has some PPPC profiles that Smart Software will find for you when you upload the PKG. Be sure to add them as seen below:
Upon uploading the PKG you will see the "Add" button next to the name as seen in the image above. Click this in order to have an installation script automatically filled out. It will look similar to the below image:
Creating the KEXT configuration
For Sentinel One to function correctly, a Kernel Extension (KEXT) payload is needed.
To creat this configuration navigate to: Policies>Catalog>MDM congiurations>Add>macOS>Kernel Extensions
We recommend deploying the KEXT configuration before the Custom Software for the best functionlity.
The configuration will look like this when set up correctly:
Please note that you have to select Add after typing in the identifiers for them to be included in the configuration.
Here we provide everything you'd need to fill in the configuration:
Allowed team identifier: 4AYE5J54KN
You should be set to deploy Sentinel One after making these policy items!
If you have an Addigy account and have additional questions, you can create a ticket by emailing email@example.com.
Alternatively, you can submit a support request within Addigy.