From the desktop menu, click System Setup, and then click Remote Connections.
The Remote Connections dialog box
is displayed.
In the Broker Setup tab, from the drop-down list, select VMware view, and do the following:
Broker Server—Enter the IP address/Hostname/FQDN of the Broker
Server.
Auto Connect List—Enter 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 mode—Select the preferred security mode
from the following options:
Warning—Warn Security requires FQDN address with self-signed
certificate, or without any certificate, but corresponding warning
message is displayed for user to continue.
Full—Full Security requires FQDN address with domain certificate.
Connection Protocol—From 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. PCoIP protocol is required for PCoIP session. Horizon package is required for Blast session.
The available options are:
Server
default—Select 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 Supported—Select 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 only—Select this protocol connection to display the desktop in RDP connection only. 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.
PCoIP only—This option is available only for PCoIP enabled
clients. Select this protocol connection to display only the desktop
in the PCoIP connection, for each pool in the broker. If a desktop pool
is configured with default protocol as RDP 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.
Blast only—VMware Blast display protocol can be used for remote
applications and for remote desktops that use virtual machines or
shared-session desktops on an RDS host. Select this protocol connection
to display the desktop with the Blast protocol.
Blast and RDP—This option is available on both PCoIP enabled
clients and non-PCoIP clients. Select this protocol connection to display the desktop in either Blast or RDP connections.
Blast and PCoIP—This option is available only for PCoIP enabled
clients. Select this protocol connection to display the desktop in either Blast or PCoIP connections.
PCoIP and RDP—This option is available only for PCoIP enabled
clients. Select this protocol connection to display the desktop in either PCoIP or RDP connections.
Log in anonymously using Unauthenticated Access—Select this check box to anonymously log in to the VMware session with application remoting.
Click OK to save the settings.
Limitations
Video performance is low when you play a video in Blast session with 4K resolution.
ThinOS supports audio device USB redirection. However, Dell does not recommend using audio device USB direction due to low audio quality.
The text copy and paste functionality between local and Blast sessions works only after you perform a session switch.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\