RDP versus remote support software: two different jobs

The session model is the fundamental difference

RDP logs you in as yourself and creates your own desktop session. On a server that is exactly right — you want your own environment, your own profile, and no interference with anyone else. On a user's workstation it is precisely wrong: you either get a separate session, so you cannot see the problem they are describing, or you disconnect them from their own desktop.

Remote support software attaches to the existing console session. You see what the user sees, they see what you do, and you can talk them through it. That shared view is the whole point of support work, and it is not something RDP was designed to provide.

Network exposure and where each one lives

RDP expects network reachability. Inside a LAN or across a VPN that is straightforward. Exposed directly to the internet it becomes one of the most commonly exploited entry points in ransomware incidents — a pattern documented repeatedly in public advisories from national cyber security bodies. If RDP is in use, it should sit behind a VPN, a gateway or a bastion, with strong authentication and account lockout.

Remote support tools take the opposite approach: the agent makes an outbound TLS connection to a broker on 443, and the operator connects to the same broker. Nothing listens for inbound connections on the endpoint, which is why the model works for home workers, client sites and mobile networks without any firewall change.

• RDP: inbound listener, needs reachability, must be wrapped in VPN or gateway
• RDP: exposed instances are actively scanned and brute-forced continuously
• Support tools: outbound-only from the endpoint, no inbound rule required
• Support tools: work across networks you have no control over

Consent, visibility and the human factor

Support tools prompt the user, show a visible indicator during the session, and let the user end it. That is not decoration — for staff support it is often a policy requirement, and it is what makes remote assistance feel like help rather than surveillance.

RDP has no equivalent concept for the person at the machine, because it was never intended to involve them. Using it on a staffed workstation therefore raises governance questions that a support tool answers by design.

Auditability

RDP produces authentication events in the operating system's logs. That is genuinely useful, but it is per-machine, easy to lose if the endpoint is rebuilt, and requires central log collection before it answers estate-wide questions.

Support tools log centrally by design: operator, device, start and end time, held outside the endpoint. If your evidence requirement is 'show me every session on this device group last month', that difference decides it.

Where each one belongs

Use RDP for server and infrastructure administration inside a network you control, behind a VPN or gateway, with multi-factor authentication on the path in. It is efficient, native and well understood.

Use remote support software when you are helping a person, when the device is on a network you do not control, when you need consent and a visible session, or when you need central logging and role-based access across an estate. Most organisations run both, and the boundary between them is easy to write down.