Citrix Do Not Ask Me Again for This Site

CTX133565

{{tooltipText}}

How to Configure Default Device Access Behavior of Receiver, XenDesktop and XenApp

Article | How To / General Question Configuration | {{likeCount}} found this helpful | Created: {{articleFormattedCreatedDate}} | Modified: {{articleFormattedModifiedDate}}

Objective

This article is intended for Citrix administrators and technical teams only. Non-admin users must contact their company's Assistance Desk-bound/It support squad and can refer to CTX297149 for more information.

This article is intended for Citrix administrators and technical teams but.

Non-admin users must contact their company's Aid Desk/Information technology back up team and can refer to

CTX297149 for more information.

Citrix Virtual Apps and Desktops, formerly XenDesktop, fits the enterprise demand to bring both VDI and apps into a user-axial experience.

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

This commodity describes how to configure the default device admission beliefs of Receiver, XenDesktop and XenApp.

Notation:When setting Customer Selective Trust on a Windows seven 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, Spider web Interface, or StoreFront. Currently beingness observed on Receiver 4.iii+. It seems when the Client Selective Trust is enabled Chrome is unable to observe 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:
ane. 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. Past default, the Desktop Viewer client device restrictions are based on the Internet region and this behavior tin can exist changed by creating the Client Selective Trust feature registry keys nether the HKey_Local_Machine hive in the registry and past 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 : I n the ADM template there is the 'Create Client Service Trust Key' value, which tin exist used to automatically create all the required registry keys otherwise i mport registry keys beginning and make changes in registry values as explained and so use ADM files and perform changes for ADM files. If you have applied ADM files first and and so 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 social club: Step 1. Registry Hive, Step 2. ADM File.
It is also applicable for Citrix Receiver 4.x.

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

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

2. Open ane of the following registry keys on the computer:
   HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Customer\Client Selective Trust
   Or
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Client Selective Trust.

   Notation: The key "HKEY_CURRENT_USER\SOFTWARE\Citrix\ICA Client\Customer Selective Trust" has higher priority than "HKLM\SOFTWARE\Citrix\ICA Client\Client Selective Trust". This Central will be created every fourth dimension a user makes changes in the preferences of Receiver. As this key has priority, it needs to exist deleted at every reboot.

3. In the appropriate region(southward), change the default value of any of the post-obit resource according to the list of Access Values:

Resource Key	Resource Description
FileSecurityPermission	Client Drives
MicrophoneAndWebcamSecurityPermission	Microphones and Webcams
ScannerAndDigitalCameraSecurityPermission	USB and Other Devices

Access Values:

• 0 = No Access

• 1 = Read Only Admission

• 2 = Total Access

• 3 = Prompt User for Access

4. Export the Client Selective Trust central to a new .reg file.

5. Import the modified .reg file on each customer device.

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

Notation: Included in the Null annal 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 power to modify the values every bit explained in the preceding section. If an Organizational Unit (OU) or grouping of computers contains multiple architectures, ensure to use a method such equally Windows Management Instrumentation (WMI) filtering to apply the advisable settings.

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

---

Additional Resources

---

Disclaimer

Caution! Using Registry Editor incorrectly tin can cause serious issues that might crave you to reinstall your operating system. Citrix cannot guarantee that issues resulting from the incorrect employ of Registry Editor tin be solved. Apply Registry Editor at your own risk. Be sure to back up the registry before you lot edit it.

clarksontich1952.blogspot.com

Source: https://support.citrix.com/article/CTX133565

Share this post