Attachment 3527 Details for Bug 23616

Zu prüfende Doku

thin-client-policies_en.tex (text/x-tex), 5.12 KB, created by Moritz Muehlenhoff on 2011-09-14 15:32 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Moritz Muehlenhoff

Created: 2011-09-14 15:32 CEST

Size: 5.12 KB

patch

obsolete

>\begin{ucsTabbox}{'[Client devices]' tab}
>This tab is only found on thin client computers.
>
>\ucsTabentry{Activate access to client devices}
>Selecting this checkbox allows access from this thin client to
>peripherals such as CD-ROM and disk drives connected to this thin
>client.
>\end{ucsTabbox}
>
>
>\begin{ucsTabbox}{'[Sound]' tab}
>This tab sets up the sound output. It is only shown on thin client
>computers.
>
>\ucsTabentry{Sound enabled}
>Selecting this checkbox activates sound support. As standard sound
>support is not activated.
>
>\ucsTabentry{Sound module}
>Normally the setting \emph{auto detect} provides an appropriate driver
>module for sound support automatically. Alternatively, a driver module
>for the sound card can be specified manually in the selection list.
>\end{ucsTabbox}
>
>
>\begin{ucsTabbox}{'[Thin client]' tab}
>This tab is only found on thin client computers. Changed values will
>apply from the next time the thin client is booted. Some input fields
>require a server to be specified. To avoid problems during the
>resolution of names, the fully qualified domain name should always be
>entered. In addition, it must be verified it can be resolved in an IP
>address.
>
>\ucsTabentry{Authentication server}
>The users who log on to this thin client authenticate themselves on
>the servers specified here.
>
>If nothing is entered here and a user tries to log on, the system
>establishes all Kerberos servers using service records in the DNS. The
>system then attempts to authenticate the user using one of these
>Kerberos servers.
>
>\ucsTabentry{File server}
>The file server for the thin client can be entered and edited
>here. The \ucsURL{/home} directory is mounted on the thin client from
>this server when a user logs on, for whom no mountable share is
>defined (see also \ucsMenuEntry{POSIX (Linux/UNIX)} tab in
>Chapter~\ref{module:user:benutzerverwaltung:karteikarte-linux-unix} on
>page
>\pageref{module:user:benutzerverwaltung:karteikarte-linux-unix}). If a
>mountable share is entered for the user, it is mounted. There
>is no need to enter the file server if a mountable share is entered
>for all users. Users can not log on without a mounted home directory.
>
>\ucsExclamation\ucsAttention{If the user data should be saved on the
>  file server by the Linux terminal server, the file server must be
>  mounted on the terminal server manually! It goes without saying that
>  this is not necessary when the terminal server and the file server
>  are in fact the same computer. Windows terminal servers find out
>  where a user's home directory is via the log-in server.}
>
>If more than one file server is entered the thin client tries to
>connect the file server at the top in the \emph{Entries} list
>first. If this fails, it tries the next one, etc.
>
>\ucsTabentry{Linux terminal server}
>One or more Linux terminal servers can be added or edited here for the
>thin client.
>
>A Linux terminal server is a server which provides the programs for
>the Linux workstation on which the \emph{Terminal services} component
>is installed.
>
>The decision of which server is used when multiple entries exist is
>taken automatically by UCS using a load balancing mechanism.
>
>\ucsTabentry{Windows terminal server}
>If the users should be provided with a Windows environment on this
>thin client, a server must be entered in this input field which is
>to provide this Windows interface.
>
>If several Windows terminal servers are entered, the first one in the
>list will be used.
>
>\ucsTabentry{Windows domain}
>If the users should be provided with a Windows workstation on this
>thin client, the name of the Windows domain where the user is
>registered is to be entered in this input field.
>
>\ucsNote{As standard, a \emph{default-settings} policy is created,
>  which is valid for the whole domain. Computers on which the
>  \emph{Terminal services} component is installed enter themselves
>  automatically as Linux terminal servers in the policy when a domain
>  is joined; computers on which the \emph{univention-nfs} package is
>  installed enter themselves as file servers. The package is installed
>  on all UCS servers (DC masters, backups and slaves) as standard.}
>\end{ucsTabbox}
>
>
>\begin{ucsTabbox}{'[Autostart]' tab}
>\emph{This tab is only available on thin clients, managed clients and mobile clients.}
>
>Thin clients can be operated without a log-in mask to start a Citrix
>client automatically and exclusively every time the computer is switched
>on, for example.
>
>\ucsTabentry{Autostart session}
>The name of the autostart script should be entered here which should
>be started the next time the client is started. An autostart script is
>a shell script in which programs are entered which are started each
>time the user \ucsName{autostart} logs in automatically. This script
>must be saved under
>\ucsURL{/var/lib/univention-client-root/etc/gdm/Autostart/} on the
>thin client's terminal server. On a managed or mobile client it is
>saved under \ucsURL{/etc/gdm/Autostart/}.
>
>Examples for integrating the Citrix client, \ucsCommand{nxclient} or
>\ucsCommand{rdesktop} in autostart scripts can be found on a UCS
>server with installed thin client infrastructure package
>(\ucsName{univention-thin-client}) under
>\ucsURL{/var/lib/univention-client-root/etc/gdm/Autostart/}.
>\end{ucsTabbox}
>

Actions: View

Attachments on bug 23616: 3526 | 3527