It is 9 p.m. on a Tuesday and a client’s file server has stopped sharing files. The office that houses it closed at six. If your remote access depends on someone at the far end reading out a session code, your evening now includes convincing a facilities manager to drive back and press a button.
Attended screen sharing is the right tool for helping a person at their desk. It is the wrong foundation for supporting machines, and most small IT shops discover the difference exactly like this.
Where session codes stop scaling
The one-off session model has a ceiling, and it arrives earlier than most teams expect.
Nobody is present after hours, which is precisely when servers prefer to fail. Every session starts with a small ritual of codes and confirmations, fine once, tedious the fortieth time. Machines accumulate faster than memory: by the time a shop supports six clients, “the gray box in the back room” is not a device inventory. And when the workaround becomes a shared password kept in a spreadsheet so anyone on the team can get in anywhere, you have traded convenience for a security posture you would never recommend to a client.
Doing unattended access properly
Unattended access means your tooling can reach an authorised machine with nobody sitting at it. Done carelessly, that is a liability. Done properly, it is four habits.
Get the authorization in writing. Standing access to a client’s machines belongs in the services agreement, named per site or per device group, not in a verbal okay from whoever signed the deal. Treat it the way you would treat holding keys to their building, because that is what it is.
Install the agent as a service and verify it survives. A lightweight agent on each machine is what makes unattended access work. Confirm it comes back after a reboot and after an OS update before you rely on it at 9 p.m., not during the incident.
Organise devices by client from day one. Predictable names and per-client groups are boring and they are also the difference between “connect to acme-office-fileserver” and asking a colleague which gray box it was. Online and offline status per device tells you whether the problem is the service or the whole machine before you commit to a drive across town.
Scope access to people, not to the team. A junior technician who supports two clients should see those two clients and nothing else. Role-based access per device group means the blast radius of any one account, and any one departure, stays small. When a technician leaves, offboarding is disabling one account, not rotating passwords across twenty client sites and hoping the spreadsheet was complete.
What to check before you standardise on a tool
A few practical tests, run against your real client mix rather than a demo environment. Coverage first: that one Linux box at the accounting client counts, so Windows, macOS, and Linux support is not optional. Check the technician side too: sooner or later you will work from a hotel computer or a locked-down site machine, and starting a session from a browser without installing a desktop client is what saves that day. For servers, a terminal or SSH session is often faster and lighter than a full desktop, and for moving patches or log bundles you want file transfer over an encrypted channel rather than email round-trips.
And be honest about the boundary. Unattended access gets you to the machine; it does not watch the machine for you. If you are also expected to monitor health, apply patches, and catch problems before the client calls, that is monitoring and management territory, which is a different product category with different costs.
Where LynxTrac Remote fits
We build LynxTrac Remote for exactly this shape of team: individuals, freelancers, and small IT shops that need reliable access to remote computers without a full management platform. It covers remote desktop, browser-based sessions, unattended access, SSH and terminal on the Professional and Team plans, and encrypted file transfer with SFTP on those same plans, across Windows, macOS, and Linux. Device groups and role-based access for small support teams come with the Team plan. Plans and pricing are on the official site, and the overview lives on the LynxTrac Remote product page. If your work also includes monitoring and patching, look at LynxTrac instead; it is the same platform grown up.