Citrix DaaS

Client Drive Mapping (CDM)

September 7, 2023

Contributed by:

Client Drive Mapping makes storage drives on the client endpoint available inside a Citrix HDX session to allow files and folders to be transferred from the client to the session host, and vice versa. This feature is enabled by default with both read and write privileges. To prevent users from adding or changing files and folders on mapped client-devices, enable the Read-only client drive access policy setting. When adding this setting to a policy, ensure that the Client drive redirection setting is set to Allowed and is also added to the policy.

As a security precaution, endpoint drives are mapped without the run permission by default. To allow users to run executables directly from the mapped client drives, edit the ExecuteFromMappedDrive registry value in the session host. For details, see Mapped client drives in the HDX features managed through the registry section.

Requirements

The following are the requirements for using CDM:

Citrix Control plane

Citrix Virtual Apps and Desktops 1912 or later
Citrix DaaS

Session host

Operating system
- Windows 10 1809 or later
- Windows Server 2016 or later
- Linux: Refer to the Linux VDA system requirements
VDA
- Windows: Citrix Virtual Apps and Desktops 1912 or later
- Linux: Refer to the Linux VDA documentation

Client device

Operating system
- Windows 10 1809 or later
- Linux: Refer to the Workspace app for Linux system requirements

Refer to Policy settings reference section for CDM settings.

Double-hop scenarios

CDM is supported in double-hop scenarios. By default, the client endpoint’s drive is mapped to the second hop session and the first hop’s drives are not available. However, this can be set so that the first hop’s drives are mapped in the second hop’s session instead of the client endpoint’s drives.

To configure the functionality, edit the following registry value:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive\
Value name: NativeDriveMapping
Value type: REG_SZ
Value data:
- True - Maps the drives of the first hop session in the second hop session
- False - Maps the drives of the client endpoint in the second hop session

Note:

Editing the registry incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that the problems resulting from an incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk. Be sure to back up the registry before you edit it.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Client Drive Mapping (CDM)

September 7, 2023

Contributed by:

September 7, 2023

Contributed by:

Client Drive Mapping (CDM)

Requirements

Citrix Control plane

Session host

Client device

Related Policies

Double-hop scenarios

In this article