RDGW RPC HTTP Proxy Test

The RPC HTTP Proxy (also known as RPC over HTTP) is a technology that allows clients to use the Remote Procedure Call (RPC) protocol over HTTP or HTTPS instead of the traditional RPC over TCP/IP. This can be useful in scenarios where a client needs to connect to an internal Exchange server or other Microsoft services through a firewall or proxy without directly exposing internal ports.

This test monitors the RPC HTTP proxy in the RD gateway and reports the rate at which data were transmitted/received. In addition, this tests reports the connections that had failed, thus helping administrators to reason out why and take corrective actions.

Target of the test : Microsoft RD Gateway

Agent deploying the test : An internal agent

Outputs of the test : One set of results for Microsoft RD Gateway that is currently launched.

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.

Host

The nick name of the Microsoft RD Gateway component for which this test is to be configured.

Port

Refers to the port at which the specified host listens to. By default, this is 3389.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Data transmitted to RPC proxy

Indicates the rate at which data were transmitted to RPC proxy.

MB/Sec

 

Data received from RPC proxy

Indicates the rate at which data were received from RPC proxy.

MB/Sec

 

Load balancing messages attempted

Indicates the rate at which the load balancing messages were attempted by the RPC proxy.

Requests/sec

Load balancing messages in RD Gateway environments refer to the communications exchanged between the load balancer and the RD Gateway servers to manage the routing of incoming RDP traffic.

Load balancing messages failed

Indicates the rate at which the load balancing messages handled by the RPC proxy had failed.

Requests/sec

A low value close to 0 is desired.

Load balancing decisions attempted

Indicates the rate at which the load balancing decisions were attempted by the RPC proxy.

Requests/sec

Load balancing decisions in RD Gateway are made by the load balancer to determine which RD Gateway server should handle a new incoming RDP connection. The goal is to distribute traffic evenly, ensure high availability, and avoid overloading any single server.

Load balancing decisions failed

Indicates the rate at which the load balancing decisions handled by the RPC proxy had failed.

Requests/sec

A low value close to 0 is desired.

Connections to back-end server attempted

Indicates the rate at which the RPC proxy had attempted to establish connections to the back-end server.

Connections/sec

 

Connections to back-end server failed

Indicates the rate at which the connections to the back-end server had failed.

Connections/sec

A low value close to 0 is desired.

Front-end HTTP connections

Indicates the number of front-end HTTP connections the RPC proxy had established.

Number

 

Users connected to back-end server

Indicates the number of users that were connected to the back-end server.

Number

 

RPC/HTTP request rate

Indicates the rate at which the RPC/HTTP requests were handled by the RPC proxy.

Requests/sec