Skip to main content
COSMICBYTEZLABS
NewsSecurityHOWTOsToolsStudyTraining
ProjectsChecklistsAI RankingsNewsletterStatusTagsAbout
Subscribe

Press Enter to search or Esc to close

News
Security
HOWTOs
Tools
Study
Training
Projects
Checklists
AI Rankings
Newsletter
Status
Tags
About
RSS Feed
Reading List
Subscribe

Stay in the Loop

Get the latest security alerts, tutorials, and tech insights delivered to your inbox.

Subscribe NowFree forever. No spam.
COSMICBYTEZLABS

Your trusted source for IT intelligence, cybersecurity insights, and hands-on technical guides.

429+ Articles
114+ Guides

CONTENT

  • Latest News
  • Security Alerts
  • HOWTOs
  • Projects
  • Exam Prep

RESOURCES

  • Search
  • Browse Tags
  • Newsletter Archive
  • Reading List
  • RSS Feed

COMPANY

  • About Us
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CosmicBytez Labs. All rights reserved.

System Status: Operational
  1. Home
  2. HOWTOs
  3. SentinelOne Agent Deployment: EDR Installation and
SentinelOne Agent Deployment: EDR Installation and
HOWTOIntermediate

SentinelOne Agent Deployment: EDR Installation and

Deploy and manage SentinelOne EDR agents across your environment. Covers manual installation, verification, troubleshooting, and best practices.

Security Team

Security Engineering

February 3, 2026
8 min read

Prerequisites

  • SentinelOne Management Console access
  • Windows endpoints
  • Administrator privileges

Overview

SentinelOne is an endpoint detection and response (EDR) platform that provides autonomous protection against threats. This guide covers agent deployment, verification, and management for Windows endpoints.

Who Should Use This Guide:

  • Security engineers deploying endpoint protection
  • IT administrators managing EDR rollouts
  • SOC teams verifying agent health
  • MSPs onboarding client environments

SentinelOne Agent Capabilities:

FeatureDescription
Autonomous ProtectionReal-time threat prevention without cloud dependency
Behavioral AIDetects unknown threats through behavior analysis
RollbackRansomware remediation through system rollback
Deep VisibilityFull endpoint telemetry for threat hunting
Remote ShellSecure command execution on endpoints

Requirements

System Requirements:

ComponentRequirement
Operating SystemWindows 10/11 (1809+), Windows Server 2016/2019/2022
RAM2GB minimum, 4GB recommended
Disk Space2GB free
Architecturex64 (primary), x86 (legacy support)
NetworkHTTPS/443 to management console

Prerequisites:

PrerequisitePurpose
Console AccessDownload installer, obtain site token
Admin RightsInstallation requires local admin
No Conflicting AVRemove existing EDR/AV products
Network ConnectivityAgent must reach management console

Process

Step 1: Download Agent Installer

Obtain the SentinelOne agent from the management console.

Download Process:

  1. Log in to SentinelOne Management Console
  2. Navigate to Sentinels → Downloads
  3. Under Endpoint Agents, select Windows
  4. Choose agent version:
    • GA (General Availability): Recommended for production
    • EA (Early Availability): For testing new features
  5. Download appropriate architecture:
    • SentinelInstaller_windows_64bit_v\<version\>.msi
  6. Save to accessible location

Verify Installer Integrity:

# Check file hash against console-provided SHA256
$installerPath = "C:\Temp\SentinelInstaller_windows_64bit.msi"
$hash = Get-FileHash -Path $installerPath -Algorithm SHA256
Write-Host "SHA256: $($hash.Hash)"
# Compare with hash shown in console Downloads page

Step 2: Obtain Site Token

Get the site token required for agent registration.

Process:

  1. In console, navigate to Settings → Sites
  2. Select target site (e.g., "Production", "Corporate")
  3. Click site name to open details
  4. Under Site Token, click Show Token
  5. Click Copy to clipboard
  6. Store securely (do not commit to version control)

Token Format:

  • Length: 96-128 characters
  • Characters: Alphanumeric (JWT format)

Important: Site tokens are sensitive credentials. Store securely and rotate if compromised.


Step 3: Prepare Target System

Ensure the endpoint is ready for installation.

Check for Conflicting Software:

# List installed security products
Get-WmiObject -Namespace "root\SecurityCenter2" -Class AntiVirusProduct |
    Select-Object displayName, productState
 
# Common conflicts: McAfee, Symantec, Trend Micro, CrowdStrike
# Windows Defender will be automatically managed by SentinelOne

Verify System Requirements:

# Check disk space (need 2GB+)
Get-PSDrive C | Select-Object @{N="FreeGB";E={[math]::Round($_.Free/1GB,2)}}
 
# Check RAM (need 2GB+)
[math]::Round((Get-CimInstance Win32_ComputerSystem).TotalPhysicalMemory/1GB,2)
 
# Check OS version
Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version

Test Console Connectivity:

# Replace with your console hostname
Test-NetConnection -ComputerName "\<tenant\>.sentinelone.net" -Port 443

Expected Result: TcpTestSucceeded should be True.


Step 4: Install Agent

Deploy the SentinelOne agent using silent installation.

Silent Installation:

# Define parameters
$installerPath = "C:\Temp\SentinelInstaller_windows_64bit.msi"
$siteToken = "<your-site-token>"
$logPath = "C:\Temp\SentinelOne-Install-$(Get-Date -Format 'yyyyMMdd').log"
 
# Execute installation
$process = Start-Process msiexec.exe -ArgumentList @(
    "/i `"$installerPath`""
    "/qn"
    "SITE_TOKEN=`"$siteToken`""
    "/l*v `"$logPath`""
) -Wait -PassThru -NoNewWindow
 
# Check result
if ($process.ExitCode -eq 0) {
    Write-Host "[SUCCESS] Installation completed" -ForegroundColor Green
} elseif ($process.ExitCode -eq 3010) {
    Write-Host "[SUCCESS] Installation completed - reboot required" -ForegroundColor Yellow
} else {
    Write-Host "[ERROR] Installation failed: Exit code $($process.ExitCode)" -ForegroundColor Red
    Write-Host "Review log: $logPath"
}

Common MSI Exit Codes:

CodeMeaning
0Success
1603Fatal error (check log for details)
1618Another installation in progress
1638Another version already installed
3010Success, reboot required

Step 5: Verify Service Status

Confirm the agent service is running.

Check Service:

# Wait for service to start (up to 2 minutes)
$maxAttempts = 24
$attempt = 0
 
do {
    $service = Get-Service -Name "SentinelAgent" -ErrorAction SilentlyContinue
    if ($service -and $service.Status -eq "Running") {
        Write-Host "[SUCCESS] SentinelAgent service is running" -ForegroundColor Green
        break
    }
    Start-Sleep -Seconds 5
    $attempt++
    Write-Host "Waiting for service... ($attempt/$maxAttempts)"
} while ($attempt -lt $maxAttempts)

Expected Result: Service status shows "Running".


Step 6: Verify Agent Registration

Confirm the agent appears in the management console.

Local Verification:

# Check registry configuration
$regPath = "HKLM:\SOFTWARE\SentinelOne\Sentinel Agent"
if (Test-Path $regPath) {
    $config = Get-ItemProperty -Path $regPath
    Write-Host "Management Server: $($config.ManagementServerUrl)"
    Write-Host "Site ID: $($config.SiteId)"
    Write-Host "Agent ID: $($config.AgentId)"
}
 
# Check agent version
$agentExe = Get-ChildItem "C:\Program Files\SentinelOne" -Recurse -Filter "SentinelAgent.exe" | Select-Object -First 1
Write-Host "Agent Version: $($agentExe.VersionInfo.FileVersion)"

Console Verification:

  1. Log in to SentinelOne console
  2. Navigate to Sentinels → Agents
  3. Search for computer name or IP
  4. Verify:
    • Status: Connected (green icon)
    • Last Active: Within last 5 minutes
    • Agent Version: Matches installed version
    • Site: Correct site assignment

Expected Timeline:

  • Agent appears in console: 30 seconds to 2 minutes
  • Full asset inventory: 5-15 minutes
  • Initial scan completion: 15-30 minutes

Step 7: Run Verification Script

Use a comprehensive verification script.

Verification Script:

function Test-SentinelOneAgent {
    Write-Host "`n=== SentinelOne Agent Verification ===" -ForegroundColor Cyan
 
    $results = @{}
 
    # Check 1: Service status
    $service = Get-Service -Name "SentinelAgent" -ErrorAction SilentlyContinue
    if ($service -and $service.Status -eq "Running") {
        Write-Host "[PASS] Service running" -ForegroundColor Green
        $results.Service = $true
    } else {
        Write-Host "[FAIL] Service not running" -ForegroundColor Red
        $results.Service = $false
    }
 
    # Check 2: Process running
    $process = Get-Process -Name "SentinelAgent" -ErrorAction SilentlyContinue
    if ($process) {
        Write-Host "[PASS] Process active (PID: $($process.Id))" -ForegroundColor Green
        $results.Process = $true
    } else {
        Write-Host "[FAIL] Process not found" -ForegroundColor Red
        $results.Process = $false
    }
 
    # Check 3: Registry configuration
    $regPath = "HKLM:\SOFTWARE\SentinelOne\Sentinel Agent"
    if (Test-Path $regPath) {
        $config = Get-ItemProperty -Path $regPath
        Write-Host "[PASS] Registry configured" -ForegroundColor Green
        Write-Host "  - Server: $($config.ManagementServerUrl)" -ForegroundColor Cyan
        $results.Registry = $true
    } else {
        Write-Host "[FAIL] Registry not configured" -ForegroundColor Red
        $results.Registry = $false
    }
 
    # Check 4: Console connectivity
    try {
        $consoleUrl = (Get-ItemProperty -Path $regPath).ManagementServerUrl
        $consoleHost = ([System.Uri]$consoleUrl).Host
        $connection = Test-NetConnection -ComputerName $consoleHost -Port 443 -WarningAction SilentlyContinue
        if ($connection.TcpTestSucceeded) {
            Write-Host "[PASS] Console connectivity verified" -ForegroundColor Green
            $results.Connectivity = $true
        } else {
            Write-Host "[FAIL] Cannot reach console" -ForegroundColor Red
            $results.Connectivity = $false
        }
    } catch {
        Write-Host "[FAIL] Connectivity check failed" -ForegroundColor Red
        $results.Connectivity = $false
    }
 
    # Summary
    $passed = ($results.Values | Where-Object { $_ }).Count
    $total = $results.Count
 
    Write-Host "`n=== Summary: $passed/$total checks passed ===" -ForegroundColor Cyan
 
    return ($passed -eq $total)
}
 
Test-SentinelOneAgent


Troubleshooting

Common Issues:

SymptomPossible CauseSolution
Installation fails (1603)Conflicting AV or disk spaceRemove conflicting software, free disk space
Agent not in consoleNetwork blockedVerify HTTPS/443 to console host
Service won't startDriver issueCheck Event Log, reinstall agent
Wrong site assignmentIncorrect tokenUninstall, reinstall with correct token

Diagnostic Commands:

# Check installation log
Select-String -Path "C:\Temp\SentinelOne-Install*.log" -Pattern "error|failed" -Context 2,3
 
# Check agent log
Get-Content "C:\ProgramData\SentinelOne\Logs\Agent.log" -Tail 50
 
# Check Windows Event Log
Get-WinEvent -LogName Application -MaxEvents 20 |
    Where-Object { $_.ProviderName -like "*Sentinel*" }
 
# Test network connectivity
Test-NetConnection -ComputerName "\<tenant\>.sentinelone.net" -Port 443 -InformationLevel Detailed

Uninstall and Reinstall:

# Get product code
$product = Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like "*SentinelOne*" }
 
# Uninstall
msiexec /x $product.IdentifyingNumber /qn /l*v "C:\Temp\sentinel-uninstall.log"
 
# Wait and reboot
Start-Sleep -Seconds 30
Restart-Computer
 
# Reinstall with correct token after reboot

Best Practices

Deployment Best Practices:

PracticeDescription
Test FirstDeploy to pilot group before mass rollout
Remove ConflictsUninstall existing AV/EDR before installation
Use GroupsOrganize agents by department/location using site groups
Monitor RolloutTrack deployment progress in console

Operational Best Practices:

PracticeDescription
Keep UpdatedMaintain agents on supported versions
Monitor AlertsReview threat detections promptly
Test ExclusionsValidate exclusion policies don't create gaps
Regular AuditsVerify all endpoints have agents deployed

Verification Checklist

Pre-Installation:

  • System requirements met
  • Conflicting software removed
  • Console connectivity verified
  • Site token obtained

Post-Installation:

  • Service running
  • Process active
  • Agent appears in console
  • Status shows "Connected"

Operational:

  • Policy applied correctly
  • Exclusions configured (if needed)
  • Alerts being monitored
  • Agent version current

References

  • SentinelOne Documentation
  • SentinelOne Knowledge Base
  • SentinelOne API Documentation

Last Updated: February 2026

#sentinelone#edr#Endpoint Security#Security#Threat Detection

Related Articles

SentinelOne Health Check: Agent Status Monitoring and

Organizations deploying SentinelOne endpoint protection require continuous monitoring of agent health to ensure comprehensive threat coverage across their...

17 min read

Deploy SentinelOne Policy

Deploy, manage, and validate SentinelOne security policies across your endpoint estate using the SentinelOne Management API. This automated workflow supports:

25 min read

Invoke SentinelOne Threat Hunt

Proactive threat hunting is essential for identifying sophisticated threats that evade automated detection systems. This script automates the process of...

20 min read
Back to all HOWTOs