Make sure you have all requirements before you start the installation.
For Windows Agents: If there is a web proxy between the endpoints and the Console, we recommend you configure the proxy for the Windows Agent in the installation command. If you did not configure a proxy, the Agent is already installed, and there is no connection between the Agent and the Management, see How to Fix Never Connected Agents.
The installation requires a user role with Administrator permissions.
During Agent installation, you must add Agents to a Site with the Site Token or to a Group with a Group Token.
You can use a Group Token for a Manual Group (previously a Static Group) or a Pinned Group. You cannot add Agents to a Dynamic Group. Agents are moved to Dynamic Groups from Manual Groups, if they match the conditions of the group.
To install the Agent on a Windows endpoint:
1. Get the site or group token. For more information, see Getting a Site or Group Token.
2. In the Sentinels toolbar, click Packages.
3. Download the applicable Windows Installer package. Make sure the Access Level of the package includes the Site that the Agent will go to.
Best Practice: Download the file to the local endpoint.
4. Run the installer package and follow the instructions.
- To install with the interactive GUI wizard:
Run the installation package and enter the Site or Group Token when prompted in the installation wizard.
Note: The 22.1 EXE new installation package DOES NOT support the installation GUI wizard. New installation packages 22.2 EXE and later DO support the installation GUI wizard.
- To install silently without user interaction:
In a command prompt run as administrator, run the installer with switches for the token and silent installation.
Example for EXE packages: C:\Users\S1\Desktop\Sentinel\SentinelInstaller.exe /SITE_TOKEN=<site_Token or group_Token> /quiet
Example for MSI packages: C:\Users\S1\Desktop\Sentinel\SentinelInstaller.msi SITE_TOKEN=<site_Token or group_Token> /QUIET
Tip: Add /NORESTART to prevent a forced reboot
Note: For Windows Agents 22.1.x, if you installed the Agent with the new installation package, you cannot use /quiet or QUIET.You can start the installation through a CLI with the token. Example of CLI with the new EXE installer: SentinelOneInstaller.exe -t <site_Token or group_Token>
5. Complete the installation:
In Windows Agent 22.1 and later, most Agent functionality is operational after installation, even if you do not reboot the endpoint. This includes Static AI detection, Deep Visibility™, all Agent menu actions, and all response functions. The Behavioral AI detection and mitigation capability requires a reboot. For earlier Agent versions, most Agent functionality cannot be guaranteed without a reboot.
The Behavioral AI mode becomes active after you or the end user restart the endpoint. In the Management Console, the endpoint status remains Pending Reboot until it restarts.
6. Important for all endpoints: We recommend that you enhance endpoint security with protection against physical theft and hacking (such as unauthorized disk mount modification). Enable full disk encryption, apply OS patches, and maintain measures according to your vendor recommendations and corporate policies.