Three or four different Windows features all get called 'remote', and they do very different jobs. Mixing them up is why people expect a help session to behave like a second desktop. Here is the clear split, feature by feature.
When someone says 'just remote in and fix it', they might mean any of four things: watching the user's screen, driving the user's screen, supervising a session on a server, or opening a private desktop of their own. Windows has a distinct tool for each — and only one of them gives you a desktop of your own.
Only the last row is a private workspace. The first three all involve somebody else's screen.
Quick Assist is built into Windows 10/11: the helper gets a code, the person at the PC enters it and allows the connection, and both see the identical screen. With permission, the helper can take control of mouse and keyboard. The older Remote Assistance works on the same idea — one shared session, started by invitation.
This is the right tool for training, demonstrations and 'my screen shows an error' support. The person at the PC must be present to allow it, which is a feature, not an inconvenience: nobody watches your screen uninvited.
On a Windows Server running Remote Desktop Services, an administrator can shadow a user's live session — view it, and with the right policy, control it — while the user keeps working. Admins launch it from the server tools or with the documented command form mstsc /shadow together with the session ID.
A Remote Desktop session is different in kind: it is a private desktop belonging to one account, with its own apps and files view. The user whose session it is does not share it with the person at the machine — which is exactly why client Windows only allows one of them at a time, and why running many at once is the Windows Server RDS product.
If your need is 'let me do my own work on that machine', you are asking for a session. If your need is 'let me see what is on their screen', you are asking for assistance or shadowing. Naming the need correctly picks the tool — and often avoids the whole multi-session problem.
A quick field guide:
Every one of these features can show you somebody's work, salary spreadsheet or personal messages. The professional rules are the same regardless of tool: ask first, connect second; keep consent prompts enabled where they exist; never shadow or assist silently 'just to check'; and end the connection when the job is done. Offices that follow these rules keep trust in their IT help — offices that do not, find staff hiding problems instead of reporting them.
Watch the video for the multi-user RDP concept on screen, and use this page to pick the right remote tool for each job.
▶️ Watch Full VideoNo. Quick Assist mirrors your screen — your colleague sees and can control your session. It is a help tool, not a way to run a second, private desktop.
No. Shadowing is a Remote Desktop Services feature of Windows Server, used by administrators to view or assist a user's server session. On a Windows 11 PC, use Quick Assist for the same support purpose.
With the recommended policy, yes — the user is prompted to consent before the administrator can view the session. Administrators can configure shadowing without consent on a server, which is exactly why the consent setting should stay on.