Connection Broker: The Connection Broker assigns the RDP client to an RD Session Host within a server farm according to an algorithm to optimize load balancing. Preconditions The RD Session Host is operational and listening for an RDP connect request. A Connection Broker is available to redirect the RDP client to an alternate RD Session Host server. If the RDP client is using the IPv6 protocol, then the RD Session Host supports the IPv6 protocol. Main Success Scenario Trigger: The RDP client initiates the connection when the user provides the name of the remote desktop to connect to. The RDP client resolves the server name to an IP address using DNS services. The RDP client establishes a secure RDP connection to the RD Session Host server. The target RD Session Host server can redirect the RDP client connection attempt using a Connection Broker if the load on the server does not permit this new connection. If redirected, the RDP client opens a port on a different server in a farm and initializes an RDP connection to the alternate server. The RDP client successfully negotiates the client license with the RD Session Host. The RD Session Host creates a user session for the RDP client after credentials are checked. The RD Session Host sends the session desktop to the RDP client, and the RDP client displays the remote desktop. The user of the RDP client interacts with the remote desktop. Extensions In Windows 7 implementations, an RDP client can connect to a virtual machine on a VM Host, rather than a user session on an RD Session Host. Establish a Transport UDP Connection Over an Already Established RDP Connection to a RD Session Host Goal To transfer data between an RDP client and an RD Session Host using multi transport UDP. Context of Use A user launches the RDP client to display and interact with a remote desktop or remote application. The RDP client establishes a connection to the RD Session Host that is hosting the remote desktop or remote application. In this use case, a multi transport UDP connection between the RDP client and the RD Session Host server is established on top of the existing RDP connection. The preconditions are met, and licensing, authentication, authorization, and Domain Name System (DNS) services are available. Actors User: The primary actor is the user. RDP client: The RDP client establishes a connection to the RD Session Host in to interact with a remote desktop or remote application.
Connection Broker: The Connection Broker assigns the RDP client to an RD Session Host within a server farm according to an algorithm to optimize load balancing. Preconditions The RD Session Host is operational and listening for an RDP connect request. A Connection Broker is available to redirect the RDP client to an alternate RD Session Host server. If the RDP client is using the IPv6 protocol, then the RD Session Host supports the IPv6 protocol. Main Success Scenario Trigger: The RDP client initiates the connection when the user provides the name of the remote desktop to connect to. The RDP client resolves the server name to an IP address using DNS services. The RDP client establishes a secure RDP connection to the RD Session Host server. The target RD Session Host server can redirect the RDP client connection attempt using a Connection Broker if the load on the server does not permit this new connection. If redirected, the RDP client opens a port on a different server in a farm and initializes an RDP connection to the alternate server. The RDP client successfully negotiates the client license with the RD Session Host. The RD Session Host creates a user session for the RDP client after credentials are checked. The RD Session Host sends the session desktop to the RDP client, and the RDP client displays the remote desktop. The user of the RDP client interacts with the remote desktop. Extensions In Windows 7 implementations, an RDP client can connect to a virtual machine on a VM Host, rather than a user session on an RD Session Host. Establish a Transport UDP Connection Over an Already Established RDP Connection to a RD Session Host Goal To transfer data between an RDP client and an RD Session Host using multi transport UDP. Context of Use A user launches the RDP client to display and interact with a remote desktop or remote application. The RDP client establishes a connection to the RD Session Host that is hosting the remote desktop or remote application. In this use case, a multi transport UDP connection between the RDP client and the RD Session Host server is established on top of the existing RDP connection. The preconditions are met, and licensing, authentication, authorization, and Domain Name System (DNS) services are available. Actors User: The primary actor is the user. RDP client: The RDP client establishes a connection to the RD Session Host in to interact with a remote desktop or remote application.