IGEL Linux v4 Universal Desktop User Guide

PDF

سند

تبلیغات

Universal Desktop Linux v4
User Guide
IGEL Technology GmbH
Universal Desktop Linux v4
25.02.2015
Contents
1.
2.
3.
IGEL Universal Desktop Firmware ......................................................................................................................8
Quick Installation ...............................................................................................................................................9
Boot Procedure ................................................................................................................................................10
3.1.
3.2.
3.3.
4.
Application Launcher .......................................................................................................................................12
4.1.
4.2.
4.3.
4.4.
4.5.
5.
Time and Date ..............................................................................................................................20
Update..........................................................................................................................................21
Buddy Update ..............................................................................................................................22
Remote Management ..................................................................................................................22
VNC (Shadowing) .........................................................................................................................22
Remote Access (SSH / RSH) ..........................................................................................................27
Energy ..........................................................................................................................................27
Firmware Customization ..............................................................................................................28
IGEL System Registry ....................................................................................................................28
User Interface ..................................................................................................................................................29
7.1.
7.2.
7.3.
7.4.
7.5.
8.
Starting the Setup ........................................................................................................................16
Completing the Setup ..................................................................................................................16
Setup Areas ..................................................................................................................................17
Setup Search ................................................................................................................................18
System Settings ..............................................................................................................................................20
6.1.
6.2.
6.3.
6.4.
6.5.
6.6.
6.7.
6.8.
6.9.
7.
General System Information ........................................................................................................13
Sessions ........................................................................................................................................13
System Tools ................................................................................................................................14
License..........................................................................................................................................15
Shutdown and Restart .................................................................................................................15
Setup Application ............................................................................................................................................16
5.1.
5.2.
5.3.
5.4.
6.
Boot Menu ...................................................................................................................................10
Network Integration ....................................................................................................................11
X-Server ........................................................................................................................................11
Language ......................................................................................................................................29
Bildschirm.....................................................................................................................................29
Input .............................................................................................................................................37
Keyboard Commands - Hotkeys ...................................................................................................40
Font Services ................................................................................................................................40
Network ..........................................................................................................................................................42
8.1.
8.2.
8.3.
8.4.
8.5.
LAN Interfaces ..............................................................................................................................43
Authentication .............................................................................................................................44
Wireless (Wi-Fi) Connections .......................................................................................................45
Dial-up connections - ADSL ..........................................................................................................47
Virtual Private Network - VPN .....................................................................................................47
2
IGEL Technology GmbH
Universal Desktop Linux v4
8.6.
8.7.
8.8.
8.9.
9.
Sessions..........................................................................................................................................................55
9.1.
9.2.
9.3.
9.4.
9.5.
9.6.
9.7.
9.8.
9.9.
9.10.
9.11.
9.12.
9.13.
9.14.
9.15.
9.16.
9.17.
9.18.
9.19.
9.20.
9.21.
9.22.
9.23.
10.
Citrix ICA - global settings ............................................................................................................55
Citrix ICA - Sessions ......................................................................................................................64
Citrix StoreFront / Web Interface ................................................................................................67
Citrix Access Gateway ..................................................................................................................70
RDP - global settings ....................................................................................................................70
RDP session ..................................................................................................................................76
VMware Horizon Client ................................................................................................................78
Quest vWorkspace Client and AppPortal.....................................................................................78
Leostream Connection Broker .....................................................................................................79
Appliance Mode ...........................................................................................................................80
NoMachine NX .............................................................................................................................80
SSH Session ..................................................................................................................................81
VNC Viewer ..................................................................................................................................81
IBM iSeries Access ........................................................................................................................82
ThinLinc ........................................................................................................................................82
PowerTerm WebConnect .............................................................................................................82
PowerTerm terminal emulation...................................................................................................83
X Session ......................................................................................................................................83
Firefox Browser ............................................................................................................................84
SAP Client .....................................................................................................................................85
Media Player ................................................................................................................................85
Java Web Start Session ................................................................................................................87
VoIP Client ....................................................................................................................................87
Accessories .....................................................................................................................................................88
10.1.
10.2.
10.3.
10.4.
10.5.
10.6.
10.7.
11.
Simple Certificate Enrollment Protocol - SCEP ............................................................................50
Routing .........................................................................................................................................52
Hosts ............................................................................................................................................52
Network Drives ............................................................................................................................53
Local Terminal ..............................................................................................................................88
Card reader ..................................................................................................................................88
Setup Session ...............................................................................................................................88
Application Launcher ...................................................................................................................88
Sound Mixer .................................................................................................................................89
Java Control Panel ........................................................................................................................89
Network Diagnostics ....................................................................................................................90
Devices ...........................................................................................................................................................92
11.1. Printers .........................................................................................................................................92
11.2. USB Storage Devices ....................................................................................................................95
11.3. PC/SC Interface ............................................................................................................................96
12.
Security ...........................................................................................................................................................97
12.1. Password ......................................................................................................................................97
12.2. Login Options ...............................................................................................................................97
12.3. AD/Kerberos Configuration..........................................................................................................98
3
IGEL Technology GmbH
Universal Desktop Linux v4
13.
IGEL Smartcard .............................................................................................................................................100
13.1.
13.2.
13.3.
13.4.
14.
Firmware Customization ................................................................................................................................103
14.1.
14.2.
14.3.
14.4.
14.5.
14.6.
15.
16.
17.
18.
Company Key .............................................................................................................................101
Save User and Password ............................................................................................................101
Save Sessions .............................................................................................................................102
Test Smartcard ...........................................................................................................................102
Custom partition ........................................................................................................................103
Custom Application ....................................................................................................................107
Custom Commands ....................................................................................................................107
Custom Bootsplash ....................................................................................................................109
Environment Variables ...............................................................................................................109
Features .....................................................................................................................................110
IGEL Support .................................................................................................................................................111
Maximum supported screen resolutions ........................................................................................................112
Supported formats and codecs ......................................................................................................................113
Index .............................................................................................................................................................114
4
IGEL Technology GmbH
Universal Desktop Linux v4
About this Manual
All illustrations and descriptions in this manual relate to Version 4.14.100 of the IGEL Linux firmware.
This manual is divided into the following sections:
Introduction (page 7)
General information about the product
Quick installation (page 9)
Setting up the thin client for the first time
Boot procedure (page 10)
Boot menu, network integration, X-Server
Application Launcher (page
12)
Important system data such as the firmware version, list of
applications, licensed services, system tools
Setup application (page 16)
Setting up sessions and system configuration
System settings (page 20)
System setting options
User interface (page 29)
Language, screen, entry options, font services
Network (page 42)
Interfaces, protocols, authentication, drives
Sessions (page 55)
Creating and configuring application sessions
Accessories (page 88)
Session accessories, card readers, sound control, Java Manager,
network diagnostics
Devices (page 92)
Hardware, printers, storage devices, interfaces
Security (page 97)
Password, logging on, AD/Kerberos configuration
IGEL smartcard (page 100)
Company keys, saving a user/password/session, testing a card
Firmware configuration
(page 103)
Customer-specific partition, applications, commands, start screen,
environment variables, features
5
IGEL Technology GmbH
Universal Desktop Linux v4
Formatting and meanings
The following formatting is used in the document:
Hyperlink
Internal or external links
Proper names
Proper names of products, firms etc.
GUI text
Items of text from the user interface
Menu→Path
(Context) menu paths in systems and programs
Entry
Program code or system entries
Keyboard
Commands that are entered using the keyboard
Note regarding operation
Warning: Important note which must be observed
Examples and screenshots
The examples and screenshots featured in this document are mainly produced from the example database
which is available on the IGEL download server www.myigel.biz as a backup.
Warning: To avoid inadvertently assigning example profiles, please do not use the IGEL example database
on your actual system!
6
IGEL Technology GmbH
Universal Desktop Linux v4
Introduction
IGEL Thin Clients comprise the very latest hardware and an embedded operating system. Depending on the
product concerned, this operating system may be based on IGEL Linux or Microsoft Windows Embedded
Standard&reg;. We have done our utmost to provide you with an excellent overall solution and promise to
provide the very same level of quality service and support.
7
IGEL Technology GmbH
Universal Desktop Linux v4
1.
IGEL Universal Desktop Firmware
IGEL Thin Clients comprise the very latest hardware and an embedded operating system. Depending on the
product concerned, this operating system may be based on IGEL Linux or Microsoft Windows Embedded
Standard&reg;. We have done our utmost to provide you with an excellent overall solution and promise to
provide the very same level of quality service and support.
The firmware included with every IGEL Universal Desktop product is multi-functional and contains a wide
range of protocols allowing access to server-based services. The IGEL Universal Desktop Firmware is
available with two possible operating systems and with the following options:
Operating system
Options
Windows Embedded Standard 7
•
Ericom PowerTerm
Terminalemulation
•
•
IGEL Shared Workplace
IGEL Universal
MultiDisplay (LX only)
Codec package (LX only)
IGEL Linux
•
The structure of the IGEL setup is almost identical on all thin clients and in the Universal Management
Suite (UMS) management software. This means that the configuration parameters in the local device setup
can be found in the same location in the tree structure as a profile used in the management software for
example.
The IGEL Universal Management Suite is available to all customers on the IGEL download site. It allows
management of an unlimited number of IGEL thin clients.
8
IGEL Technology GmbH
Universal Desktop Linux v4
2.
Quick Installation
If you follow the procedure below, you can install the thin client within your network environment in just a
few minutes:
1. Connect the thin client to a monitor (VGA, DVI, DisplayPort), an AT-compatible keyboard with a PS/2 or
USB connection, a USB mouse and the LAN using an RJ45 connector.
2. Connect the thin client to the power supply.
3. Start the thin client and wait until the graphical user interface has loaded.
4. Click on the Setup symbol in the taskbar, or launch the IGEL Setup using the key combination Ctrl + Alt + s .
5. Select the system language and keyboard layout under User Interface→Language.
6. Select the display resolution under User Interface→Display.
7. Enter a local IP address in the Network section of the setup
or retain the default DHCP mode for automatic network configuration.
8. Click on OK to save and apply your changes.
The device will now restart if necessary and will use the new settings thereafter.
A handy tool tip is available for virtually every setting. If you would like to know more about a setting or
option, move your mouse pointer over it and wait for a moment. You can configure the tool tips under
User Interface→Screen→Desktop.
9
IGEL Technology GmbH
Universal Desktop Linux v4
3.
Boot Procedure
The quick installation procedure is complete.
 Restart the system in order to start the boot procedure.
3.1. Boot Menu
 During the boot procedure, press the ESC key in the Secondstage Loader when the Loading Kernel
message is shown on the screen.
A menu with four boot options as well as an option for resetting the thin client to the default factory
settings will appear:
Quiet Boot (page 10)
Normal boot
Verbose Boot (page 10)
Boot with system messages
Emergency Boot (page 10)
Setup only
Failsafe Boot (page 11)
With CRC check
Reset to Factory Defaults (page
11)
Resets the thin client to the default
factory settings
3.1.1.
Quiet Boot
Quiet Boot is the default boot mode. In this mode, all kernel messages are disabled and the graphical user
interface is started.
3.1.2.
Verbose Boot
Unlike in Quiet Boot mode, the boot messages are shown in Verbose Boot mode. A diagnostics shell is also
available. This can be used to execute common commands (such as ifconfig etc.) when searching for and
rectifying faults.
 Enter init 3 to close this shell.
The boot procedure will then resume.
3.1.3.
Emergency Boot
Emergency Boot is a setup with default parameters.
If you select Emergency Boot, the Secondstage Loader looks for a bootable system in the flash memory and
then resumes the boot procedure as in the other boot modes.
10
IGEL Technology GmbH
Universal Desktop Linux v4
Essentially speaking, the X-Server is started without network drivers and with a resolution of 1024 x 768 60 Hz during an Emergency Boot. The Setup menu is then opened directly.
This option is useful if, for example, you have selected an excessively high screen resolution or a wrong
mouse type and these settings can no longer be changed in the normal setup.
3.1.4.
Failsafe Boot - CRC check
During a Failsafe Boot, a check of the file system is carried out first. The thin client then starts in Verbose
Mode.
3.1.5.
Reset to Factory Defaults
If you select Reset to Factory Defaults, all personal settings on the thin client (including your password and
the sessions you have configured) will be lost.
A warning message will appear on the screen before the procedure is carried out.
 You must then confirm your decision.
If the device is protected by an administrator password, you will be prompted to enter this password. You
have three attempts to do so.
Do you not know the password?
1. When you are prompted to enter the password, press the Enter key three times.
2. Press c to bring up the Terminal Key, the individual key for the thin client.
3. Contact us using an RMA form:
https://www.igel.com/en/service-support/rma-request.html
(https://www.igel.com/en/service-support/rma-request.html)
4. Enter the Terminal Key shown, the firmware version and your contact details.
Our service department will send you a so-called Reset to Factory Defaults Key specially for your device.
To ensure that the process is as straightforward and yet as secure as possible, each key is valid for just one
device.
3.2. Network Integration
Is the kernel loaded?
If it is, the next step is the network configuration.
There are three possible ways of integrating the terminal into the network environment. Depending on the
terminal's settings, you can choose between DHCP, BOOTP or a manually configured IP address.
3.3. X-Server
The final step in the boot procedure involves starting the X-Server and the local window manager.
11
IGEL Technology GmbH
Universal Desktop Linux v4
4.
Application Launcher
 To launch the tool, click on the Application Launcher symbol in the quick launch bar or in the Start
menu.
The various Launcher sub-areas allow access to configured sessions/system programs or show information
relating to licenses, the system and network connections.
Abbildung 1: Application Launcher
Because the setup program is the central configuration tool for all thin client settings, a setup session is
already pre-defined under Sessions and System.
Sessions (page 55)
System (page 14)
License (page 15)
Network information
Shutting down and restarting a device (page 15)
12
IGEL Technology GmbH
Universal Desktop Linux v4
4.1. General System Information
Within the Application Launcher you will find the Information page with important system data such as the
firmware version, licensed services and hardware specifications.
Abbildung 2: System Information
Details of the current network configuration with the IP address and device name are also given here.
4.2. Sessions
All sessions created are shown in a list of applications if they are enabled for the main session page.
 To open an application, double-click on it or click on Run.
 Alternatively, you can launch sessions via icons on the desktop, in the quick launch bar or from the Start
menu and context menu.
 Applications can also be launched automatically and a key combination (hotkey) can be defined.
The available options for launching a session can be defined under Desktop Integration in the session
configuration.
13
IGEL Technology GmbH
Universal Desktop Linux v4
4.3. System Tools
On the System page, you can run various tools including the firmware updating tool with the pre-set
update information.
Abbildung 3: System Information
The following tools are available:
Firmware Update
Carries out the update with the settings made during the setup.
Identify Monitors
Shows the screen's number and manufacturer details.
Network Tools
Provides detailed information on the network connection and offers a number
of problem analysis tools such as Ping or Traceroute.
Smart Card Personalization
Allows access data and sessions which are to be available to a smartcard user
to be written to an IGEL smartcard.
Touchscreen Calibration
Allows a connected touchscreen monitor to be calibrated.
UMS registering
Logs the thin client on to a UMS server (access data for the server are
required).
Upgrade Feature Set
Upgrades and imports the feature set on the device.
14
IGEL Technology GmbH
Universal Desktop Linux v4
4.4. License
You will find the following here:
•
•
The licenses for the components used in the UD system
Information on the provision of source code, e.g. under GPL
4.5. Shutdown and Restart
Within the Application Launcher you will find two buttons for starting or shutting down the device. Both
actions can be disabled for the user and will then be available to the administrator only.
You can change the standard action when shutting down the device using the button on the screen or the
on/off button on the device itself in the setup under System→Energy→Shut Down.
15
IGEL Technology GmbH
Universal Desktop Linux v4
5.
Setup Application
With the help of the setup, you can change the system configuration and session settings.
Any changes you have made in the UMS take precedence and may no longer be able to be changed. A lock
symbol before a setting indicates that it cannot be changed.
Starting the setup (page 16)
Completing the setup (page 16)
Setup areas (page 16)
Setup search (page 18)
5.1. Starting the Setup
You can open the setup in the following ways:
 Double-click on Setup in the Application Launcher
or click on Run.
 Double-click on Setup on the desktop (if available based on the settings).
 Select Setup in the context menu on the desktop (if available based on the settings).
 Select System→Setup in the Start menu.
 Click on Setup in the quick launch bar.
 Launch the setup using the keyboard command Ctrl + Alt + s , or
in the Appliance mode using Ctrl + Alt + F2 .
You can configure how the setup can be launched under Accessories. The options described above as well
as combinations thereof are available.
5.2. Completing the Setup
The buttons OK, Cancel and Apply are usually available on every individual setup page.
 Click on Apply if you have finished configuring a setup area and would like to save your settings without
closing the setup program.
 Click on Cancel if you have not made any changes and would like to abort the setup.
 Click on OK to save your changes and exit the setup.
16
IGEL Technology GmbH
Universal Desktop Linux v4
5.3. Setup Areas
The setup is divided into following areas:
1. navigation bar with breadcrumb navigation
2. main area with structure tree
3. icons for possible settings depending on the selected topic
4. content area
5. quick link bar
Abbildung 4: Setup Areas
The quick link bar has been added with IGEL setup version 4.14.100. Use these direct links to jump to
related setup pages for further configurations.
17
IGEL Technology GmbH
Universal Desktop Linux v4
The setup application comprises the following main areas:
Abbildung 5: Setup areas
Sessions
Allows you to configure application sessions such as ICA, RDP, PowerTerm,
browser and others
Accessories
Allows you to configure various local tools - setup pages for the local shell
(Terminal), sound mixer, screen keyboard (for touchscreen monitors), options for
the Application Launcher and the setup application itself.
User interface
Allows you to configure display settings, entry devices, hotkey commands etc.
Network
Allows you to configure all network settings for LAN/WLAN interfaces and the
dial-up connections
Devices
Allows you to configure various devices
Security
Allows you to set the administrator/user passwords and user authorizations etc.
System
Allows you to set various basic system parameters including the date and time,
information regarding the firmware update, remote management etc.
 Click on one of the areas to open up the relevant sub-structure.
The tree structure allows you to switch between the setup options.
Three navigation buttons are available. The buttons allow you to move back and forth between the setup
pages you have visited or reach the next level up within the structure.
You will find a more detailed description of the individual setup options elsewhere. This is merely a brief
overview.
5.4. Setup Search
The Search function enables you to find parameter fields or values within the setup.
1. To start a search, click on the button below the tree structure.
2. Enter the text you wish to search for.
18
IGEL Technology GmbH
Universal Desktop Linux v4
3. Specify the details for your search – narrow it down to field headers for example.
4. Select one of the hits.
5. Click on Show Result and you will be taken to the relevant setup page.
The parameter or value found will be highlighted as shown below.
Abbildung 6: Setup search
19
IGEL Technology GmbH
Universal Desktop Linux v4
6.
System Settings
As previously explained under Quick installation (page 9), various basic system settings can be configured in
the sub-structure.
Date and time (page 20)
Update (page 21)
Remote management (page 22)
VNC (mirroring) (page 22)
Remote access (SSH / RSH) (page 27)
Energy (page 27)
Firmware configuration (page 28)
IGEL System Registry (page 28)
6.1. Time and Date
1. Go to System→Time and Date
Abbildung 7: Set time and date
2. Maintain your changes.
3. Click Set time and date to save your settings.
You can use a time server within your network (via Network Time Protocol (NTP)) to set time and date
automatically during system boot and with periodic update.
Make sure the time zone is configured correctly. Choose the region from the drop-down-menus .
20
IGEL Technology GmbH
Universal Desktop Linux v4
Note: If choosing General as Time Zone Area you have to set your GMT time zone (Location) following the
POSIX standard (as usual in Linux) - which means you have to invert the offset of your common UTC time
zone! (See tool tip for Location as well.) Therefore it is preferable to set the system's time zone by
choosing the corresponding area and location instead of defining the GMT offset.
Example for America/New York: In POSIX standard GMT+5 is
the time zone 5 hours west of Greenwich and corresponds to
UTC-5.
6.2. Update
On the Update page, a simple dialog for updating your thin client firmware is displayed. The normal
procedure for updating your thin client is as follows:
1. Go to www.myigel.biz and download the desired firmware image from the IGEL server.
2. Unzip the ZIP file (the usual format in which updates are provided).
3. Save all files in the directory provided either on your local FTP/HTTP server or on a drive which is
accessible from the client (e.g. a USB stick, NFS share etc.).
4. Configure the necessary settings (see below).
5. Save your changes and click on Update Firmware.
The update process will now proceed automatically.
The update procedure cannot be carried out via PPP/ISDN connections. In this case, you should use a local
storage medium (USB stick) to provide the update.
The following information must be given before the update can start (the details required vary depending
on the protocol chosen):
Protocol
Allows you to select the protocol to be used (FTP, HTTP, HTTPS etc.) from the
drop-down list.
Server name and port
Details of the name or IP address of the server used as well as the port that is
to be used
Path name on the server
Details of the directory in which you have saved the update files - starting from
the root directory
User name
The user account name
Password
The password for this user/this account
21
IGEL Technology GmbH
Universal Desktop Linux v4
6.3. Buddy Update
Under Buddy Update, you can specify your thin client as an update server for other IGEL thin clients. If you
use a thin client as an update server, only the FTP protocol can be used to update the firmware. A number
of thin clients can be set up as buddy update servers within the network.
Thin clients without a specified update server search for available servers during the update. The first
update server found then provides the update.
6.4. Remote Management
If the thin client is registered by an IGEL UMS server, the server address and the port number will be shown
under Remote Management.
You can also register to a UMS Server directly:
1. Open the Application Launcher.
2. Start the application System &gt; UMS Registering.
3. Enter the UMS Server's Address and User Credentials.
If a valid entry exists in DNS for the UMS Server you can keep the default value igelrmserver for
the server's address.
4. Optional: Choose a target Directory on the server.
5. Optional: Define a Structure Tag to register the thin client according to the UMS default directory rules.
Structure Tags can also be deployed to thin clients via DHCP option 226 to support the automatic
registration and sorting in the UMS database. A Structure Tag received via DHCP overrides a manually
configured tag when the client gets registered to the UMS.
6. Click Register.
6.5. VNC (Shadowing)
For helpdesk purposes, you can observe the client through shadowing. This is possible via the IGEL Remote
Manager or another VNC client (e.g. TightVNC) . The options for the VNC functions are as follows:
Ask user for permission
In a number of countries, unannounced mirroring is prohibited by law.
Do not disable this option if you are in one of these countries!
Allow entries from remote
computer
If this option is enabled, the remote user may make keyboard and
mouse entries as if they were the local user.
Use password
Enable this option to set up a password which the remote user must
enter before they can begin mirroring.
22
IGEL Technology GmbH
Universal Desktop Linux v4
6.5.1.
Secure shadowing (VNC with SSL)
The Secure Shadowing function improves security when remote maintaining a thin client via VNC at a
number of locations:
•
Encryption: The connection between the shadowing computer and the shadowed thin client is
encrypted.
This is independent of the VNC viewer used.
•
Integrity: Only thin clients with a valid UMS server certificate can be shadowed.
Only thin clients in the UMS database can be shadowed.
•
Authorization: Only authorized persons (UMS administrators with adequate authorizations) can
shadow thin clients.
Direct shadowing without logging on to the UMS is not possible.
•
Limiting: Only the VNC viewer program configured in the UMS (internal or external VNC viewer) can be
used for shadowing.
Direct shadowing of a thin client by another thin client is likewise not permitted.
•
Logging: Connections established via secure shadowing are recorded in the UMS server log.
In addition to the connection data, the associated user data (shadowing UMS administrator) can be
recorded in the log too.
Of course, this is only relevant to thin clients which meet the requirements for secure shadowing and have
enabled the corresponding option. Other thin clients can be &quot;freely&quot; shadowed in the familiar manner
and, if necessary, secured by requesting a password.
Basic principles and requirements
The Secure Shadowing option can be enabled with the following components:
•
IGEL Universal Desktop Linux from version 5.03.190 onwards
or IGEL Universal Desktop OS 2 from version 5.03.190 onwards
or IGEL Universal Desktop OS from version 4.14.100
or IGEL Universal Desktop Windows Embedded Standard 7 from version 3.09.100 onwards.
•
•
•
IGEL Universal Management Suite from Version 4.07.100 onwards
Thin client is registered on the UMS server
Thin client can communicate with UMS console and UMS server (see below)
Basic technical principles:
Unlike with &quot;normal&quot; shadowing, the connection between the VNC viewer and the VNC server (on the thin
client) is not established directly during secure shadowing. Instead, it runs via two proxies – one for the
UMS console and one for the VNC server on the thin client. These proxies communicate via an
SSL-encrypted channel, while the local communication, e.g. between the VNC viewer application and the
UMS proxy, takes place in the conventional unencrypted manner. As a result, a secure connection can also
be established with external VNC programs that do not support SSL connections.
23
IGEL Technology GmbH
Universal Desktop Linux v4
The two proxies (UMS console and thin client) communicate with SSL encryption via the same port as the
&quot;normal&quot; VNC connection: 5900. As a result, no special rules for firewalls need to be configured in order to
perform secure shadowing.
If secure shadowing is active for a thin client (Setup→System→Shadowing→Secure Shadowing), the thin
client generates a certificate in accordance with the X.509 standard and transfers it to the UMS server
when the system is next started. The UMS server checks subsequent requests for a secure VNC connection
using the certificate. The certificate in PEM format can be found in the /wfs/ca-certs/tc_ca.crt
directory on the thin client. The validity of the certificate can be checked on the thin client using the
command: x11vnc -sslCertInfo /wfs/ca-certs/tc_ca.crt
Abbildung 8: Thin client certificate for secure shadowing
If a UMS administrator calls up the Shadowing function in the UMS console for the thin client, the console
receives a signed request from the UMS server which is then passed on to the thin client to be shadowed.
This in turn passes on the request to the UMS server which checks the validity of the request using the
original certificate. If this check is successful, the console reports that the channel for the connection
between the proxies can be established. The UMS proxy on the console connects to the server proxy on the
thin client, and the server proxy in turn establishes on the thin client the connection to its VNC server.
Only when these connections have been established does the console call up the VNC viewer which then
connects to the console proxy. The VNC client and VNC server are now connected via the two proxies which
transfer data with SSL encryption.
Shadow thin clients securely
In order to shadow a thin client securely (with encryption), the administrator must log on to the server via
the UMS console. When doing so, it is irrelevant whether a purely local UMS administrator account is used
or the user was adopted via an Active Directory for example. As always, however, the UMS administrator
must have the right to shadow the object.
24
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 9: Shadowing administrator right
The thin client to be shadowed is called up in the navigation tree and, as usual, can be executed via Shadow
in the context menu. The connection widow however differs from the dialog for normal VNC shadowing.
The IP and port of the thin client to be shadowed cannot be changed and a password for the connection is
not requested – this is superfluous after logging on to the console beforehand.
Abbildung 10: Secure shadowing connection dialog
When a VNC connection has been established, the symbol in the connection tab indicates secure
shadowing:
25
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 11: Secure VNC connection
VNC logging
Connections via secure shadowing are always logged in the UMS. Via UMS Administration→Additional
Settings→Secure VNC, you can configure whether the user name of the person shadowing is to be
recorded in the log (the default is inactive).
Abbildung 12: Options for VNC logging
The VNC log can be called up via the context menu of a thin client or folder (for several thin clients,
Logging→Secure VNC Logs). The name, MAC address and IP address of the shadowed thin client, the time
and duration of the procedure and, if configured accordingly, the user name of the shadowing UMS
administrator are logged.
26
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 13: Log entries for secure VNC connections
 To sort the list (e.g. according to user names), click on the relevant column header or filter the content
shown by making entries in the Filter field.
6.6. Remote Access (SSH / RSH)
In order to allow central administration, the thin client can be configured in such a way that it can be
accessed via the WAN.
Remote access to the local setup is permitted by default. However, you can restrict remote access to a
specific user from a specific host. To enable restriction, give the full name of the host (e.g.
xterm.igel.de) and the permitted user.
6.7. Energy
Shutdown / Power Management
Here you can allow or prevent the user from shutting down the
terminal or placing it in standby mode and configure the
time-controlled standby mode. The standard action when the
on/off button is pressed can also be pre-configured.
DPMS
If your screen supports Display Power Management Signaling,
other energy saving functions are available. Three different
modes are offered: Standby, Suspend and Off. Each mode is
activated after a configurable time period (in minutes).
Naturally, all stages are gone through only if the X-Server does not receive any new entries during this
period.
27
IGEL Technology GmbH
Universal Desktop Linux v4
6.8. Firmware Customization
Various parts of the firmware can be adjusted or expanded. The individual functions are described in the
chapter entitled Firmware customization (page 103). An overview is given below:
Custom partition
Allows you to dump your files
Custom application
Allows you to define the options for launching your own applications from
the customer partition
Custom commands
Allows you to mount your own system commands and call up applications
at specific times (rc.custom)
Custom bootsplash
Allows you to replace the IGEL start logos with your own graphics
Environment variables
Allows you to use dynamic parameters when configuring a number of
session types
Features
Allows you to disable system components, e.g. session types that are not
needed
6.9. IGEL System Registry
You can change virtually every firmware parameter in the Registry. You will find information on the
individual items in the tool tips.
However, changes to the thin client configuration via the Registry should only be made by experienced
administrators. Incorrect parameter settings can easily destroy the configuration and cause the system to
crash. In cases like these, the only way to restore the thin client is to reset it to the factory defaults!
You can search for setup parameters within the IGEL Registry by clicking on the Parameter Search button. If
you would like to find the FTP settings for updating the Linux firmware, you can search for the parameter
name ftp. The parameter found in the Registry structure is highlighted:
Abbildung 14: Parameter search in the IGEL Registry
28
IGEL Technology GmbH
Universal Desktop Linux v4
7.
User Interface
Configure the user interface exactly as you want it:
•
•
•
Set the system language (page 29).
Define your entry options (page 37).
Expand the character sets (page 40).
7.1. Language
Select the system language from the list. You can also set the keyboard layout and the entry language
depending on the system language.
The chosen language is the language for the user interface and therefore applies for all local applications.
7.2. Bildschirm
Die grundlegenden und erweiterten Bildschirmeinstellungen nehmen Sie standardm&auml;&szlig;ig im IGEL-Setup vor
oder &uuml;ber die Windows-Systemoptionen.
Abbildung 15: Erweiterte Bildschirmeinstellungen
So konfigurieren Sie Multiscreen-Umgebungen im IGEL-Setup:
1. Erh&ouml;hen Sie den Parameter Anzahl der Bildschirme.
2. W&auml;hlen Sie die zugeh&ouml;rigen Aufl&ouml;sungen.
29
IGEL Technology GmbH
Universal Desktop Linux v4
3. Geben Sie die Position der Bildschirme zueinander an.
Die von den jeweiligen IGEL-Modellen unterst&uuml;tzten maximalen Aufl&ouml;sungen entnehmen Sie bitte der
Tabelle im Anhang dieses Dokuments Anhang 1 – Unterst&uuml;tzte maximale Bildschirmaufl&ouml;sungen (page 112).
W7 – F&uuml;r die Rotation (Pivot) m&uuml;ssen im BIOS des Clients mindestens 128 MB als Videospeicher konfiguriert
sein (Default sind 64 MB). Im BIOS finden Sie die Einstellung unter Integrated Peripherals→VGA Share
Memory Size. Sobald eine Bildschirmdrehung konfiguriert wird und weniger als 128-MB-Videospeicher
eingestellt sind, erscheint eine entsprechende Meldung:
Abbildung 16: Warnhinweis bei zu wenig Videospeicher
30
IGEL Technology GmbH
Universal Desktop Linux v4
7.2.1.
General Display Settings
Abbildung 17: Screen settings
Color depth
Allows you to select the desktop color depth. The following options are
available:
•
16 bits per pixel (High Color / 65,000 colors)
•
24 bits per pixel (True Color / 16.7 million colors)
Make sure that all screens connected to the thin client support the color setting.
DDC
Allows you to activate the Display Data Channel in order to share information
between the system and the screen. If screen problems should occur, enable
and disable the DDC setting in the Options by way of a test. DDC is enabled by
default and the native resolution supported by the screen is determined
automatically.
Screen configuration
Every screen connected to the IGEL UD device can be configured independently.
The position of the individual screens can be determined in relation to Screen
1. Click on the Identify button to show the screen identifier on each device.
You will find the maximum supported resolutions on the data sheet of your device.
31
IGEL Technology GmbH
Universal Desktop Linux v4
7.2.2.
DPMS
If your screen supports Display Power Management Signaling, other energy saving functions are available.
Three different modes are offered:
•
•
•
Standby
Suspend
Off
Each mode is activated after a configurable time period (in minutes).
Naturally, all stages are gone through only if the X-Server does not receive any new entries during this
period.
7.2.3.
XDMCP
Enable the XDMCP function for the screen in order to be able to select the appropriate connection type.
Please note that the local setup can then be accessed only using the hotkey Ctrl + Alt + s . This should
therefore not be disabled for the setup application (Accessories→Setup).
Connection type
Allows you to select the appropriate connection type. If you select
broadcast, the graphical login from the first XDMCP server that responds to
a broadcast query will be provided. If you choose the connection type
indirect via local host, a list of XDMCP hosts will be shown during the
startup procedure. Select from this list the host that provides the graphical
login.
Name or IP of the server
This field is enabled if you select the connection type direct or indirect.
Give the name or the IP address of the XDMCP server you wish to use. In
the direct mode, you are provided with the graphical login mask straight
from the XDCMP server which you specified in the entry field. If you chose
the indirect mode, a list of available XDMCP servers will be shown by the
server you specified.
Make sure the Display Manager daemon (XDM, KMD, GDM ...) is running and that access authorization is
available on the remote host.
7.2.4.
Access Control
Thin client access control is enabled by default. If you disable access control, it will be possible to access
your terminal screen from any UNIX host.
32
IGEL Technology GmbH
Universal Desktop Linux v4
Fixed X-Key
You can grant specific users permanent remote access to your thin client.
To do this, you will need to enable this option, click on the Calculate button
and enter the 32-character key you have received into the Xauthority file on
the user's computer.
List of permitted X hosts
Click on the Add button to open the entry mask. Give the name of the
remote host (not the IP address) you would like to add and confirm this by
clicking on OK.
7.2.5.
Desktop
With the help of the following five dialog fields, you can configure the look and behavior of the desktop,
windows, taskbar, pagers (virtual screens) and start menu.
Only the pager mask is described in detail. You should therefore refer to the tool tips for all other masks.
33
IGEL Technology GmbH
Universal Desktop Linux v4
General settings
Allows you to configure the look of the desktop by changing desktop themes, fonts
or the size of desktop symbols and the display and delay time for tool tips.
Background image
Here you can set up the desktop background image with pre-defined IGEL
backgrounds, a fill color or a color gradient. You can also use a background image of
your own. You can set up a separate background image for each monitor that is
connected to the thin client.
Own background
image
A user-specific background image can be provided on a download server. In the
Desktop→Background window, enable the option Enable Own Background Image
and give the name of the background image file. You can specify the download
server in the Desktop→Background→Background Image Server window. If you
have already defined a server for the system update files, you can use the same
server setting for downloading the background image.
The user-specific background image will be downloaded from the specified server if
the function was enabled and if requested manually (Update Background Image).
The download can also be launched from the IGEL Universal Management Suite
via Update Desktop Changes.
Own bootsplash
A user-specific boot image can be provided on a download server. Under
System→Firmware Configuration→Own Bootsplash, enable the user-defined
bootsplash and specify a download server along with the name of the image file. If
you have already defined a server for the system update files, you can use the same
server settings for downloading the boot image.
The user-specific bootsplash will be downloaded from the specified server if the
function was enabled and if requested manually (Update bootsplash). The
download can also be launched from the IGEL Universal Management Suite
(Update Desktop Changes command or update request). The image is 800 x 600
pixels in size (aspect ratio remains unchanged). The image can be positioned
vertically and horizontally by changing the position values (between 0 and 100,
standard setting 50 (centered)).
The file types BMP, JPG, GIF, TIF, PNG and SVG are supported for an own background image and
bootsplash. A total storage area of 25 MB is available for all user-specific images.
34
IGEL Technology GmbH
Universal Desktop Linux v4
Taskbar
Allows you to enable/disable and configure the taskbar
Pager
Allows you to enable/disable the use of several &quot;virtual desktops&quot;
The Pager is a tool with &quot;virtual desktops&quot; which can be used as an easy way of
switching between open applications. This window is shown at the right of the
taskbar. It can contain either a single &quot;virtual desktop&quot; or several &quot;virtual desktops&quot;.
If you use a Pager, you can switch between full-screen applications at the click of a
mouse.
Instead of minimizing/maximizing sessions or switching between them using key
combinations, you simply click on the desired screen using the mouse. The screen is
then shown as it was when you closed it (unless you restarted the system
beforehand).
Abbildung 18: Pager setup
Reference
Allows you to access all open sessions of all virtual desktops via the taskbar on each
screen
Menu
Determines the behavior of the start menu
7.2.6.
Screen Saver and Screen Lock
You can set up the screen saver so that it is activated either automatically or in response to a key
combination (hotkey). You can also select a password option. The look of the taskbar can be configured
separately for the login dialog and the locked screen.
Example configuration of a Screen Lock:
General
The screen can be locked via taskbar or desktop icons or using hotkey Ctrl-Shift-L .
35
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 19: Startup Options of Screen Lock
Options
The screen lock starts automatically after 5 minutes without user action at the thin client. The screen lock
can be stopped by entering a user password or administrator password (see Password (page 97)).
Abbildung 20: Autostart and Password Settings
Taskbar
The locked screen does not display the taskbar until the login dialog appears. The user can bring up a soft
keyboard, e.g. to login using touchscreen monitor.
36
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 21: Taskbar on Login Dialog
7.3. Input
These setup pages allow you to set the keyboard layout and other entry options.
The following parameters can be configured:
•
•
•
Keyboard (page 37)
Mouse (page 38)
Touchscreen (page 38)
7.3.1.
Keyboard and additional Keyboard
Keyboard layout
Determines the keyboard layout. The selected layout applies for all parts of the
system including emulations, window sessions and X applications.
Keyboard type
Determines the keyboard type.
Key repeat
Determines the automatic repeat behavior for the keyboard:
•
Initial key repeat delay – Determines the delay (in milliseconds) before
automatic repetition begins.
•
Key repeat rate – Determines how often a character repeats per second.
Enable dead keys – Enable this function if the keyboard used supports dead
keys for special characters.
•
Boot with NumLock
enabled
Stipulates that NumLock is to be automatically enabled during the boot
procedure.
 You can define additional keyboard layouts which can be selected by the user. The layout can be
selected in the taskbar.
37
IGEL Technology GmbH
Universal Desktop Linux v4
7.3.2.
Mouse
Mouse type and mouse
connection
Determines the type of mouse used and how it is connected
Left-handed mode
Changes the orientation of the mouse by switching the mouse buttons to
left-handed mode.
3-button mouse emulation (no
support for serial mouse)
Enables/disables emulation of the third (middle) mouse button for mice
with only two physical buttons. This third button is emulated by pressing
both buttons at the same time. If 3-button emulation was enabled, the
emulation time limit determines how long (in milliseconds) the driver
waits before deciding whether two buttons were pressed at the same
time.
Mouse speed
Determines the mouse resolution in counts per inch
Mouse double-click interval
Changes the maximum interval (in milliseconds) between two consecutive
mouse clicks which are to be recognized as a double-click.
7.3.3.
Touchscreen
To ensure that you can open the setup and navigate within it, the initial configuration should take place
with a mouse and keyboard connected. The setup procedure with a screen keyboard is described below.
A list of the touchscreens currently supported by IGEL Universal Desktop Linux can be found in the IGEL 3rd
party hardware database
https://www.igel.com/en/service-support/linux-3rd-party-hardware-database.html.
38
IGEL Technology GmbH
Universal Desktop Linux v4
Touchscreen is already calibrated
If you enable the touchscreen function, the touchscreen must be
calibrated first. If this option was not enabled, calibration will begin
automatically after each system boot.
Swap X and Y values
Enable this option if the mouse pointer moves vertically when you
move your finger in a horizontal direction.
Minimum/maximum X value/Y value
These values are determined by the calibration tool. However, you
can also change them manually.
Let-go limit
The maximum permitted time (in milliseconds) between two
instances of contact in order to still be registered a single touch.
When moving windows by drag-and-drop, for example, your contact
with the screen may inadvertently be interrupted. Increasing this
value prevents the thin client from recognizing two individual
contacts if you let go in this way.
Contact limit
Determines how long (in milliseconds) the screen needs to be
touched in order for the contact to be recognized.
Baud rate (for serial touchscreens only) Determines the speed of communication via the selected connection.
(If in doubt, read the monitor manual.)
Touchscreen connection
You can connect the touchscreen either to COM1 or COM2. Select
your preferred connection here.
Set driver-specific default settings
Click on this button once after changing the touchscreen type or to
restore the default settings.
 Enable the screen keyboard for touchscreen use in the setup under Accessories→Screen Keyboard.
The layout for the normal keyboard will also be used for the screen keyboard.
Calibrate the touchscreen for optimum contact recognition. The touchscreen calibration application can be
found in the Application Launcher→System.
After launching the calibration program, you will see a pattern with calibration points which must be
touched one after another.
39
IGEL Technology GmbH
Universal Desktop Linux v4
7.4. Keyboard Commands - Hotkeys
You will find a list of existing keyboard commands for window management here. A keyboard combination
can be defined for each function.
Abbildung 22: Keyboard commands
7.5. Font Services
You can import further font sets in addition to the ones provided by IGEL:
•
•
XC font service (page 40)
NFS font service (page 41)
7.5.1.
XC Font Service
If you need other fonts in addition to the ones offered by the thin client, you can use the XC font service.
This service must be installed on the server and fully configured there.
The advantage of using the XC font service rather than NFS is its better performance.
 Click on Enable XC Font Service in order to enable the following entry fields.
XC font server
Give the name of the server on which the XC font service operates.
Port number
Give the number of the port used by the font service for reception purposes
- the default setting is port number 710.
Favor local fonts
Enable this option if local fonts are to be used before a request is sent to the
font server.
40
IGEL Technology GmbH
Universal Desktop Linux v4
7.5.2.
NFS Font Service
Using the NFS font service is another way to import additional fonts. The NFS font service also offers the
advantage that the mount point for the fonts can be configured. This is necessary for a number of remote
applications that search for your fonts in a specific directory.
 Define and enable an NFS font path entry in order to use the NFS font service.
This will be added to the list of NFS mounted font directories.
 Click on Add to open the dialog window:
Local directory
Defines the local directory for the mount point
NFS server
Name or IP address of the server that makes available the font directories via
NFS.
Server path
Path on the server under which the fonts are available.
Favor local fonts
If this option is enabled, local fonts are to be used before a request is sent to the
font server.
 Click on Enable to enable the entry.
 Export the font directory to the server via NFS read-only for the thin client.
41
IGEL Technology GmbH
Universal Desktop Linux v4
8.
Network
LAN interfaces (page 42)
Authentication (page 44)
Wireless (Wi-Fi) Connections (page 45)
Dial-up connections - ADSL (page 47)
VPN (page 47)
SCEP (page 51)
Routing (page 52)
Hosts (page 52)
Network drives (page 53)
42
IGEL Technology GmbH
Universal Desktop Linux v4
8.1. LAN Interfaces
 Click on Network→LAN Interfaces in the client setup.
 Choose between automatic network setup with the protocols DHCP and BOOTP or manual network
configuration in order to set the thin client for each network interface.
Abbildung 23: LAN Interfaces
DHCP
Via the Dynamic Host Configuration Protocol, the thin client receives its IP address,
network mask, DNS, gateway and other network configurations from a DHCP server.
DHCP is enabled by default for LAN 1 (internal). DHCP options can be enabled in the
DHCP Client menu. A list of standard options is available. However, you can also
define your own options.
BOOTP
Via the BOOTP, the thin client receives its IP address, network mask, DNS, gateway
and other network configurations from a BOOTP server database.
The transferring of a setup.ini file or a boot script is not supported. BOOTP is not used to call up a
boot image from a server and boot this image, in spite of what the term may imply.
43
IGEL Technology GmbH
Universal Desktop Linux v4
Specify IP address
manually
Configures the network settings manually instead of searching for a DHCP server.
Ensure that the fixed IP address that you enter is not used by another computer in
your network.
If you have to use a gateway to forward the data packages to and from the target
network, click on Enable and enter the gateway IP address.
Terminal name
Give the local name of the thin client. Otherwise, the standard name IGEL-&lt;MAC
address&gt; will be generated.
Enable DNS
Configures the DNS - Specify the standard domain in which the device will work as
well as the IP address of up to two name servers which will be queried one after the
other.
8.2. Authentication
Enables IEEE 802.1x authentication
(Wired 802.1x only)
Enables network port authentication in accordance with the 802.1x
standard. The following authentication methods are currently
supported:
•
•
•
EAP-PEAP/MSCHAPv2
EAP-PEAP/TLS
EAP-TLS
The entry options in the Authentication menu vary depending on the authentication method chosen. If
the fields User Name and Password are not already populated, an entry mask for authentication purposes
will be shown.
44
IGEL Technology GmbH
Universal Desktop Linux v4
EAP type
Selects the authentication method:
•
PEAP for EAP-PEAP/MSCHAPv2 and EAP-PEAP/TLS
•
TLS for EAP-TLS
Check server certificate
Checks the authentication server
CA root certificate
Path name of the file with root certificate(s) for server authentication.
The file may be in PEM or DER format.
PEAP/Auth method
Select the Phase 2 authentication method
•
MSCHAPv2 for EAP-PEAP/MSCHAPv2
•
TLS for EAP-PEAP/TLS.
EAP-PEAP/MSCHAPv2/User name
Retains the user name for logging in for MSCHAPv2 authentication.
EAP-PEAP/MSCHAPv2/Password
Retains the password for MSCHAPv2 authentication.
EAP-PEAP/TLS/Client certificate
Path name of the file with the certificate for client authentication in
the PEM (base64) or DER format. Leave empty if a private key in the
PKCS12 format is used.
EAP-PEAP/TLS/Private key
Allows you to enter the path name of the file with the private key for
the client certificate in the PEM (base64), DER or PFX format
EAP-PEAP/TLS/User name
User name for logging in for TLS authentication
EAP-PEAP/TLS/Password for private
key
Password for accessing the encrypted private key in the private key
file
EAP-TLS/Client certificate
Path name of the file with the certificate for client authentication in
the PEM (base64) or DER format; leave empty if a private key in the
PKCS12 format is used.
EAP-TLS/Private key
Path name of the file with the private key for the client certificate in
the PEM (base64), DER or PFX format
EAP-TLS/User name
User name for logging in for TLS authentication
EAP-TLS/Password for private key
Password for accessing the encrypted private key in the private key
file.
For IEEE 802.1x authentication purposes, the client certificate can also be requested and administered via
SCEP. See Network/SCEP (page 51).
8.3. Wireless (Wi-Fi) Connections
Compatible wireless network interfaces can be found in our IGEL Linux 3rd party hardware database
https://www.igel.com/en/service-support/linux-3rd-party-hardware-database.html.
1. Configure your Wi-Fi network interface in this Wireless dialog:
45
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 24: Wi-Fi Interface Activation
-
Activate your wireless interface
Choose your IP address setup (DHCP or manually configured)
2. Set your location in Wireless regulatory domain dialog:
Abbildung 25: Wireless Regulatory Domain
Note: Make sure your regulatory domain is set correctly to avoid illegal transmission of your device.
3. Configure a wireless network connection in Default Wi-Fi network dialog:
Abbildung 26: Wi-Fi network configuration
46
IGEL Technology GmbH
Universal Desktop Linux v4
-
Set Network Name (SSID)
Choose Encryption method
Set parameter values depending on your encryption method
For WPA(2) Enterprise encryption, the client certificate can also be requested and administered via
SCEP. See Network/SCEP (page 51).
More Wi-Fi connections can be defined in Additional Wi-Fi networks dialog.
8.4. Dial-up connections - ADSL
Automatically establishing a connection during the boot procedure
In order to set up a client which is fully configured to automatically establish a connection (Autostart), you
may need to dial up first:
1. Enable ADSL Dial-Up Connections so that the client connects to the host before the desktop is
launched.
2. Click on Add to set up new connections.
3. Enter your user account configuration.
4. Select whether you wish to connect via a DSL modem connected to the network interface or use an
internal PCI device.
5. Specify whether the network interface eth0 or eth1 is used for the DSL connection.
6. Specify the protocol used.
7. Specify on the Options tab the name service and the IP configuration for the DSL connection.
These data will normally be transferred from the provider's RAS server. This means that both DNS and
IP address will be set to automatic by default.
8. Specify on the Tuning tab the duration and the network package size for the connection as well as the
error handling procedure:
-
Decide under Permanent Connection and On-Demand Connection whether your connection
should be permanent or used only on demand.
If you select On-Demand, the connection will be interrupted after a specific time-out (in seconds).
-
Under MTU and MRU, specify the maximum package size (maximum transmission and reception
units).
8.5. Virtual Private Network - VPN
Remote users securely access company networks via virtual private network protocols (VPN). You can set
up your client accordingly for this purpose.
47
IGEL Technology GmbH
Universal Desktop Linux v4
8.5.1.
PPTP
PPTP (point-to-point tunneling protocol) is one of the most common virtual private network (VPN)
protocols allowing remote users to securely access company networks.
Automatically establishing a connection during the boot procedure
In order to set up a client which is fully configured to automatically establish a connection, you may need to
dial up first.
1. Enable this option before the desktop is launched.
The client connects to the host.
2. Click on Add to set up new connections.
3. Configure the necessary settings in order to dial up the RAS server on the desired remote station.
4. Select the network device and specify whether a dial-up connection is to be used.
5. Specify on the Options tab the name service and the IP configuration for the PPTP connection.
These data will normally be transferred from the remote station's RAS server. This means that both
DNS and IP address will be set to automatic by default.
You can set up additional network routes on the next three setup pages (Routing).
8.5.2.
3rd Party VPN-Clients
IGEL Universal Desktop Linux v5 includes two clients from other manufacturers for access to a VPN:
Cisco (page 48)
GeNUCard (page 49)
Cisco
You will find the configuration parameters for the Cisco Client in the IGEL setup.
To use the software, please read the VPN Client Administrator Guide and the User Guide from Cisco:
http://www.cisco.com/en/US/products/sw/secursw/ps2308/prod_maintenance_guides_list.html
http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_user_guide_list.html
NCP
The configuration parameters for the NCP Client are configured exclusively via the client program interface
itself.
You will find the documentation regarding the NCP Secure Enterprise Client at:
http://www.ncp-e.com/de/support/produktunterlagen/handbuecher.html
48
IGEL Technology GmbH
Universal Desktop Linux v4
GeNUCard
The GeNUCard offers a choice of pre-configured Internet and VPN connections. The selection window
opens as soon as the GeNUCard session is launched.
The available options for launching the session can be defined under Desktop Integration in the session
configuration.
Abbildung 27: GeNUCard configuration
A valid combination of connection and user data can be pre-populated in the IGEL setup:
Network→VPN→GeNUCard→Options.
Abbildung 28: Automatically establishing connections
A facility for automatically establishing a connection during the boot procedure can also be enabled. This is
necessary when updating the IGEL firmware via the VPN for example.
The GeNUCard is configured and administered centrally via the genucenter management station. Further
information is available from www.genua.de.
49
IGEL Technology GmbH
Universal Desktop Linux v4
Optionally, an administrator session allowing the GeNUCard Internet connection to be configured can be
set up:
1. Click on Add Instance under System→Registry→genucard%.
The GeNUCard icon will appear on the desktop.
2. Click on the GeNUCard icon.
The GeNUCard login window will open.
3. Enter a user name and password.
4. Click on Login.
The Internet/VPN window will open.
Abbildung 29: Internet/VPN window
5. In the Internet area, configure the connection with the help of the Create, Edit, Delete buttons.
8.6. Simple Certificate Enrollment Protocol - SCEP
The SCEP allows the automatic provision of client certificates via an SCEP server and a certification
authority. This type of certificate is automatically renewed before it expires and can be used for purposes
such as network authentication (e.g. IEEE 802.1x).
A Microsoft Windows 2008 Server (MSCEP, NDES) for example can serve as a queried counterpart (SCEP
server and certification authority). More information can be found at Microsoft, e.g. in the white paper.
http://download.microsoft.com/download/a/d/f/adf2dba9-92db-4765-bf2d-34b1c8df9ca3/Microsoft%20S
CEP%20implementation%20whitepaper.doc
 Enable certificate management via SCEP client (NDES) and then make the necessary configuration
settings.
50
IGEL Technology GmbH
Universal Desktop Linux v4
8.6.1.
Certificate
 Under Certificate, specify the basic date for the certificate to be issued by the certification authority.
Type of CommonName
If the client automatically obtains its network name, DNS Name (auto) is a good
type of thin client certificate.
Organizational unit
Stipulated by the certification authority.
Organization
A freely definable designation for the organization to which the client belongs.
City, state, country
Enter the location of the client here.
RSA key length
Select a key length (one able to be used by the certification authority) for the
certificate that is to be issued.
8.6.2.
Certification Authority
 Enter the name of the certification authority (CA) and the hash value of the root certificate.
You will receive both of these from the certification authority.
8.6.3.
SCEP
In addition to a certification authority, an SCEP server must also be defined.
 Enter the address and query password for the SCEP server here.
The SCEP server generates the password as a one-time password. It is needed when a certificate is
requested for the first time. New certificates will be requested before the old ones expire. In this case,
the still-valid certificate will serve as a means of authentication.
 For the purpose of checking validity, define an interval (checking frequency) and a period of time in
which certificate renewal must occur.
Example:
A certificate is valid until 31.12 in any one year. The period for renewal is 10 days. This means that a
new certificate will first be requested on 21.12 of the same year.
Because of the need to enter a fingerprint (root certificate of the certification authority) and the query
password (SCEP server), the configuration process is somewhat awkward. Ideally, it should be set up in the
UMS as a profile and distributed to the clients. At the same time, the certificate still cannot be used for
communication purposes.
51
IGEL Technology GmbH
Universal Desktop Linux v4
8.6.4.
Checking the Client Certificate
If a certificate from the certification authority has been forwarded from the SCEP server to the client, it is
then stored there in the /wfs/scep_certificates folder.
The data for the certificate (e.g. its validity, creation date and hash value) can be displayed by using the
shell command cert_show_status.
8.6.5.
Example
Certificates issued and managed via SCEP can be used for purposes such as network authentication.
Relevant options can be found when configuring IEEE 802.1x authentication
Network→LAN Interfaces→Interface 1→Authentication
or when setting up the wireless network
Network→LAN Interfaces→Wireless→Authentication, WPA Enterprise Encryption, EAP Type TLS.
One problem when the client certificate is distributed via the network is that the same certificate is needed
for communication. The use of the SCEP in conjunction with 802.1x authentication presents no problems to
the extent that the initial request for the certificate should also be possible without a certificate.
 Enable the 802.1x authentication method after the SCEP has been configured.
When requesting the certificate, the client will attempt to establish a connection to the SCEP server
without using any authentication. It will use the authentication only after having received the
certificate.
For WLAN connections, a method of certificate-less PSK encryption must first be set up. The client will then
use this connection to obtain the certificate. After this, the WLAN connection can be reconfigured once
again.
While the above-mentioned method for Ethernet connections will also function via the UMS, the initial
configuration of the WLAN can only be performed on the client as the WLAN is disabled by default.
8.7. Routing
This setup page allows you to specify additional network routes if necessary.
 In the Interface field, specify &quot;eth0&quot;, &quot;eth1&quot; or &quot;wlan0&quot;, i.e. Interface 1+2 or Wireless LAN.
You can specify up to five additional network routes.
8.8. Hosts
If no DNS (Domain Name Service) is used, you can specify a list with hosts in order to allow translation
between your IP address, the full qualified host name and the short host name.
Click on Add to open the dialog window.
1. Enter the IP address of the host you would like to add.
2. Give the full qualified host name (e.g. &lt;mailserver.igel.de&gt;).
52
IGEL Technology GmbH
Universal Desktop Linux v4
3. Give the short host name of the host (e.g. &lt;mailserver&gt;).
4. Confirm the details you have entered by clicking on OK.
The specified host will now be added to the computer list.
8.9. Network Drives
Drives shared within the network can be linked to the thin client via NFS or SMB - depending on the
protocol offered by the server.
8.9.1.
NFS
With NFS (Network File System), you can share files via the network. The NFS server exports a system file,
and the NFS client (your thin client) links this file to a mount point within its own file system. The exported
file system then becomes a logical part of the thin client file system although, in physical terms, it remains
on the server.
In order to set up an NFS mount, the server must first be configured. You will find detailed information on
NFS on the relevant pages of the manual for your server operating system.
The procedure for sharing files via the NFS server is as follows:
 Click on Add to open the dialog window for NFS.
You can then enter the following:
Enabled
The NFS mount is enabled by default and is mounted each time the system
boots.
Disable this entry if the shared file system is not universally needed.
Local directory
Details of the local directory onto which the shared items are to be mounted
on the local thin client file system.
Server
The name or IP address of the NFS server which provides the shared files.
Path name
Details of the path name as exported by the NFS server.
8.9.2.
Windows Drive - SMB
SMB is used by Microsoft Windows NT, Windows 95/98, Windows 2000 and Windows XP etc. to share hard
drives and printers. As Unix (including Linux) can process this protocol with Samba Suite tools, hard drives
and printers can be used along with Windows hosts. Consequently, items shared via SMB can be integrated
into the thin client by Windows or Unix Samba hosts.
The SMB protocol is used only to share files via the network (not for printers). Shared items which are to
be mounted must first be created on the Windows or Unix host.
53
IGEL Technology GmbH
Universal Desktop Linux v4
Local directory
Details of the local directory onto which the shared items are to be mounted on
the local thin client file system.
Server
For a Windows host, the Net BIOS name must be entered here. For a Unix Samba
host, the host name or the IP address must be used.
Share path name
Path name as exported by the Windows or Unix Samba host.
User name/password
Details of the user name and password for your user account on the Windows or
Unix Samba host.
Enabled
The SMB mount is enabled by default and is mounted each time the system boots.
Writable for users
If this option is enabled, the user who is logged on can write data. Otherwise, this
is only possible via root.
54
IGEL Technology GmbH
Universal Desktop Linux v4
9.
Sessions
Application sessions can be created and configured in the Sessions sub-structure of the IGEL setup
application. The Session Overview provides an overview of all available session types and existing sessions.
Abbildung 30: Session overview
 Click on Add to create a new session.
Disabled services are not shown in the drop-down list.
For each session there is a configuration page entitled Desktop Integration on which the following actions
can be performed:
•
•
Determining the look of the session on the local desktop
Setting up the name of the session
Note: None of these characters can be used in the session name: \ / : * ? “ &lt; &gt; | [ ] { } (
)
•
•
Selecting the session start options (autostart, restart)
Enabling hotkey use
9.1. Citrix ICA - global settings
This section describes the procedure for configuring the global Citrix settings. This configuration applies for
all Citrix sessions.
These are the standard values for all Citrix sessions. Most of these properties, in particular the color
depth, resolution and the server IP or server name, can be changed separately for each session.
Both versions of Citrix Receiver client are available - Citrix Receiver 12 and Citrix Receiver 13. As default
the client version 12 will be used and you can activate version 13 in IGEL Setup→Sessions→Citrix→Citrix
Receiver Selection→Use Citrix Receiver 13 .
55
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 31: Citrix Receiver 13 Activation
Please note that there are a lot dependencies when changing the version of Citrix Receiver. There are some
hints in the IGEL Setup application and a feature comparison of both versions can be found in our FAQ:
Citrix Receiver Feature Matrix http://faq.igel.com/otrs-igel/public.pl?Action=PublicFAQZoom;ItemID=619
IMPORTANT: Citrix Receiver 13 on Linux does only support connections via HTTPS while the Citrix server's
default setting is HTTP - so the connection will fail. You have to enable HTTPS connections on Citrix server
and you have to make sure the thin client has a valid root certificate of the Certificate Authority (CA)
available! A best practice document on how to distribute the certificate is available in the IGEL knowledge
base: Deploying Trusted Root Certificates
IMPORTANT: Citrix Receiver 13 does currently not support Kerberos authentication!
IMPORTANT: Users can only change their expired password if this option has been enabled on the Citrix
server. See FAQ Warning message when changing password
http://faq.igel.com/otrs-igel/public.pl?Action=PublicFAQZoom;ItemID=621.
9.1.1.
Window
The following settings are configured under Window:
56
IGEL Technology GmbH
Universal Desktop Linux v4
Standard number of colors
Specifies the standard color depth - the default setting is a color depth of
256 colors.
Approximate colors
Given the differences between the color palettes used by the ICA client and
the &quot;thin client&quot; desktop, the screen may flash annoyingly if you switch
between windows on a pseudo-color screen. The ICA client's color
adaptation scheme prevents this flashing as it uses the colors from the local
desktop palette in order to display the ICA window session. If Approximate
Colors is enabled, flashing when switching between windows is avoided.
Window size
Specifies the width and height of the window.
Embed systray icons in window
manager taskbar
Inserts an application icon into the local taskbar
Font smoothing
Enables font smoothing - in the event of performance problems, font
smoothing should be switched off as it requires additional computing power.
Multi Monitor
Stipulates whether the full-screen mode is to be extended to all monitors.
9.1.2.
Server location
The Server Location option - also referred to as server browsing - allows you to bring up via the Citrix ICA
client connected to the network a list of all Citrix servers and all published applications which are accessible
via the network and use the selected browsing protocol.
The standard functionality for this option is Auto-Locate (Broadcast). With this function, the ICA client
sends a &quot;Get nearest Citrix server&quot; package. The address of the first Citrix server to reply then functions as
the master ICA browser.
You can also specify a separate address list for each network protocol. This can be TCP/IP, TCP/IP + HTTP
or SSL/TLS + HTTPS.
TCP/IP
If your network configuration uses routers or gateways, or if additional network traffic
owing to transmissions is to be avoided, you can specify special server addresses for the
Citrix servers from which the list of available servers and/or published applications is to
be requested.
You can add a number of addresses to the address list so that the clients can establish a connection and
function even if one or more servers are not available.
TCP/IP + HTTP
You can also call up information from the available Citrix servers and published
applications via a firewall. To do this, you use the protocol TCP/IP + HTTP as the server
location.
The &quot;TCP/IP + HTTP&quot; server location does not support the auto-locate function.
57
IGEL Technology GmbH
Universal Desktop Linux v4
SSL/TLS + HTTPS
Secure Sockets Layer (SSL) and Transport Layer Security (TLS) encryption offer server
authentication and data stream encryption. They also allow you to check the integrity of
messages.
If you try to establish a non-SSL/TLS connection to an SSL/TLS server, you will not be connected. A
Connection Failed message will be shown.
9.1.3.
Keyboard / hotkey assignment
On the Keyboard page, you can define alternative key combinations for hotkeys commonly used during ICA
sessions. In MS Windows for example, the key combination Alt + F4 closes the current window. It also works
in ICA sessions too. All key combinations with Alt which are not used by the X Window Manager function in
the familiar way during an ICA session.
The key alternatives are restricted to Ctrl + Shift + Key by default. However, you can change the settings by
clicking on the Hotkey Modifier drop-down field and/or hotkey symbol for the relevant key combination.
•
•
Possible keys: F1 – F12 , Plus , Minus , Tab
Possible modifiers: Shift , Ctrl , Alt , Alt + Ctrl , Alt + Shift , Ctrl + Shift
If you would like to use the PC key combination Ctrl
combination Ctrl Alt Enter or Ctrl Alt Return key .
9.1.4.
Alt Delete
during an ICA session, use the key
Mapping
Locally connected devices such as printers or USB storage devices can be made available in ICA sessions.
Drive mapping
Through drive mapping, each directory mounted on the thin client (including CD-ROMs and disk drives) is
made available to you during ICA sessions on Citrix servers. On this page, you can specify which folders or
drives are mapped during the logon. This then applies for all ICA connection sessions.
Abbildung 32: Drive mapping
58
IGEL Technology GmbH
Universal Desktop Linux v4
The Enable Drive Mapping option allows you to temporarily enable/disable drive mapping. This offers the
advantage that stored settings can be enabled or disabled without being lost.
Local (USB) devices which are to be used for drive mapping purposes must first be set up as devices.
The procedure for setting up drive mappings is as follows:
1. Click on Add to bring up the mapping window.
2. Select a target drive from the list under which the local device or the folder is to be mapped.
If the drive letter you have selected is no longer available on the Citrix server, the specified directory
or local drive will be given the next free letter during the logon.
3. Give the path name of the local directory to which the mapping is to refer.
If you map a locally connected device, use the pre-defined path names available in the drop-down
field. The directories in question are those on which the devices are mounted by default during the
boot procedure (e.g. /autofs/floppy for an integrated disk drive).
4. Specify the access authorizations for the mapping.
For each mapping, you have the option of granting read access or write access. You can also select the
Ask option to query the read/write access rights when each ICA session is accessed for the first time.
The drive mappings and access data defined here are then valid for all ICA connections.
COM ports - serial connections
Enable Com Port Mapping in order to perform bidirectional mapping between serial devices connected to
the thin client (e.g. scanners, serial printers) and the serial ports of the Citrix server.
As a result, programs running on the server can exchange data with the local devices.
 Click on Add under Serial Devices.
 From the drop-down list, select the serial port to which a device is connected or click on Search
Devices... to select an available device.
/dev/ttyS0
Denotes the local serial connection COM1
/dev/ttyS1
Denotes the local serial connection COM2
COM3 and COM4
Denote possible expansion cards installed in the
PCI/ISA slot, e.g. an internal modem
USB COM1 to USB
COM4
Denote serial connections to USB-to-serial adapters.
Your selection will be mapped to the virtual COM1 connection. A second device will be mapped to the
virtual COM2 connection and so on.
59
IGEL Technology GmbH
Universal Desktop Linux v4
Printers
You can set up a printer for ICA sessions here.
With the Enable Client Printer Mapping function, the locally connected thin client printer is made available
for your ICA sessions, provided that it was not disabled on the server side.
The printers must be set up on the Devices→Printers→CUPS→Printers page and must be enabled there for
mapping in ICA sessions, see ICA sessions (page 64).
Because the thin client merely places incoming printer jobs in a queue, you need to install the printer on
the server. Proceed in the usual way: Start→settings→Printers etc.
Please note that you will need to be logged on as administrator to the terminal to which the printer is
connected.
Device support / virtual communication channels
Enable virtual ICA channels for communicating with various devices connected to the thin client. These can
be card readers, dictation machines or even USB storage devices. Channels of this type allow the device to
communicate with the relevant server application.
Abbildung 33: Supported devices
When using CenterTools DriveLock, ensure that the use of USB devices is not universally restricted:
Devices→USB Access Control
60
IGEL Technology GmbH
Universal Desktop Linux v4
DriveLock
The virtual DriveLock channel (ICA protocol) is included in the UDLX from Version 4.11.100 and must be
installed on the Citrix-XenApp server.
DriveLock can read hardware data from local USB devices and transfer these data with the help of the
Virtual ICA Channel Extension to the XenApp server. When using whitelists, rules based on the hardware
properties of the connected drive (e.g. manufacturer details, model and serial number) are taken into
account.
The following steps are important in order to be able to define the access rights for drives via the
DriveLock server configuration:
 Enable the USB devices via drive mapping so that they are available as drives within your terminal
session.
 Check the settings under Sessions→ICA→ICA Global→Mapping→Drive Mapping, they should
correspond to the DriveLock settings.
 Disable Citrix USB redirection, because this will otherwise prevent drives being recognized by
DriveLock.
 Check the device settings Devices→Storage Devices→USB Storage Hotplug, as they can influence the
USB devices during the Citrix session.
 Install and enable the DriveLock channel in the Universal Desktop setup under Sessions→ICA→ICA
Global→Mapping→Device Support.
In the Centertools download area, you will find a document which describes in greater detail the
procedure for configuring DriveLock on the server side: How to use Centertools DriveLock with IGEL Thin
Clients
9.1.5.
Firewall
Use alternative address
Define a proxy or secure gateway server as an alternative address for
connections via a firewall. Note the tool tips regarding the individual
configuration parameters.
Secure Gateway (relay mode)
If you would like to use a Citrix Secure Gateway in relay mode, you must
give the full domain name – the IP address is not sufficient in this case.
After enabling the alternative address, add the server to the address list in the Server Location field in
Global Settings for ICA.
9.1.6.
USB redirection
USB devices can be permitted or prohibited during a Citrix session on the basis of rules. Sub-rules for
specific devices or device classes are also possible.
Use either Native USB Redirection or Fabulatech USB Redirection.
61
IGEL Technology GmbH
Universal Desktop Linux v4
For Fabulatech USB Redirection, a special Fabulatech server component must be installed on the Citrix
server (USB for Remote Desktop Igel Edition).
More detailed information on the function can be found on the Fabulatech partner site:
http://www.usb-over-network.com/partners/igel/ (http://www.usb-over-network.com/partners/igel/).
Enable either native or Fabulatech USB redirection – not both together.
Disable USB redirection if you use Centertools DriveLock (page 61).
9.1.7.
Multimedia redirection
Citrix HDX multimedia acceleration improves playback via Media Player within an ICA session on the
remote desktop and allows isosynchronous transmissions, e.g. of webcams within the session.
See Supported formats and codecs (page 112).
Abbildung 34: Multimedia redirection
To improve multimedia playback on the remote desktop, follow the procedure below:
1. To take advantage of improved playback, ensure that the necessary codecs are installed on the remote
desktop page.
2. Enable multimedia redirection on the thin client.
3. Create the session.
4. Begin playback on the remote desktop.
62
IGEL Technology GmbH
Universal Desktop Linux v4
9.1.8.
Local logon
Use Kerberos pass-through authentication in This option enables single sign-on for all ICA sessions if Log on
all ICA sessions
to the thin client with AD/Kerberos is configured.
The server too must be configured for pass-through
authentication. When launching ICA sessions, it is then no
longer necessary to enter a user name and password again as
the local logon data (domain logon) are transferred for
session logon purposes.
Use the local logon module if problems with load balancing
occur. The user's logon information is transferred when
connecting to the metaframe master browser.
Use local logon window
If this option is enabled, you will need to enter the password
again when logging on.
Restart mode
The logon module is automatically restarted after being
closed.
Type
Here, you can pre-populate the user name and domain in the
logon window and choose between the settings from the last
logon and the session setup.
Pre-populate logon information
The logon window is pre-populated with the user name and
domain.
Show domain
Shows the domain entry in the logon window.
Use client name as user name
This setting may help to resolve reconnection problems
during load balancing.
Allow logging on with smartcard
Only specific smartcard types are supported. You will find a
list of compatible types in the Smartcard sub-section of the
setup.
Domains
Allows you to add domains which are to be available. If you
enter a number of domains, these will be shown in the
Domains drop-down area in the logon module.
smartcard
Allows local access to smartcards and tokens from various
manufacturers.
9.1.9.
ICA global options
On this page, you can set up additional options to optimize the system's general behavior and its
performance.
63
IGEL Technology GmbH
Universal Desktop Linux v4
Use server redraw
The Citrix server is responsible for refreshing the screen content.
Disable Windows warning sounds
This option allows you to disable Windows warning sounds.
Use backing store
The X Server temporarily stores hidden desktop content.
Delayed screen update mode
Enables delayed updates from the local video buffer on the
screen. The local video buffer is used if the seamless Windows
mode or HDX latency reduction is used.
Caching
Allows you to change the settings for the bitmap cache. If you
work with images that are displayed over and over again, you can
significantly improve the performance of your ICA session(s).
Specify the maximum amount of local system storage capacity (in
kilobytes) used for temporary storage purposes. You can also
specify the minimum size of bitmap files which are to be stored in
the cache as well as the directory in which the files can be stored
locally.
An excessively high setting can mean that the thin client has too little storage space for its own system
and other applications. If in doubt, you can equip your thin client with additional RAM.
Scrolling control
Depending on the speed of your network or the response time of
your server, there may be a delay between you letting go of the
mouse button on a scroll bar and the scrolling actually stopping
(e.g. when using EXCEL). Setting the value to 100 or higher may
help to rectify this problem.
Enable auto-reconnect
Allows you to specify the parameters for reconnecting the session
Allow Kerberos pass-through in
Program Neighborhood sessions
Allows the use of Kerberos pass-through authentication in the
Citrix Program Neighborhood session.
9.2. Citrix ICA - Sessions
If a session is created or edited, you can change the ICA session settings if they differ from the global
settings.
The primary source of further information relating to Citrix connections should always be the relevant
Citrix documentation. This manual merely gives general configuration tips.
64
IGEL Technology GmbH
Universal Desktop Linux v4
9.2.1.
Server
Browser protocol
Allows you to select the protocol needed for transmission or the global
standard setting
Do not use standard server location Lifts the standard server requirement – for each protocol separately
Server
By clicking on the Search button, you send a transmission signal which
queries all available servers and published applications.
•
By selecting the server, the user is connected to the entire desktop
as if logging on at the server itself. As a result, all applications,
rights and settings contained in the user's profile (local server
profile) are available.
•
If one of the published applications is selected, the session is
opened in a window which contains just one application. The
session is ended if you close this application.
•
You can also manually enter the IP address or the host name of the
server in the Server field.
Application
If you have entered the server manually, you can specify a published
application here. These fields are automatically filled in if you have
selected one of the recognized published applications.
Work directory
Details of the path name of the work directory for the application
9.2.2.
Logon
Use Kerberos pass-through
authentication
Enables single sign-on for this ICA session if Log on to the thin client with
AD/Kerberos is configured. The server too must be configured for
pass-through authentication. When launching the ICA session, it is no
longer necessary to enter a user name and password again.
Use pass-through authentication
Enables single sign-on for this ICA session if Log on to the thin client with
AD/Kerberos is configured. The fact that the user name and password are
temporarily stored when logging on to the thin client means that they no
longer need to be entered again when launching a session.
User, password, domain
A user name, password and domain for the ICA session can be entered
here. These details are automatically forwarded to the server and no
longer need to be entered on the logon screen.
Hide password protection before
logging on
This option switches the Windows splash screen on and off. This option
must be disabled when logging on to Windows using a smartcard!
65
IGEL Technology GmbH
Universal Desktop Linux v4
9.2.3.
Window settings
The following settings are configured under Window settings:
Number of colors
The color depth is set as a global default. You can change it for this session.
Use standard setting for
color table
The color table is preset on a global basis. You can approximate it for this session.
Window size
By disabling the full-screen mode, you can choose between the global default
setting and a session-specific setting.
Start monitor (Dualview)
Specifies which monitor in an environment with several monitors is to be used for
the session.
Enable seamless window
mode
The seamless window mode can only be used with published applications or with
a specified start program for the server connection.
Font smoothing
Font smoothing is preset on a global basis. You can change it for this session.
9.2.4.
Firewall
Use alternative address
Define a proxy or secure gateway server as an alternative address for
connections via a firewall. Note the tool tips regarding the individual
configuration parameters.
Secure Gateway (relay mode)
If you would like to use a Citrix Secure Gateway in relay mode, you must
give the full domain name – the IP address is not sufficient in this case.
After enabling the alternative address, add the server to the address list in the Server Location field in
Global Settings for ICA.
9.2.5.
Options
Under Options, you can optimize performance and system behavior within the ICA session.
66
IGEL Technology GmbH
Universal Desktop Linux v4
Compression
Reduces the amount of data transmitted via the ICA session. This results
in a reduction in network traffic to the detriment of CPU performance. If
you connect your server(s) via WAN, you should use compression. If you
use a relatively low-performance server and only work in one LAN, you
should disable this option.
Caching image data
Enables caching in the cache memory (configured in the global ICA
settings) for each session. This makes sense if you use a number of ICA
sessions but only one or two sessions are critical from a network
bandwidth point of view or are intensively used during the day. In this
case, you should reserve the cache memory for these settings.
Encryption method
Encryption increases the security of your ICA connection. Basic encryption
is enabled by default. You should therefore ensure that the Citrix server
supports RC5 encryption before you select a higher degree of encryption.
Audio transfer
Transfers system sounds and audio outputs from applications to the thin
client. These are then output via the speakers connected. The higher the
level of audio quality you select, the more bandwidth is needed for
transferring audio data.
HDX latency reduction
Improves the performance of connections with a high level of latency by
immediately reacting to keyboard entries or mouse clicks. This makes the
thin client feel more like a normal PC.
Mouse click feedback
The mouse pointer immediately turns into an hourglass symbol, thus
providing visual feedback in response to a mouse click.
Local text echo
Displays text entered more quickly and avoids latency within the network.
Select a mode from the drop-down list:
•
Select On for slower connections (connection via WAN) in order to
reduce the delay between the user entering text and the text being
displayed on the screen.
•
•
For faster connections (connection via LAN), select Off.
Select AUTO if you are not sure how fast the connection is.
HDX must be enabled and configured on the Citrix server for it to work.
9.2.6.
Reconnect
You can edit Global Settings for ICA for the Reconnect option.
9.3. Citrix StoreFront / Web Interface
Some of the settings are already configured under Global settings for ICA and in the ICA session setup (page
64).
 Select the start options for the Citrix XenApp session, see Desktop integration.
67
IGEL Technology GmbH
Universal Desktop Linux v4
9.3.1.
Connections
 Select the Citrix server type:
Web Interface / Service Site
•
•
StoreFront (Legacy)
Enter the address of your Citrix server.
Select up to 4 backup server.
Enter the address of your Citrix server.
If you add domains they will be displayed in the login window.
9.3.2.
Logging on
To be able to use pass-through authentication you need first to enabled Login to Active Directory Login
under Security-&gt;Logon-&gt;Active Directory / Kerberos.
Enable Use Pass-Through Authentication in order to use temporarily stored logon data for listing and
launching applications.
 Select the Login methods.
 Select the type of smartcard under Logon-&gt;Active Directory / Kerberos-&gt;Smartcard.
It is possible to use the smartcard also without pass-through authentication.
9.3.3.
Options
Specify audio, keyboard and display options if they differ from the global settings.
68
IGEL Technology GmbH
Universal Desktop Linux v4
9.3.4.
Appearance
You can configure the XenApp/Program Neighborhood applications in such a way that they are displayed
in various areas of the local system, e.g. on the local desktop or in the Start menu.
 Enable Scale Symbols for the Start Menu to automatically adjust the size of the application symbol.
Abbildung 35: Citrix XenApp layout
9.3.5.
Change password
This setup page is only active if Citrix Receiver 12 with Web Interface is selected as server type.
Specify how a connection for changing a password is to be established.
Generic session
Searches for servers/applications and subsequently establishes a
connection
Pre-configured ICA session
Selects a pre-defined ICA session according to session name
Citrix XenApp services site
Allows you to change a password via the Citrix Web Interface itself
If Kerberos authentication is set up on the XenApp Server, the password can also be changed via this route.
9.3.6.
Reconnecting and updating
 Select the required option when reconnecting with sessions.
You can establish a connection
69
IGEL Technology GmbH
Universal Desktop Linux v4
•
•
during the logon process and
through using a reconnect session, e.g. on the desktop.
With the help of the reconnect procedure, you can launch active and terminated sessions, terminated
sessions only or sessions on demand.
An updating session reloads the XenApp session without terminating it.
9.4. Citrix Access Gateway
With the Citrix Access Gateway (CAG) client, you can establish a VPN connection to a CAG standard server
4.6. The VPN connection is an SSL tunnel. A certificate is transferred from the server to the client in the
process. If the certificate is not trustworthy, a warning will be given when an attempt to establish a
connection is made. In order to avoid the warning, the server certificate can be stored on the thin client in
the /wfs/cagvpn/cagvpn-trusted-CAs.crt file. The warning can also be disabled in the CAG
client configuration.
9.5. RDP - global settings
This section describes the procedure for configuring the global RDP settings. This configuration applies for
all RDP sessions. The protocol version can no longer be configured manually, while the version used by the
server is automatically recognized and used.
9.5.1.
Local Logon - RDP
Local login allows user data pre-population, e.g. with data from the domain login, when establishing the
connection to the terminal server. This can save you having to enter the same login data on a number of
occasions.
You can also use Local login to freely select the server in the login window of an RDP session.
Enable Use local login window to
•
•
Pre-populate user data
Freely select the server in the login window of an RDP session.
If the user data, e.g. the data from the domain login, are pre-populated, this can save you having to enter
the same login data on a number of occasions.
70
IGEL Technology GmbH
Universal Desktop Linux v4
Use local login window
If this option is enabled, you will need to enter the password in the
RDP login window on the terminal side when logging in.
Pre-populate login information
The login window is pre-populated with the user name and domain.
Type
Here, you can pre-populate the user name and domain in the login
window and choose between the settings from the last login and the
session setup.
Show domain
Shows the domain entry in the login window.
Set client name as user name
This setting may help to resolve reconnection problems during load
balancing.
Restart mode
The RDP login window is displayed in restart mode and cannot be
closed.
Enable network authentication
Enables network authentication via NTLM. Smartcards are not
supported here.
Domains
Allows you to add domains which are to be available. If you enter a
number of domains, these will be shown in the Domains drop-down
area in the login module.
9.5.2.
Window
The following settings are configured under Window:
Standard number of colors
Specifies the standard color depth - the default setting is a color depth of 256
colors.
Approximate colors
Given the differences between the color palettes used by the ICA client and the
&quot;thin client&quot; desktop, the screen may flash annoyingly if you switch between
windows on a pseudo-color screen. The ICA client's color adaptation scheme
prevents this flashing as it uses the colors from the local desktop palette in order
to display the ICA window session. If Approximate Colors is enabled, flashing
when switching between windows is avoided.
Window size
Specifies the width and height of the window.
Embed systray icons in
window manager taskbar
Inserts an application icon into the local taskbar
Font smoothing
Enables font smoothing - in the event of performance problems, font smoothing
should be switched off as it requires additional computing power.
Multi Monitor
Stipulates whether the full-screen mode is to be extended to all monitors.
9.5.3.
Mapping
Locally connected devices such as printers or USB storage devices can be made available in RDP sessions.
71
IGEL Technology GmbH
Universal Desktop Linux v4
Drive Mapping
Through drive mapping, connected mass storage devices can be made available to the user. Specify which
folders or drives are mapped during the login.
Via Enable drive mapping, you can temporarily enable/disable drive mapping. This offers the advantage
that stored settings can be enabled or disabled without being lost.
Local (USB) devices which are to be used for drive mapping purposes must first be set up as devices.
The procedure for setting up drive mappings is as follows:
1. Click on Add to bring up the mapping window.
2. Select a target drive from the list under which the local device or the folder is to be mapped.
If the drive letter you have selected is no longer available on the server, the specified directory or local
drive will be given the next free letter during the login.
3. Give the path name of the local directory to which the mapping is to refer.
If you map a locally connected device, use the pre-defined path names available in the drop-down
field. The directories in question are those on which the devices are mounted by default during the
boot procedure (e.g. /autofs/floppy for an integrated disk drive).
Serial (COM) Ports
Enable Enable COM Port Mapping in order to perform bidirectional mapping between serial devices
connected to the thin client (e.g. scanners, serial printers) and the serial ports of the Citrix server.
As a result, programs running on the server can exchange data with the local devices.
 Click on Add under Serial Devices.
 From the drop-down list, select the serial connector to which a device is connected or click on Search
Devices... to select an available device.
/dev/ttyS0
Denotes the local serial connection COM1
/dev/ttyS1
Denotes the local serial connection COM2
COM3 and COM4
Denote possible expansion cards installed in the
PCI/ISA slot, e.g. an internal modem
USB COM1 to USB
COM4
Denote serial connections to USB-to-serial adapters.
Your selection will be mapped to the virtual COM1 connection. A second device will be mapped to the
virtual COM2 connection and so on.
72
IGEL Technology GmbH
Universal Desktop Linux v4
Printers
You can set up a printer for ICA sessions here.
With the Enable Client Printer function, the locally connected thin client printer is made available for your
ICA sessions, provided that it was not disabled on the server side.
The printers must be set up on the Devices→Printers→CUPS→Printers page and must be enabled there for
mapping in ICA sessions, see ICA sessions (page 64).
Because the thin client merely places incoming printer jobs in a queue, you need to install the printer on
the server.
Device Support
Enable virtual RDP channels for communicating with various devices connected to the thin client. These can
be card readers (smartcards), dictation machines or even USB storage devices. Channels of this type allow
the device to communicate with the relevant server application.
Abbildung 36: Device Support
Audio
 Enable local audio transmission.
 Define the Audio Quality Mode, you want to use.
The higher the quality, the higher also the caused network traffic.
73
IGEL Technology GmbH
Universal Desktop Linux v4
9.5.4.
Performance
In the event of performance-related problems, disable graphics functions which are not absolutely
necessary. In low-bandwidth environments, you should use compression in order to reduce the network
traffic.
Please note that this uses additional CPU power.
RemoteFX Support
With the Service Pack 1 for Windows Server 2008 R2, local system functions such as Windows Aero or 3D
display can be made available in RDP sessions too. In order to do this, the RemoteFX extension for RDP
must be enabled. You can configure the relevant settings under RDP Global→Performance or on the
corresponding session settings.
Abbildung 37: Windows Aero
Globally enabling Remote FX is not recommended as conventional RDP sessions may also be affected by
this. With RemoteFX, all graphics effects available under Performance are enabled. This may slow down the
session as a result. It is better to enable the function only for individual sessions which establish a
connection to appropriately equipped servers.
Further information on Remote FX and the server-related requirements is available from Microsoft at
http://technet.microsoft.com/en-us/library/dd736539%28WS.10%29.aspx.
In the IGEL Registry, you can configure the number of frames sent by the server without confirmation under
the key rdp.winconnect.remotefx-ack. The standard value is 1. A value of 2 or 3 can lead to
improved performance in networks with high latency times.
74
IGEL Technology GmbH
Universal Desktop Linux v4
9.5.5.
Options
Disable Mouse Motion Events
Instructs the client not to show &quot;unnecessary&quot; cursor movements in order
to conserve power.
Reset License
If you have to remove the MS license from the device, enable this option
and restart the device.
Client Name
Give a client name for terminal service identification - the standard
setting is the host name of the computer.
Enforce TLS encrypted
connection
Permits TLS-encrypted connections only / verifies server certificates /
deletes certificates that are no longer needed
RDP Legacy Mode
Switches to prior (IGEL Linux v4.x) RDP client version - see note below!
Before using RDP Legacy Mode to solve any occurring problem with the current RDP client (IGEL Linux
v5) please contact IGEL support to address your issue. RDP Legacy Mode may be removed with any later
version of IGEL LInux.
9.5.6.
Native USB Redirection
USB devices can be permitted or prohibited during an RDP session on the basis of rules. Sub-rules for
specific devices or device classes are also possible.
Use either Native USB Redirection or Fabulatech USB Redirection.
For Fabulatech USB Redirection, a special Fabulatech server component must be installed on the server
(USB for Remote Desktop Igel Edition).
More detailed information on the function can be found on the Fabulatech partner site:
http://www.usb-over-network.com/partners/igel/ (http://www.usb-over-network.com/partners/igel/).
Enable either native or Fabulatech USB redirection – not both together.
Disable USB redirection if you use Centertools DriveLock (page 61).
75
IGEL Technology GmbH
Universal Desktop Linux v4
9.6. RDP session
The following configuration pages offer you detailed setup options for the session:
Server and logon
Allows you to specify a server and a start application for the terminal server
session. The necessary logon information is configured here. Otherwise, the
terminal server logon window for entering the user and the password will be
displayed.
Window
Allows you to specify the size of the session window and the color mode. The
local taskbar can be configured so that it remains visible during a full-screen
session.
Performance
Allows you to disable non-essential graphical functions such as skin styles,
window animation etc. This is useful in the event of performance problems.
Mapping
Allows you to specify the audio output device (local/remote) and determine
how key strokes and clipboard content are handled. The mapping of serial
connections and local drives can be enabled for a session.
You can make connected mass storage devices available to the user using the
appropriate mapping: Select Enable, choose the drive letter and the device to
be mapped.
Options
Determines the start application and the work directory for use during the
session (how authentication errors are handled during the logon procedure).
If, when connecting to the server, a terminal server gateway is to be used, you
can configure the relevant settings here (No Gateway is pre-set).
9.6.1.
Server / logon
If a session is created or edited, you can change the RDP session settings if they differ from the global
settings:
1. Specify a server and, where appropriate, a start-up application for the terminal server session.
2. Configure the necessary logon information.
Otherwise, the terminal server logon window will be displayed for you to enter a user name and
password. If the local logon is used (see above), this window is the thin client's logon window.
 The option for freely entering the server can also be enabled under Server →Variable Server
Connection for Local Logon.
If the Pass-Through Authentication option is enabled, the session with the local logon data for the terminal
user, e.g. from the domain logon, is used. However, this setting will be overridden by the Local Logon
global parameter. You should therefore not use both options at the same time.
76
IGEL Technology GmbH
Universal Desktop Linux v4
9.6.2.
Display, keyboard and allocation of resources
 Under Window, specify the color depth, window size and the multiscreen behavior.
 Under Keyboard, configure the keyboard layout and the hotkey properties.
 Enable/disable the allocation of resources for the client, e.g. COM port or printer mapping.
The global parameters (page 70) are the default setting.
9.6.3.
Performance and options
Specify the performance settings for the session if they differ from the global configuration (page 70).
Abbildung 38: Performance settings
77
IGEL Technology GmbH
Universal Desktop Linux v4
9.6.4.
Microsoft RemoteApp
Abbildung 39: RemoteApp settings
Like the published applications of a Citrix server, MS Windows Server 2008 offers the option of passing on
RemoteApps to the thin client. Detailed instructions regarding server configuration can also be found on
the Microsoft website: TS RemoteApp Step-by-Step Guide.
On the client side, only a few parameters need to be configured after enabling the RemoteApp mode.
Please note that the name of the application to be launched must be preceded by two vertical bars (||),
e.g. ||Excel.
9.7. VMware Horizon Client
By default, Horizon Client session settings are carried over from the RDP global setup pages. You can
change the configuration for Horizon Client sessions on the relevant setup pages. You can also set up
multimedia and USB redirection for the session as well as enable various smartcard types for login
purposes.
9.8. Quest vWorkspace Client and AppPortal
By default, vWorkspace Client session settings are carried over from the RDP Global setup pages. You can
change the configuration for vWorkspace Client sessions (USB and multimedia redirection) on the relevant
setup pages.
The vWorkspace Client is based on hypervisors from other providers and is therefore compatible with
VMware, vSphere, Microsoft Hyper-V and XenServer. All configuration parameters for the vWorkspace
Client and the vWorkspace AppPortal Farm are described in detail in the original documentation for the
relevant client version, for Quest, see https://support.quest.com/Default.aspx.
78
IGEL Technology GmbH
Universal Desktop Linux v4
Abbildung 40: AppPortal farms configuration
9.9. Leostream Connection Broker
Specify a server, user and domain for logging on to Leostream Connection Broker. By default, the rdesktop
Client is used for the connection in UDLX. rdesktop must therefore be set as the Leostream API protocol
with priority 1 on the server.
Abbildung 41: Leostream-Api protocol
More information on the Leostream Connection Broker is available from Leostream by visiting:
http://www.leostream.com/resources/downloads.php.
79
IGEL Technology GmbH
Universal Desktop Linux v4
9.10. Appliance Mode
The Appliance Mode can be enabled for Horizon or XenDesktop or Imprivata connections as well as
SPICE client sessions. If you run an Appliance Mode, no other application access is possible. Only the server
session for the specified Horizon/Imprivata/XenDesktop delivery server or for Red Hat desktop
virtualization is shown.
The system hotkey Ctrl + Alt + s for launching the IGEL setup application does not work in the Appliance
Mode. Please use Ctrl + Alt + F2 instead.
1. Enable one of the appliance options.
2. Configure access to the relevant hypervisor of the virtualization platform. i.e. to the VMware Horizon
Server, XenDesktop Delivery Server or Red Hat Enterprise Virtualization Hypervisor.
9.11. NoMachine NX
If you configure an NX session, retain the NX server data and select the session type (Unix, Windows, VNC).
Depending on the session type chosen, either the Unix Desktop, Windows Desktop or VNC Desktop setup
pages are enabled to allow further configuration.
Abbildung 42: NX server configuration
The IGEL setup pages for NX sessions are essentially an adapted graphical user interface for the NoMachine
NX Client. Further information regarding configuration (performance, services etc.) can be found in the
original documentation provided by NoMachine: http://www.nomachine.com/documents.php.
80
IGEL Technology GmbH
Universal Desktop Linux v4
9.12. SSH Session
This section describes the procedure for configuring an SSH session.
Use the SSH session to launch a remote application on the host via SSH (Secure Shell) and display it on the
terminal. SSH allows secure, encrypted communication between two hosts or host and terminal via an
unsecured network. X11 connections can also be routed via this secure channel.
Command
All necessary entries for creating an executable command to
remotely launch the application via SSH
User name (remote)
Name of the remote user - The selected user must have a user
account on the remote host.
Computer (remote)
Name or IP address of the remote host from which the remote
application is launched.
Command line
Allows you to enter the name of the application program which
is to be launched.
Forward X11 connection
X11 connections are automatically forwarded to the remote
computer so that each X11 program launched from the shell or
the command passes through the encrypted SSH channel. The
authentication data are also defined automatically. This option
is enabled by default.
Enable compression
Reduces the amount of data transmitted via the data channel This option is disabled by default.
Get protocol version
You must prove your identity to the remote host using one of
the various identification methods. These depend on the
protocol version used. In this area, you can obtain details of the
protocol version after opting for a particular identification
method.
Options
You will find detailed information on SSH and the various authentication methods on the relevant pages of
the manual for your server operating system.
9.13. VNC Viewer
Create a VNC Viewer session in order to be able to access remote computers (VNC server) via the thin
client. Connection options such as the server address or the full-screen mode can be pre-populated for
each session or defined individually when the system starts.
If a server address is specified for the session, the connection dialog will not appear when the session
starts – the connection will be established immediately.
81
IGEL Technology GmbH
Universal Desktop Linux v4
9.14. IBM iSeries Access
IBM iSeries Access for Linux (5722-XL1) offers emulation of the IBM-5250 terminal. A full description of
the emulation is available from IBM by visiting:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzatv%2Frzatvl5250.htm.
The configuration is not accessible until the user confirms that the necessary license is available.
9.15. ThinLinc
ThinLinc is a Linux terminal server solution which uses server based computing to virtualize desktops and
applications. In addition to the ThinLinc framework itself, the package includes a VNC client for
transferring the graphical information of the (virtual) remote desktop or application as well as OpenSSH for
securing the connection by means of encryption.
In the session configuration, you can select display parameters such as the screen size, resolution or
full-screen mode. You can also optimize the compression in order to conserve bandwidth. The SSH port can
be adapted accordingly to meet your needs. The standard port 22 is pre-set.
You can map various local resources to a ThinLinc session:
•
•
•
•
Printers
Serial connections
Local files, e.g. NFS with read and/or write authorization
Audio devices such as audio output through local speakers
The desktop can be mirrored for the purposes of a ThinLinc session. This option is disabled by default.
You will find further information on setting up the session in the &quot;Client Configuration&quot; chapter of the
ThinLinc administration handbook: http://www.cendio.com/resources/docs/adminguide.pdf.
9.16. PowerTerm WebConnect
You can access the following applications locally or remotely via PowerTerm WebConnect:
•
•
•
•
Windows terminal server
A virtual desktop (on hypervisors such as VMware, Microsoft, Xen and Virtual Iron)
Blade PCs
Legacy hosts
 Enter the host name of the WebConnect server you would like to establish a connection to.
The server configuration is described in Ericom's WebConnect documentation:
http://www.ericom.com/doc/QRG/WebConnectGettingStarted.pdf.
82
IGEL Technology GmbH
Universal Desktop Linux v4
9.17. PowerTerm terminal emulation
The PowerTerm InterConnect software we use in IGEL Linux is the official Linux version from ERICOM
Software Ltd.
To use your Ericom PowerTerm Terminalemulation you need a free license key from IGEL. To get to the
activation form please register yourself at our support and ticket system
(https://www.igel.com/members-area/login-logout.html).
1. Click on Add New Session.
2. Select PowerTerm as the session type.
The PowerTerm Emulation Setup window opens.
Abbildung 43: PowerTerm Emulation setup
This setup offers a good overview of the emulation types supported.
The setup pages used here were designed to look as similar as possible to the setup pages described in the
original documentation from ERICOM Software Ltd. You will find detailed information on configuring the
PowerTerm software in the PowerTerm manual on the Ericom documentation website
(http://www.ericom.com/help.asp).
9.18. X Session
Set up the basic connection data (type, server and command) on the server side and specify the necessary
hotkey and window parameters in order to launch an X session.
83
IGEL Technology GmbH
Universal Desktop Linux v4
9.19. Firefox Browser
In order to allow central configuration via the IGEL UMS, the original configuration parameters for the
Firefox web browser are assigned to the IGEL setup. Most global settings can be changed for each browser
session.
9.19.1. Firefox Browser Session
The original Firefox parameters are pre-set under Settings. The standard settings are carried over from the
Browser Global setup.
The following settings for the browser session can also be configured:
Window
Allows you to specify the full-screen mode and multi-monitor options as well as the
Firefox language / prevent users making changes to the browser / hide the
configuration page (about:config) and the printer dialog
Symbol bars and
toolbar
Allows you to hide/show toolbar items or complete toolbars in a session / configure a
kiosk mode (browser in full-screen mode, restricted access to toolbars and
autostart/restart configuration)
Hotkeys
Allows you to enable/disable hotkeys used in the Firefox browser.
Context menu
Allows you to enable/disable items in the browser context menu.
9.19.2. Browser Plug-ins
Various plug-ins such as a PDF viewer, Adobe Flash Player or Red Hat Spice are available. However, they
may need to be licensed by the user first. Integration of the SecMacer security solution Net iD can also be
configured here.
Flash Player
Before you can download and install Adobe Flash Player, you need to confirm that the software is licensed
- IGEL Universal Desktop Linux does not contain a license to use the Flash Player.
The external link for downloading the Flash Player is up to date at the time of release of this software.
However, it may change over time.
In addition to the official download source, you can specify your own source in the company network or the
pre-configured firmware update source.
If the Flash Player fails to download via the external link, check the current path and file name in the
browser as these may have changed in the meantime.
84
IGEL Technology GmbH
Universal Desktop Linux v4
9.20. SAP Client
The SAP GUI for Java allows you to access the SAP system. If a configuration file is provided, the
corresponding setting will be used by the client. No other configuration parameters are available in the
IGEL setup.
9.21. Media Player
Set up the Media Player for your multimedia applications here.
The following codecs are licensed via either the Fluendo Codec Pack or the MPEG LA Advanced Feature
Pack:
Supported formats:
Supported codecs:
AVI
MPEG
ASF (restricted under Linux)
WMA
WMV (restricted under Linux)
MP3
OGG
MP3
WMA stereo
WMV 7/8/9
MPEG 1/2
MPEG4
H.264
AC3 is not licensed.
9.21.1. Media Player Global
 Configure universal settings which will apply by default during all Media Player sessions.
If need be, the settings can be changed in the individual sessions.
Window
 Under Image Aspect Ratio, specify the required aspect ratio for video playback.
You can also choose the following options:
•
•
•
•
Full-screen mode
Automatically change window size as soon as a new video is loaded
Main window should remain in the foreground
Show operating components
85
IGEL Technology GmbH
Universal Desktop Linux v4
Playback
 Specify how you would like to play back media files:
Endless loop
Automatically plays back a play list endlessly
until you stop it.
Random mode
Plays back the files in a play list in a random
order.
 If you wish, choose the visual effects to be used during audio playback.
Visualization type
Determines the visualization plug-in.
Visualization size
Determines the visualization size.
Video
Video output
GConf:
System-wide configuration
Auto:
Automatically selects the output
XVideo:
Hardware-accelerated, uses shared memory to write images to the
graphics card memory
Not hardware-accelerated, playback via the X Window System
display protocol
 Specify the brightness, saturation, contrast and color settings for videos.
X11:
Audio
Audio output
Audio output type
GConf:
System-wide configuration
Auto:
Automatically selects the output
ALSA:
Direct output via kernel driver for sound cards
Select Stereo if you are working with an IGEL thin client.
Options
 Specify whether you would like to disable the screen saver during audio playback.
 Specify the network connection speed in order to influence media file playback.
 Specify the necessary buffer size for your network in order to ensure smooth audio and video playback.
 Specify whether you would like to automatically load subtitles as soon as a video begins. Currently, the
coding for subtitles is always UTF-8.
 Specify the font and text size for the subtitles.
86
IGEL Technology GmbH
Universal Desktop Linux v4
Browser Plug-in
If you would like to use the Media Player as a browser plug-in, you can change the configuration values
here.
This will affect manually configured Media Player sessions.
9.21.2. Media Player Sessions
You can set up your own personal Media Player sessions here.
1. Click on Add to create a new session.
2. Specify a session name.
3. Specify which possible ways of launching the session you would like. You may choose a number of
options here.
4. You may like to select the option of using hotkeys and define them.
5. You can also specify whether autostart (following a system start) and/or restart (after a connection is
established) are to be used.
6. For the autostart option, you can also specify by how many seconds the session start is to be delayed.
As soon as you have set up a Media Player session of your own, it will appear in the structure tree under
the Media Player Sessions directory. Your own session in turn contains three folders: Playback, Options
and Desktop Integration.
9.22. Java Web Start Session
In order to be able to access Java web applications, you must enter the address of the necessary JNLP file.
For example, this may be an IGEL UMS console which can also be run as a Java Web Start application.
9.23. VoIP Client
This section describes the procedure for setting up voice-over IP telephony (VoIP). The IGEL Universal
Desktop Linux firmware includes the Ekiga voice-over IP client (http://ekiga.org). This client allows you to
use the SIP (Session Initiation Protocol) and H.323. In addition to the local contact list, the telephone book
can also search the LDAP address books. You will find a detailed description of all Ekiga options under
http://wiki.ekiga.org/index.php/Documentation.
87
IGEL Technology GmbH
Universal Desktop Linux v4
10. Accessories
Information on other accessories provided by the Universal Desktop can be found here.
10.1. Local Terminal
With a terminal session, you can execute local commands via a shell. In this case, the shell is similar to the
Windows DOS command prompt.
It is also possible to access a local shell without a terminal session: You can switch to the virtual terminals
tty11 and tty12 by pressing Ctrl + Alt + F11 / Ctrl + Alt + F12 .
10.2. Card reader
This type of session is used exclusively to read German health insurance cards.
The necessary parameter data depend on the card and the reader used, e.g. Cherry G80 keyboard with
reader. In the future, this function will be adapted to support the new electronic health card . Separate
documentation regarding use of a health insurance card is available on the IGEL download website.
10.3. Setup Session
Specific areas of the setup can be made available to the user, even if the overall setup can only be accessed
by the administrator. This is useful for example for keyboard and mouse settings or for screen
configuration.See Enable Setup Pages for Users.
10.4. Application Launcher
 Show the Setup and Application Launcher on the local desktop or in the start menu, or define hotkeys
and the autostart option.
You can hide various items, e.g. buttons for shutting down or restarting the device, from the user.
88
IGEL Technology GmbH
Universal Desktop Linux v4
10.5. Sound Mixer
Use the sound control to adjust the output volume and the input level as well as the balance between the
input and output.
Abbildung 44: Sound control
The system's default volume can be configured or muted in Accessories &gt; Sound Mixer &gt; Configuration.
These parameters can also be remotely set via IGEL UMS.
10.6. Java Control Panel
The Java Control Panel is an operating console which is used for various purposes.
 Specify how Java runs on your computer on the basis of various parameters.
 Manage temporary files used for the Java plug-in.
By doing this, you allow your web browser to use Sun Java to run applets and Java Web Start. As a
result, you can launch Java applications via the network.
 Check certificates via the operating console. This gives you the security you need to use applets and
applications via the network.
 Define runtime parameters for applets executed with Java plug-in and applications run with Java Web
Start.
Further information can be found at
http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/jcp.html.
89
IGEL Technology GmbH
Universal Desktop Linux v4
10.7. Network Diagnostics
The IGEL Universal Desktop Linux firmware features a number of tools for network analysis. These
include:
•
•
•
•
•
Device information (page 90)
Ping (page 90)
Netstat (page 91)
Traceroute (page 91)
Look-up (page 91)
10.7.1. Device Information
This tool provides information regarding the status of the network device used. This includes:
•
•
•
MAC and IP address
Link speed
Various interface statistics (bytes transferred, errors etc.)
10.7.2. Ping
The Ping tool allows you to send contact queries to a network address. You can specify the exact number of
queries to be sent. Alternatively, you can enable Unlimited Requests which means that the echo requests
will be sent until you stop the process.
The Ping result is shown below, and the Ping duration of the last five Pings is illustrated in a bar chart.
Abbildung 45: Ping network tools
90
IGEL Technology GmbH
Universal Desktop Linux v4
 Enable Program→Signal Tone for Ping to configure the thin client to output an audible signal each time
a Ping is sent.
10.7.3. Netstat
Netstat provides information on active network services with protocol and port information as well as a
routing table and multicast information for your network devices.
10.7.4. Traceroute
With Traceroute, you can trace the route to a network address.
10.7.5. Look-up
The Look-up tool shows various information regarding your network address. The available information
types are shown in this screenshot.
Abbildung 46: Information types for network address
10.7.6. Soft Keyboard (On-screen Keyboard)
Enable the soft keyboard (on-screen keyboard) for use with a touchscreen, e.g. IGEL UD9.
10.7.7. Calibration Pattern
When calibrating your monitor (auto adjust), please use this special pattern. Generally speaking, you will
achieve better results than if you calibrate the monitor with a conventional desktop and windows. Clicking
on the pattern with the mouse closes the application again.
91
IGEL Technology GmbH
Universal Desktop Linux v4
11. Devices
 Click on Hardware Information for an overview of your IGEL thin client device.
11.1. Printers
Various printing systems can be used with the thin client.
11.1.1. CUPS - Common UNIX Printing System
The Common UNIX Printing SystemTM (or CUPS) is the software which allows you to print from within
applications, e.g. from this web browser.
CUPS converts the page descriptions produced by the application, e.g. &quot;Insert Paragraph&quot;, &quot;Draw Line&quot; etc.,
into data which can be read by the printer, and then sends this information to the printer.
With the appropriate configuration, CUPS can use printing devices via the following connections:
•
•
•
•
Parallel (LPT 1, LPT 2)
Serial (COM1, COM2, USB COM1, USB COM2 – with USB serial adapter)
USB (1st and 2nd USB printer)
Network (TCP/IP, LPD, IPP)
Printers
Printers can be created and edited here.
 In the edit dialog, specify a printer name which begins with a letter.
General
 Under Printer Connection, select the interface type for locally connected
printers or the network protocol for network printers.
 Enter the relevant configuration data for the interface or network
printer.
 Select the local printer driver under Manufacturer and Printer Name.
Mapping in sessions
Map printer in NX
sessions:
Makes the printer available in NX sessions.
Map printer in ICA
sessions:
Makes the printer available in ICA sessions.
Map printer in RDP
sessions:
Makes the printer available in RDP sessions.
The remaining parameters are used to select the printer driver in ICA and RDP sessions on Windows
servers.
 Give the name of the driver under Windows which is to be used.
If it does not feature in the list, it can be specified under Use User-Defined Windows Driver Name.
92
IGEL Technology GmbH
Universal Desktop Linux v4
When printing in ICA and RDP sessions, the print data are normally prepared for the printer model by the
Windows printer driver and are passed unchanged from the thin client to the printer. An exception is
encountered when using the Windows driver in ICA sessions:
Manufacturer: Generic,
Model: Generic PostScript
(Citrix Universal Printer Driver Postscript)
In this case, the print data are prepared on the thin client with the help of the printer driver defined above
under Printers for the printer model. This requires thin client resources depending on the size of the print
job.
IPP printer sharing
The IPP (Internet Printing Protocol) offers the following configuration options:
Network or host for sharing Allows printing on the local device from either
local printers
the local or the global network.
Enable IPP printer browsing Allows you to search for shared printers in the
local or global network and show your shared
printers within the network. A shared printer
is visible within the network but it may not be
possible to print from the network if you do
not have the necessary authorization.
11.1.2. LPD - Line Printer Daemon
LPD printers are used by the BSD printing system and are also supported by Windows servers.
Enable LPD print server
Makes the thin client an LPD print server. The CUPS printers defined
under 11.2.1.1 can be addressed under their printer name as a queue
name via the LPD protocol.
Print data conversion
Attempts to automatically recognize whether or not the print data need
to be prepared by the local printer driver. The None option always
forwards the print data unchanged to the printer.
Max. simultaneous connections
Limits the number of print jobs that can be accepted at the same time.
Restrict LPD access
Specifies the sub-networks or hosts from which print jobs can be
accepted.
11.1.3. TCP/IP
You can assign printers connected to your device to a TCP/IP port. The LPT1 (TCP/IP port 3003) is enabled
by default. The printer can be connected to one of the following connections, provided that they are
available on the device:
93
IGEL Technology GmbH
Universal Desktop Linux v4
•
•
•
•
Serial connection (COM 1 or COM 2)
Parallel connection (LPT 1)
USB (USBLP 1)
Additional serial connections: USB adapter or Perle expansion card
Data are forwarded bidirectionally at serial interfaces. This means that other serial devices such as barcode
scanners or scales can be operated too.
11.1.4. ThinPrint
ThinPrint allows the bandwidth provided for the transfer of print jobs to be reduced depending on the
resources available. The ThinPrint client prints either on printers connected to a local interface (serial,
parallel or USB), on an LPD network printer or on a CUPS printer defined on the thin client.
The following parameters can be found on the ThinPrint setup page:
Port number
Specify the port number via which the ThinPrint daemon is to communicate. Make
sure that the port number on the ThinPrint client and the ThinPrint server is the
same (communication will otherwise not be possible).
Bandwidth
Enter a bandwidth value (in bits per second) which is lower than or equal to the
value specified on the ThinPrint server. A higher value, the disabling of client
control or no entry at all means that the ThinPrint server values will be used.
Waiting time between
print attempts
Maximum waiting time (in seconds) if a printer is unavailable
Number of print
attempts
Number of attempts to contact a printer in order to start a print job.
The list of ThinPrint printers is shown on the Printers page.
 Here you can manage printer configurations by adding, editing or deleting printers.
The page provides an overview of pre-configured ThinPrint printers:
Active
Indicates whether or not the printer is visible.
Name of the printer
Name under which the printer can be addressed.
Printer class
Name of the printer class - optional, max. 7 characters without spaces
Device
The following options are available here:
•
+ /dev/ttyS0, /dev/ttyS1, ... serial interface
•
•
+ /dev/lp0, /dev/lp1, ... parallel interface
+ /dev/usblp0, /dev/usblp1, ... USB printer
•
+ Name of a CUPS printer with LPD network printer connection: ThinPrint client
prints via the network to the LPD network printer.
+ Name of another CUPS printer: ThinPrint client forwards print jobs to the
appropriate printer in the CUPS printing system.
•
Standard
Defines the selected device as the standard printer.
94
IGEL Technology GmbH
Universal Desktop Linux v4
11.2. USB Storage Devices
USB storage devices can be configured here.
11.2.1. Storage Device Hotplug
 Specify how USB devices are set up here.
The most important details are
•
•
•
the number of possible devices,
the allocation of drive letters,
the access type available to users in ICA sessions (read and/or write access).
Newly connected devices are automatically recognized by default. The terminal gives an audible signal and
a pop-up window informing you that a new device has been found and will be started appears.
Abbildung 47: USB storage hotplug
11.2.2. Automount Devices
Here you can define the devices which are to be mounted automatically when accessed:
95
IGEL Technology GmbH
Universal Desktop Linux v4
List of automount devices
Overview of the automount devices - The most commonly used devices
such as the disk drive, CD-ROM etc. are pre-configured.
Edit
Opens and enables one of the pre-defined devices
Add
Manual configuration of devices not pre-defined in the automount device
list .
Name
Name given to a device - This name is also used for the sub-directory
created in /autofs/.
Device
Allows you to select a suitable device synonym - This can also be entered
manually.
File system type
Definition of the file system - The auto option should normally be used. If,
however, you use ext2 or a problem occurs, you should clearly indicate the
file system that you use.
Automount time-out
Regulates the time-out period - Specify in seconds how long the system
should wait before the devices accessed are unmounted. The time period
ranges from 0 to 600 seconds (10 minutes).
Do not set the time-out period to zero! This may result in data loss.
11.3. PC/SC Interface
PC/SC is a service which makes smartcard readers and inserted smartcards available to application
programs. RDP and ICA connections make it possible to provide server-side applications with client-side
smartcard readers and smartcards. Local applications, e.g. browsers, can also use smartcards in the
readers. For these functions to work, the PC/SC daemon must be enabled.
 Click on Enable PC/SC Daemon to use the PC/SC interface on the thin client.
The PC/SC Devices Currently Active window shows the smartcard readers which are currently available.
Optional internal readers and a variety of USB smartcard readers are also supported.
96
IGEL Technology GmbH
Universal Desktop Linux v4
12. Security
In order to prevent unauthorized access to the thin client setup which could allow deeper penetration into
your network, it is essential that you set up an administrator password following the initial configuration.
 You can also use an additional user password which offers variable options for permitting restricted
configuration by users.
12.1. Password
 Under Password, set up an administrator password and a user password.
Administrator and user password
Sets passwords for the administrator and user accounts. The
setup will be protected by the administrator password unless
the user has been granted access to specific areas.
By enabling this password, the IGEL setup, shell access to Xterm and access to the console will be
restricted to the administrator. The Reset to Factory Defaults option may only be used with this
password. If the setup is locked by an administrator password single setup pages can be enabled for the
user - see Enable Setup Pages for User.
Remote user password
Sets a password for the remote session user (SSH).
Setup user
Allows the user to access the local setup.
When you enter a password, ensure that the correct keyboard layout is enabled. After all, you will only
see stars instead of characters when entering the password and will not be able to see why the password
was not accepted.
12.2. Login Options
 Here you can configure the local login procedure for the thin client. You can login via the IGEL
smartcard or via the Kerberos protocol, e.g. in a Windows domain.
97
IGEL Technology GmbH
Universal Desktop Linux v4
12.2.1. Smartcard
Anmeldung mit IGEL Smartcard
Aktivieren der lokalen Anmeldung am Thin Client mit IGEL-Smartcard.
Auf der Smartcard abgelegte Sitzungen werden verf&uuml;gbar. Ohne
Smartcard und optionales Passwort ist der Thin Client gesperrt.
IGEL-Smartcard ohne Sperren der
Arbeitsfl&auml;che aktivieren
Aktivieren von auf der Smartcard abgelegten Sitzungen nach Eingabe
eines optionalen Passworts. Der Thin Client wird auch ohne
Smartcard nicht gesperrt.
Firmenschl&uuml;ssel
Gemeinsamer Schl&uuml;ssel der Smartcards und Thin Clients. Zur
Smartcard-Personalisierung siehe IGEL Smartcard (page 100).
12.2.2. AD/Kerberos
Logging in with Kerberos
Enables local login to the thin client via the Kerberos protocol.
AD/Kerberos must also be configured (page 98) for this purpose. The
login can be used for single sign-on in a number of session types
(ICA, RDP).
Link for logging off
Allows you to configure the way(s) in which the user can log off.
12.3. AD/Kerberos Configuration
 Enable and configure Kerberos on these setup pages in order to use this service for login and single
sign-on purposes.
Standard realm
Specifies the standard Kerberos realm for the client. Set this value so that it
corresponds to your Kerberos realm (Windows domain).
DNS look-up KDC
Specifies whether DNS SRV records should be used to find key distribution centers
(KDCs, domain controllers) and other servers for a realm if they are not indicated.
DNS look-up realm
Specifies whether DNS TXT records should be used to determine the Kerberos realm of
a host.
No addresses
If this option is set, the first Kerberos ticket is addressless. This may be necessary if the
client is located behind an NAT device (Network Address Translation).
12.3.1. Realm 1-4
Up to 4 realms where a login is possible can be configured here.
98
IGEL Technology GmbH
Universal Desktop Linux v4
Realm
The name of the realm/the domains where you would like to authenticate yourself.
KDC list
IP or FQDN list of the key distribution centers (domain controllers) for this realm. An
optional port number preceded by a colon can be attached to the host name.
12.3.2. Domain-Realm Mapping
Domain-realm mapping offers translation of a host name into the Kerberos realm name for the services
provided by this host.
Standard domain-realm mapping
This should be enabled if the DNS and realm names match.
Otherwise, you will need to create user-specific entries in the list.
DNS host or domain name
The entry can be a host name or a domain name. Domain names
are indicated by a preceding dot. Host names and domain names
should be entered in lower-case letters.
Realm
Kerberos realm name for this host or this domain
99
IGEL Technology GmbH
Universal Desktop Linux v4
13. IGEL Smartcard
Logging in with IGEL smartcard
Enables local login to the thin client with the IGEL smartcard. Sessions
stored on the smartcard become available. The thin client is locked
without the smartcard and optional password.
Enable IGEL smartcard without
locking the desktop
Enables sessions stored on the smartcard after entering an optional
password. The thin client is not locked – even without a smartcard.
Company key
Shared key for smartcards and thin clients. For details of smartcard
personalization, see IGEL smartcard (page 100).
You can use the optional IGEL smartcard for local authentication and personalized session configuration
(&quot;Flying Doctor Scenario&quot;).
Abbildung 48: IGEL Smartcard
The procedure when using the IGEL smartcard with the internal card reader or an external reading device
(USB) is as follows:
1. Enable the IGEL smartcard solution under Security→ Login→ Smartcard in the setup application.
2. Enter a company key to describe your IGEL smartcard.
3. Save your settings before you start personalizing the card.
4. In the Personalization window, you can set a login password and add sessions to the card.
100
IGEL Technology GmbH
Universal Desktop Linux v4
Session configurations are stored on the card's IC (integrated circuit) and the session can be used on
any IGEL thin client which reads the card.
Abbildung 49: Smartcard personalization
13.1. Company Key
The IGEL smartcard solution also contains a company key. This is an additional code which is written to the
card and which must match the code of the terminal used. If the two codes do not match, the smartcard
cannot be used on that particular terminal. This additional security feature ensures that your terminals
cannot be accessed from outside your company. It can also be used within the company in order to restrict
employees' access to specific terminals.
13.2. Save User and Password
The procedure for saving users and passwords for authentication is as follows:
 Enter the first name and surname of the user.
You will then be prompted to enter the password for this name.
101
IGEL Technology GmbH
Universal Desktop Linux v4
If the Demand Password option is enabled, a pop-up window will always open when a smartcard is
inserted. If the wrong password is entered, access to the terminal will be denied.
If the smartcard is merely used to control access to the terminal, the procedure is as follows:
1. Insert a suitable smartcard.
2. Click on Write to Card in order to write the data to the card.
3. Remove the smartcard once the writing operation is complete.
You can now program the next smartcard.
13.3. Save Sessions
Saving sessions on the smartcard
If an employee uses a number of different terminals or the terminals are used by many different
employees, it may be a good idea to save the sessions used by an employee on their smartcard instead of
on the terminal. In this way, the user only needs to call up the applications they require in order to perform
their duties.
The procedure for saving sessions on the smartcard is as follows:
1. Insert the employee's smartcard into the terminal.
The applications used by the employee are shown on the terminal.
2. Create the sessions you would like to add to the smartcard on the terminal (including an autostart
option and personalization of login information).
In addition to the first name/surname of the card user and an optional password, you can also add to
the smartcard the sessions shown in the Available Sessions area.
3. Once you have added all the required sessions, click on Write to Card in order to save the data on the
smartcard.
13.4. Test Smartcard
 Test the card you have created.
After performing a warm start and inserting the smartcard, the sessions will be shown immediately on the
desktop. Every session which is set to start automatically when you insert the smartcard will be launched.
102
IGEL Technology GmbH
Universal Desktop Linux v4
14. Firmware Customization
Configure the firmware to create your own personal workstation.
14.1. Custom partition
IGEL Linux offers users a data partition on the storage medium (CF card). A download/update function
which loads data from a server and, where appropriate, updates them can be set up for this dedicated
storage area.
If the thin client is reset to the default settings, the customer partition and all data stored on it will be
deleted.
14.1.1. Enabling the partition
Customer partition is disabled by default.
 Click System→Firmware Customization→Custom Partition→Partition in the setup to enable the
customer partition in the IGEL setup for the thin client (or with the IGEL Universal Management
Suite) via the setup path.
The size of the partition is shown in the form of a numerical value (bytes) followed by a multiplier.
Sensible figures are for example 100 K (for 100 KiB = 100 * 1024 bytes) or 100 M (for 100 MiB = 100 * 1024
* 1024 bytes).
Abbildung 50: Activating customer-specific partition
103
IGEL Technology GmbH
Universal Desktop Linux v4
The size of the partition should be set to at least 100 KiB. However, no more than 1000 MiB should be
reserved for the customer-specific partition (based on the 2 GB standard flash storage used in IGEL Linux
thin clients). This is because subsequent firmware updates may require more storage space than the
current version.
Abbildung 51: System feedback
 Click Apply or OK in order to confirm your settings.
The partition will be created and mounted at the specified location.
A status window provides information on the process and gives details of any errors when creating the
partition. If for example there is insufficient space on the storage medium, it will not be possible to create
the partition.
Abbildung 52: Error messages
If you attempt to change the size of a previously created customer partition, you may find that you are
unable to do so if a process is still accessing the partition, e.g. its content is being shown in the terminal
window.
14.1.2. Defining download source
5In order to load data onto the customer partition, at least one source for partition data must be specified
in the Download area.
104
IGEL Technology GmbH
Universal Desktop Linux v4
 Click Add.
Abbildung 53: Defining download source
The transfer protocols are the same as the ones for updating the firmware, e.g. HTTP, HTTPS, FTP. An INF
file which in turn references a tar archive zipped using bzip2 must be given as the target.
The structure of the INF file is as follows:
[INFO], [PART]
Header information
file=&quot;test.tar.bz2&quot;
Zipped tar archive
version=&quot;1&quot;
Version of the file
The files to be transferred must therefore be zipped in a tar archive which is then compressed using
bzip2. This file is referenced in the INF file which is the target of the URL.
The tar archive can be created under Windows, e.g. with the open source program 7-Zip (www.7-zip.org).
This program also allows bzip2 compression. Under Linux, tar and bz2 files can often be created using
onboard resources.
The procedure makes it possible to replace the file(s) on the server with a new version which the thin client
loads the next time it is booted. The Version parameter in the INF file must be increased for this
purpose.
14.1.3. Carrying out actions
Once the customer partition has been mounted or unmounted, commands (Shellscript) can automatically
be executed (Initializing Action and Finalizing Action). For example, a program loaded to the partition can
be launched or closed upon shutdown (the partition will be unmounted again in the process).
105
IGEL Technology GmbH
Universal Desktop Linux v4
14.1.4. Example
A customer-specific background image is to be used. The image
named igel.jpg is zipped into the referenced test.tar.bz2 file
using 7-Zip (see INF file above).
The INF file and the zipped archive are moved to an IGEL UMS web resource. This can be accessed from
the thin client via HTTP.
Make the following settings in the UMS thin client configuration:
1. Enable Customer Partition (size e.g. 1 M) and have it mounted on /custom.
Under Download, a new URL whose target is the test.inf file on the UMS server is created:
http://[ums-server:9080]/web-ressource/test.inf
2. Enter the access data for the web server and enable Automatic Updates if the image is to be replaced
later on.
3. Enter the following copy command as an initialization action in order to copy the unzipped image to the
correct location:
cp /custom/igel.jpg /usr/share/pixmaps/IGEL_UD_4x3_blue.jpg
4. Under User Interface→Screen→Desktop, select the entry Igel blue (4x3) as the background image.
The associated file will be replaced by your own file.
Abbildung 54: Original background image
5. Save your changes in the IGEL Setup and restart the thin client so that it takes the modified settings
from the UMS Server.
The customer partition is created and mounted.
The zipped file is transferred, unzipped and copied to the target directory.
106
IGEL Technology GmbH
Universal Desktop Linux v4
The new background image is loaded and displayed:
Abbildung 55: New background image
To replace this image with a new one:
1. Change the JPG in the test.tar.bz2 file.
2. Increase the version number in the test.inf file.
The new version will be downloaded and used then next time you restart the client.
Executable files can also be loaded to the customer partition and called up after mounting.
14.2. Custom Application
Applications which were loaded onto a customer partition for example can be launched via the Application
Launcher or an icon on the desktop once they have been defined as own applications. In order for this to
be possible, a command to call up the application must be entered under Settings.
14.3. Custom Commands
Custom commands can be mounted at various points in time during the system start.
Basic commands run once during the boot procedure.
The commands are executed at the following times:
107
IGEL Technology GmbH
Universal Desktop Linux v4
Initialization
Not all drivers loaded, not all devices available
Network scripts not started, network not available
Partitions available except firefox profile, scim data, ncp data,
custom partition
Session Early
Not all driver loaded, not all device available
Network scripts started, network not available
Partitions available except firefox profile, scim data, ncp data,
custom partition
Sessions not configured
Session Final
All drivers loaded, all devices available
Network available
Partitions available except custom partition
System daemons not started (CUPS, ThinPrint etc.)
UMS-configuration loaded but not effective
Final
All partitions available
All system daemons started
UMS-configuration effective
Network commands run each time the relevant interface starts (standard eth0). The interface can be
defined by using the environment variable $INTERFACE (eth0, eth1, wlan0).
The commands are executed at the following times:
Network Initialization
Network authentication successful (802.1x, WPA)
No other network settings effective
Network DNS
Executed after change of IP address or hostname
IP address / Nameserver settings effective (e.g. via DHCP)
Network Early
IP address / Nameserver settings effective (e.g. via DHCP)
VPN connected if VPN autostart option is enabled
Network / Host routing configuration not effective
Network Final
Network / Host routing configuration effective
NFS and SMB mounts available
System time synchronized with time server
UMS-configuration loaded but not effective
Desktop commands run each time the X Server starts.
The commands are executed at the following times:
108
IGEL Technology GmbH
Universal Desktop Linux v4
Desktop Initialization
Executed once during the boot procedure
Desktop environment configured but not started
User not logged in (Kerberos, Smartcard etc.)
Desktop Early
Executed once during the boot procedure
Desktop environment started
Message service started
Session D-Bus started
User not logged in (Kerberos, Smartcard etc.)
Desktop Final
Executed after login procedure or desktop restart
User logged in (Kerberos, Smartcard etc.)
User desktop started
Reconfiguration commands run when settings are changed via the local setup or the UMS. The commands
are executed at the following times:
Reconfiguration
Executed after effective change of Thin Client configuration (local
setup, UMS)
14.4. Custom Bootsplash
See the description in the chapter User Interface (page 29).
14.5. Environment Variables
Environment variables allow you to use dynamic parameter content for a number of session types, e.g. so
as not to have to enter ICA or RDP servers for every session. Within the IGEL Setup, the variables can be
found under: System→Firmware Configuration→Environment Variables
Pre-defined variables can also be supplied and distributed via the IGEL UMS. Additional defined variables
can only be used locally and may be overwritten by a UMS configuration.
The following session parameters can be configured though variables:
•
•
•
•
•
ICA - User name (ICA sessions→ *Session name+→Login)
ICA - Citrix Server or Published Application (ICA sessions→*Session name+ -&gt; Server)
XenApp - User name (Citrix XenApp/Program Neighborhood→Login)
RDP - User name (RDP sessions→*Session name+→Login)
RDP - Server (RDP sessions→*Session name+→Server)
How to use environment variables
1. Enable environment variables under Allow Variable Substitution in Sessions.
2. Specify the variable name and content (e.g. Variable Name = SERVER NAME | Value = test server)
3. Enter the variable name in the session parameter field. The name is preceded by a $ sign (e.g.
$SERVERNAME for the server for an RDP session)
109
IGEL Technology GmbH
Universal Desktop Linux v4
In the case of RDP and ICA sessions, the setting is implemented after being saved and is entered into the
session file. With XenApp, the setting is not implemented until a session starts and is running.
14.6. Features
Using this list of available services, you can quickly enable or disable firmware components such as
Powerterm, Media Player etc. If a service was disabled, the associated session type will no longer be
available when the system is restarted. Existing sessions will not be shown but will not be deleted either. A
disabled session type will not be updated during a firmware update. You should therefore disable unused
services in order to speed up update processes.
110
IGEL Technology GmbH
Universal Desktop Linux v4
15. IGEL Support
IGEL Support and Knowledge Base
If you have any questions regarding an IGEL product and are already an IGEL customer, please contact
your dedicated sales partner first.
If you are currently testing IGEL products or your sales partner is unable to provide the help you need,
please fill in the support form after logging on at the IGEL Support Portal
https://www.igel.com/en/members-area/login-logout.html.
We will then contact you as soon as possible. It will make things easier for our support staff if you provide
us with all the information that is available. Please see also our notes regarding support and service
information.
Please visit our IGEL Knowledge Base http://edocs.igel.com to find additional Best Practice and How To
documentation as well as the IGEL Support FAQ
http://faq.igel.com/otrs-igel/public.pl?Action=PublicFAQExplorer;CategoryID=3.
111
IGEL Technology GmbH
Universal Desktop Linux v4
16. Maximum supported screen
resolutions
Linux
Single-View
Dual-View
Device
DVI
UD2-x20
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
32MB
UD2-x21
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
32MB
UD2-x30
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
32MB
UD3-x20
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
32MB
UD3-x21
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
32MB
UD3-x30
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
64MB
UD5-x20
1920 x 1200 1920 x
1200
24bit
1920 x 1200 1920 x 1200 16bit
64MB
VGA
Color depth* DVI
VGA
Color depth* Shared
memory
(BIOS)
Please note: The resolutions above are the maximum configurable resolution for the particular system.
This does not mean that any other resolution below this upper limit can be configured.
112
IGEL Technology GmbH
Universal Desktop Linux v4
17. Supported formats and codecs
The following codecs are licensed via either the Fluendo Codec Pack or the MPEG LA Advanced Feature
Pack:
Supported formats:
Supported codecs:
AVI
MPEG
ASF (restricted under Linux)
WMA
WMV (restricted under Linux)
MP3
OGG
MP3
WMA stereo
WMV 7/8/9
MPEG 1/2
MPEG4
H.264
AC3 is not licensed.
113
IGEL Technology GmbH
Universal Desktop Linux v4
18. Index
Citrix StoreFront / Web Interface ...................... 68
COM ports - serial connections ......................... 60
3
3rd Party VPN-Clients .........................................49
A
About this Manual ................................................ 5
Access Control ....................................................33
Accessories .........................................................89
AD/Kerberos .......................................................99
AD/Kerberos Configuration ................................99
Appearance.........................................................70
Appliance Mode..................................................80
Application Launcher .................................... 13, 89
Audio ............................................................ 74, 86
Authentication ....................................................45
Automount Devices ............................................96
Company Key ................................................... 102
Completing the Setup ........................................ 17
Connections ....................................................... 69
CUPS - Common UNIX Printing System ............. 93
Custom Application ......................................... 108
Custom Bootsplash .......................................... 110
Custom Commands.......................................... 108
Custom partition .............................................. 104
D
Defining download source ............................... 105
Desktop .............................................................. 34
Device Information ............................................ 91
Device Support .................................................. 74
Device support / virtual communication channels
........................................................................... 61
B
Basic principles and requirements .....................24
Devices ............................................................... 93
Bildschirm ...........................................................30
Display, keyboard and allocation of resources .. 77
Boot Menu ..........................................................10
Domain-Realm Mapping .................................. 100
Boot Procedure...................................................10
DPMS ................................................................. 33
Browser Plug-in ..................................................87
Drive mapping.................................................... 59
Browser Plug-ins .................................................84
Drive Mapping ................................................... 73
Buddy Update .....................................................23
DriveLock ........................................................... 62
C
Calibration Pattern .............................................92
E
Emergency Boot................................................. 10
Card reader .........................................................89
Enabling the partition ...................................... 104
Carrying out actions..........................................106
Energy ................................................................ 28
Certificate ...........................................................52
Environment Variables .................................... 110
Certification Authority ........................................52
Example ......................................................53, 107
Change password ...............................................70
Examples and screenshots....................................6
Checking the Client Certificate ...........................53
Cisco....................................................................49
Citrix Access Gateway .........................................71
Citrix ICA - global settings ...................................56
Dial-up connections - ADSL ................................ 48
F
Failsafe Boot - CRC check ................................... 11
Features ........................................................... 111
Firefox Browser.................................................. 84
Citrix ICA - Sessions.............................................65
114
IGEL Technology GmbH
Universal Desktop Linux v4
Firefox Browser Session......................................84
Logging on.......................................................... 69
Firewall ......................................................... 62, 67
Login Options ..................................................... 98
Firmware Customization ............................ 29, 104
Logon ................................................................. 66
Flash Player .........................................................85
Look-up .............................................................. 92
Font Services.......................................................41
LPD - Line Printer Daemon................................. 94
Formatting and meanings..................................... 6
M
Mapping ........................................................59, 72
G
General Display Settings .....................................32
Maximum supported screen resolutions......... 113
General System Information ..............................14
Media Player ...................................................... 85
GeNUCard ...........................................................50
Media Player Global........................................... 85
H
Hosts ...................................................................53
Media Player Sessions ....................................... 87
I
IBM iSeries Access ..............................................82
Mouse ................................................................ 39
ICA global options ...............................................64
IGEL Smartcard .................................................101
N
Native USB Redirection...................................... 76
IGEL Support .....................................................112
NCP .................................................................... 49
IGEL System Registry ..........................................29
Netstat ............................................................... 92
IGEL Universal Desktop Firmware ........................ 8
Network ............................................................. 43
Input ...................................................................38
Network Diagnostics .......................................... 91
Introduction .......................................................... 7
Network Drives .................................................. 54
J
Java Control Panel ..............................................90
Network Integration .......................................... 11
Java Web Start Session .......................................87
NFS Font Service ................................................ 42
K
Keyboard / hotkey assignment ...........................59
Keyboard and additional Keyboard ....................38
Keyboard Commands - Hotkeys .........................41
L
LAN Interfaces ....................................................43
Microsoft RemoteApp ....................................... 78
Multimedia redirection...................................... 63
NFS ..................................................................... 54
NoMachine NX ................................................... 80
O
Options ............................................. 67, 69, 76, 87
P
Password............................................................ 98
PC/SC Interface .................................................. 97
Language.............................................................30
Performance ...................................................... 74
Leostream Connection Broker ............................80
Performance and options .................................. 78
License ................................................................16
Ping .................................................................... 91
Local logon ..........................................................64
Playback ............................................................. 86
Local Logon - RDP ...............................................71
PowerTerm terminal emulation ........................ 83
Local Terminal ....................................................89
PowerTerm WebConnect .................................. 83
115
IGEL Technology GmbH
Universal Desktop Linux v4
PPTP ....................................................................49
Simple Certificate Enrollment Protocol - SCEP .. 51
Printers ................................................... 61, 73, 93
Smartcard .......................................................... 99
Q
Quest vWorkspace Client and AppPortal ...........79
Soft Keyboard (On-screen Keyboard) ................ 92
Quick Installation .................................................. 9
SSH Session ........................................................ 81
Quiet Boot ..........................................................10
Starting the Setup .............................................. 17
R
RDP - global settings ...........................................71
Storage Device Hotplug ..................................... 96
RDP session.........................................................76
System Settings.................................................. 21
Realm 1-4 ............................................................99
System Tools ...................................................... 15
Reconnect ...........................................................68
Reconnecting and updating ................................70
T
TCP/IP ................................................................ 94
Remote Access (SSH / RSH) ................................28
Test Smartcard ................................................. 103
Remote Management.........................................23
ThinLinc .............................................................. 82
RemoteFX Support..............................................75
ThinPrint ............................................................ 95
Reset to Factory Defaults ...................................11
Time and Date.................................................... 21
Routing ...............................................................53
Touchscreen....................................................... 39
S
SAP Client............................................................85
Traceroute ......................................................... 92
Sound Mixer....................................................... 90
Supported formats and codecs........................ 113
Save Sessions ....................................................103
U
Update ............................................................... 22
Save User and Password...................................102
USB redirection .................................................. 62
SCEP ....................................................................52
USB Storage Devices .......................................... 96
Screen Saver and Screen Lock ............................36
User Interface .................................................... 30
Secure shadowing (VNC with SSL) ......................24
Security ...............................................................98
V
Verbose Boot ..................................................... 10
Serial (COM) Ports ..............................................73
Video .................................................................. 86
Server..................................................................66
Virtual Private Network - VPN ........................... 48
Server / logon .....................................................77
VMware Horizon Client...................................... 79
Server location....................................................58
VNC (Shadowing) ............................................... 23
Sessions ........................................................ 14, 56
VNC logging........................................................ 27
Setup Application ...............................................17
VNC Viewer ........................................................ 82
Setup Areas.........................................................18
VoIP Client ......................................................... 87
Setup Search .......................................................19
Setup Session ......................................................89
W
Window...................................................57, 72, 86
Shadow thin clients securely ..............................25
Window settings ................................................ 66
Shutdown and Restart ........................................16
Windows Drive - SMB ........................................ 54
116
IGEL Technology GmbH
Universal Desktop Linux v4
Wireless (Wi-Fi) Connections .............................46
X
X Session .............................................................84
XC Font Service ...................................................41
XDMCP ................................................................33
X-Server ..............................................................11
117
IGEL Technology GmbH
Universal Desktop Linux v4
">

سلام! من یک ربات چت هوش مصنوعی هستم که به طور خاص برای کمک به شما در مورد IGEL Linux v4 Universal Desktop User Guide آموزش دیده‌ام. من سند را به طور کامل بررسی کرده‌ام و می‌توانم به شما کمک کنم اطلاعات دقیقی را که نیاز دارید پیدا کنید یا محتوا را به زبان ساده و واضح توضیح دهم. چه به دنبال راهنمایی در مورد ویژگی‌های خاص، مراحل عیب‌یابی یا استفاده عمومی باشید، می‌توانید سوالات خود را بپرسید. هرچه جزئیات بیشتری در مورد نگرانی‌ها یا نیازهای خود ارائه دهید، من می‌توانم دقیق‌تر و موثرتر به شما کمک کنم!

دستیار در حال تایپ

دستیار از صفحه کلید خارج شده است. لطفا بعدا دوباره امتحان کنید.

به نظر می‌رسد به سندی رسیده‌اید که به چندین زبان نوشته شده است، از جمله زبانی که زبان مادری شما نیست. می‌توانید از پیوندهای زیر برای پنهان کردن موقت صفحاتی که زبان مورد نظر شما را ندارند استفاده کنید.

تبلیغات

مرتبط

IGEL Universal Desktop Linux v5 User Manual

IGEL Universal Desktop Linux v5 User Manual

IGEL Zero HDX Manual

IGEL IZ2 RFX Specification

IGEL Universal Desktop User Guide

IGEL Universal Desktop W7 User Manual

IGEL Universal Desktop W7 User Manual

IGEL Universal Management Suite v5 User Manual

IGEL Universal Management Suite v5 UMS User Manual

IGEL Thin client Universal Desktop Windows Embedded Standard User Guide

IGEL Thin Client User Guide UDS-720 WES

IGEL Universal Management Suite v4 User Manual