Skip to content

Supported platforms

This page lists the operating systems the Outpost agent runs on and what Outpost can do on each one. Use it to check a computer before you enroll it, and to understand why a control is unavailable for a particular endpoint.

Each endpoint also reports what it can do, so the console knows the difference between “this endpoint cannot do that” and “this endpoint found nothing”. When a control is unavailable on one endpoint, the console says why.

Operating systemVersionsArchitecturesDownload choices in the console
WindowsWindows 10, Windows 11, and Windows Server 2016 and laterx64Windows x64 (single file) (.exe), Windows x64 (MSI, for GPO or Intune) (.zip holding the MSI and its configuration file)
LinuxDistributions that use systemdx86-64, arm64Linux x64, Linux ARM64 (.tar.gz)
FreeBSDNo minimum release publishedx86-64, arm64FreeBSD x64, FreeBSD ARM64 (.tar.gz)
OpenBSDNo minimum release publishedx86-64, arm64OpenBSD x64, OpenBSD ARM64 (.tar.gz)
macOS (Preview)macOS 14 and laterApple silicon, IntelmacOS Apple silicon, macOS Intel (.zip holding the .pkg and its configuration file)

The download choices are the Platform options under Enroll a device on the endpoint list. The Install the agent step of the first-run setup wizard offers the same downloads with shorter labels, such as Windows installer and Linux (x86-64).

The agent runs on 64-bit Windows 10, Windows 11, Windows Server 2016, and later releases. Windows 8.1, Windows Server 2012 R2, and earlier releases are not supported. There is no installer for Windows on ARM.

Some features depend on the Windows build or the hardware:

  • The full-screen remote terminal needs Windows 10 version 1809 or later, or Windows Server 2019 or later. Earlier builds get a line-based terminal.
  • Outpost Sync needs Windows 10 version 1709 or later, or Windows Server 2019 or later.
  • Managing BitLocker drive encryption needs a TPM.
  • Patching needs the Windows Update service. An endpoint where it is disabled reports that it cannot scan or install updates.
  • Deploying software from winget needs winget on the endpoint. Most Windows Server releases do not include it.

The agent runs on Linux distributions that use systemd, on x86-64 and arm64. Patching and software deployment use the distribution’s own package manager:

Distribution familyPackage manager
Debian and Ubuntuapt
Red Hat Enterprise Linux and Fedoradnf

zypper, pacman, and apk are not supported. On a distribution without apt or dnf, the agent still reports inventory and runs scripts, but patching and software deployment are unavailable.

Remote desktop works on endpoints with a display: X11 sessions, Wayland sessions, and the login screen before anyone signs in. A server with no display gets the remote terminal instead. Locking the screen, signing a user out, and messaging a user need systemd-logind. Messaging a user also needs wall.

FreeBSD and OpenBSD endpoints get a smaller feature set: basic inventory (identity, operating system, uptime, processor, memory, storage, and network), the running process list, the remote terminal, scripts, patching, and agent self-update. Patching uses pkg and freebsd-update on FreeBSD, and syspatch and pkg_add on OpenBSD. There is no remote desktop, software deployment, policy enforcement, or tray app on these platforms.

macOS support is a preview. It runs on macOS 14 and later, on Apple silicon and Intel Macs.

  • The macOS download choices appear in the console only when macOS installers are turned on for your Outpost.
  • The macOS package is not signed or notarized by Apple, so Gatekeeper blocks it until an administrator on the Mac allows it.
  • Remote desktop needs the Screen Recording and Accessibility permissions on the Mac. Without Accessibility, a session is view only.
FeatureWindowsLinuxmacOS (Preview)FreeBSD and OpenBSD
Hardware and software inventoryYesYesYesBasic only
Live metricsYesYesYesNo
Running process listYesYesYesYes
Remote terminalYesYesYesYes
Remote desktopYesYes, with a displayYesNo
ScriptsPowerShell, cmd, batchsh, bash, zsh, Pythonsh, bash, zsh, Pythonsh, bash, zsh, Python
Run a script as the signed-in userYesYesYesNo
Run a script at sign-inYesYes, with systemd-logindYesNo
Scheduled scripts while offlineYesYesYesYes
PatchingWindows Updateapt or dnfmacOS Software Updatepkg and freebsd-update (FreeBSD), syspatch and pkg_add (OpenBSD)
Software deploymentwinget, Chocolatey, and installersapt or dnfHomebrew, .pkg, and .dmgNo
Profiles and policy enforcementYesYesYesPlatform-neutral settings only, no enforcement
Drive encryptionManaged (BitLocker)Reported only (LUKS)Managed (FileVault)No
Local administrator password rotationYesYes (root)YesNo
Restart and shut downYesYesYesNo
Lock screen, sign out, and message a userYesYes, with systemd-logindYesNo
End a processYesYesYesNo
Start, stop, and restart servicesYesYes, with systemdYesNo
Switch neighbor detection (LLDP and CDP)YesYesYesNo
Outpost SyncYesNoNoNo
Outpost tray appYesYesYesNo
Agent self-updateYesYesYesYes

bash, zsh, and Python scripts run only on endpoints where that interpreter is installed. sh is always available on Linux, macOS, and the BSDs.

The console is a web application. It supports current versions of Google Chrome, Microsoft Edge, Mozilla Firefox (including the Extended Support Release), and Apple Safari.

Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either license.