MeshCentral, one click from the machine
Connect MeshCentral and every machine you link opens its remote desktop, terminal and files from its Wegweiser page. Wegweiser only reads: a fixed list of questions to what MeshCentral has already stored, and nothing sent to an agent. Linking now also weighs the system UUID, which for a virtual machine is often the only identity there is.
Wegweiser tells you what is wrong with a machine. Until today, fixing it meant leaving: finding the same machine in your remote access tool, under whatever name it has there, and opening a session. If that tool is MeshCentral, the machine's page now does the finding for you.
Connect it once
Integrations > MeshCentral asks for your server's address and a login token, which you make in MeshCentral under My Account > Login Tokens. A token signs in as the MeshCentral user who made it, and you can revoke it there at any time without touching anything in Wegweiser. Wegweiser checks the login before it stores anything, reads your devices straight away, and reads them again once a day.
Link it, then one click
Machines are linked the way VSA devices are since this morning: on Link devices, where every suggestion shows its evidence and a person decides. A linked machine's page shows In MeshCentral with three buttons beside it: remote desktop, terminal and files. They open MeshCentral in your own browser, where you sign in as yourself. Wegweiser never signs anybody in and never opens a session of its own.
A link whose evidence stops holding goes to review: the record disappears from MeshCentral, the operating system changes on either side, or MeshCentral's agent falls silent while ours keeps reporting. Its buttons disappear until somebody looks, because a remote desktop opened on the wrong machine is exactly the mistake the page exists to prevent.
The UUID, for machines with no serial
Suggestions now also weigh the machine's system UUID, which MeshCentral reports and the Wegweiser agent reports from version 0.3.109. For a virtual machine it is often the only identity there is: no serial number, and a network address the hypervisor made up. On our own estate, 15 of the 32 devices in MeshCentral report no serial at all.
The first read of our own MeshCentral found what a look at any RMM usually finds: old records beside the machines that replaced them. Two virtual machines are still in MeshCentral as the Hyper-V guests they used to be, silent for months beside the KVM machines of the same names, and a workstation reinstalled with Linux still has its Windows record there. Each is shown with the evidence against it, and none is linked.
It only reads
A MeshCentral login token carries its user's rights, and those usually include remote control. So what Wegweiser may ask is fixed in Wegweiser, not left to the token: the device groups, the devices, when each last connected, and each machine's hardware identifiers and network adapters, all from what MeshCentral has already stored. Nothing reaches a MeshCentral agent, and any other request is refused before it is sent. The connection never follows a redirect, so the token only ever goes to the address you typed.
Also new
One Link devices page for every RMM. VSA and MeshCentral share it, and the next RMM will too. In a list of same-machine pairs, Not the same machine now dismisses the pair you clicked; it used to dismiss the first one ticked.