π Deploying SentinelOne via Guardz: Best Practices & Installation Guide
π Introduction
Deploying SentinelOne through Guardz is slightly different from deploying it directly from the SentinelOne Console. Guardz simplifies the process by providing:
β
Pre-configured installation packages for different OS types.
β
Deployment scripts for mass rollout via MDM/RMM tools.
β
Guidance on installation & troubleshooting per OS.
π‘ Before deploying, it's important to choose the right package and install method based on your environment.
π Step 1: Choosing the Right Installation Method
SentinelOne offers two primary installation methods:
1οΈβ£ Installer-based deployment (EXE, MSI, PKG, RPM)
2οΈβ£ Script-based deployment (MDM, RMM, GPO, Intune, SCCM)
π Which method should you choose?
Scenario | Recommended Method |
Small-scale deployment | Installer-based (EXE, MSI, PKG, RPM) |
Large-scale rollout (100+ devices) | Script-based (MDM, RMM, GPO, SCCM, Intune) |
Remote installation | Script-based (MDM, RMM) |
Multi-OS environment | Combination of both methods |
π Mass deployment via script is recommended for large organizations.
π Step 2: Downloading Installation Packages & Scripts
Guardz provides pre-configured SentinelOne installation packages along with deployment scripts that work out-of-the-box.
πΉ How to Get the Installation Files
1οΈβ£ Log into Guardz.
2οΈβ£ Navigate to Security Controls > Endpoint Security > SentinelOne Managed.
3οΈβ£ Click "Deploy" to enable the SentinelOne integration.
4οΈβ£ Select the appropriate OS and architecture (Windows, macOS, Linux).
5οΈβ£ Download the installer package or deployment script.
π Step 3: Deploying SentinelOne Using Mass Deployment Scripts
π‘ Why Use Deployment Scripts?
π Script-based deployment is recommended for MDM, RMM, and remote installation across multiple devices.
β Guardz provides pre-built scripts with all necessary variables included.
π Deployment best practices:
Group devices by OS/Architecture/Version before running mass deployments.
Use MDM/RMM tools (Intune, Jamf, SCCM, GPO) for script execution.
Ensure devices have the correct permissions applied before deployment (e.g., Full Disk Access for macOS).
π¨ Disclaimer: The provided scripts are for guidance only and should be tested in a non-production environment before deployment.
π Step 4: Deploying SentinelOne Per OS
πΉ Windows Deployment (EXE/MSI or Script)
Option 1: Installer Deployment (EXE/MSI)
1οΈβ£ Download the MSI package from Guardz.
2οΈβ£ Open Command Prompt (Admin) and run:
msiexec /i SentinelOneInstaller.msi /qn /norestart
3οΈβ£ Verify the agent installation in Control Panel > Programs.
Option 2: Script Deployment via MDM/RMM
1οΈβ£ Deploy the Windows script via GPO, Intune, or SCCM.
2οΈβ£ Ensure Windows Defender policies are properly configured.
3οΈβ£ Verify that the SentinelOne agent appears in Guardz > Devices.
πΉ macOS Deployment (PKG or Script)
Option 1: Installer Deployment (PKG)
1οΈβ£ Download the PKG file from Guardz.
2οΈβ£ Open Terminal and run:
sudo installer -pkg SentinelOneInstaller.pkg -target /
3οΈβ£ Grant Full Disk Access permissions to SentinelOne.
Option 2: Script Deployment via MDM (Jamf, Intune)
1οΈβ£ Deploy the macOS script via MDM (Intune, Jamf).
2οΈβ£ Ensure Full Disk Access and System Extension Approval are enabled.
3οΈβ£ Confirm the SentinelOne agent is running via:
sudo launchctl list | grep sentinelone
πΉ Linux Deployment (RPM/DEB or Script)
Option 1: Installer Deployment (RPM/DEB)
1οΈβ£ Download the Linux package (RPM or DEB).
2οΈβ£ Open Terminal and install:
sudo dpkg -i SentinelOneInstaller.deb # For Debian-based systems sudo rpm -i SentinelOneInstaller.rpm # For RHEL-based systems
3οΈβ£ Confirm the installation via:
systemctl status sentinelone
Option 2: Script Deployment via SSH or Automation Tool
1οΈβ£ Deploy the Linux script via Ansible, Puppet, or SSH-based automation.
2οΈβ£ Ensure the agent registers with Guardz successfully.
π Step 5: Post-Deployment Configuration
πΉ Verify Device Enrollment in Guardz
After installing SentinelOne:
1οΈβ£ Log into Guardz.
2οΈβ£ Navigate to Security Controls > Endpoint Security > Devices.
3οΈβ£ Check that all endpoints report correctly in Guardz.
β
πΉ Adjust SentinelOne Security Policies
1οΈβ£ Navigate to Security Controls > Endpoint Security > SentinelOne Managed.
2οΈβ£ Click the edit icon to modify SentinelOne Policy Settings.
3οΈβ£ If required, override the global policy settings per customer.
β
π Your SentinelOne agents are now fully deployed & managed via Guardz!
π Troubleshooting Deployment Issues
πΉ Issue: "Installer Failed to Execute"
β
Fix:
Verify the installer matches the OS architecture (32-bit vs. 64-bit).
Run the installer as Administrator (Windows) or with sudo (macOS/Linux).
πΉ Issue: "SentinelOne Agent Not Appearing in Guardz"
β
Fix:
Ensure the agent is installed correctly on the endpoint.
Verify that the correct Site Token was used during installation.
πΉ Issue: "macOS Agent Does Not Have Full Disk Access"
β
Fix:
Deploy an MDM profile that grants Full Disk Access to SentinelOne.
πΉ Issue: "Linux Agent Not Running After Installation"
β
Fix:
Run:
systemctl restart sentinelone
Verify SentinelOne logs for errors.
π Best Practices for SentinelOne Deployment
β Test deployment in a small group before mass rollout.
β Use script-based deployment for large-scale installations.
β Ensure required permissions (e.g., Full Disk Access for macOS) are applied.
β Monitor Guardz > Devices to ensure proper agent enrollment.