Remote access technologies matching lab

Match RDP, VNC, RMM, and WinRM; leave SPICE-as-RDP and open-3389 unused.

Match each remote access ticket. Leave SPICE-as-RDP and open-3389 unused.

CompTIA 4.9 chooses RDP, VPN, VNC, SSH, RMM, SPICE, or WinRM with the security tradeoff named.

Help desk needs a full Windows desktop GUI on TCP 3389

Microsoft remote desktop.

Mixed Linux/Windows lab needs a simple cross-platform framebuffer

VNC family.

MSP manages hundreds of endpoints with agents and scripting

Remote Monitoring and Management.

Automate Windows config with PowerShell remoting

WinRM under the hood.

Still on the bench

RDP — Windows Remote Desktop (TCP 3389) — Native Windows GUI remoting. Lock down NLA and network exposure.
VNC — cross-platform remote framebuffer — Encrypt or tunnel it; plain VNC is eavesdroppable.
RMM platform — agent inventory, patch, remote control — MSP scale: one pane for many machines, not one-off RDP.
WinRM — PowerShell remoting / Windows Remote Management — Automation channel. Pair with HTTPS listeners and constrained endpoints.
Use SPICE on every corporate Windows laptop instead of RDP — SPICE is a virtualization display protocol, not the default Windows help-desk path.
Forward RDP 3389 straight to the internet without VPN/NLA — Exposed RDP is ransomware candy. VPN, gateway, or zero-trust brokering.