Skip to main content
Version: v42

RDS Connections

This guide helps connect to Remote Desktop Services (RDS) via PrivX.

PrivX supports connections to RDS via load balancer or RD Connection Broker.

RDS Connections via Load Balancer​

To connect to an RDS that uses a load balancer, add a host service as follows:

  • Type: RDP
  • Address and Port: Set to the RDS load balancer's address and port.
  • RDS Type: Load Balancer
  • Max Session Hosts: Set to the maximum number of session hosts behind the load balancer.

Session Host Certificates Management​

The RD Session Hosts connected via the load balancer can be viewed and managed by clicking Manage Session Hosts Certificates. This allows administrators to maintain the certificates for all session hosts in the load balancer pool.

RDS Connections via RD Connection Broker​

To connect to an RDS that uses an RD Connection Broker, add a host service as follows:

  • RDS Type: Broker
  • Broker Hostname and Broker Port: The address and port of the RD Connection Broker.
  • Max Session Hosts: Set to the maximum number of session hosts behind the RD Connection Broker.
  • Collection Name: The name of the virtual grouping defined in the RD Connection Broker.

There are two methods for establishing connections through the RD Connection Broker.

  • For direct connections, PrivX establishes a direct connection to the RD Connection Broker. (the service type, address, and port must be unique, following standard PrivX requirements).
  • For Extender-based connections, the Extender name is prefixed to the service address, which allows for routing connections through the PrivX Extender component to reach the RD Connection Broker.

Session Host Certificates Management​

Similar to the load-balancer configuration, the session hosts connected via the RD Connection Broker can be viewed and managed by clicking Manage Session Hosts Certificates.

Licensing Considerations​

Max Session Hosts count toward your PrivX license's Max Hosts limit. This applies to both load-balancer and RD Connection Broker RDS targets. Each session host configured in the deployment, whether behind a load balancer or managed by an RD Connection Broker, is counted individually for licensing purposes.

If you no longer need RDS connections, consider removing the associated host entries from PrivX to free up their license count.