Download page Mapping USB Storage Media into Citrix Sessions.
Mapping USB Storage Media into Citrix Sessions
How to configure USB Storage mapping so that users can access USB storage media attached to the IGEL LX Client within Citrix sessions?
Basic Configuration of the Device
Within the IGEL Setup or a UMS profile, you basically need to configure these parameters:
Activate Devices > Storage Devices > Storage Hotplug > Client drive mapping > Dynamic. This option activates dynamic client drive mapping. It automatically recognizes new storage media as they are connected to the thin client. The thin client beeps and shows a notification while it mounts the new device. The storage devices automatically become usable on the thin client and in Citrix ICA Sessions.
Additional Parameters to Check
The following parameters are set by default, thus storage mapping will work, but maybe for some reason you have changed these and need to adjust them to allow the storage mapping:
Sessions > Citrix > Citrix Global > Mapping > Drive Mapping > Drive mapping (set checkmark)
Sessions > Citrix > Citrix Global > Native USB Redirection > Native USB redirection (remove checkmark)
Sessions > Citrix > ICA/HDX Global > Fabulatech USB Redirection > Fabulatech USB redirection (remove checkmark)
Devices > USB access control > Enable (remove checkmark)
Sessions > RDP > RDP Sessions > [session name] > USB Redirection > Enable Native USB Redirection (global setting)
Sessions > RDP > RDP Sessions > [session name] > Mapping > Enable Drive Mapping (global setting)
Assigning a Drive Letter within the Session (Optional)
subst T: \\tsclient\t
net use T: \\tsclient\t
In this example, "T on IGEL-123456789" is assigned to drive letter T: within the session. You may also assign the mapped drive to another drive letter than is used in its name.
Configuration on the Server Side
On the server side, e.g. with Windows Server 2008R2, a user in the group "Users" with access to the terminal server will have the mapping default. This is true for a newly installed server. But the mapping can be prevented by changing the policies: