Remote DX Overview and Client Metrics
- Print
- DarkLight
- PDF
Remote DX Overview and Client Metrics
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Use Remote DX to monitor metrics such as CPU usage and WiFi signal strength from client devices that are logged into your virtual environment. Remote DX gives you visibility of user client devices regardless of where they work or what type of workspace they use.
Remote DX supports Citrix, VMware, and Microsoft Azure. For full details on supported client operating systems for each platform, visit the Remote DX Support Matrix.
Requirements
The client device must have:
- The relevant Remote DX plugin for the client OS and virtualization platform.
- Access to the internet latency IP/DNS target to test the device's latency. The default latency target for all operating systems is 8.8.8.8. When installing the Windows plugin, you can set a custom latency target.
- Access to https://fabric.controlup.com to collect client location and ISP data.
The virtual machine must have:
Install the Remote DX Plugin
learn how to install the Remote DX plugin for:
- Windows
- macOS
- HP ThinPro (VMware)
- HP ThinPro (Citrix)
- IGEL
- Dell Wyse
- Stratodesk NoTouch
- Unicon eLux
- ChromeOS
Collected Client Device Metrics
When a client device with the Remote DX plugin connects to a Citrix, VMware Horizon or AVD machine with the ControlUp Agent installed, the following client device metrics are collected.
| Metric Name | Description | Note |
|---|---|---|
| The CPU utilization of the client device connected to the session | ||
| EUC client's inactive time while the client device is connected to the session | ||
| Time on the remote client of the VM | ||
| The geographical location of the client device connected to the session based on the public IP | Client devices need to access https://fabric.controlup.com | |
| The NIC name of the client device connected to the session | ||
| The NIC speed of the client device connected to the session | ||
| NIC type of the client device connected to the session | ||
| The OS type of the client device connected to the session | ||
| The OS Version of the client device connected to the session | ||
| Percentage of network packet loss on the client device connected to the session | ||
| The public IP Address of the client device connected to the session | ||
| Latency between the client device connected to the session and the internet latency target. | The default latency target for all operating systems is 8.8.8.8. When installing the Windows plugin, you can set a custom latency target. | |
| Latency between the client device connected to the session and closest ISP router | Client devices need to access https://fabric.controlup.com | |
| ISP Name | Client devices need to access https://fabric.controlup.com | |
| Latency between the client device connected to the session and the local router | ||
| Client device's local router IP while connected to the session | ||
| The Remote DX client version installed on the client device connected to the session | ||
| Total session latency from the client device calculated from the second callback | ||
| Authentication type used to connect to the wireless network by the client device connected to the session | ||
| MAC address of the access point to which the client device is currently connected | ||
| Access point channel of the client device connected to the session | ||
| Radio protocol/type of the wireless network used by the client device connected to the session | ||
| WiFi signal strength of the client device connected to the session measured in dBm displayed in percentage | ||
| Name of the connected wireless network used by the client device connected to the session |
Client Device Score
The Client Device Score metric is displayed with a colored 
icon:
Client Device Score indicates the connectivity performance of a device, displaying the lowest value among the following metrics:
- Client WiFi Signal
- LAN Latency
- Total Session Latency
- Internet Latency
- Client CPU
- ISP Latency
Was this article helpful?