Get Citrix to Ask Permissions Questions Again

CTX133565

{{tooltipText}}

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

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

Objective

This commodity is intended for Citrix administrators and technical teams just. Non-admin users must contact their company's Aid Desk/It support team and can refer to CTX297149 for more than information.

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

Non-admin users must contact their company'southward Assist Desk/IT back up squad and can refer to

CTX297149 for more than information.

Citrix Virtual Apps and Desktops, formerly XenDesktop, fits the enterprise demand 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 direction environment.

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

Note:When setting Client Selective Trust on a Windows seven Motorcar launching applications using Google Chrome via NetScaler Gateway Site, the application volition never launch. Only Published Desktops volition launch.

Backend could contain any version of XenApp, Web Interface, or StoreFront. Currently being observed on Receiver four.3+. Information technology seems when the Customer Selective Trust is enabled Chrome is unable to notice the ICA file URL. This is currently existence looked into.

If using Windows 10 machines and trying to launch applications using Google Chrome via NetScaler Gateway site, this might neglect. Going into Google Chrome Settings and changing the Privacy/Content settings for Plugins to "Run All Plugins" will resolve information technology. This does non work for Windows seven Machines.

Working Scenarios:
ane. Disabling Client Selective Trust
two. Using IE instead with Client Selective Trust enabled

Background

With the introduction of Receiver 3.10 client, administrators can configure the default behavior for device access when connecting to a Citrix XenDesktop or XenApp surroundings. By default, the Desktop Viewer client device restrictions are based on the Cyberspace region and this beliefs tin exist inverse 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 announced when accessing local files, webcams, or microphones:

• HDX File Access

• HDX Microphone and Webcam

---

Instructions

To configure default device access beliefs of Receiver, XenDesktop or XenApp, consummate the following steps:
Annotation : I n the ADM template at that place is the 'Create Client Service Trust Fundamental' value, which can exist used to automatically create all the required registry keys otherwise i mport registry keys outset and make changes in registry values as explained and then employ ADM files and perform changes for ADM files. If you have applied ADM files get-go and then registry changes, in that location could be a possibility of continued unresolved issues. Using ADM files ONLY and not importing registry hive or making changes to registry values volition not resolve the issue. Both steps are required and should exist applied in the correct club: Footstep 1. Registry Hive, Step 2. ADM File.
It is also applicable for Citrix Receiver 4.x.

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

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

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

   Note: The key "HKEY_CURRENT_USER\SOFTWARE\Citrix\ICA Client\Client Selective Trust" has college priority than "HKLM\SOFTWARE\Citrix\ICA Customer\Client Selective Trust". This Fundamental will be created every time a user makes changes in the preferences of Receiver. Every bit this key has priority, it needs to exist deleted at every reboot.

3. In the appropriate region(s), modify the default value of any of the post-obit resources co-ordinate to the list of Admission Values:

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

Admission Values:

• 0 = No Access

• one = Read Simply Access

• two = Full Access

• iii = Prompt User for Admission

4. Consign the Client Selective Trust primal to a new .reg file.

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

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

Note: Included in the Cypher archive are the Group Policy ADM files specifically for x86 or x64 operating systems which create the required registry keys on the client automobile and add together 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

---

Additional Resources

---

Disclaimer

Caution! Using Registry Editor incorrectly tin cause serious bug that might require you to reinstall your operating arrangement. Citrix cannot guarantee that problems resulting from the incorrect utilize of Registry Editor can be solved. Use Registry Editor at your ain risk. Be sure to support the registry before you edit information technology.

jenningsasequou2000.blogspot.com

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

Share this post