Machines with nobody in front of them, always reachable

The problem with administering unattended machines

A server has nobody sitting at it, so the "ask permission and have someone accept" model does not apply. The usual alternatives each carry a cost:

• RDP exposed to the internet: it works, and it is one of the most heavily exploited entry points for ransomware. An open remote desktop port starts receiving login attempts within hours of going live.
• VPN: the right answer from a security standpoint, but it has to be built, maintained and paid for. For a company with two servers it is usually disproportionate.
• Commercial remote desktop licences: the price grows with your device count, exactly when what you want is to add more machines to your coverage.

LineDesk covers this case with unattended access, without exposing any port and with no cap on devices, because there is no plan counting them.

Configuring an unattended machine

1. Install LineDesk on the server and open it. Note the 9-digit ID.
2. In Settings, enable unattended access and set a long, unique password for that machine. Do not reuse one password across the fleet: if one leaks, I do not want every machine opening.
3. Disable sleep on the machine. A sleeping box does not answer connections.
4. Leave LineDesk running. It lives in the system tray, so closing the window does not shut it down.
5. From your own PC, add it to the address book with a descriptive name and test the connection before you leave.

The features that matter here

Persistent sessions

After a drop, LineDesk first tries to repair the existing connection. If that fails it rebuilds the session using the stored password and keeps retrying until you close the tab. In practice that means you can start a long job — a migration, a backup, an update — and go do something else: if the network blinks, the session comes back on its own.

Address book with live status

The book shows in real time whether each machine is up. That is basic monitoring for free: if a server went down, you see it when you open the program instead of finding out when you try to connect.

Several machines in parallel

Update five servers at once, each in its own tab. Sessions you are not watching drop their video quality automatically, so they do not compete for bandwidth with the one in front of you.

File transfer

Push a patch up, pull a 200 MB log down to analyse properly, take a database copy before touching it. Block size adapts to the link speed and the transfer never adds lag to your control.

Elevation to administrator

Almost everything you do on a server needs elevated privileges, and Windows will not let a normal process drive an elevated window. On a server the answer is to configure LineDesk to always start as administrator: it comes up elevated at boot, with nobody needed at the other end.

Security: good practice

Unattended access is convenient, and for that exact reason it deserves care. Concrete recommendations:

• A different password per machine. Long, random and stored in a password manager — not on paper and not in a spreadsheet.
• Rotate it when someone no longer needs the machine. Changing the unattended password revokes their access instantly.
• Enable privacy mode on machines sitting in walkways. The curtain stops passers-by seeing what you are doing.
• Document which machines have unattended access. An out-of-date list of open doors is a security problem in itself.
• Review periodically which machines still have it enabled and turn it off where it is no longer needed.

Limitations worth knowing up front

For this use case in particular, two restrictions can be decisive:

• Ctrl+Alt+Del cannot be sent and the Windows sign-in screen is not visible remotely. Windows reserves the secure desktop for the system, and only products that install a dedicated service can reach it. In practice: if the server reboots and lands on the lock screen, you will not be able to unlock it remotely.
• The usual workaround is to configure automatic sign-in on unattended machines, so that after a reboot they come back with a session started and LineDesk running. Judge whether an always-signed-in session is an acceptable risk in your situation; on a server with restricted physical access it normally is.
• No central console. There is no panel for pushing policies to hundreds of machines at once. If you administer a very large fleet, you will feel that gap.