WHITE PAPER / 3
Configuring Kiosk Mode
Introduction
Many organizations provide interactive customer kiosks in public places where users can perform specific
tasks without having to log in. VMware Horizon® with View supports this “anonymous use” functionality with
View kiosk mode. Endpoint devices configured as kiosk clients display View virtual desktops and allow users to
perform a limited set of functions specified by the Horizon administrator.
How Kiosk Mode Works
Kiosk mode associates a View virtual desktop with the MAC address or client ID of a kiosk endpoint device
rather than with a user’s login credentials. The endpoint device can be a zero client, a thin client, or a locked-
down PC running either Windows or Linux.
When a kiosk user activates an input device—for instance, by pressing a key or clicking a mouse button—the
kiosk client contacts a View Connection Server. The View Connection Server authenticates the client, connects
it to a View virtual machine running in kiosk mode, and launches a remote desktop session. The session is then
displayed on the endpoint device.
The kiosk user is normally presented with a session that displays either a View desktop with a limited set
of applications or a single, dedicated application that appears to be running on the kiosk endpoint. The
infrastructure is user-transparent.
With View kiosk mode
•Users do not have access to the operating system or file system of the View desktop.
•No user authentication is required.
•No user data is preserved.
•There is no need for persistent virtual desktops.
These considerations mean that kiosk functionality can be provided at low cost, with inexpensive endpoints,
non-persistent virtual desktops, and no additional storage. Very little is required of IT resources beyond initial
setup and provisioning.
Authentication
Using MAC addresses or client IDs to associate View virtual desktops with kiosk
devices
rather than with
users
simplifies the authentication model.
Although kiosk users might be required to provide authentication information for certain applications, they
do not ordinarily log in to the View desktop. In most cases, they simply use the session or application that is
presented to them.
In some circumstances, however, an administrator might require all kiosk users to log in to the View desktop
with the same, predetermined username and password. This scenario can be desirable when use of the kiosk
or an application is restricted to a known set of users, such as company employees or registered students, but
is not available to the general public. In this case, people who know the password can use the kiosk, but these
users are not identified by personal credentials.
Because kiosks are usually placed in public locations, kiosk mode is not recommended for transactions that
require transfer of sensitive information, such as credit card numbers, user email addresses and passwords, or
patient records.
For general information on View security, including comments about kiosk mode, see the VMware Horizon with
View Security Hardening Overview.
(258 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji