Installing on Windows

The Windows agent installs from a scripted install run with administrative privileges. You need the install token generated for the target client and site, and your console host.

# Run from an elevated PowerShell session
$Server = "https://<your-console-host>"
$Token  = "<INSTALL_TOKEN>"

Invoke-WebRequest -Uri "$Server/api/agents/download/windows" `
  -OutFile "$env:TEMP\aegisone-agent.exe"

& "$env:TEMP\aegisone-agent.exe" install --token $Token --server $Server

The install registers the agent as a service so it survives reboot and starts before a user logs in. Confirm the service is running before you consider the machine enrolled — an agent that installed but did not start will not appear in the console, and the absence is easy to misread as a network problem.

Get-Service -Name "AegisOne*" | Format-List Name, Status, StartType

For fleet deployment, run the same command through whatever mechanism you already use to execute elevated commands at scale — a Group Policy startup script, an existing configuration-management tool, or your current management platform if you are migrating from one. The install is non-interactive by design, so it works unattended without additional flags.

Generate one token per deployment batch rather than reusing a single long-lived token across your whole estate. Tokens have a configurable lifetime; a batch token that expires shortly after the deployment window closes limits the damage if the script leaks into a shared drive, a ticket, or a chat channel, all of which happen.

A note on endpoint protection: security software occasionally quarantines a newly downloaded unfamiliar binary before it can install. If installs fail silently on machines that are otherwise reachable, check the protection product logs before debugging the network.