There are three ways to uninstall the agent:
In Guardz: open the customer, go to Devices, then Remove Agent → Uninstall, one device at a time.
In the SentinelOne console: go to Sentinels, find the device, then Actions → Uninstall.
Locally on the device: see the steps below.
If the uninstall shows as sent but the agent is still there
Don't send more uninstall commands. The existing ones are already queued.
Restart the devices that are online. Some uninstalls only complete after a reboot.
Power on and connect any offline devices so they can receive the command.
Wait about 30 minutes. If the agent is still installed, uninstall locally.
Uninstall locally
In the SentinelOne console, go to Sentinels → Endpoints and search for the device by name. If the device was already decommissioned, turn on the Decommissioned agents filter. If more than one record shares the hostname, use the correct one.
Open the device's details panel and click Actions → Show Passphrase. You may need to re-enter your password or MFA code. Each device has its own passphrase.
With the customer selected in Guardz, download the SentinelOne installer from Security Controls → Endpoint Security → Deploy.
Open Command Prompt as Administrator in the folder where you saved the installer.
Run the installer with that device's passphrase, using the installer's full file name, for example: SentinelOneInstaller_windows_64bit_VERSION.exe -c -k "PASSPHRASE"
Check the result with: echo %errorlevel%
Why the site-token-only command fails
A command that uses only the site token works only when Anti-Tamper is disabled. Otherwise, the uninstall passphrase is required.
If the local uninstall rolls back (code 1603)
Code 1603 is a general Windows Installer failure. If the machine and its disk are being permanently wiped, with no snapshots to restore, you can decommission it in the SentinelOne console instead (Sentinels, select the device, Decommission).