Installing the SentinelOne Agent

Overview

Learn how to install the SentinelOne agent application on your server for either the Windows or Linux environment.

SentinelOne Agent packages

Windows

Connect to the following server location: \\isfiles.uoregon.edu\Public\SentinelOne\Windows

Linux

Client package can be obtained in two ways:

• UO RedHat Satellite hosts DEB or RPM packages and doesn't require Windows or Samba on a client system to obtain.
• Alternatively, it can be obtained by connecting to the following server location: \\isfiles.uoregon.edu\Public\SentinelOne\Linux

SentinelOne console and site token

• Clients are additionally obtainable from the SentinelOne console via the left-hand navigational toolbar - Sentinels > Packages menu
• Site Token: A site (or group) token is required to add an endpoint into the correct SentinelOne site and is part of the agent install cmdlet
  • Obtaining Site Token: Site tokens can be obtained via your specified site in the SentinelOne console via the left-hand navigation menu - Sentinels > Site Info > Site Token or by submitting a service request to Systems Monitoring.

Windows installation process

Run the following command prompt as admin:

• msiexec /i "SentinelInstaller_windows_64bit_v*.msi" SITE_TOKEN=<SITE_TOKEN> /q
  • /q parameter performs a quiet installation. No reboot by default in current agent versions.

Expanded installation options can be viewed via the SentinelOne Customer Portal (account required)

Verification

Run the sentinelctl status command as admin from the SentinelOne agent directory

• c:\Program Files\SentinelOne\Sentinel Agent 24.2.3.471>sentinelctl status

Linux installation process

Create a file s1_agent_install.conf at a location of your choosing on your server with contents like:

• S1_AGENT_MANAGEMENT_TOKEN=<site-token>
• S1_AGENT_AUTO_START=true
• S1_AGENT_CUSTOMER_ID=<your server's puppet role, for example> *optional

On Redhat-based systems, for example, run:

• env S1_AGENT_INSTALL_CONFIG_PATH=<path to s1_agent_install.conf>  rpm –i SentinelAgent_linux_x86_64_v24_3_3_6.rpm

On Debian-based systems, for example, run:

• env S1_AGENT_INSTALL_CONFIG_PATH=<path to s1_agent_install.conf> dpkg –i SentinelAgent_linux_x86_64_v24_3_3_6.deb

Verification

Run systemctl status sentinelone from the host's command line. Output should begin like this:

$ systemctl status sentinelone