Product Documentation

Map user devices

Apr 30, 2015

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.

Map client drives

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.

Two types of drive mapping are available:
  • Static client drive mapping enables administrators to map any part of a user device's file system to a specified drive letter on the server at logon. For example, it can be used to map all or part of a users home directory or /tmp, as well as the mount points of hardware devices such as CD-ROMs, DVDs, or USB memory sticks.
  • Dynamic client drive mapping monitors the directories in which hardware devices such as CD-ROMs, DVDs and USB memory sticks are typically mounted on the user device and any new ones that appear during a session are automatically mapped to the next available drive letter 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.

Note: By default, enabling static client drive mapping also enables dynamic client drive mapping. To disable the latter but enable the former, set DynamicCDM to False in wfclient.ini.

Map client printers

Receiver supports printing to network printers and printers that are attached locally to user devices. By default, unless you create policies to change this, XenApp lets users:
  • Print to all printing devices accessible from the user device
  • Add printers

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

  1. Open the configuration file, wfclient.ini, in one of the following:
    • $HOME/.ICAClient directory to limit the printers for a single user
    • $ICAROOT/config directory to limit the printers for all Receiver users—all users in this case being those who first use the selfservice program after the change
  2. In the [WFClient] section of the file type:


    where printer1, printer2 and so on are the names of the chosen printers. Separate printer name entries by a colon (:).

  3. Save and close the file.

Map client printers on XenApp for Windows

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

  1. From Receiver, start a server connection and log on to a computer running XenApp.
  2. On the Start menu, click Settings > Printers.
  3. On the File menu, click Add Printer.
  4. Use the wizard to add a network printer from the Client Network, Client domain. In most cases, this will be a standard printer name, similar to those created by native Remote Desktop Services, such as "HP LaserJet 4 from clientname in session 3".

Map client printers on XenApp for UNIX

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.

Map client audio

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.

You configure client audio mapping using policies. For more information, see the XenApp and XenDesktop documentation.

Note: Client audio mapping is not supported when connecting to Citrix XenApp for UNIX.

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:

  1. Choose and open a configuration file according to which users you want your changes to affect. See Customize Receiver using configuration files for information about how updates to particular configuration files affect different users.
  2. Add the following option, creating the section if necessary:


AudioDevice = <device>

where device information is located in the ALSA configuration file on your operating system.
Note: The location of this information is not standard across all Linux operating systems. Citrix recommends consulting your operating system documentation for more details about locating this information.