Understanding Proxy Handling for ControlUp Remote Control Traffic in VDI Environments
In a Virtual Desktop Infrastructure (VDI) environment configured to route internet traffic through a proxy server, an issue was encountered with the ControlUp "Remote Control" feature accessed via the ControlUp Web Console. While most internet traffic correctly utilized the proxy, traffic related to Remote Control was observed to bypass the proxy and instead hit the firewall directly. This discrepancy prompted investigation into whether this behavior was expected or a misconfiguration.
The root cause lies in the distinction between different components of the ControlUp system and how they handle proxy settings. The proxy configuration set within the ControlUp Real-Time (RT) Console and monitors applies primarily to console and monitoring traffic. However, Remote Control traffic originates from the ControlUp agent installed on the managed machines (VDI endpoints). The agent does not use the proxy configuration specified in the RT Console; instead, it relies on the proxy settings configured locally on the endpoint machine itself.
Therefore, it is expected behavior that Remote Control traffic does not traverse the proxy configured in the RT Console but uses the machine’s proxy settings. If Remote Control traffic is bypassing the proxy and hitting the firewall directly, it may indicate that the local proxy settings on the VDI endpoints are not properly configured or are absent. Ensuring that the VDI machines have correct proxy configurations consistent with the environment’s proxy policies will enable Remote Control traffic to route properly.
For definitive guidance or if further troubleshooting is necessary, it is advisable to contact ControlUp support by opening a support ticket. More detailed reference on Remote Control in ControlUp VDI or DaaS environments can be found in the official ControlUp documentation at https://support.controlup.com/docs/remote-control-your-vdi-daas-devices. Read the entire article here...


