Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 38

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 220
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 37
Chapter 5. Printer Features
After creating the symlinks, try connecting to your ThinLinc cluster with a ThinLinc cluster and bring up
an application that lists the available printers. The list of printers should now be limited according to
configuration.
Note: The printer list limitation doesn’t work for applications that use the deprecated cupsGetPrinters
library call. This means that older applications might show the whole list of printers. The access
control are still enforced, which means that even if a disallowed printer is shown in the list of printers,
users can’t submit jobs to it.
Most applications in a modern Linux distribution doesn’t have this problem.
5.5.4. Configuration
Configuration of the printer access control feature is mostly a matter of using tlwebadm (see Chapter 16
for details) to add the hardware address of all terminals as well as information about where they are
located and which printers are to be available for each location.
5.5.4.1. Unknown Terminals / Terminals Without Hardware Address
When a client reports a hardware address that is not present in the database of terminals, or when no
hardware address is reported, the default behaviour is to disallow access to all printers, rendering an
empty printer list for the user.
There is however a way to give even unknown terminals access to one or more printers - define a special
location and check the Use for unknown terminals and terminals without hardware address checkbox.
Then add the printers that should be available for the unknown terminals.
One common configuration is to add such a location and then add the thinlocal printer to this location.
This way, unknown terminals, for example people working from their home computers, will be able to
user their locally connected printer, but no other printer will be available.
5.6. Printer Configuration on Windows Terminal Servers
If your ThinLinc setup uses a Windows Terminal Server for some applications, access to printers for
these applications is handled automatically by redirection over RDP. When rdesktop is started via
tl-run-rdesktop as is the case when applications on Windows Terminal Servers are started via any of the
ThinLinc wrapper commands, the list of printers available to the user on the Linux or Solaris server
running the ThinLinc session is automatically fetched. Each printer is then added to the rdesktop
commandline in a way that makes it appear in the user’s session on the WTS.
One advantage of this feature is that the Section 5.5 will be active even for programs running on
Windows Terminal Servers, since only the printers the user are allowed to see and use are exported.
For some special cases, manually configuring printers on the Windows Terminal Server may be required.
This is the case for example if some application requires that the name of the printer is exactly the same
across sessions, as printers added automatically have names that contain the WTS session ID. For
information on how to configure printers manually, see Appendix D
28
Vista de pagina 37
1 2 ... 33 34 35 36 37 38 39 40 41 42 43 ... 219 220

Comentarios a estos manuales

Sin comentarios