There are four practical ways to reach a Windows VPS — mstsc (RDP), RD Gateway, RemoteApp, and WinRM/SSH — and each has different port, certificate, and permission requirements. Choosing the wrong one for your environment creates avoidable firewall holes or unnecessary complexity. This guide compares them on what they need and when each is the right tool. For platform basics, see our Windows VPS overview.
mstsc: The Default
Plain RDP on port 3389 is the default and the simplest. It needs one inbound firewall rule, a user with Remote Desktop rights, and network-level authentication enabled for security. It is the right choice for a single administrator on a trusted network. Its weaknesses: the port is constantly scanned, so use an alternate port or a VPN, and it offers no per-application granularity.
RD Gateway: RDP Without the Open Port
RD Gateway tunnels RDP over HTTPS on port 443, so you never expose 3389 publicly. It requires a gateway server, a certificate matching the gateway’s public name, and an authorization policy mapping users to machines. The setup cost is higher, but it is the correct choice for exposing RDP to the internet for a team. If your provider offers RD Gateway as a service, it is usually worth the small premium over a VPN for simplicity.
RemoteApp: Applications, Not Desktops
RemoteApp publishes individual applications rather than a full desktop session. Users launch a single program as if it were local, with its own window, and never see the server desktop. Licensing considerations apply: Remote Desktop Services Client Access Licenses are required for multi-user RemoteApp deployment. It is the right choice when users need a specific application but should not have desktop access.
RemoteApp also reduces the attack surface: a user who can only launch one program cannot browse the filesystem or run arbitrary commands. For line-of-business applications, that is a security benefit as well as a usability one.
WinRM and OpenSSH: For Automation
WinRM is PowerShell remoting over HTTP or HTTPS, and OpenSSH for Windows provides an SSH server. Neither gives you a desktop; both give you a command channel suitable for scripting and configuration management. Use them for automation platforms, not for interactive administration. WinRM over HTTPS on 5986 with a certificate is the supported secure configuration; WinRM HTTP on 5985 should be restricted to a trusted management network.
Choosing by Environment
Solo admin on a trusted network: mstsc with an alternate port. Team needing remote access from anywhere: RD Gateway, or a VPN plus mstsc. Users needing one application: RemoteApp with the correct RDS licensing. Automation and configuration management: WinRM over HTTPS or SSH. Interactive troubleshooting by a managed provider’s staff: provider-specific console or a scoped RDP account with session recording.
Hardening Every Path
Regardless of method, enforce network-level authentication, restrict the allowed source IPs where possible, enable account lockout, and monitor logon events for failures. For RDP specifically, disable the default administrative shares if unused and require an account name that is not “Administrator”. The connection method determines the attack surface; the hardening determines whether a compromised path stays contained.
Pick the method by environment, then harden it: RD Gateway or VPN for team access, RemoteApp for single-application users, WinRM for automation, and mstsc only on a restricted port. See the plan options in the Windows VPS overview if you need a provider that supports RD Gateway.



