There are a lot of differences and improvements between Windows Virtual Desktop (WVD) and a traditional Microsoft Remote Desktop Services (RDS) environment, one of the core changes in Windows Virtual Desktop is the way the client devices connect to the environment resources.
When connecting to a traditional Remote Desktop Services environment from an external location, clients would usually connect the RD Gateway over TCP 443. Once connected the client would authenticate with Active Directory, the Gateway would create a secure inbound session connection to the selected Remote Desktop Services resource allowing the external client access. The Remote Desktop Services Gateway can also be setup to use UDP (port 3391) in the later versions of Remote Desktop Services, this improves the connection quality, especially over high latency networks.
Connecting to a Windows Virtual Desktop environment does not require any inbound ports to be configured on the virtual desktops external clients will be connecting to. The communication between the host pools and the core SaaS components of Windows Virtual Desktop is established using TCP on port 443 (UDP connections are in development but not available at the current time). Reverse connect has additional feature over the transitional Remote Desktop Services connection, where access can be restricted by time of day or by the client IP address.
The use of reverse connect for external clients improves the security of the deployment as no inbound rules need to be open to internet.
If you would like more detail on how reverse connect functions follow the link to Ryan Mangans IT blog post on Windows Virtual Desktop Reverse connect.
- Download our Windows Virtual Desktop whitepaper to find out more
- Download our Windows Virtual Desktop datasheet
- book a free Windows Virtual Desktop workshop with Systech here