> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows.md). # Windows Install the SentinelOne agent on a Windows workstation or server manually, through an MDM or with a GPO. To deploy the EDR on a large scale, start with a manual test installation on a few endpoints. ## Prerequisites * Windows 8.1 and above for the standard installer. Older versions need a legacy installer: see `Supported Windows versions` in the first step. * Your current antivirus is completely uninstalled: SentinelOne replaces it. If the firewall is managed separately, keep it running. If it is part of the same solution, copy any custom rules to Windows Firewall first. * If outbound traffic is blocked, the addresses in [Network requirements](/mdr/deploy/sentinelone/network.md) are allowed. ## Installation {% stepper %} {% step %} ### Download the installer The executable is only available from Stoïk Protect: go to `MDR` > `Settings`, click `Windows`, then click `Download the executable` (Windows 8.1 and above). The download menu lists three files. Choose the one that matches the machine and how you deploy: * **ARM (arm64)**: `SentinelOneInstaller_windows_arm64_v.exe` * **AMD / Intel (x64), manual installation on each machine**: `SentinelInstaller_windows_64bit_v.msi`. We recommend the `.msi` for manual installations, as several customers had problems installing with the `.exe`. * **AMD / Intel (x64), MDM or GPO deployment**: `SentinelOneInstaller_windows_64bit_v.exe` {% hint style="info" %} If you use an `.exe`, run it from a command prompt rather than by double-clicking it. {% endhint %} Come back here once it's downloaded to continue the installation.
Supported Windows versions **Standard installer** (Windows 8.1 and above): * Windows 8.1 / 10 / 11 / 11 23H2 / 11 24H2 64-bit * Windows Server IoT 2019 / 2022 / 2025 * Windows Server / Server Core 2012 R2 / 2016 / 2019 / 2022 / 2025 **Legacy installer**: request it at * Windows 8.1 / 10 32-bit * Windows 7 SP1 / 8 32/64-bit * POSReady 7 * Windows Server / Storage Server / Server Core 2012 (not R2) 32/64-bit * Windows Server 2008 R2 SP1 32/64-bit **Legacy Plus installer**: available from `MDR` > `Settings` > `Windows` > `Download the executable` in Stoïk Protect * Windows XP SP3 / Vista SP2 32/64-bit * Windows XP SP2 64-bit (AMD64/EM64T) * Windows Embedded POSReady 2009 * Server 2003 SP2 / 2003 R2 SP2 / 2008 SP2 (not R2) 32/64-bit
{% endstep %} {% step %} ### Find your customer ID Go to `MDR` > `Settings` and copy your customer ID.
{% endstep %} {% step %} ### Install SentinelOne {% tabs %} {% tab title="Manual" %} 1. Launch the executable on the target machine. 2. Enter your customer ID in the `Site Token` or `Group Token` field. 3. Click `Install`. {% endtab %} {% tab title="MDM" %} Run the following command: ``` .exe -t -q ``` Replace `` with your customer ID. {% endtab %} {% tab title="GPO" %} 1. Place the `.exe` installer in a network share. Example: `\\Server\Share\SentinelOneInstaller_windows_64bit_v.exe`. Give **Read** permissions on the share to `Domain Computers` (the computer accounts), not only to users: the script runs as the machine, not as a user. 2. Create a deployment script named `InstallSentinelOne.bat` with the content below. It is a plain batch script: it runs in the command prompt, which is what the SentinelOne `.exe` requires. ```batch @echo off set "INSTALLER=\\\\SentinelOneInstaller_windows_64bit_v.exe" set "SITETOKEN=" set "LOG=C:\Windows\Temp\S1_GPO_Install.log" :: Skip if SentinelOne is already installed sc query SentinelAgent >nul 2>&1 if %errorlevel% equ 0 ( echo %date% %time% SentinelOne already installed >> "%LOG%" exit /b 0 ) echo %date% %time% Starting installation from %INSTALLER% >> "%LOG%" start "" /wait "%INSTALLER%" -t "%SITETOKEN%" -q echo %date% %time% Installer exit code: %errorlevel% >> "%LOG%" ``` Replace the installer path with your share path and `` with your customer ID. Remove the `<` and `>` characters as well. The check at the top stops the script from reinstalling SentinelOne at every restart. 3. Create a GPO: 1. Open the Group Policy Management Console: `Windows + R` > `gpmc.msc` > `Enter`. 2. Right-click the target container (domain or OU) and click `Create a Group Policy Object in this domain and link it here`. Name it (e.g. `SentinelOne Deployment`). 3. Right-click the new GPO and select `Edit`. 4. Go to `Computer Configuration` > `Policies` > `Windows Settings` > `Scripts (Startup/Shutdown)`. Use `Computer Configuration`, not `User Configuration`: startup scripts run with system rights, so there is no administrator prompt and users have nothing to do. 5. Double-click `Startup`, click `Show Files`, and copy `InstallSentinelOne.bat` into the folder that opens. 6. Click `Add`, then `Browse`, select `InstallSentinelOne.bat` and click `OK`. 4. Apply the GPO: 1. On a target machine, run `gpupdate /force`, then restart it to trigger the script. 2. Check that the machine appears in Stoïk Protect under `MDR` > `Monitored Assets`. 3. If it does not, open `C:\Windows\Temp\S1_GPO_Install.log` on that machine and see [Troubleshooting](#troubleshooting). {% endtab %} {% endtabs %} {% endstep %} {% endstepper %} ## Troubleshooting
GPO deployment: no log file `C:\Windows\Temp\S1_GPO_Install.log` does not exist: the script did not run. Run `gpresult /h gpresults.html` to check the GPO is applied to the machine.
GPO deployment: exit code other than 0 The installer started but failed. Exit code `2015` means the machine does not meet SentinelOne's requirements. `C:\Windows\Temp\SC-exit-code.txt` names the failing requirement. Usual causes: a pending restart (Windows Update or removal of the previous antivirus), leftovers of the previous antivirus, or an outdated Windows build.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stoik.io/mdr/deploy/sentinelone/os/windows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.