UplinkOps

Current release

Which version is current

UplinkOps never calls home, so your server cannot tell you whether a newer release exists. This page is the answer. If the version below is higher than the one in your dashboard, there is an upgrade waiting.

1.19.0
Released
Components
Server and agent
Upgrade
Replace the server, then press Update agents
How to upgrade. Double-click the new server installer on the server machine; your database, certificates and settings are left alone. Then open the dashboard, press Update agents, and reload the page. Machines that are switched off collect the new agent themselves when they next start.
Check what you downloaded. Our installers are not yet code-signed, so Windows will warn about an unknown publisher. From 1.19.1 onwards every release package carries a SHA256SUMS.txt listing the SHA-256 checksum of each file in it; compare it before you run anything. On Linux: sha256sum -c SHA256SUMS.txt  On Windows: Get-FileHash .\uplinkops-server-setup-1.19.0.exe

What is in 1.19.0

1.19.0

Server + agent

Fixed: patch monitoring had stopped reporting. A syntax error in the update-collector script meant that from 25 October no Windows machine reported anything about patches. The pending and failed update alerts could not fire, three items were missing from Needs attention, the patch check dropped out of the posture score, and the patch sections went missing from the machine report, the fleet report and the report builder. The agent logged the failure on every machine, but that message is only visible on one card of one page, so it went unnoticed for six days.

Also new: every PDF now carries the update-check date. The date on which someone last confirmed they checked for a newer UplinkOps release is printed on the cover page and in the footer of every report. If it has never been confirmed, the line says so rather than being left out — a blank space in this product means checked and fine, never not checked.

Still open: the Last update check and Last install fields on the machine page read a registry value that Windows does not always write, so they can stay empty. That is a separate, smaller issue and was not changed here.

Releases are built from a tagged commit and reproduce byte for byte from that tag, so the file you download can be checked against the source it was built from.

Need the installer?

Write to us and say which platform you need, and we will send the file with its checksum.