Installing on macOS

macOS has two supported install paths. The signed installer package is the right choice for user-facing machines and for deployment through a device-management platform. The scripted install is the right choice for servers, build machines and anything you are already managing from a terminal.

Choose the architecture explicitly. Builds exist for both Apple Silicon (arm64) and Intel (amd64).

# Confirm the architecture of the target machine
uname -m        # arm64 = Apple Silicon, x86_64 = Intel

SERVER="https://<your-console-host>"
TOKEN="<INSTALL_TOKEN>"

# Apple Silicon
curl -fsSL "$SERVER/api/agents/download/darwin-arm64" -o /tmp/aegisone-agent
# Intel
# curl -fsSL "$SERVER/api/agents/download/darwin-amd64" -o /tmp/aegisone-agent

chmod +x /tmp/aegisone-agent
sudo /tmp/aegisone-agent install --token "$TOKEN" --server "$SERVER"

For the package install, download the .pkg and install it non-interactively, supplying the token so the agent can enrol on first start.

sudo installer -pkg /path/to/AegisOneAgent.pkg -target /

macOS requires explicit user or administrator consent for several of the things an endpoint agent does. Screen access in particular depends on the Screen Recording privacy permission being granted to the agent. Without it the agent runs and reports normally, but a screen session will produce nothing useful — and the failure looks like a product fault rather than a permissions state, which costs teams a surprising amount of time.

If you deploy through a device-management platform, pre-approve the required permissions in a configuration profile so that end users are not asked to make a security decision they are not equipped to evaluate. If you deploy by hand, grant the permission during the same visit as the install rather than leaving it for the first time someone needs support.

The package supports managed uninstall, so removal through your management platform is clean rather than leaving an orphaned service behind.