Dell ThinOS 2211, 2208, and 2205 Administrator’s Guide

Configure the proxy settings

1. From the desktop menu, click System Setup > Network setup.
   The Network setup dialog box is displayed.

   Table 1. Supported protocolsSupported protocols

   Component	Supported protocols	Additional information
   Wyse Management Suite	HTTPS, and SOCKS5	N/A
   Citrix RealTime Media Engine (RTME)	HTTP	N/A
   Azure Virtual Desktop (AVD)	HTTP	N/A
   Horizon	HTTP	N/A

2. Click the Proxy tab, and configure the following options:
   • Proxy Types—You can use HTTP proxy, HTTPS proxy and SOCKS5 proxy types. The proxy type enables the thin client to connect to the application such as Wyse Management Suite.
   • Proxy values—You can enter values for the HTTP proxy, HTTPS proxy and SOCKS5 proxy types. Adding proxy values enable the thin client to connect to the proxy server.
   A new app list value HORIZON is added. For the VMware Broker agent logon to use the proxy, you should specify the Apply proxy server on field as HORIZON. Unauthenticated proxy is accepted when using HORIZON. Username and password are ignored.

   A new proxy app list value called MTOP is added for Microsoft Teams in an ICA session.

   

   Use the following guidelines:
   1. Configure the proxy servers based on your requirement.
      • Enter the HTTP proxy port number or HTTPS proxy port number, username, and password in the respective fields. However, credential pass through ($UN/$PW) is not recommended because it starts before user sign on.

        Wyse Management Suite uses both HTTP/HTTPS and MQTT protocols to communicate with the WMS/MQTT server. However, the HTTP proxy cannot redirect TCP packages to the MQTT server which requires a SOCKS5 proxy server. If there is only the HTTP server available, the real-time command that requires MQTT does not work.

        NOTE:The HTTP/HTTPS proxy default port is 8080.
      • Enter the SOCKS5 proxy port number, username, and password in the respective fields. If SOCKS5 proxy is configured, Wyse Management Suite proxy uses the SOCKS5 only. If SOCKS5 is not configured, then Wyse Management Suite proxy searches for alternative protocols, for example, HTTP in the configuration.
        NOTE:The SOCKS5 proxy default port is 1080.
      • Select the Use the first proxy server for all protocols check box to enable all the protocols to use the same server in the HTTP Proxy fields. Both HTTP and HTTPS proxy use the same host and port, and SOCKS5 proxy agent uses HTTP host with default Socks5 port (1080).
   2. Specify the supported applications as Wyse Management Suite, Azure Virtual Desktop (AVD), and RTME separated by a semicolon in the Apply proxy server on field.
3. Click OK to save your settings.
   ThinOS supports the usage of DHCP option tag 252. This option enables the device to fetch the proxy information from the DHCP server when the device is reset to factory default settings or when you restart the thin client. For example, http://x.x.x.x/proxy.pac. The proxy settings from DHCP option 252 are not displayed on the ThinOS GUI.

   Proxy is enabled only for configured applications regardless of the availability of DHCP option 252. If you configure an empty value on the ThinOS local user interface, proxy is enabled for all supported applications by default. If you configure an empty value in the Wyse Management Suite policy settings or the Admin Policy Tool, proxy is not enabled for any applications. If DHCP option 252 is available and is supported by the configured application, WPAD (DHCP 252) takes priority. If DHCP 252 is available, WMS is enabled to go through proxy even if it is not configured in the Proxy Application List configuration.

   Table 2. VDI logon or session launch that goes through proxyVDI logon or session launch that goes through proxy

   Component	Features	PAC proxy	GUI proxy
   Citrix	http broker log in	No	No
   	http broker session launch	No	No
   	https broker log in	Yes	Yes (RTME value added in the Apply proxy server on application list field)
   	https broker session launch	Yes	Yes (RTME value added in the Apply proxy server on application list field)
   VMware	broker log in	Yes	Yes (HORIZON value added in the Apply proxy server on application list field)
   	session launch	Yes	Yes (HORIZON value added in the Apply proxy server on application list field)
   Azure Virtual Desktop	broker log in	Yes	Yes (AVD value added in the Apply proxy server on application list field)
   	session launch	No	No
   Microsoft Remote Desktop Services	broker log in	No	No
   	session launch	No	No
   Amazon WorkSpaces	broker log in	No	No
   	session launch	No	No
   Teradici Cloud	broker log in	No	No
   	session launch	No	No
   Wyse Management Suite	Wyse Management Suite connection	Yes	Yes (WMS value added in the Apply proxy server on application list field)