banner



Home  ›  How To Configure Citrix Receiver For Mac To Manually Add Http Stores

How To Configure Citrix Receiver For Mac To Manually Add Http Stores

Written By Wednesday, May 25, 2022 Add Comment Edit

Navigation

Workspace app is the new proper noun for Receiver. This post applies to all Workspace app versions, including the Electric current Release version 2205, and the LTSR versions 2203.one and 1912.7000.

  • Change Log
  • Workspace app versions
  •  Overview
    • Workspace app Modules
    • Workspace app Discovery and Buoy Procedure
    • Virtual Monitors
  • Uninstall One-time Receiver Clients
  • Installation and Configuration
    • Administrator vs not-administrator
    • Workspace app Machine-Update
    • Splash Screen
    • Add together Account Wizard
    • CitrixWorkspaceApp.exe Control line switches
    • Workspace app Registry values
    • Workspace app Group Policy settings
    • Client-side Registry for Microsoft Border
  • Workspace app ADMX GPO Template
  • Pass-through Authentication
  • Automatically add StoreFront Accounts to Workspace app
  • Control Shortcut placement on Desktop and Showtime Menu – and Workspace Command (Session Reconnect)
  • Enable Prelaunch
  • Control Device Mapping Prompts
  • Desktop Lock
  • Employ Studio to configure Workspace app Accounts in Published Desktop
  • Published Desktop – configure Workspace app to place shortcuts
  • Script / Automate Workspace app and Receiver Self-Service
  • Microsoft Teams
  • Skype for Business concern
  • Troubleshoot:
    • Citrix QuickLaunch
    • Workspace app Logging
    • Clean upward Duplicate Stores

💡 = Recently Updated

Alter Log

  • 2022 May 16 – updated unabridged article for Workspace app 2205
  • 2022 April 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7 Hotfix i
  • 2022 Apr 7 – Versions – updated for Workspace app 2203.one LTSR
  • 2022 Apr seven – updated entire article for Workspace app 2204.1
  • 2022 Mar 17 – Versions – updated for Workspace app 1912 LTSR Cumulative Update vii
  • 2022 February 7 – updated entire commodity for Workspace app 2202
  • 2021 Dec ix – Versions – updated for Workspace app 1912 LTSR Cumulative Update 6
  • 2021 Dec eight – updated entire article for Workspace app 2112.1
  • 2021 Oct 4 – updated entire article for Workspace app 2109.1
  • 2021 Sep 29 – updated entire article for Workspace app 2109
  • 2021 Aug 30 – updated entire article for Workspace app 2108
  • 2021 Aug eleven – Versions – updated for Workspace app 1912 LTSR Cumulative Update 5
  • 2021 July 29 – updated entire commodity for Workspace app 2107
  • 2021 June sixteen – updated entire article for Workspace app 2106
  • 2021 May 11 – Workspace app 1912 CU4 and Workspace app 2105 and newer fix security vulnerabilities
  • 2021 May 10 – updated unabridged commodity for Workspace app 2105
  • 2021 May x – Versions – updated for Workspace app 1912 LTSR Cumulative Update four
  • 2021 Mar 23 – updated entire article for Workspace app 2103.1
  • 2021 Mar sixteen – updated entire article for Workspace app 2103
  • 2021 Feb ane – updated entire article for Workspace app 2102
  • 2021 Jan xx – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 Dec eighteen – updated entire article for Workspace app 2012.1
  • 2020 December 8 – updated unabridged commodity for Workspace app 2012
  • 2020 Nov 2 – updated entire article for Workspace app 2010
  • 2020 Oct fifteen – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct 1 – updated entire commodity for Workspace app 2009.6
  • 2020 Sep 24 – updated entire commodity for Workspace app 2009.5
  • 2020 Sep 15 – updated entire article for Workspace app 2009

Workspace app Versions

Workspace app is the new name for Receiver.

The systray icon for Workspace app is blue instead of black, only Workspace app is otherwise identical to Receiver, except for new features that are only in Workspace app (east.g. Browser Content Redirection, App Protection).

Workspace app uses a YYMM (twelvemonth/month) versioning format, of which version 2205 (22.v.i) is the newest.

Workspace app 2009 and newer have the new Citrix logo.

Workspace app 1912 and newer support App Protection. Information technology'due south available in both the LTSR versions (1912 and 2203) and the Electric current Release 2205 version.

There are two LTSR (Long Term Service Release) versions of Workspace app: 2203.1, and 1912 Cumulative Update vii (aka xix.12.7000) (or 1912 Cumulative Update seven Hotfix 1). 1912 CU5 and newer comprise many Teams optimization enhancements. The LTSR versions of Workspace app do non support Browser Content Redirection (BCR) because the embedded browser is not included in the LTSR Workspace app.


Workspace app Modules

The Workspace app installer deploys multiple modules. Here are the important ones:

  • ICA Engine (wfica.exe) – process that uses the ICA protocol to connect to published apps and desktops.
  • Self-Service (selfservice.exe) – gets icons from StoreFront and displays them in a Window. When an icon is clicked, Self-service passes the ICA file to the ICA Engine to establish a connectedness.
  • Single Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs afterwards an ICA connection is established
  • Workspace Auto-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The most recent name for this component is Citrix Workspace Update.

The PNAgent module is not included in Workspace app. The older Receiver Enterprise includes the PNAgent module, simply does not include Cocky-Service. The last version of Receiver Enterprise is 3.4.

Custom ICA files are no longer supported. However, Ryan Butler has created a script that asks StoreFront for an ICA file. Explicit credentials are supported. Find the script at Github.

Workspace app Discovery and Buoy Process

If you lot are using Workspace app'due south built-in user interface (instead of a web browser), then Workspace app starting time prompts you to perform discovery, which is likewise called Add Business relationship.

The Citrix logo changed in Workspace app 2009 and newer.

The Add Account sorcerer inverse in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Cloud Workspace FQDN. Merely enter the FQDN. At that place's no need to enter https or a path.

Workspace app will contact the FQDN and request download of the StoreFront Provisioning File.

  • If yous entered a StoreFront FQDN, then Workspace app will download the Provisioning File straight from the StoreFront server.
  • If you entered a Gateway FQDN, so Gateway will showtime prompt the user to cosign. After authentication, Gateway volition connect to its configured Business relationship Services accost, and download the Provisioning File from StoreFront. The Account Services accost is configured in the NetScaler Gateway Session Profile on the Published Applications tab.

If your StoreFront server is configured with multiple stores, then the user volition be prompted to select a shop. Unfortunately, in that location's no configuration choice in NetScaler Gateway to force a particular store.

  • One workaround is to hide the store that you don't desire visible externally. Come across How to configure Receiver to a Shop that is not advertised for special syntax.

The Provisioning File downloaded from StoreFront is an XML document containing values for several items configured in the StoreFront console. You can export the Provisioning File from the StoreFront console by correct-clicking a Shop.

The ReceiverConfig.cr Provisioning File looks something like this:

Here are the values in the Provisioning File:

Workspace app reads the Provisioning File, and configures itself past inserting the file'south contents into the user's registry. The values are located nether HKCU\Software\Citrix\Dazzle\Sites and HKCU\Software\Citrix\Receiver\SR. If you performed discovery through NetScaler Gateway, notice that the internal Base of operations URL is added to the user's registry.

Once Workspace app is configured, it then performs the following steps:

  1. Endeavor to connect to the Internal Beacon.
  2. If the Internal Buoy is reachable, connect direct to the StoreFront Base URL (Address).
  3. If the Internal Beacon is not reachable:
    1. Attempt to connect to the External Beacons. If the External Beacons are not reachable, so stop attempting to connect.
    2. Connect to the Gateway address configured in the Provisioning File. If there is more than than one Gateway, connect to the Gateway that is marked every bit the Default.

Hither are some interesting notes on this connection process:

  • The FQDN you entered during Discovery has absolutely nothing to exercise with how Workspace app connects to StoreFront or Gateway. The bodily connection procedure is controlled by the contents of the Provisioning File, not the Discovery address.
  • If the Provisioning File has multiple Gateways defined, Workspace app uses whichever Gateway is marked as Default. Workspace app and Receiver completely ignore whatever Gateway FQDN you entered during Discovery. To utilise a non-default Gateway, the user must manually select the other Gateway in Workspace app's / Receiver's Advanced Preferences.

In StoreFront Console, if any configuration changes are performed that affect the Provisioning File, do the Workspace apps / Receivers reconfigure themselves automatically? Or exercise users have to remove Accounts and re-add (or Reset Citrix Workspace / Receiver) and so the updated Provisioning File is imported?

Hither are some additional methods of performing Workspace app Discovery:

Virtual Monitors

In Workspace app 1812 and newer, when continued to a published desktop on a single monitor, yous can split the screen into virtual monitors. This feature is intended for large 4K monitors.

Uninstall Erstwhile Clients

Workspace app and Receiver 4.4 and newer includes Receiver Make clean-Up, so, in theory, it's not necessary to uninstall sometime clients first. For more details, see Citrix CTX135933 Upgrading to Citrix Receiver for Windows.

  • In Workspace app 1908 and older (including Receiver), to run it silently, run CitrixWorkspaceApp.exe /RCU /Silent orCitrixReceiver.exe /RCU /Silent.
  • In Workspace app 1909 and newer, /forceinstall switch is the replacement for /rcu switch.

For a reliable upgrade experience, write a script to remove the quondam clients, clean up the registry and file system, and then deploy the new Workspace app.

Citrix Weblog Post Cookbook to Upgrade from Receiver iii.4 for Windows to Receiver 4.2.100 and Citrix Article CTX135933 Upgrading to Citrix Receiver for Windows contains pace-past-step procedure to use Grouping Policy to uninstall Receiver Enterprise 3.4 and install/configure Workspace app.

The Receiver Clean-Up utility for Receiver 4.three and older is designed to assist with the following scenarios:

  • When errors occur during upgrade from an earlier version of Receiver, or Online Plug-in
  • When unexpected behavior or operation is experienced after upgrade from an before Receiver or Online Plug-in
  • If Receiver upgrade is non possible due to feature incompatibility and/or a clean uninstall is required
  • The Receiver Make clean-Up Utility removes components, files, and registry values of Online Plug-in 11.x, 12.x, and Receiver for Windows 3.x, 4.x (Online Plugin-in 13.ten, fourteen.x). This includes the Offline Plug-in component if installed.

Citrix CTX325140: How to Remove Client Files Remaining on Organisation afterward Uninstalling Receiver for Windows.

Weblog posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Client and Install Citrix Receiver 3.x
  • Full listing of Citrix Customer Uninstall Strings

Installation and Configuration

This department contains a summary of all common command line switches, registry keys, and policy settings for Workspace app and Receiver.

Links:

  • Citrix Blog Post: Optimizing Citrix Receiver for Pre-launch and Unmarried Sign-On
  • Citrix CTX202002 How To Deploy Citrix Receiver for Windows Using SCCM 2012 R2

Workspace app 1912 CU5 and Workspace app 2105 and newer fix security vulnerabilities.

CitrixWorkspaceApp.exe current release version 2205, LTSR version 2203.1, or LTSR version 1912 CU7 (aka xix.12.7000) (or 1912 CU7 Hotfix 1) can be installed by simply double-clicking it. Note: LTSR Workspace app does not support Browser Content Redirection. Workspace app 2006 and newer practice non support Windows 7.



Administrator vs not-administrator

  • Non-administrator – If a non-administrator installs Workspace app, then each non-administrator that logs in to the same workstation will have to reinstall Workspace app.
    • Non-ambassador installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.
  • Ambassador – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator account. then the Workspace app but needs to be installed once.
    • Administrator installations are installed to C:\Plan Files (x86)\Citrix\ICA Customer.
    • Ambassador installations of Workspace app 1912 and newer can be manually upgraded by not-administrators by clicking Check for Updates. Older versions cannot be upgraded past non-administrators.
  • Conflicts – If an administrator install of Workspace app is performed on a automobile that has non-ambassador installs of Workspace app, then the ii installations will disharmonize. Best selection is to uninstall non-admin Workspace app and Receiver before installing admin Workspace app. Otherwise, the user's profile probably has to exist reset before Workspace app is functional once more.
    • Citrix article CTX249920 Workspace App for Windows – Your apps are non available at this time – Issue when installing Citrix Receiver in not elevated/per-user install style describes the HKEY_CURRENT_USER registry keys that must be deleted to fix this outcome.
    • For a script to clean-up the per-user installs, encounter Mark DePalma at Citrix Receiver Per-User Install Cleanup.

Machine-Update

Workspace app supports automobile-update.

Some notes:

To troubleshoot Auto-update, run across Citrix CTX226779 Troubleshooting Citrix Receiver Updates.

Auto-update is broken in Receiver for Windows 4.11 and older, and Receiver for Mac 12.9 and older. To ready information technology, manually upgrade to the next version (east.g. Workspace app for Mac), or install the Fix that can exist downloaded from the Receiver download page (Source = CTX234657 Receiver Updater stops working with "Problem Checking for updates" error)

Auto-update is configured using Workspace app grouping policy nether the Citrix Workspace Updates,Receiver Updates or Auto-Update node.




Workspace app Splash Screen

Workspace app shows a Splash Screen on first launch with the text "Citrix Workspace app extends the capabilities of Citrix Receiver".

To prevent this splash screen, fix the post-obit registry value: (source = Dennis Span on Twitter)

  • Fundamental = HKEY_CURRENT_USER\SOFTWARE\Citrix\Splashscreen
    • Value (REG_SZ) =SplashscreenShown = ane

Add together Account Magician

From Citrix CTX135438 How to Suppress the Add together Business relationship Window in Citrix Receiver for Windows: After installation, Workspace app will launch and ask you to add an account. If Workspace app, notice the checkboxExercise not testify this window automatically at logon.

For Workspace app and Receiver 4.4 and newer, FTU (First Time Use aka Add Business relationship Magician) will exist displayed only if a store is non configured. If a store is already configured via control line, GPO, or Citrix Studio, then FTU screen volition non be available after installation. Otherwise, FTU tin can be suppressed past doing one of the following:  (Note: Receiver 4.4.yard and newer has a gear up for preventing the Add Account wizard)

  • Rename CitrixReceiver.exe to CitrixReceiverWeb.exe.
  • RenameCitrixWorkspaceApp.exe toCitrixWorkspaceAppWeb.exe.
  • Install using a command line switch:
    • CitrixWorkspaceApp.exe/ALLOWADDSTORE=Northward
    • CitrixReceiver.exe/ALLOWADDSTORE=Due north
  • Set the registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\EnableFTU=dword:00000000 (or EnableX1FTU =dword:0)
  • Disable the EnableFTU policy setting inReceiver.admx.
  • Change Registry values mail service installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, fix AllowAddStore value to N.
  • Set the registry value: HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\NeverShowConfigurationWizard (REG_SZ) = true
  • Also see Suppressing Add Account dialog at Citrix Docs.

Discover Subconscious Stores

When Receiver is first launched, it must perform Discovery, which is the process of downloading the .xml provisioning file from StoreFront. Discovery is performed by entering a StoreFront FQDN or Gateway FQDN. To observe a subconscious store (a store that's not advertised), add together ?StoreName to the end of the FQDN. CTX214819 How to configure Receiver to a Store that is not advertised.

CitrixWorkspaceApp.exe / CitrixReceiver.exe Command line switches

CTX227370 Citrix Workspace app Commandline Tool contains a GUI tool to build your installer control line.

For unattended installation of Workspace app, see CTA Dennis Span Citrix Workspace App unattended installation with PowerShell or Citrix Receiver unattended installation with PowerShell.

Installer Command Line Switches are detailed at Configure and install Receiver for Windows using command-line parameters at Citrix Docs. Mutual Control line switches include the following:

  • /silent
  • /includeSSON – enables pass-through hallmark. GPO configuration is also required as detailed beneath. 
    CitrixWorkspaceApp.exe /includeSSON  CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A – by default, just SSL (HTTPS) stores are accepted. To allow non-SSL stores: 
    CitrixWorkspaceApp.exe /ALLOWADDSTORE=A  CitrixReceiver.exe /ALLOWADDSTORE=A
  • / STORE0 – To add a store from the installation control line: 
    CitrixWorkspaceApp.exe STORE0="AppStore;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"  CitrixReceiver.exe STORE0="AppStore;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"
    • Workspace App and Receiver four.10 and newer tin discover the Store through NetScaler Gateway. 
      CitrixWorkspaceApp.exe STORE0="AppStore;https://gateway.corp.com#MyStore;On;App Store"  CitrixReceiver.exe STORE0="AppStore;https://gateway.corp.com#MyStore;On;App Store"
  • /SELFSERVICEMODE=False – disables the Self-Service interface and enables shortcut-but mode: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=False  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=motorcar /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets it to LTSR Branch only. AutoUpdateCheck can besides be set up to manual or disabled. AutoUpdateStream tin also be set to Current. See Configuring Citrix Workspace Updates at Citrix Docs. 
    CitrixWorkspaceApp.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR  CitrixReceiver.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR
  • /ENABLEPRELAUNCH=Truthful – enables prelaunch: 
    CitrixWorkspaceApp.exe /ENABLEPRELAUNCH=Truthful  CitrixReceiver.exe /ENABLEPRELAUNCH=Truthful
  • /ALLOW_CLIENTHOSTEDAPPSURL=1 – enables Local App Access: 
    CitrixWorkspaceApp.exe /ALLOW_CLIENTHOSTEDAPPSURL=i  CitrixReceiver.exe /ALLOW_CLIENTHOSTEDAPPSURL=ane

Registry values

HKLM\Software\Wow6432Node\Citrix\Dazzle on the Workspace app machine. All are of type REG_SZ (string) unless specified. Note: several of these are configurable using the Reciever.admx grouping policy template.

  • SelfServiceMode (REG_SZ) = Fake – Turns off Workspace app'due south / Receiver'due south Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = Truthful – If Cocky-Service interface is disabled, places all shortcuts on desktop.
  • UseDifferentPathsforStartmenuAndDesktop (REG_SZ) = True
    • UseCategoryAsStartMenuPath (REG_SZ) = True or False
    • UseCategoryAsDesktopPath (REG_SZ) = True or False
  • StartMenuDir (REG_SZ) = name of binder on Start Card where shortcuts are placed.
  • DesktopDir (REG_SZ) = proper noun of folder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = True – If SSON is enabled and then PreLaunch is already enabled past default.
  • AllowAddStore (REG_SZ) = A – Simply if using http (instead of https) to connect to StoreFront.
  • AllowSavePwd (REG_SZ) = A – Only if using http (instead of https) to connect to StoreFront.
  • UserDomainName (REG_SZ) = pre-filled domain name
  • InitialRefreshMinMs (REG_SZ) = 1 – minimizes the launch delay before contacting shop
  • InitialRefreshMaxMs (REG_SZ) = 1 – minimizes the launch delay before contacting shop
  • RefreshMs (REG_SZ) = 3600000 (i hour) – interval for Receiver icon refreshes. ane hr is the default value.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Hallmark Window Periodically When Receiver is Non Opened
  • MaxSimultaneousFetches (REG_DWORD) = 6  – improves the fourth dimension of loading icons in Starting time Menu
  • MaxSimultaneousSubscribes (REG_DWORD) = 6 – improves the time of loading icons in Commencement Carte du jour
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resources are removed from the server. (or False)
  • SilentlyUninstallRemovedResources (REG_SZ) = True – prevents dialog boxes when resources are removed from the server
  • PreferTemplateDirectory (REG_SZ) = UNC path or local path containing shortcuts copied by the adopt keyword. Give the shortcuts a short name.
  • PnaSSONEnabled (REG_SZ) = True – Enables Single Sign-on for PNAgent (Web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Workspace app is running inside a VDA published desktop, set information technology to 0.
    • If you're having trouble getting sessions to reconnect, see Receiver 4.3 Desktop will non auto-reconnect when logging into a machine at Citrix Discussions
  • AlwaysUseStubs (REG_SZ) = True. Workspace app and Receiver 4.3.100 and newer don't create .exe stubs by default. Fix this to create .exe stubs. Too see Citrix CTX211893 Controlling Shortcut behavior in Receiver 4.three.100.
  • DontCreateAddRemoveEntry (REG_SZ) = True – don't create "Delivered by Citrix" entries in Programs and Features
  • DesktopNameFormatString = format string for shortcut names – For example "{0}_{1}_{2}_{3}". Come across the link for details.
  • SelfServiceFlags (REG_DWORD) = 4 – prevents indistinguishable shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = five to stop external SSON from prompting for authentication
  • ReEvaluateNetwork (REG_SZ) = true – for Beacon detection with Single FQDN

To prevent the Win+G popup on Windows 10 machines:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GameDVR
    • AllowGameDVR (REG_DWORD) = 0

To permit calculation not-HTTPS stores to Workspace app:

  • HKLM\Software\Wow6432Node\Citrix\AuthManager
    • ConnectionSecurityMode (REG_SZ) = Any

To increment ICA bandwidth consumption over high latency links, set:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Advanced\Modules\TCP/IP
    • OutBufCountClient2 = Number of OutBufs (default is 44)
    • OutBufCountHost2 = Number of OutBufs (default is 44)
    • Come across CTX125027 How to Optimize HDX Bandwidth Over High Latency Connections for some recommended values (multiples of 44)

To preclude beacon probing from using proxy, set:

  • HKEY_LOCAL_MACHINE\Software\WOW6432Node\Citrix\Receiver\inventory
    • BeaconProxyEnabled (REG_DWORD) = 0

To enable foreground progress bar, fix:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client
    • ForegroundProgressBar (REG_DWORD) = ane

For customer-to-server file type redirection, gear up:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive
    • NativeDriveMapping="True"

To fix USB devices that emulate a keyboard, set:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Keyboard
    • KeyboardTimer="10"

To prevent "USB Hub Power Exceeded" message, gear up (not needed in 4.ii.100 and newer):

  • HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB (same path for 32-bit and 64-bit, create the keys)
    • DisableInternalDeviceCtlDispatchHook (DWORD) = 0x1

To override the devices that are mapped using optimized channels instead of generic USB, run across Citrix CTX123015 How to Configure Automatic Redirection of USB Devices

Grouping Policy Settings

Copy the Workspace app ADMX template (C:\Program Files (x86)\Citrix\ICA Client\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). Also re-create receiver.adml to C:\Windows\PolicyDefinitions\en-us (or Sysvol).

Edit a GPO that applies to client machines, go to Estimator Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) and configure the following:

  • To enable pass-through authentication: get to | User Authentication |.
    • Local Username and Password – Check the top two boxes.
    • As well add the StoreFront FQDN to the Local Intranet zone in Internet Explorer.
    • Single Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add a store, get to | StoreFront |
    • StoreFront Accounts List – run into the assistance text
  • To enable Auto-Update, get to|AutoUpdate| or|Receiver Updates| or|Citrix Workspace Updates|. (the node was renamed in 4.11 and Workspace app)
    • Enable or Disable AutoUpdate or
    • Receiver Updates or
    • Citrix Workspace Updates
  • To enable Local App Access, go to | User Experience |
    • Local App Access Settings
  • To configure the Self-Service interface, go to | SelfService |
    • Set Manage SelfServiceMode to Disabled to completely disable the Cocky-Service window. This causes all icons to be placed on the Start Menu.
    • Enable Manage App Shortcut and configure it every bit desired.
      • To allow the Self-Service window, merely forestall it from automatically opening (reside in systray), tickForbid Citrix Workspace (or Receiver) performing a refresh of the awarding list when opened. Source
    • Enable Command when Workspace (or Receiver) attempts to reconnect to existing sessions. If this is a VDA published desktop, set it to Disabled. Otherwise configure it equally desired.
    • Gear up Enable FTU to Disabled  to forestall the Add Account wizard from displaying.
    • EnableAllow/Preclude users to publish unsafe content if publishing content that's opens a file or file share.

Enable automatic client drive and client microphone mapping.

  • In a client-side GPO, add the GPO ADM template from http://support.citrix.com/article/CTX133565.
  • Enable the setting Create Client Selective Trust Keys. Run into Below for details.
  • Configure the FileSecurityPermission setting in one or more of the regions.
  • Configure the MicrophoneAndWebcamSecurityPermission setting in ane or more of the regions.

Citrix CTX203658 Get-go Menu Icons Set to Default (Blank Document) After Update to Receiver 4.3.100 – Windows 8 and newer

  • Reckoner Configuration | Policies | Administrative Templates | Windows Components | File Explorer
    • Let the use of remote paths in file shortcut icons = enabled

Deploy Workspace app using Agile Directory

To deploy Workspace app using Agile Directory, configure a GPO with a computer startup script that runs the Workspace app installer executable. Citrix provides sample scripts that tin exist downloaded from one of the Workspace app download pages (Workspace app electric current release version 2205, LTSR version 2203.ane, or LTSR version 1912 CU7 (aka nineteen.12.7000), by expanding Downloads for Admins (Deployment Tools).

Too see CTA Dennis Bridge Citrix Receiver unattended installation with PowerShell.

Change Workspace App's Store Configuration, including Reset Citrix Workspace / Receiver

You lot can modify Workspace app'due south / Receiver'southward configured Store/Account with a couple control lines:

"C:\Programme Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -deleteproviderbyname Corporate  "C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -init -createprovider Corporate https://storefront.corp.com/Citrix/Store/discovery

It is sometimes necessary toReset Citrix Workspace orReset Receiver by right-clicking the Workspace app systray icon, clickingAdvanced Preferences, and clicking theReset link. Y'all can practise this from the control line by running "C:\Plan Files (x86)\Citrix\ICA Client\SelfServicePlugin\CleanUp.exe" -cleanUser -silent. See CTX140149 How to Reset Receiver Using the Command Line.


Receiver for Edge

The Receiver for Web experience in Microsoft Edge is not ideal. Every fourth dimension a user clicks an icon, the user has the click theOpen button afterward the .ica file is downloaded.

Citrix Web log Post Providing Full Receiver for Web Experience for Microsoft Edge has instructions for enabling the Receiver Launcher for Edge. Use your preferred text editor to open web.config for the RfWeb site yous would like to configure (typically C:\inetpub\wwwroot\Citrix\StoreWeb\web.config). Locate the line similar this: <protocolHandler enabled="true" platforms="(Macintosh|Windows NT).*((Firefox/((5[3-ix]|[6789][0-9])|\d\d\d))|(Chrome/((4[ii-ix]|[56789][0-9])|\d\d\d)))(?!.*Edge)". Remove (?!.*Edge) and save the file.

But one time you lot do that, you get a new switch apps prompt every time you launch an icon from Edge.

To finish theswitch apps pop-upwardly, on the client side, edit the registry, get to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Net Explorer\ProtocolExecute\receiver (create missing registry keys), create DWORD valueWarnOnOpen, and fix it to 0 (zero). You tin can apply Group Policy Preferences to deploy this registry value.

Workspace app Group Policy ADMX Template

Many of the Workspace app configuration settings must be configured in group policy. These Workspace app settings are only available afterward installing the GPO templates.

  1. From a machine that has Workspace app installed, find the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • You can as well download the ADMX files from i of the Workspace app download pages (Workspace app current release version 2205, LTSR version 2203.one, or LTSR version 1912 CU7 (aka 19.12.7000), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. Besides copy theen-Usa folder. In Workspace app, the files are nevertheless namedreceiver.admx.
  3. Go to your domain's SYSVOL share and in the Policies folder wait for a PolicyDefinitions folder. If one exists, paste the .admx file directly into the PolicyDefinitions folder. If this binder doesn't be in SYSVOL, instead copy the .admx file to C:\Windows\PolicyDefinitions. Overwrite any existing Receiver ADMX files.
  4. The GPO settings tin can and so be found at 1 of the following:
    • Figurer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace
    • Calculator Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For instance, you can disable Customer Experience Improvement Program (CEIP) from hither.
  6. Encounter https://www.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip for boosted places where CEIP is enabled.
  7. Workspace app 1905 and newer has a setting toDisable sending data to third party (e.g. Google Analytics).
  8. Workspace app 1905 and newer permit you disable embedded browser caching.
  9. Workspace app 1905 and newer accept NetScaler LAN Proxy underNetwork routing > Proxy.
  10. Workspace app 1808 and newer haveUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver 4.12 adds Network Routing | Deprecated cipher suites to configure deprecated ciphers.

  12. Citrix Workspace Updates, (akaAutoUpdate) tin can be configured using group policy. See Configuring Citrix Workspace Updates at Citrix Docs.
  13. Workspace app 1912 and newer tin can be configured to require in-retention ICA files only. The setting chosen Secure ICA file session launch is under the Client Engine node. Encounter Citrix Docs for details on in-memory ICA files instead of writing ICA files to deejay.
  14. Workspace app has settings to hide Advanced Preferences, enable/disable DPI, and enable/disable H265.
  15. Workspace app 4.8 and newer have SplitDevices GPO setting underCitrix Workspace | Remoting customer devices | Generic USB Remoting. See Configuring composite USB device redirection at Citrix Docs.

Pass-through Authentication

Citrix blog mail service – A Comprehensive Guide to Enabling Pass-Through Authentication with XenDesktop 7.five

  1. Run the command
    Ready-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on a Commitment Controller.
    • In XenApp 6.5, this is a Citrix Policy > Calculator > Trust XML Requests.
  2. Login to the PC as an ambassador.
  3. If installing Workspace app, as an administrator, during installation, on the Enable Single Sign-on page, cheque the box side by side to Enable Single Sign-on. And so terminate the installation.

  4. If installing an older version of Receiver:
    1. Become to the downloaded Citrix Receiver. Shift-correct-click CitrixReceiver. exe, and click Copy as path.
    2. Open up a command prompt.
    3. Correct-click to paste the path in the command prompt and then add /includeSSON to the end of the command. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, become to C:\Program Files (x86)\Citrix\ICA Client and look for the file ssonsvr. exe.
  6. And if yous open regedit and go to HKLM\Organization\CurrentControlSet\Control\NetworkProvider\Order, you should meet PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if yous haven't already.
  8. Edit a GPO that is applied to the client PCs where the Workspace app is installed.
  9. Go to Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace.
  10. Expand Citrix Workspace and click User hallmark.
  11. On the right, double-click Local user proper noun and password.
  12. Select Enabled then check the box next to Allow laissez passer-through authentication for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, you can enableSingle Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Internet Explorer. Yous tin can use a GPO to configure this on the client side.
  15. Local Intranet zone should have Automatic logon only in Intranet zone enabled.
  16. Logoff Windows and log back on. In Task Manager you should now meet ssonsvr. exe. This won't appear unless you lot logoff and log back on.
  17. If Workspace app won't connect or is slow to enumerate icons, so you might take to disable Automatically detect settings in IE.
  18. Right-click the Workspace app icon and click Advanced Preferences.
  19. ClickConfiguration Checker.
  20. Check the box side by side toSSONChecker and clickRun.
  21. The lines with ruby x will indicate the result and cosmetic activeness.

StoreFront Accounts

Yous can use a customer-side GPO to add a store (Account) to Workspace app Cocky-Service.

  1. Install the receiver.admx (and .adml) template into PolicyDefinitions if you haven't already.
  2. Edit a GPO that applies to endpoint devices that have Citrix Workspace app installed.
  3. Become to Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
  4. On the right, double-click NetScaler Gateway URL/StoreFront Accounts Listing.
  5. Select Enabled, and then clickShow.
  6. Enter a shop path based on the example shown in the Help box. Workspace app lets you enter a Gateway path. Then click OK.
  7. Note: Gateway paths work in GPO, just might non work when specified in the CitrixWorkspaceApp.exe installation command line.

Published Shortcuts and Reconnect

Citrix CTX200924 How to Customize App Shortcuts with Receiver for Windows

Workspace app has a user interface for setting Shortcut Paths. Right-click the Workspace app systray icon, click Advanced Preferences, and then clickShortcuts and Reconnect, orSettings Option.


From Citrix Docs Configuring application delivery: There are several methods of controlling how Workspace app displays shortcuts on the Outset Menu and Desktop every bit detailed below:

  • Workspace app Registry values
  • receiver.admx GPO Template
  • From StoreFront in C:\inetpub\wwwroot\Citrix\Roaming\spider web.config
  • Published App Keywords (east.g. adopt).
  • Workspace app and Receiver 4.2.100 and newer supports published app Delivery configuration for calculation the shortcut to the desktop. This just works if the app is a Favorite, or if Favorites are disabled, or Mandatory Shop.

Under HKLM\Software\Wow6432Node\Citrix\Dazzle (or HKCU\Software\Wow6432Node\Citrix\Dazzle) are several registry values related to shortcuts. Some of the settings only utilise if SelfServiceMode is set to False. Here are some common options:

  • SelfServiceMode – set to Faux so Receiver disables the Self-Service interface and automatically places all published shortcuts on the Start Carte du jour and/or Desktop. More than details in Configuring application delivery at Citrix Docs.
  • PutShortcutsOnDesktop– set up toTrue to place every app on the desktop
  • DesktopDir – Workspace app places every shortcut on the desktop so it's probably best to place them in a folder.
  • StartMenuDir – If there is potentially a conflict between local apps and remote apps, then you should identify the First Card shortcuts in a binder.
  • PreferTemplateDirectory (with KEYWORDS:adopt=shortcutname) – copies the shortcutname from the template directory to the Start Carte and/or Desktop.

If yous import the receiver.admx (and .adml) into the PolicyDefinitions folder, under Computer Configuration > Administrative Templates > Citrix Components > Citrix Workspace (or Receiver) is a node called SelfService.

Disable the Manage SelfServiceMode setting to hide the Workspace app Window.

Enable the Manage App shortcut setting to control placement of shortcuts.

Workspace app and Receiver 4.2.100 and newer have the ability to configure (or disable) Workspace Command using group policy. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure information technology as desired.

Prelaunch

Staring with Receiver 4.2, prelaunch is automatically enabled if Workspace app is installed with SSON enabled. Otherwise, fix registry values to enable prelaunch. Receiver four.ii.100 prevents the prelaunch icon from appearing on the Starting time Bill of fare.

  • HKLM\Software\[Wow6432Node\]Citrix\Dazzle
    • EnablePreLaunch (REG_SZ) = true or false

Additional customizations can exist configured at:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Prelaunch

  • Name: State
    • REG_SZ: 0 = disable, 1 = just-in-time pre-launch, 2 = scheduled pre-launch
  • Name: Schedule
    • REG_SZ: HH:MM|K:T:Westward:Th:F:S:SU where HH and MM are hours and minutes. M:T:W:Thursday:F:Due south:SU are the days of the week. For example, to enable scheduled pre-launch on Mon, Wednesday, and Friday at 1:45 p.g., gear up Schedule as Schedule=13:45|1:0:1:0:one:0:0 . The session actually launches between 1:15 p.chiliad. and 1:45 p.m.
  • Proper noun: UserOverride
    • REG_SZ: 0  = HKLM overrides HKCU, 1 = HKCU overrides HKLM

Device Admission Behavior (Client Selective Trust)

When connecting to a XenApp/XenDesktop session, you might meet the following:

To configure the default beliefs, see the Citrix Knowledgebase article How to Configure Default Device Access Beliefs of Receiver, XenDesktop and XenApp. Notation: there is a problems fixed in Receiver iv.ii.100 and newer.

  1. Download the ADMX file from http://support.citrix.com/commodity/CTX133565.
  2. Copy the .admx and .adml files to PolicyDefinitions (Sysvol, or C:\Windows).
  3. The.adml file goes in theen-Us binder.
  4. Edit a GPO that applies to the endpoint devices that are running Receiver.
  5. Get to Calculator Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) |Citrix Client Selective Trust (x64).
  6. Enable the setting Create Client Selective Trust Keys.

  7. Then aggrandize the regions, and configure the permission settings as desired.

Desktop Lock

Every bit an culling to Workspace app Desktop Lock, come across Transformer in Citrix Workspace Environment Manager.

External links:

  • Dale Scriven YouTube video – Citrix Desktop Lock installation and configuration
  • Jarian Gibson and Andrew Morgan – Citrix Receiver Desktop Lock
  • An alternative to Desktop Lock – ThinKiosk

Utilise Studio to configure Workspace app Accounts in Published Desktop

In published desktops, Workspace app can be used for placement of shortcuts on the user's Starting time Menu and Desktop. Employ group policy to hide the common program groups and then use Workspace app to place published applications back on the Outset Carte du jour and Desktop based on user's group membership and subscription preference.

  1. In Citrix Studio, on the left, expand the Configuration node, right-click StoreFront and click Add StoreFront.
  2. Enter a descriptive name for the StoreFront server.
  3. Enter the internal https URL of the load counterbalanced StoreFront servers. Add the path to your shop (east.grand. /Citrix/Store) and then /discovery on the end of the URL. The full URL would be like to https://citrix.corp.com/Citrix/Shop/discovery. Click OK.
  4. Edit a Delivery Group that has a published desktop and Citrix Workspace app installed.
  5. On the StoreFront folio, change the selection to Automatically, using the StoreFront servers selected below, and then bank check the box next to the StoreFront URL. Click OK. At present when users launch the published desktop, Workspace app will exist automatically configured with this URL.

Published Desktop – utilise Workspace app to command Shortcuts

If you install Workspace app inside a published desktop (Workspace app on a VDA), then Workspace app can get icons from StoreFront and put those icons on the user'due south published desktop First Menu and Desktop. This is an alternative to using a User Experience Management product to control shortcut placement.

Note: Workspace app tends to exist deadening to create Showtime Menu shortcuts, so make sure you perform a Proof of Concept to decide how this functionality impacts logon times.

Configuration of Workspace app within a published desktop is simplified if y'all have the post-obit minimum versions:

  • Workspace app installed inside the VDA
  • VDA seven.17 or newer
  • StoreFront iii.xiv or newer

If you meet these minimum version requirements, then Workspace app installed in the VDA automatically tries to launch published applications on the same local VDA rather than trying to launch them from a dissimilar VDA (aka double-hop). This feature is called vPrefer.

  • If you lot don't meet these minimum version requirements, and then yous'll need to employ the older Prefer Keyword method of handling Workspace app shortcuts as detailed after.
  • For a detailed explanation of vPrefer, see Citrix Weblog Post VPrefer: Session Sharing Betwixt a Published Desktop and a Published Application Fabricated Like shooting fish in a barrel

Practice the following for all versions of Workspace app, VDA, and StoreFront, whether using the Prefer keyword or not:

  1. Make sure Workspace app or Receiver version four.eleven or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if yous oasis't already. For vPrefer, brand sure they are the ADMX files from Workspace app.
  3. Enable the Group Policy settingRemove common programme groups from Showtime Card and use information technology to non-administrators.
    • This removes all Public (aka All Users) Start Carte shortcuts. Workspace app will re-add the shortcuts based on user group membership.
  4. On the VDA, configure the following Workspace app Registry keys (or corresponding settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\WSCReconnectMode="0″ so Workspace app doesn't try to reconnect to the published desktop you're already running.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\SelfServiceMode to Simulated. This turns off the Workspace app Cocky-Service GUI and acts like all icons are subscribed. Otherwise, simply subscribed (favorited) icons would be placed on the Start Menu and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True. This creates a Outset Menu folder based on the published app's configured Category.
  5. Configure each desired published app to Add shortcut to user's desktop.
    • Or, configure HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop = Truthful to place all icons on the desktop.
  6. To control icon placement, configure the following registry values:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to identify published applications in a sub-folder. Note: Windows Server 2012 and Windows ten and newer but supports a single level of Start Menu folders, so setting this effectively turns off published app categories.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\DesktopDir to identify published applications in a sub-folder on the desktop.
  7. Pass-through hallmark:
    1. In a GPO that applies to the VDA, import the receiver.admx file, and set Local user name and password to Enabled. Check the box next to Allow pass-through authentication for all ICA connections.
    2. If you're using Gateway internally, and if Workspace app 1808 or newer, so likewise enableSingle Sign-on for NetScaler Gateway.
    3. In a user-level GPO that applies to the VDA, add the StoreFront FQDN to the Local Intranet zone. Brand sure it is not in the Trusted Sites zone, or enable Automated logon with current user proper noun and countersign for the Trusted Sites zone.
    4. Brand sure ssonsvr. exe is running after you login to the VDA. If not, troubleshoot it.
  8. When configuring Citrix Profile Management, make sure !ctx_startmenu! is non excluded from roaming.
  9. In Citrix Studio, configure a Delivery Group with delivery type = Desktop and Applications. Assign users to the commitment grouping, and the private published applications (if visibility is limited).
    1. In Citrix Studio, edit each published application, and on the Commitment tab, specify a category. This volition become the Start Carte binder name.
    2. If Workspace app Self Service Mode (GUI) is enabled, in Studio, edit each application, and add KEYWORDS:Auto and/or KEYWORDS:Mandatory to the published application description. This forces the applications to be subscribed/favorited. Only subscribed (or Favorite) apps are displayed in the Get-go Menu and Desktop. Unless you disable Workspace app'southward SelfService interface as described earlier.
    3. Another option is to get to the StoreFront Console, click Stores on the left, and on the right, click Configure Shop Settings, and click Disable User Subscriptions. This causes all apps to appear on the Start Menu and/or Desktop depending on Workspace app configuration.
  10. Create a grouping policy that applies to VDAs, and configure the group policy to define the Store URL for Workspace app similar to https://citrix.corp.com/Citrix/Store/discovery. Replace the FQDN with your load balanced StoreFront FQDN. Also replace the path to the store with your shop path. Make certain in that location is /discovery on the end. By default, Workspace app and Receiver only supporthttps.
    1. Your StoreFront store probably delivers both awarding and desktop icons. If you want to filter out the desktop icons, and then create a new StoreFront store, and configure the Workspace app on the VDA to connect to the new Store.
    2. In StoreFront Console, click the store for VDAs, and click Configure Store Settings. On the Advanced Settings folio, in the Filter resources by type row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA vii.17 (or newer), and StoreFront iii.fourteen (or newer), edit a GPO that applies to the VDAs.
    1. Go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is merely in Workspace app ADMX templates from Workspace app.
    3. Set it toAllow all apps. Source = 7.17 vPrefer – not working with 32Bit Apps at Citrix Discussions.
  12. On your Commitment Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $truthful
    • This is required for Pass-through Authentication from Workspace app.
  13. Configure your customer devices to connect to the published desktop.
    1. When users connect to the published desktop, Workspace app will motorcar-launch and hopefully auto-login.
    2. If Workspace app Cocky-Service Mode is disabled, all published applications should automatically appear in the First Menu and Desktop.
    3. If Workspace app Cocky-Service Mode is enabled, then only applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published awarding description will be displayed. Users can open the systray icon to subscribe to more applications.
    4. Users can copy icons from the Offset Menu to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    5. Users can so launch applications direct from the Kickoff Menu, from the Desktop, or from the Workspace app (if the Cocky-Service interface is enabled).
    6. If Workspace app 4.11 (or newer), VDA 7.17 (or newer), and StoreFront iii.14 (or newer), thenvPrefer is enabled by default. When launching an app icon that came from Workspace app, Workspace app checks the local VDA auto to run across if the application tin be launched on the local VDA instead of by creating a new Citrix double-hop session.
    7. If the application is installed locally on the VDA and then the local application shortcut should launch quickly. If the awarding is on a unlike commitment grouping then a second (double-hop) Citrix HDX/ICA connectedness will be established.
    8. If the user deletes Workspace app shortcuts from the Start Menu, yous can get them dorsum by going to the systray icon and refreshing the applications. Or sometimes you accept to reset Workspace app.

If you are running components older than Receiver 4.11, VDA 7.17, and StoreFront iii.xiv, then you'll need to configure theadopt keyword to get Receiver delivered icons to launch on the local VDA instead of in a new double-hop Citrix connectedness.

  1. Enable the Group Policy settingRemove common plan groups from Commencement Menu and apply it to non-administrators.
    1. For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory group membership. Applications on other delivery groups are handled by Receiver.
    2. Or use the prefer keyword to copy shortcuts from the PreferTemplateDirectory.
  2. On the VDA, configure the following Receiver Registry keys (or respective settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PreferTemplateDirectory = a UNC path or local path containing shortcuts to be copied by the adopt keyword. This can indicate to C:\ProgramData\Microsoft\Windows\Start Menu.
  3. In Citrix Studio, configure a Delivery Group with commitment blazon = Desktop and Applications. Assign users to the Delivery Group and the applications (if visibility is limited).
    1. In Studio, edit each application and alter KEYWORDS:Prefer to KEYWORDS:adopt. Observe the lower instance p. It doesn't piece of work with uppercase P.
      • With the prefer keyword, if you publish an application that is also created using Group Policy Preferences, the Group Policy Preferences icon volition take precedence. This is proficient. Otherwise the Receiver published application icon would result in a new Citrix double-hop session.
      • See Ralph Jansen Citrix Receiver iv.1 Prefer keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter it every bit KEYWORDS:prefer=shortcutname where shortcutname is the proper name of the shortcut that is copied from the Template directory.
  4. Configure your client devices to connect to the published desktop.
    1. When users connect to the published desktop, Group Policy Preferences will create shortcuts to local applications.
    2. Receiver will car-launch and hopefully machine-login.
    3. If Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Carte and Desktop.
    4. If Receiver Cocky-Service Mode is enabled and so only applications with KEYWORDS:Car and/or KEYWORDS:Mandatory in the published awarding description will exist displayed. Users tin can open the systray icon to subscribe to more applications.
    5. For published applications with KEYWORDS:prefer=shortcutname, Receiver should re-create icons from the template directory to the Beginning Bill of fare and/or Desktop. See below for considerations.
    6. Users can re-create icons from the Starting time Bill of fare to the desktop. Make certain the user Copies the icon and doesn't Movementit.
    7. Users can so launch applications directly from the Start Carte, from the Desktop, or from the Receiver (if Cocky-Service interface is enabled).
    8. If a local shortcut (e.thousand. Group Policy Preferences shortcut, or copied from template directory) matches a published application withKEYWORDS:prefer then the local shortcut will override the published application icon.
    9. If the application is installed locally on the VDA then the local application shortcut should launch rapidly. If the awarding is on a different commitment grouping then a second (double-hop) Citrix HDX/ICA connection will be established.
    10. If the user deletes Receiver shortcuts from the Start Menu, you can get them back past going to the systray icon and refreshing the applications. Or sometimes you lot have to reset Receiver.

Notes regarding Prefer Template Directory

  • Prefer Template Directory can betoken toC:\ProgramData\Microsoft\Windows\Commencement Menu, which is the All Users Outset Card.
  • The shortcuts copied from the Prefer Template Directory are renamed to friction match the published app name.
  • For prefer local apps, any command line parameters specified in the published app are ignored. If y'all need these control line parameters, add together them to the shortcut in the Prefer Template Directory.
  • If y'all have multiple published apps pointing to the same prefer local shortcut, and then simply i copy volition be fabricated, and it will have the proper noun of only 1 of the published apps. To workaround this, in the Adopt Template Directory, create separate shortcuts for each published app, and arrange the published app prefer keyword accordingly.
  • Jan Hendrik Meier Automated Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp 7.x surround has a script that tin create shortcuts based on the published apps withprefer keyword. These shortcuts tin can so be copied to your Adopt Template Directory.

How to Script/Automate Workspace app and Receiver Cocky-Service

From Citrix Knowledgebase commodity Driving the Citrix Receiver Self-Service Plug-in Programmatically: by default, Workspace app Self-Service (SSP) activities are driven by user interaction. However, SSP exposes sufficient information for its activities to exist scripted.

When SSP builds a shortcut, information technology builds it to a minor stub application in a file %appdata%\Citrix\SelfService\app-proper name-with-spaces-removed.exe for each resource. These files allow SSP to create a fake 'install' tape for Add/Remove Software. Running these .exe files causes the application to launch. Note: Workspace app and Receiver 4.three.100 and newer don't create stubs by default. To enable, ready HKLM\Software\Wow6432Node\Citrix\Dazzle\AlwaysUseStubs (REG_SZ) = true.

If y'all want to bulldoze SSP directly for launch instead of through an .exe stub, look at the keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall. There will be keys in there named subcontract-name@@server-farm-proper noun.app-friendly-proper noun. In these keys you'll find a LaunchString value that shows the relevant parameters. These parameters are user-independent and tin can therefore exist cloned from a reference user to a general instance. Yous can re-create and reuse these parameters without interpretation.

Running the command selfservice.exe –init –ipoll –leave starts SSP, performs a refresh (interactive poll) from the current provider, and forces a clean exit.

Additional command line parameters are detailed at Driving the Citrix Receiver Self-Service Plug-in Programmatically.

Citrix Workspace app and Receiver come with a .dll file that implements the Citrix Common Connectedness Director SDK. You lot can utilise the CCM SDK to practice the following:

  • Launch Sessions
  • Disconnect Sessions
  • Logoff Sessions
  • Get Session Information

Citrix was kind plenty to develop a PowerShell module that calls functions from the .dll. Become the CCMPowershellModule from Github. The PowerShell module contains functions like the following:

  • CCMTerminateApplication
  • CCMLaunchApplication
  • CCMGetActiveSessionCount
  • CCMDisconnectAllSessions

Launcher Scripts

Ryan C Butler Storefront ICA file creator at Github. See Create an ICA File from Storefront using PowerShell or JavaScript for more info.

Stan Czerno – Powershell Script to launch one or more Published Applications from Citrix Storefront ii.x through three.11: the script launches a browser, connects to StoreFront (or NetScaler Gateway), logs in, and launches an icon. This is a very well-written script that uses a .dll file from Citrix Workspace app to display session data.

Citrix Solutions Lab StoreFront Launcher Script at Github. Information technology attempts to closely resemble what an actual user would practise by:

  1. Opening Net Explorer.
  2. Navigating direct to the Receiver for Spider web site or NetScaler Gateway portal.
  3. Completing the fields.
  4. Logging in.
  5. Clicking on the resources.
  6. Logging off the StoreFront site.

David Ott StoreFront App/Desktop Launch Testing Script uses Internet Explorer to login to StoreFront and launch a resource. Sends email with the consequence. Uses wficalib.dll to go session information.

Microsoft Teams

Citrix and Microsoft jointly support the delivery of Microsoft Teams from Citrix Virtual Apps and Desktops using optimization for Microsoft Teams.

Microsoft Teams optimization/offloading (like to Skype optimization/offloading) requires the following:

  • An upcoming release of Microsoft Teams
  • Citrix VDA 1906 or newer
  • Citrix Workspace app 1905 or newer

The redirection components are built into VDA and Workspace app. There is no need to install anything separately. The feature is based on Browser Content Redirection then don't exclude that characteristic when installing the VDA.

Approachable screensharing is not supported.

Come across Citrix Docs Optimization for Microsoft Teams.

Skype for Concern

Citrix has a HDX RealTime Optimization Pack for Workspace app that enables offloading of Skype for Concern media protocols to the client device. Here are the bachelor versions:

  • Version 2.9 is a Long Term Service Release (LTSR). See HDX RealTime Optimization Pack 2.9 LTSR at Citrix Docs.
  • Version 2.4.3000 (Cumulative Update iii) is a Long Term Service Release (LTSR). More details at CTX200466 Lifecycle Information for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the ii.iii release can be found in Citrix Web log Post The Only Virtualization Solution for Skype Meetings Just Got Even Amend!

The HDX RealTime Optimization Pack comes in two pieces: the Connector (on the VDA), and the Media Engine (on the Workspace app car). Commonly both pieces must be the same version, just versions ii.3 and college now allow version mixing.

  • Connector ii.9 LTSR
    • Connector 2.4.3000 LTSR
  • Media Engine 2.9 LTSR
    • Media Engine ii.four.3000 LTSR

24-page Citrix PDF Delivering Microsoft Skype for Business to XenApp and XenDesktop Users.

For Skype for Business Location Based Routing, y'all'll demand the following: (Source = Citrix Derek Thorslund at Location based routing at Citrix Discussions)

  • Microsoft added support for Location Based Routing (LBR) with the virtualized Skype for Business 2016 client (and HDX RTOP 2.i and above) in the Click-to-Run (C2R) download quite a long time agone, only it hasn't yet been introduced in the MSI packet.
  • It requires setting IsLBRInVDIEnabled on the Skype for Business Server to True: 
    $x = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "truthful" Set-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add together=$x}

When offloading voice and video to Workspace app machines, don't forget to configure QoS on the client machines. See Citrix Web log Post Implementing the Citrix HDX RealTime Optimization Pack: Don't Forget About QoS/DSCP.

Citrix CTX222459 RealTime Optimization Pack Adequacy Checker: It will listing out endpoint hardware/software information which will be used to process sound and video. The tool is contained of RealTime Optimization Pack version and runs whatsoever Windows auto.

Citrix CTX214237 LOPper – Lync Optimization Pack Log Parser: parses log files generated by Citrix HDX RealTime Optimization Pack (HROP) when an audio/video telephone call is made using Lync 2013/Skype for Business (SfB) and shows relevant information in a UI.

Troubleshooting – Citrix QuickLaunch

Citrix CTX219718 QuickLaunch Tool (Testing Application and Desktop Launch) lets y'all launch Citrix sessions directly from a Controller without needing StoreFront.

You enter a Controller address, credentials, and so it shows y'all the published resource. You can choice a resources, edit properties on the other tabs, and then Connect. This allows you to easily try different connexion properties.

If y'all run into problems launching a session, use Sysinternals DebugView while running CQL in Debug style (/debug switch).

Troubleshooting – Workspace app Logging

At that place are a couple methods of logging Workspace app for Windows operations. One method is CTX141751 Citrix Receiver Diagnostics Tool – For Windows, which creates a CDF trace that can exist parsed by CDFControl.

Another method is CTX132883 How to Enable Logging on Receiver for Windows Using Registry Entries. The logfiles in%USERPROFILE%\Appdata\Local\Citrix\ are human readable. And CTX206102 Enable SSON Logging Using Registry Cardinal.

Instead of creating the registry keys manually,  you lot can employ the following .reg file provided by Wolfgang Thürr:

Windows Registry Editor Version 5.00  ;only for x64 windows os ;import with admin rights ;restart your computer to activate the logging and tracing settings ;create C:\TEMP for the launch ICA log and SSON logn (no environs variables can exist used)  ;general Workspace app and Receiver logging ;************************ ;logpath: %USERPROFILE%\Appdata\Local\Citrix\Receiver [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix] "ReceiverVerboseTracingEnabled"=dword:00000001  ;Authentication Managing director logging ;****************************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\AuthManager [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\AuthManager] "LoggingMode"="verbose" "TracingEnabled"="True" "SDKTracingEnabled"="Truthful"  ;Self Service logging ;******************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle] "Tracing"="True" "AuxTracing"="True" "DefaultTracingConfiguration"="global all –detail"  ;salve launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables immune) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Logging] "LogConfigurationAccess"="true" "LogConnectionAuthorisation"="truthful" "LogEvidence"="true" "LogICAFile"="true" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="truthful"  ;Receiver Ever On Tracing ;************************** ;generates ETL Files for analyzing with CDFControl see CTX111961 for details ;can be configured or overruled by GPOs (icaclient.admx) ;path %USERPROFILE%\AppData\Local\Temp\CTXReceiverLogs [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\ICA Client\AoLog] "EnableTracing"=dword:00000001  ;Single Sign-on Logging ;************************** ;https://back up.citrix.com/article/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="true" "LogPath"="C:\\Temp"

Troubleshooting – Duplicate Stores

Stores are sometimes duplicated in Workspace app, especially if y'all are running Workspace app within a VDA. (h/t Dan Loftier)

StoreFront URLs tin can be defined in several places:

  1. In Studio, get to Configuration > StoreFront and delete all URLs configured here.
  2. Await in GPOs for Estimator Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts List. Remove any URLs configured hither.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, y'all might run across store addresses that were specified during a control line installation of Workspace app.
  4. When Citrix Workspace app switches between StoreFront servers in multiple datacenters, it's possible for each datacenter to be treated as a separate Workspace app site. This tin can exist prevented past doing the post-obit. From Juan Zevallos at Citrix Discussions:
    1. Match the Base URL in all datacenters.
    2. Match the SRID in all datacenters – The SRID can be safely edited in the C: \inetpub\wwwroot\Citrix\Roaming\web.config. Make sure to propagate changes to other servers in the group.
    3. Lucifer the Delivery Controller names under "Manage Delivery Controllers" – The XML brokers can be different, but the actual name of the Delivery Controller/Subcontract must be identical.

If y'all are running Workspace app on a VDA, once yous've removed the configured URLs shown above, practice the following to clean upwardly the VDAs:

  1. On the VDA, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix – Delete the number folders representing policy entries.
  2. On session host VDAs, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Citrix – Remove the entries for storefront in the post-obit folders.
    1. Under \receiver\ctxaccount delete all entries.
    2. Nether \SR\Store delete the entries.
  3. On the VDA, C:\ProgramData\CitrixCseCache – Delete all files
  4. On the VDA, C:\ProgramData\Citrix\GroupPolicy – Delete all folders and files.
  5. Run gpupdate and logoff.
  6. In the user's registry, HKEY_CURRENT_USER or the profile registry hive. Possible contour reset.
    1. Under Software\Citrix\Dazzle\Sites – Delete all entries.
    2. Under Software\Citrix\Receiver\ctxaccount – delete all entries.
    3. Under Software\Citrix\SR\Shop – delete the entries.
  7. Verify no cached profile folders for user on server.

How To Configure Citrix Receiver For Mac To Manually Add Http Stores,

Source: https://www.carlstalhood.com/workspace-app-for-windows/

Posted by: mumfordcoser1975.blogspot.com

0 Response to "How To Configure Citrix Receiver For Mac To Manually Add Http Stores"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel