This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Client Drive Mapping (CDM)
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: Please refer to the Linux VDA system requirements
- VDA
- Windows: Citrix Virtual Apps and Desktops 1912 or later
- Linux: Please refer to the Linux VDA documentation
Client device
- Operating system
- Windows 10 1809 or later
- Linux: Please refer to the Workspace app for Linux system requirements
Related Policies
Please 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 this 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 problems resulting from the incorrect use of the Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.