Probe installation

What the probe needs

• An always-on Windows (8.1/Server 2012 R2 or newer) or Linux machine on the LAN you want to monitor
• Outbound HTTPS (443) to your PingIQ cloud URL — no inbound ports, no firewall changes
• Python 3.11+ — installed automatically if missing (portable install on Windows, system packages on Linux)
• Reachability to the devices it should monitor (ICMP, and SNMP/UDP 161 where used)

Download

Dashboard → Probes → Add probe gives you a zip pre-configured with your tenant key and cloud URL. Everything below is inside it.

Windows

• The installer detects Python (or downloads a portable copy), installs dependencies, and starts the probe
• The watchdog is a Scheduled Task that checks every 3 minutes and relaunches the probe if it stopped — it covers reboots, crashes and interrupted updates, with no console windows
• Run-PingIQ.bat starts the probe manually any time; starting it twice is harmless (the second instance exits cleanly)
• Running the installer without Administrator works too — the watchdog then runs with standard privileges

1. Extract the zip
2. Double-click install.bat
3. Answer Y to "Enable watchdog?"

Linux

• Installs Python 3 via your package manager if needed, then puts dependencies in a private venv inside the probe folder — works on PEP 668 "externally managed" systems (Raspberry Pi OS, Debian 12+, Ubuntu 23.04+) without touching system packages
• Registers a systemd service with automatic restart — supervision is built in
• Logs: journalctl -u pingiq-probe -f
• Raspberry Pi works great as a probe host — any Pi 3 or newer with Raspberry Pi OS

chmod +x PingIQ-Setup.sh
sudo ./PingIQ-Setup.sh

Verify

Within a minute the probe appears online under Dashboard → Probes, showing its version, last heartbeat and code-integrity status. Discovery results follow within 15 minutes.