v2.1.7

RemoteAppClient 2.1.7 — bulk note import

Two things a fleet needs before it grows: a way to attach notes to hundreds of machines at once, so a live record can be told from a stale one — and a status badge that stops calling a switched-off machine flaky. There is no database schema change.

Component versions are not aligned in this release. The Windows console is 2.1.7.0; the server, agent, updater, Lite console and Linux console are 2.1.6.0. The agent and updater have no code changes.

Notes for hundreds of devices at once

• Import notes (admin-only, the new button next to Refresh): open or paste a hostname;note list — a CSV saved from Excel, or two columns copied straight out of it — and see line by line what would happen before anything is written: New, Overwrite, Not found, Invalid line, Repeated, Empty note, Unchanged.
• It writes only to devices already enrolled. An unknown name is reported and skipped, never created, so the same list can be run again as more machines arrive — and Copy unknown names puts exactly the missing ones on the clipboard.
• A name shared by several devices goes to the one seen most recently. The others are usually stale re-enrollments, and leaving them without a note is precisely what makes them easy to find and delete.
• Nothing is lost by accident: a blank note never clears one, and overwriting an existing note stays off until you switch it on. The preview shows the current note next to the new one, and Save asks once more with the counts.
• Excel is taken as it comes: the Windows code page its plain CSV is written in, UTF-8 with or without a BOM, UTF-16 Unicode text, quoted cells, the trailing empty columns of a sheet that once had more, a header row, fully qualified names. The detected encoding is shown, so a garbled accent comes with an explanation.
• The console sends device IDs, not names, so the server writes exactly the rows you approved instead of repeating a lookup that could land elsewhere. Every changed note is committed together with its own audit entry (Note imported, filterable in the log); the note text itself stays out of the log, since notes are stored encrypted.

Offline means offline

• A machine switched off at the end of the day could still show as flaky half an hour later. Flaky means three or more reconnects within the last hour, and it was checked before offline — so a device that reconnected a few times on its way out kept the badge for the whole hour.
• Now a device that has stopped reporting is offline, whatever its link did before; flaky is kept for a machine that is still sending data over a bad connection. The server, which writes the device history, and the consoles decide it the same way, and the status column sorts by liveness instead of by the online flag alone.

Also

• Single-column lists — audit log, users, groups, device history — no longer grow a stray horizontal scrollbar that hid the last row once the rows overflowed.
• build.ps1 -SignScript <script> signs every exe before it is hashed or deployed. Agents verify an update's hash, so signing afterwards would make every agent refuse the update. Accounts and certificates stay in your own script, out of the repository, and a failed signature counts as a failed build.

Upgrading

No schema change, no SQL to run. Update the server first if you want the import: against an older server the console says so plainly instead of failing with an HTTP error. The wire contract is additive, so older consoles keep working with the new server, and nothing here needs an agent update.

Artifacts

• RemoteClient.exe (2.1.7.0), RemoteClient.Lite.exe, RemoteAgent.exe, RemoteAgent.Updater.exe — Windows x64, self-contained single-file
• RemoteServer-linux-x64.tar.gz — server
• remoteclient_2.1.6_amd64.deb — Linux operator console