30-04-2021

Citrix Workspace Local Drive Access



downloadTemplates .zipWhy can't I download this file?

Allowing the Citrix ICA client to access your local disk If you are having issues with the Citrix ICA security setting when running applications in the Virtual Office CS or SaaS environment, you need to modify webica.ini to force the ICA client security setting to allow access. Here are steps to access files on your local computer's hard drive, optical disks, or thumb drives. From Inside of the Citrix desktop. Click on the Windows Start Button and click on Computer. You will see your common network drives (G, Q, U, etc). To configure default device access behavior of Receiver, XenDesktop or XenApp, complete the following steps: Note: I n the ADM template there is the 'Create Client Service Trust Key' value, which can be used to automatically create all the required registry keys otherwise i mport registry keys first and make changes in registry values as explained and then apply ADM files and perform changes. Expand Drives Click Connection - Enable - Do Not Connect Client Drives at Logon Click Mappings - Disable Click OK. Right click policy - Apply this policy to Either apply to users or the virtual machine names depending on your requirement. If applying to users best practise is to create a group, one local and one global.

Applicable Products

  • Citrix Workspace App
  • Citrix Virtual Apps and Desktops
  • XenDesktop
  • XenApp
  • Receiver for Windows

Objective

This article is intended for Citrix administrators and technical teams only. Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.
This article is intended for Citrix administrators and technical teams only.
Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.
Citrix Virtual Apps and Desktops, formerly XenDesktop, fits the enterprise need to bring both VDI and apps into a user-centric experience.

Citrix Virtual Apps, formerly XenApp, fits the enterprise need to bring legacy apps into a cloud management environment.

This article describes how to configure the default device access behavior of Receiver, XenDesktop and XenApp.
Note: When setting Client Selective Trust on a Windows 7 Machine launching applications using Google Chrome via NetScaler Gateway Site, the application will never launch. Only Published Desktops will launch.

Backend could contain any version of XenApp, Web Interface, or StoreFront. Currently being observed on Receiver 4.3+. It seems when the Client Selective Trust is enabled Chrome is unable to find the ICA file URL. This is currently being looked into.

If using Windows 10 machines and trying to launch applications using Google Chrome via NetScaler Gateway site, this might fail. Going into Google Chrome Settings and changing the Privacy/Content settings for Plugins to 'Run All Plugins' will resolve it. This does not work for Windows 7 Machines.

Working Scenarios:
1. Disabling Client Selective Trust
2. Using IE instead with Client Selective Trust enabled

Background

With the introduction of Receiver 3.x client, administrators can configure the default behavior for device access when connecting to a Citrix XenDesktop or XenApp environment. By default, the Desktop Viewer client device restrictions are based on the Internet region and this behavior can be changed by creating the Client Selective Trust feature registry keys under the HKey_Local_Machine hive in the registry and by modifying the required values.
With the default value, one of the following dialog boxes appear when accessing local files, webcams, or microphones:

  • HDX File Access
  • HDX Microphone and Webcam

Instructions

To configure default device access behavior of Receiver, XenDesktop or XenApp, complete the following steps:
Note: In the ADM template there is the 'Create Client Service Trust Key' value, which can be used to automatically create all the required registry keys otherwise import registry keys first and make changes in registry values as explained and then apply ADM files and perform changes for ADM files. If you have applied ADM files first and then registry changes, there could be a possibility of continued unresolved issues. Using ADM files ONLY and not importing registry hive or making changes to registry values will not resolve the issue. Both steps are required and should be applied in the correct order: Step 1. Registry Hive, Step 2. ADM File.
It is also applicable for Citrix Receiver 4.x.

Citrix Workspace Local Drive Access Time

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

  1. Download the appropriate registry settings file that is attached to this article and import to a client device.
    Note: The attachment contains the file for a 32-bit and a 64-bit operating system.

  1. Open one of the following registry keys on the computer:
    HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientClient Selective Trust
    Or
    HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixICA ClientClient Selective Trust.
    Note: The key 'HKEY_CURRENT_USERSOFTWARECitrixICA ClientClient Selective Trust' has higher priority than 'HKLMSOFTWARECitrixICA ClientClient Selective Trust'. This Key will be created every time a user makes changes in the preferences of Receiver. As this key has priority, it needs to be deleted at every reboot.

  2. In the appropriate region(s), change the default value of any of the following resources according to the list of Access Values:

Resource Key

Resource Description

FileSecurityPermission

Client Drives

MicrophoneAndWebcamSecurityPermission

Microphones and Webcams

ScannerAndDigitalCameraSecurityPermission

USB and Other Devices

  • 0 = No Access

  • 1 = Read Only Access

  • 2 = Full Access

  • 3 = Prompt User for Access

  1. Export the Client Selective Trust key to a new .reg file.

  2. Import the modified .reg file on each client device.

  3. This process can be automated by using a log on script.

Note: Included in the ZIP archive are the Group Policy ADM files specifically for x86 or x64 operating systems which create the required registry keys on the client machine and add the ability to modify the values as explained in the preceding section. If an Organizational Unit (OU) or group of computers contains multiple architectures, ensure to use a method such as Windows Management Instrumentation (WMI) filtering to apply the appropriate settings.


For clients supporting adml/admx format templates follow: https://msdn.microsoft.com/en-us/library/bb530196.aspx

Citrix Receiver Access Local Files

Additional Resources

  • Citrix Documentation - Configure Receiver with the Group Policy Object template
  • ​CTX124921 - Citrix Online Plug-in 12.0 Ignores Webica.ini Settings
  • Citrix Receiver - Latest Download

Disclaimer

Caution! Using Registry Editor 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 Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.