Skip to content

v2.2.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Sep 17:54
· 2 commits to master since this release
v2.2.2
c171755
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Hardening that came out of a real fleet move: a server restored onto a new box, and a batch of new devices enrolling over poor mobile links. Every component is 2.2.2.0; there is no schema change. This release also covers 2.2.1, which was merged but never tagged.

Highlights

  • MSIs keep one ProductCode. Every generated MSI used to get a fresh ProductCode, so Intune, GPO or SCCM saw each rebuilt MSI as a different product and pushed it onto machines that already ran the agent, where the shared UpgradeCode turned it into an uninstall and a re-enrollment. The code is now constant (Server:MsiProductCode overrides it); only the PackageCode changes per build.
  • No silently smaller MSIs. After a restore the package rows exist but the files may not, because the package directory is not in the backup. A missing agent, updater, client or TightVNC file now refuses the build and names the file, instead of producing an MSI without TightVNC.
  • Package files in the snapshot. Diagnostics lists current packages whose file is missing, the server logs them at startup, and restore.sh ends with the reminder.
  • VNC provisions itself when TightVNC arrives. First-time provisioning only ran at agent start, so a device that got TightVNC through a later rollout had no VNC password until its service was restarted. The watchdog now does it within 30 seconds, backing off on real failures.
  • racctl: diag and status print the server's JSON verbatim, get works from Git Bash, devices shows the TightVNC version and the last hour's reconnects.

Upgrading

  1. Server: upload RemoteServer-linux-x64.tar.gz in Server settings → Server update, then Update server. No SQL. Afterwards take a Diagnostics → Snapshot and check that packages lists nothing as missing, especially on a server that was restored from a backup.
  2. Agent: roll it out to get the VNC self-heal. Console: needed for the new MSI messages. Updater, Lite and the Linux console carry the aligned version only.
  3. MSIs: rebuild them after the server update so they carry the fixed ProductCode, and re-point deployment-tool detection rules at it once. In Intune set Ignore app version to Yes: the agent updates itself through the release channels, so its version moves on without the MSI.

Artifacts

  • RemoteAgent.exe, RemoteAgent.Updater.exe, RemoteClient.exe, RemoteClient.Lite.exe — Windows, self-contained, signed with the maintainer's Open Source Developer code-signing certificate and timestamped.
  • RemoteServer-linux-x64.tar.gz — the server package for the console's Server update tab.
  • remoteclient_2.2.2_amd64.deb — the Linux operator console.
Assets 8
Loading