Administrator Guide

Table Of Contents
f. In some scenario the video shows no content initially; when user resizes browser the video appears normally; it is likely to
happen with x86 desktops and is a known issue for Citrix HDX FR Linux client.
g. Playback with videos that can work with HDX FR on Linux or Windows client: There are a number of videos/websites
known as not working with Citrix HDX FR solution such as msn.com, espn.com, movies.yahoo.com, and dell.com. Flash
videos simply cannot load with these websites using HDX FR solution. Some of them are working periodically; for
example, videos on dell.com were working well during this Feb/March but stopped working afterwards; the results can
vary depending on user location as well (US/Europe/Asia). It is therefore recommended to make sure the target videos
work with HDX FR on Linux or Windows, before working with it on ThinOS.
h. The solution on ThinOS is based on Citrix HDX FR Linux version. It is advised to compare with Linux client in case of any
issues.
i. Playback YouTube.com videos may run into some issues; for example, cannot show video unless user copy the URL and
paste it to the browser to visit again. In case any observation we recommend to compare with Linux client.
Configuring VMware
VMware virtualization allows you to run multiple virtual machines on a single physical machine. VMware Horizon Client is a locally
installed software application that communicates between View Connection Server and thin client operating system. It provides
access to centrally hosted virtual desktops from your thin clients.
This section provides information about how to configure a VMware broker connection on your ThinOS device, and other
VMware features that you can configure on ThinOS.
Configuring the VMware broker connection
To configure the VMware broker setup:
1. From the desktop menu, click System Setup, and then click Remote Connections.
The Remote Connections dialog box is displayed.
2. In the Broker Setup tab, from the drop-down list, select VMware view, and do the following:
Broker ServerEnter the IP address/Hostname/FQDN of the Broker Server.
Auto Connect ListEnter the name of the desktops that you want to launch automatically after logging in to the
respective broker. More than one desktop can be entered. Each desktop name is separated by semicolon, and is
case-sensitive.
Security modeSelect the preferred Security mode from the following options:
WarningWarn Security requires FQDN address with self-signed certificate, or without any certificate, but
corresponding warning message is displayed for user to continue.
FullFull Security requires FQDN address with domain certificate.
LowSecurity allows FQDN/IP address with/without certificate.
DefaultFollows global security mode settings.
Connection ProtocolFrom the drop-down list, select the type of protocol connection. By default, the option is set to
Server Default.
NOTE:
The PCoIP only connection protocol is applicable only to PCoIP clients. If you do not install Horizon
package, then the Blast only protocol option is not available for selection. The connection protocols are not
available for non-PCoIP clients without the Horizon package.
The available options are:
Server defaultSelect this protocol connection to display the desktop with default protocol as configured in the
VMware View Admin console, for each pool in the broker. If a desktop pool is configured with default protocol as RDP
in the View Admin console, then only the RDP connection of the desktop is displayed in ThinOS after users sign in to
the device.
All SupportedSelect this protocol connection to display the desktop in all the available connections, when a
desktop pool is configured to allow users to select protocol as yes. If a desktop is configured with default protocol as
PCoIP and allow user to select protocol as no, then ThinOS only displays the desktop in the PCoIP connection.
RDP onlySelect this protocol connection to display only the desktop in RDP connection. If a desktop pool is
configured with default protocol as PCoIP in the View Admin console, and allow user to select protocol as no, then
this desktop is not displayed in ThinOS after user signs in to the device.
Configuring the connection brokers
89