Receiver supports client device mapping for connections to XenApp and XenDesktop servers. Client device mapping enables a remote application running on the server to access devices attached to the local user device. The applications and system resources appear to the user at the user device as if they are running locally. Ensure that client device mapping is supported on the server before using these features.
Client drive mapping allows drive letters on the XenApp or XenDesktop server to be redirected to directories that exist on the local user device. For example, drive H in a Citrix user session can be mapped to a directory on the local user device running Receiver.
Client drive mapping makes any directory mounted on the local user device, including a CD-ROM, DVD or a USB memory stick, available to the user during a session. When a server is configured to allow client drive mapping, users can access their locally stored files, work with them during their session, and then save them again either on a local drive or on a drive on the server.
When Receiver connects to XenApp or XenDesktop, client drive mappings are reestablished unless client device mapping is disabled. You can use policies to give you more control over how client device mapping is applied. For more information see the XenApp and XenDesktop documentation.
Users can map drives using the Preferences dialog box. For information on this, see Set preferences.
These settings, however, might not be the optimum in all environments. For example, the default setting that allows users to print to all printers accessible from the user device is the easiest to administer initially, but might create slower logon times in some environments. In this situation, you may wish to limit the list of printers configured on the user device.
Likewise, your organization’s security policies might require that you prevent users from mapping local printing ports. To do so, on the server configure the ICA policy Auto connect client COM ports setting to Disabled.
To limit the list of printers configured on the user device
where printer1, printer2 and so on are the names of the chosen printers. Separate printer name entries by a colon (:).
Receiver for Linux supports the Citrix PS Universal Printer Driver. So, in most cases no local configuration is required for users to print to network printers or printers that are attached locally to user devices. You may, however, need to manually map client printers on XenApp for Windows if, for example, the user device’s printing software does not support the universal printer driver.
To map a local printer on a server
In a UNIX environment, printer drivers defined by Receiver are ignored. The printing system on the user device must be able to handle the print format generated by the application.
Before users can print to a client printer from Citrix XenApp for UNIX, printing must be enabled by the administrator. For more information, see the XenApp for UNIX section in eDocs.
Client audio mapping enables applications executing on the XenApp server to play sounds through a sound device installed on the user device. You can set audio quality on a per-connection basis on the XenApp server and users can set it on the user device. If the user device and server audio quality settings are different, the lower setting is used.
Client audio mapping can cause excessive load on servers and the network. The higher the audio quality, the more bandwidth is required to transfer the audio data. Higher quality audio also uses more server CPU to process.
To set a non-default audio device
The default audio device is typically the default ALSA device configured for your system. Use the following procedure to specify a different device:
AudioDevice = <device>