Deploying SentinelOne

ShZaidan
New Contributor II

Hi Guys,

 

I'm trying to deploy SentinelOne and followed all the steps in the HCSOnline PDF, but I'm still getting an error.

I've attached a screenshot of the error. Any advice or help would be really appreciated!

Thanks in advance!

ShZaidan_0-1746079466309.png



3 ACCEPTED SOLUTIONS

AJPinto
Esteemed Contributor

Sent1 is an odd bird, you need to cache the package, not install the package and the script need to run after the package has cached. Make sure the package is set to cache, and the script is set to run after.

 

AJPinto_0-1746098921774.pngAJPinto_1-1746098968442.png

 

You did not share your script, but just incase it should look like this.

#!/bin/bash
sudo echo "$4" > /Library/Application\ Support/JAMF/Waiting\ Room/com.sentinelone.registration-token 
sudo /usr/sbin/installer -pkg "/Library/Application Support/JAMF/Waiting Room/$5" -target /

 

View solution in original post

ShZaidan
New Contributor II

Hi @AJPinto  
Thanks for your help is works now it was my script 😁
but now I have issue with application permission after the S1 installed 

ShZaidan_0-1746101872467.pngShZaidan_1-1746101893400.png

Just to know 

I have make this before 

ShZaidan_2-1746101946926.png

 



View solution in original post

AJPinto
Esteemed Contributor

Looks like you left off the Allowed System Extension, com.sentinelone.network-monitoring should be added.

 

Another suggestion, break up the Configuration Profiles. Unrelated payloads should be in their own Configuration Profiles. For example the certificate for an 802.1x network would be related and need to go in the same Configuration Profile. However, a Packet Filleter and PPPC Configuration are not related and should be separated. This allows you to troubleshoot one at a time without messing with the other. All of this may be for Sentinel One, but a single Configuration Profile with a ton of payloads can be a beast to troubleshoot.

 

AJPinto_0-1746103527504.png

 

View solution in original post

4 REPLIES 4

AJPinto
Esteemed Contributor

Sent1 is an odd bird, you need to cache the package, not install the package and the script need to run after the package has cached. Make sure the package is set to cache, and the script is set to run after.

 

AJPinto_0-1746098921774.pngAJPinto_1-1746098968442.png

 

You did not share your script, but just incase it should look like this.

#!/bin/bash
sudo echo "$4" > /Library/Application\ Support/JAMF/Waiting\ Room/com.sentinelone.registration-token 
sudo /usr/sbin/installer -pkg "/Library/Application Support/JAMF/Waiting Room/$5" -target /

 

ShZaidan
New Contributor II

Hi @AJPinto  
Thanks for your help is works now it was my script 😁
but now I have issue with application permission after the S1 installed 

ShZaidan_0-1746101872467.pngShZaidan_1-1746101893400.png

Just to know 

I have make this before 

ShZaidan_2-1746101946926.png

 



AJPinto
Esteemed Contributor

Looks like you left off the Allowed System Extension, com.sentinelone.network-monitoring should be added.

 

Another suggestion, break up the Configuration Profiles. Unrelated payloads should be in their own Configuration Profiles. For example the certificate for an 802.1x network would be related and need to go in the same Configuration Profile. However, a Packet Filleter and PPPC Configuration are not related and should be separated. This allows you to troubleshoot one at a time without messing with the other. All of this may be for Sentinel One, but a single Configuration Profile with a ton of payloads can be a beast to troubleshoot.

 

AJPinto_0-1746103527504.png

 

ShZaidan
New Contributor II

Hey @AJPinto 
Yes it works now thanks