The Hyperping agent now runs on Windows. Until today, Server monitoring covered Linux and macOS, and teams with a few Windows boxes in the fleet had to watch those somewhere else, or not at all. Now one PowerShell command installs the agent as a Windows service, and the host shows up in the same Servers view as your Linux machines, with the same charts and the same offline alerts.


Key takeaways

  • The agent supports Windows 10 and Windows Server 2016 and later, on 64-bit x86.
  • Install it with one command in an Administrator PowerShell window. The dashboard gives you the command with your install token already in it.
  • Windows hosts report CPU, memory, disk, disk I/O, network and host details every 30 seconds, like Linux and macOS hosts.
  • Offline alerting, escalation policies, groups and status pages work the same way for every platform.
  • The agent runs as the hp-agent Windows service and logs to the Application event log.

Install it with one PowerShell command

Open the Servers view and switch the install command from Linux / macOS to Windows. Copy it, open PowerShell with Run as Administrator on the host, and paste:

& ([scriptblock]::Create((irm https://hyperping.com/install.ps1))) HP_INSTALL_xxxxx

The installer checks that it runs elevated on a supported version of Windows, downloads the agent, verifies its SHA256, enrolls the host, and starts the service. It then waits until the collector answers its local health check, so a broken setup fails in front of you instead of silently. About 30 seconds later, the server is Online in the dashboard.

The flags you already use on Linux have PowerShell equivalents:

  • -Name sets the display name.
  • -Policy binds an escalation policy.
  • -Group puts the server in a group.
  • -Interval sets the collection interval in seconds.
  • -Force overwrites name, policy and group on a host that is already enrolled.

The same environment variables work too, which helps when you roll the agent out with Group Policy, Ansible or your RMM tool.

On Windows Server 2016, PowerShell 5.1 only enables TLS 1.0 by default, and the download would fail before the installer even starts. The command copied from the dashboard starts with a line that enables TLS 1.2 for the session, so it works as pasted.

What you get for a Windows host

A Windows server gets the same page as a Linux one: CPU, memory, load, disk I/O, network bandwidth and disk usage, plus the System Info panel with OS, CPU model, core count, total RAM and boot time.

A few things are adapted to Windows:

  • Disk: each drive letter is a mount point. The system drive, C:, is the disk shown on the server row and in the host-level Disk gauge, the way / is on Linux. Other drives are listed in the Filesystems table.
  • Network: the loopback pseudo-interface and the virtual tunnel adapters Windows creates (ISATAP, Teredo and the hidden Local Area Connection* adapters) are left out of the Network table, so you only see real adapters.
  • Load average: Windows has no load average of its own, so the collector derives one from the processor queue length. It reads like a Linux load average: compare it to the number of cores.

The full list of metrics and units is in Metrics collected.

How the agent runs on Windows

The agent is a regular Windows service:

  • The binary is C:\Program Files\Hyperping\hp-agent.exe.
  • The config and the on-disk queue live in C:\ProgramData\Hyperping. agent.yaml holds the host's agent token, so only SYSTEM and Administrators can read that folder.
  • The hp-agent service starts at boot and restarts 5 seconds after a crash.
  • Logs go to the Application event log. Get-WinEvent -ProviderName hp-agent -MaxEvents 20 shows the latest entries.

Unsent metrics are written to the queue on disk, so a reboot or a network cut does not leave a hole in your charts once the host is back.

To update the agent, run the install command again. It replaces the binary in place and keeps the same server, with its history. To remove it, run the installer with -Uninstall:

& ([scriptblock]::Create((irm https://hyperping.com/install.ps1))) -Uninstall

The server page in the dashboard gives you both commands for Windows hosts.

One view for a mixed fleet

Windows hosts go through the same enrollment, install tokens, groups and escalation policies as Linux and macOS hosts. A group can mix platforms, a bound install token works the same way from PowerShell, and when a Windows host stops reporting, it turns Stale, then Offline, and the escalation policy bound to it pages your team.

If you run your SQL Server, IIS or Active Directory boxes next to a Linux fleet, they now sit in the same list, and the same people get paged the same way when one of them goes dark.

Get started

Open Servers in the dashboard and pick Windows above the install command. The install reference covers paths, flags, Windows Server 2016 and troubleshooting, and Uninstall covers removal.