RDP Broker Service Test

Oracle Virtual Desktop Infrastructure includes a built-in RDP broker that enables easy desktop access leveraging the Remote Desktop Protocol (RDP). This way, users can take advantage of existing RDP clients (for example, the remote desktop connection in Windows XP) for accessing desktops.

  1. The RDP client first contacts the Oracle VDI RDP broker (passing over any information like username, password, etc).
  2. The RDP broker will then contact the Oracle VDI Core service on behalf of the client and will ask to startup the desired desktop.
  3. The Oracle VDI Core service will first verify the username/password combination if client authentication is enabled on the service side (default).
  4. If authentication succeeds, the corresponding desktop will be started up and the Oracle VDI Core service returns the IP and optionally RDP port of the virtual machine (VM) running the desktop.
  5. This information is used by the RDP broker to construct an RDP Server Redirection Packet containing either:

    • the VM host/IP address as the server to redirect to (if using Windows RDP, as done for VMware Infrastructure 3)
    • or a routing token containing encoded IP address and RDP port information (if using the VirtualBox RDP, also known as VRDP)

    The latter is necessary, because VRDP does not use the standard Windows RDP port. Thus the RDP broker needs to hand back both the IP and the RDP port information.

  6. Finally, this RDP redirection packet is sent back to the RDP client and the client will redirect accordingly.

If the RDP Broker is not running then users connecting via RDP clients may not be able to access their desired desktops. This test promptly alerts administrators if the RDP Broker service stops, so that the service can be started before users complain.

Target of the test : An Oracle VDI Broker

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the Oracle VDI broker being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed


The host for which the test is to be configured.


The port number at which the specified Host listens to.


This test executes certain privileged VDA (Virtual Desktop Access) commands to pull out the desired metrics from the broker. To enable the test to run these commands, you first need to install a sudo package on the broker host. The procedure for installing this package is detailed in Pre-requisites for Monitoring the Oracle VDI Broker in an Agent-based Manner. Once the package is installed, you need to specify the full path to the install directory of the sudo package in the SudoPath text box.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

RDP broker service status

Indicates whether the RDP broker service is currently running or not.


If the broker service is running, then, then this measure will report the value Online. If the broker service is not running, then this measure will report the value Offline.

The table below lists the numeric values that correspond to each of the states mentioned above:

State Numeric Value
Online 100
Offline 0


Typically, this measure will report the States indicated in the table above as its values. However, in the graph of this measure, the online/offline states will be represented using their numeric equivalents only - i.e., 0 and 100.

The detailed diagnosis of this measure reveals when the RDB Broker service started and the full instance name of the service.