6.3. Desktop Access Using RDP Clients

6.3.1. Accessing Desktops With an RDP Client
6.3.2. About the Oracle VDI RDP Broker

Oracle VDI includes a built-in RDP broker that enables access desktops using an RDP client.

Supported Clients

The following RDP clients have been tested with Oracle VDI:

Other clients may also work, but have not been tested.

RDP Connection Settings

When users access a desktop from an RDP client, none of RDP settings configured for the pool apply (see Section 5.1.3.1, “Pool Sun Ray RDP Settings”). These settings include performance optimization settings, such as disabling menu animations, and device redirection settings, such as access to client drives and audio. Users have to specify any such connection settings in the RDP client, for example on the Experience tab of Microsoft Remote Desktop Connection.

RDP Broker Security

As a security precaution, Oracle VDI authenticates users each time they sign into a desktop. Users may find this inconvenient. If you prefer to disable this feature, refer to Section 6.2.5, “How to Disable Client Authentication”. For a more detailed treatment of security issues, see the Oracle Virtual Desktop Infrastructure Security Guide.

6.3.1. Accessing Desktops With an RDP Client

To access a desktop, users run the RDP client and specify the DNS name or IP address of an Oracle VDI host together with a user name, which can include a domain name. By default, users are connected to their default desktop, which can be defined in Oracle VDI Manager.

Alternatively, users can specify a particular desktop or pool by entering the user name, the pool name, and optionally a desktop ID, in the RDP client using the following syntax:

username::pool=poolname[,desktop=desktopId]

It is usually sufficient to specify just the user name and pool name. However, users with multiple desktops assigned from the same pool must specify both the pool name and the desktop ID.

To view a listing of desktop IDs, use the following command:

vda user-desktops username

In the following example, the Sun Ray Windows connector is used to connect to any machine from a pool:

/opt/SUNWuttsc/bin/uttsc -u jdoe::pool=win-xp -d example.com vdi-example.com

The following image shows a similar example using Microsoft Remote Desktop Connection.

Screen capture of the Microsoft Remote Desktop Connection dialog showing how to specify the pool name.

In the following example, the Sun Ray Windows connector is used to connect to a specific desktop:

/opt/SUNWuttsc/bin/uttsc -u jdoe::pool=win-xp,desktop=33 -d example.com vdi-example.com

The following image shows a similar example using Microsoft Remote Desktop Connection.

Screen capture of the Microsoft Remote Desktop Connection dialog showing how to specify a desktop.

If users frequently switch between desktops, it is best to save the connection settings for each desktop in the RDP client.

6.3.2. About the Oracle VDI RDP Broker

This section describes how the RDP broker mediates between several elements of Oracle VDI:

  1. The RDP client contacts the Oracle VDI RDP broker and passes it any relevant information, such as user name and password.

  2. The RDP broker then contacts the Oracle VDI service on behalf of the client and asks it to start the desired desktop.

  3. Assuming that client authentication is enabled on the service side, which it is by default, the Oracle VDI service verifies the user name and password (see Section 6.2.5, “How to Disable Client Authentication”).

  4. If authentication succeeds, the Oracle VDI service starts the corresponding desktop and returns the IP address and, optionally, RDP port of the virtual machine running the desktop.

  5. The RDP broker uses this information to construct an RDP Server Redirection Packet.

    • For Windows RDP, the packet contains the VM host/IP address as the server to redirect to. This is the model that VMware Infrastructure 3 uses.

    • For VirtualBox RDP, the packet contains a routing token. The routing token consists of an encoded IP address and RDP port information, which are needed because VRDP does not use the standard Windows RDP port. For details of the routing token encoding, see the "Routing Token Format" section of Session Directory and Load Balancing Using Terminal Server on the Microsoft website.

  6. The RDP broker sends the redirection packet to the RDP client, and the client is redirected accordingly.