Home  ›  Internet Explorer Youtube an Error Occurred Please Try Again Later Citrix

Internet Explorer Youtube an Error Occurred Please Try Again Later Citrix

Written By Sunday, May 15, 2022 Add Comment Edit

Navigation

Workspace app is the new name for Receiver. This post applies to all Workspace app versions, including the Current Release version 2204.ane, and the LTSR versions 2203.1 and 1912.7000.

  • Change Log
  • Workspace app versions
  •  Overview
    • Workspace app Modules
    • Workspace app Discovery and Buoy Process
    • Virtual Monitors
  • Uninstall Onetime Receiver Clients
  • Installation and Configuration
    • Administrator vs non-administrator
    • Workspace app Auto-Update
    • Splash Screen
    • Add Account Magician
    • CitrixWorkspaceApp.exe Command 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 Beginning Card – and Workspace Control (Session Reconnect)
  • Enable Prelaunch
  • Control Device Mapping Prompts
  • Desktop Lock
  • Use 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
  • Troubleshoot:
    • Citrix QuickLaunch
    • Workspace app Logging
    • Make clean upward Indistinguishable Stores

💡 = Recently Updated

Change Log

  • 2022 Apr 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7 Hotfix 1
  • 2022 Apr 7 – Versions – updated for Workspace app 2203.1 LTSR
  • 2022 Apr 7 – updated entire article for Workspace app 2204.ane
  • 2022 Mar 17 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7
  • 2022 February 7 – updated entire article for Workspace app 2202
  • 2021 Dec ix – Versions – updated for Workspace app 1912 LTSR Cumulative Update vi
  • 2021 Dec viii – updated entire article for Workspace app 2112.1
  • 2021 Oct 4 – updated unabridged article for Workspace app 2109.i
  • 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 unabridged commodity for Workspace app 2107
  • 2021 June xvi – updated entire commodity for Workspace app 2106
  • 2021 May 11 – Workspace app 1912 CU4 and Workspace app 2105 and newer set security vulnerabilities
  • 2021 May 10 – updated entire article for Workspace app 2105
  • 2021 May 10 – Versions – updated for Workspace app 1912 LTSR Cumulative Update four
  • 2021 Mar 23 – updated entire article for Workspace app 2103.i
  • 2021 Mar sixteen – updated unabridged article for Workspace app 2103
  • 2021 February 1 – updated entire commodity for Workspace app 2102
  • 2021 Jan 20 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 Dec xviii – updated entire article for Workspace app 2012.1
  • 2020 Dec eight – updated entire article for Workspace app 2012
  • 2020 Nov 2 – updated entire article for Workspace app 2010
  • 2020 October 15 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct ane – updated entire commodity for Workspace app 2009.6
  • 2020 Sep 24 – updated unabridged article for Workspace app 2009.5
  • 2020 Sep fifteen – updated entire article for Workspace app 2009

Workspace app Versions

Workspace app is the new proper noun 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 (e.chiliad. Browser Content Redirection, App Protection).

Workspace app uses a YYMM (twelvemonth/calendar month) versioning format, of which version 2204,1 (22.iv.1) is the newest.

Workspace app 2009 and newer take the new Citrix logo.

Workspace app 1912 and newer support App Protection. It's available in both the LTSR versions (1912 and 2203) and the Electric current Release 2204.one version.

There are ii LTSR (Long Term Service Release) versions of Workspace app: 2203.1, and 1912 Cumulative Update 7 (aka 19.12.7000) (or 1912 Cumulative Update vii Hotfix i). 1912 CU5 and newer contain many Teams optimization enhancements. The LTSR versions of Workspace app exercise not back up 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. Hither are the important ones:

  • ICA Engine (wfica.exe) – procedure 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 connexion.
  • Single Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs later an ICA connection is established
  • Workspace Motorcar-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The almost 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, but does not include Self-Service. The last version of Receiver Enterprise is three.four.

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 Beacon Process

If you are using Workspace app's congenital-in user interface (instead of a web browser), then Workspace app first prompts you to perform discovery, which is besides chosen Add Account.

The Citrix logo changed in Workspace app 2009 and newer.

The Add Business relationship wizard changed in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Deject Workspace FQDN. Just enter the FQDN. There's no demand to enter https or a path.

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

  • If you entered a StoreFront FQDN, and so Workspace app will download the Provisioning File directly from the StoreFront server.
  • If you entered a Gateway FQDN, then Gateway will get-go prompt the user to authenticate. After authentication, Gateway will connect to its configured Account Services address, and download the Provisioning File from StoreFront. The Account Services address 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 will be prompted to select a store. Unfortunately, there'southward no configuration option in NetScaler Gateway to force a particular shop.

  • One workaround is to hide the shop that you don't want 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 Store.

The ReceiverConfig.cr Provisioning File looks something similar this:

Hither are the values in the Provisioning File:

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

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

  1. Endeavour to connect to the Internal Beacon.
  2. If the Internal Beacon is reachable, connect straight to the StoreFront Base of operations 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, and 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 as the Default.

Here 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 actual connectedness process 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 equally Default. Workspace app and Receiver completely ignore whatever Gateway FQDN you entered during Discovery. To use a non-default Gateway, the user must manually select the other Gateway in Workspace app's / Receiver'south Advanced Preferences.

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

Here are some boosted methods of performing Workspace app Discovery:

Virtual Monitors

In Workspace app 1812 and newer, when connected to a published desktop on a single monitor, you tin separate the screen into virtual monitors. This feature is intended for large 4K monitors.

Uninstall Old Clients

Workspace app and Receiver 4.4 and newer includes Receiver Clean-Up, then, in theory, it's non necessary to uninstall erstwhile clients first. For more details, encounter 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 former clients, clean up the registry and file arrangement, and then deploy the new Workspace app.

Citrix Blog Mail Cookbook to Upgrade from Receiver 3.4 for Windows to Receiver 4.two.100 and Citrix Commodity CTX135933 Upgrading to Citrix Receiver for Windows contains step-past-stride procedure to utilise Group Policy to uninstall Receiver Enterprise 3.4 and install/configure Workspace app.

The Receiver Make clean-Upwardly utility for Receiver four.3 and older is designed to assist with the following scenarios:

  • When errors occur during upgrade from an before version of Receiver, or Online Plug-in
  • When unexpected beliefs or performance is experienced afterward upgrade from an before Receiver or Online Plug-in
  • If Receiver upgrade is not possible due to feature incompatibility and/or a clean uninstall is required
  • The Receiver Make clean-Upwardly Utility removes components, files, and registry values of Online Plug-in 11.10, 12.x, and Receiver for Windows 3.x, iv.x (Online Plugin-in 13.10, 14.x). This includes the Offline Plug-in component if installed.

Citrix CTX325140: How to Remove Client Files Remaining on Organization later on Uninstalling Receiver for Windows.

Web log posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Customer and Install Citrix Receiver 3.10
  • Full listing of Citrix Customer Uninstall Strings

Installation and Configuration

This section 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 Single 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 2204.1, LTSR version 2203.1, or LTSR version 1912 CU7 (aka nineteen.12.7000) (or 1912 CU7 Hotfix ane) tin exist installed past just double-clicking it. Note: LTSR Workspace app does not support Browser Content Redirection. Workspace app 2006 and newer do not back up 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 accept to reinstall Workspace app.
    • Non-administrator installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.
  • Ambassador – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator business relationship. and so the Workspace app merely needs to be installed once.
    • Ambassador installations are installed to C:\Plan Files (x86)\Citrix\ICA Client.
    • Administrator installations of Workspace app 1912 and newer can exist manually upgraded by non-administrators past clicking Check for Updates. Older versions cannot exist upgraded by non-administrators.
  • Conflicts – If an ambassador install of Workspace app is performed on a car that has non-administrator installs of Workspace app, then the two installations will conflict. All-time option is to uninstall not-admin Workspace app and Receiver before installing admin Workspace app. Otherwise, the user'south profile probably has to be reset before Workspace app is functional again.
    • Citrix article CTX249920 Workspace App for Windows – Your apps are not available at this time – Issue when installing Citrix Receiver in not elevated/per-user install mode describes the HKEY_CURRENT_USER registry keys that must be deleted to fix this issue.
    • For a script to clean-upwardly the per-user installs, come across Marker DePalma at Citrix Receiver Per-User Install Cleanup.

Auto-Update

Workspace app supports auto-update.

Some notes:

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

Car-update is cleaved in Receiver for Windows iv.11 and older, and Receiver for Mac 12.nine and older. To ready it, manually upgrade to the adjacent version (east.1000. Workspace app for Mac), or install the Ready that can be downloaded from the Receiver download folio (Source = CTX234657 Receiver Updater stops working with "Problem Checking for updates" error)

Auto-update is configured using Workspace app grouping policy under the Citrix Workspace Updates,Receiver Updates or Motorcar-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, set the following registry value: (source = Dennis Span on Twitter)

  • Key = HKEY_CURRENT_USER\SOFTWARE\Citrix\Splashscreen
    • Value (REG_SZ) =SplashscreenShown = i

Add Business relationship Wizard

From Citrix CTX135438 How to Suppress the Add Account Window in Citrix Receiver for Windows: Subsequently installation, Workspace app will launch and inquire yous to add together an account. If Workspace app, notice the checkboxDo not bear witness this window automatically at logon.

For Workspace app and Receiver 4.4 and newer, FTU (First Time Employ aka Add Account Sorcerer) will exist displayed simply if a store is not configured. If a store is already configured via command line, GPO, or Citrix Studio, then FTU screen volition non be bachelor subsequently installation. Otherwise, FTU tin can be suppressed by doing one of the following:  (Notation: Receiver 4.four.1000 and newer has a fix 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=N
  • Ready the registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\EnableFTU=dword:00000000 (or EnableX1FTU =dword:0)
  • Disable the EnableFTU policy setting inReceiver.admx.
  • Modify Registry values mail installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, set AllowAddStore value to Northward.
  • Set up the registry value: HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\NeverShowConfigurationWizard (REG_SZ) = true
  • Also see Suppressing Add Account dialog at Citrix Docs.

Discover Hidden 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 detect a hidden store (a shop that's non advertised), add ?StoreName to the end of the FQDN. CTX214819 How to configure Receiver to a Store that is non advertised.

CitrixWorkspaceApp.exe / CitrixReceiver.exe Command line switches

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

For unattended installation of Workspace app, come across CTA Dennis Bridge 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. Common Command line switches include the following:

  • /silent
  • /includeSSON – enables laissez passer-through authentication. GPO configuration is also required as detailed below. 
    CitrixWorkspaceApp.exe /includeSSON  CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A – by default, simply SSL (HTTPS) stores are accustomed. To allow non-SSL stores: 
    CitrixWorkspaceApp.exe /ALLOWADDSTORE=A  CitrixReceiver.exe /ALLOWADDSTORE=A
  • / STORE0 – To add a store from the installation command 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 Shop"
    • Workspace App and Receiver four.10 and newer can discover the Store through NetScaler Gateway. 
      CitrixWorkspaceApp.exe STORE0="AppStore;https://gateway.corp.com#MyStore;On;App Shop"  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=Imitation  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=auto /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets it to LTSR Co-operative simply. AutoUpdateCheck tin also exist set to manual or disabled. AutoUpdateStream tin as well be set to Electric current. Meet 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=True  CitrixReceiver.exe /ENABLEPRELAUNCH=True
  • /ALLOW_CLIENTHOSTEDAPPSURL=one – enables Local App Admission: 
    CitrixWorkspaceApp.exe /ALLOW_CLIENTHOSTEDAPPSURL=i  CitrixReceiver.exe /ALLOW_CLIENTHOSTEDAPPSURL=one

Registry values

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

  • SelfServiceMode (REG_SZ) = False – Turns off Workspace app'south / Receiver's Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = True – If Self-Service interface is disabled, places all shortcuts on desktop.
  • UseDifferentPathsforStartmenuAndDesktop (REG_SZ) = True
    • UseCategoryAsStartMenuPath (REG_SZ) = Truthful or Imitation
    • UseCategoryAsDesktopPath (REG_SZ) = True or False
  • StartMenuDir (REG_SZ) = name of folder on Offset Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = name 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 – Only 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) = i – minimizes the launch delay before contacting store
  • InitialRefreshMaxMs (REG_SZ) = 1 – minimizes the launch delay before contacting store
  • RefreshMs (REG_SZ) = 3600000 (1 hour) – interval for Receiver icon refreshes. one hour is the default value.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Authentication Window Periodically When Receiver is Non Opened
  • MaxSimultaneousFetches (REG_DWORD) = half-dozen  – improves the time of loading icons in Showtime Card
  • MaxSimultaneousSubscribes (REG_DWORD) = half dozen – improves the time of loading icons in Start Bill of fare
  • DontWarnOfRemovedResources (REG_SZ) = Truthful – prevents dialog boxes when resource 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 prefer keyword. Give the shortcuts a short name.
  • PnaSSONEnabled (REG_SZ) = Truthful – Enables Single Sign-on for PNAgent (Spider web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Workspace app is running inside a VDA published desktop, gear up it to 0.
    • If yous're having trouble getting sessions to reconnect, see Receiver 4.3 Desktop volition not 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. Prepare this to create .exe stubs. Too see Citrix CTX211893 Decision-making 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}_{one}_{two}_{3}". See the link for details.
  • SelfServiceFlags (REG_DWORD) = 4 – prevents duplicate shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = 5 to cease external SSON from prompting for hallmark
  • ReEvaluateNetwork (REG_SZ) = true – for Beacon detection with Single FQDN

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

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

To allow adding not-HTTPS stores to Workspace app:

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

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

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

To prevent beacon probing from using proxy, set:

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

To enable foreground progress bar, set:

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

For client-to-server file type redirection, ready:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Advanced\Modules\ClientDrive
    • NativeDriveMapping="TRUE"

To fix USB devices that emulate a keyboard, gear up:

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

To forbid "USB Hub Power Exceeded" bulletin, set (not needed in 4.2.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, see Citrix CTX123015 How to Configure Automated Redirection of USB Devices

Group Policy Settings

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

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

  • To enable pass-through authentication: go to | User Authentication |.
    • Local Username and Password – Check the superlative two boxes.
    • Also add the StoreFront FQDN to the Local Intranet zone in Cyberspace Explorer.
    • Single Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add a shop, go to | StoreFront |
    • StoreFront Accounts List – see the help text
  • To enable Machine-Update, go to|AutoUpdate| or|Receiver Updates| or|Citrix Workspace Updates|. (the node was renamed in iv.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 Cocky-Service interface, go to | SelfService |
    • Prepare Manage SelfServiceMode to Disabled to completely disable the Self-Service window. This causes all icons to be placed on the Commencement Card.
    • Enable Manage App Shortcut and configure information technology every bit desired.
      • To let the Cocky-Service window, simply prevent information technology from automatically opening (reside in systray), tickPrevent Citrix Workspace (or Receiver) performing a refresh of the application list when opened. Source
    • Enable Control when Workspace (or Receiver) attempts to reconnect to existing sessions. If this is a VDA published desktop, gear up it to Disabled. Otherwise configure information technology every bit desired.
    • Set Enable FTU to Disabled  to prevent the Add Business relationship sorcerer from displaying.
    • EnableAllow/Prevent 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/commodity/CTX133565.
  • Enable the setting Create Client Selective Trust Keys. See Below for details.
  • Configure the FileSecurityPermission setting in ane or more than of the regions.
  • Configure the MicrophoneAndWebcamSecurityPermission setting in 1 or more of the regions.

Citrix CTX203658 Start Card Icons Set up to Default (Blank Document) Afterward Update to Receiver four.3.100 – Windows eight 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 Active Directory

To deploy Workspace app using Active Directory, configure a GPO with a reckoner startup script that runs the Workspace app installer executable. Citrix provides sample scripts that can be downloaded from one of the Workspace app download pages (Workspace app current release version 2204.one, LTSR version 2203.1, or LTSR version 1912 CU7 (aka xix.12.7000), past expanding Downloads for Admins (Deployment Tools).

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

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

You can change Workspace app'southward / Receiver's configured Shop/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/Shop/discovery

It is sometimes necessary toReset Citrix Workspace orReset Receiver past correct-clicking the Workspace app systray icon, clickingAdvanced Preferences, and clicking theReset link. Yous can do 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 Spider web experience in Microsoft Edge is not ideal. Every fourth dimension a user clicks an icon, the user has the click theOpen up button after the .ica file is downloaded.

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

But in one case you exercise that, y'all get a new switch apps prompt every time yous launch an icon from Edge.

To stop theswitch apps pop-up, on the client side, edit the registry, go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ProtocolExecute\receiver (create missing registry keys), create DWORD valueWarnOnOpen, and fix it to 0 (zero). You tin use Grouping Policy Preferences to deploy this registry value.

Workspace app Group Policy ADMX Template

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

  1. From a machine that has Workspace app installed, observe the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • Yous can also download the ADMX files from one of the Workspace app download pages (Workspace app current release version 2204.1, LTSR version 2203.1, or LTSR version 1912 CU7 (aka 19.12.7000), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. Also re-create theen-US binder. In Workspace app, the files are yet namedreceiver.admx.
  3. Go to your domain's SYSVOL share and in the Policies binder look for a PolicyDefinitions binder. If one exists, paste the .admx file direct into the PolicyDefinitions folder. If this folder doesn't exist in SYSVOL, instead copy the .admx file to C:\Windows\PolicyDefinitions. Overwrite whatsoever existing Receiver ADMX files.
  4. The GPO settings can then be found at ane of the following:
    • Computer Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Workspace
    • Computer Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Receiver
  5. For example, you tin can disable Customer Feel Improvement Program (CEIP) from here.
  6. See https://www.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip for additional places where CEIP is enabled.
  7. Workspace app 1905 and newer has a setting toDisable sending information to tertiary party (east.1000. Google Analytics).
  8. Workspace app 1905 and newer allow you disable embedded browser caching.
  9. Workspace app 1905 and newer take NetScaler LAN Proxy underNetwork routing > Proxy.
  10. Workspace app 1808 and newer haveUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver four.12 adds Network Routing | Deprecated naught suites to configure deprecated ciphers.

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

Laissez passer-through Authentication

Citrix blog mail – A Comprehensive Guide to Enabling Pass-Through Authentication with XenDesktop 7.5

  1. Run the command
    Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $Truthful from a Windows PowerShell command prompt on a Delivery Controller.
    • In XenApp half-dozen.v, this is a Citrix Policy > Computer > 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, check the box adjacent to Enable Single Sign-on. Then finish the installation.

  4. If installing an older version of Receiver:
    1. Get to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver. exe, and click Copy as path.
    2. Open a command prompt.
    3. Correct-click to paste the path in the command prompt and and so add /includeSSON to the end of the control. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, get to C:\Programme Files (x86)\Citrix\ICA Client and look for the file ssonsvr. exe.
  6. And if you open regedit and go to HKLM\Arrangement\CurrentControlSet\Command\NetworkProvider\Order, you should see 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 practical to the client PCs where the Workspace app is installed.
  9. Go to Computer Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Workspace.
  10. Expand Citrix Workspace and click User authentication.
  11. On the right, double-click Local user name and countersign.
  12. Select Enabled and then check the box next to Allow pass-through authentication for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, y'all tin can enableUnmarried Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Cyberspace Explorer. You can utilize a GPO to configure this on the client side.
  15. Local Intranet zone should have Automated logon only in Intranet zone enabled.
  16. Logoff Windows and log back on. In Chore Managing director yous should at present come across ssonsvr. exe. This won't announced unless you lot logoff and log back on.
  17. If Workspace app won't connect or is boring to enumerate icons, then you might have to disable Automatically find settings in IE.
  18. Right-click the Workspace app icon and click Advanced Preferences.
  19. ClickConfiguration Checker.
  20. Check the box next toSSONChecker and clickRun.
  21. The lines with red ten volition indicate the issue and corrective activeness.

StoreFront Accounts

You can employ a client-side GPO to add together a store (Account) to Workspace app Self-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 correct, double-click NetScaler Gateway URL/StoreFront Accounts List.
  5. Select Enabled, then clickShow.
  6. Enter a shop path based on the example shown in the Help box. Workspace app lets y'all enter a Gateway path. Then click OK.
  7. Note: Gateway paths work in GPO, but might not work when specified in the CitrixWorkspaceApp.exe installation control 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: At that place are several methods of decision-making how Workspace app displays shortcuts on the Start Menu and Desktop as detailed below:

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

Under HKLM\Software\Wow6432Node\Citrix\Dazzle (or HKCU\Software\Wow6432Node\Citrix\Dazzle) are several registry values related to shortcuts. Some of the settings only apply if SelfServiceMode is ready to Fake. Here are some mutual options:

  • SelfServiceMode – gear up to Simulated so Receiver disables the Self-Service interface and automatically places all published shortcuts on the Start Bill of fare and/or Desktop. More than details in Configuring application delivery at Citrix Docs.
  • PutShortcutsOnDesktop– set toTrue to place every app on the desktop
  • DesktopDir – Workspace app places every shortcut on the desktop so it'southward probably all-time to place them in a folder.
  • StartMenuDir – If in that location is potentially a disharmonize between local apps and remote apps, then yous should place the Outset Menu shortcuts in a folder.
  • PreferTemplateDirectory (with KEYWORDS:adopt=shortcutname) – copies the shortcutname from the template directory to the Outset Menu and/or Desktop.

If you 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 command placement of shortcuts.

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

Prelaunch

Staring with Receiver 4.ii, prelaunch is automatically enabled if Workspace app is installed with SSON enabled. Otherwise, set registry values to enable prelaunch. Receiver 4.two.100 prevents the prelaunch icon from appearing on the Beginning Carte.

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

Additional customizations can exist configured at:

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

  • Proper name: State
    • REG_SZ: 0 = disable, 1 = merely-in-fourth dimension pre-launch, 2 = scheduled pre-launch
  • Name: Schedule
    • REG_SZ: HH:MM|Yard:T:W:Thursday:F:S:SU where HH and MM are hours and minutes. M:T:West:TH:F:S:SU are the days of the week. For example, to enable scheduled pre-launch on Monday, Midweek, and Friday at one:45 p.thou., set Schedule as Schedule=13:45|ane:0:1:0:1:0:0 . The session really launches between 1:xv p.m. and ane: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, y'all might run across the post-obit:

To configure the default behavior, run into the Citrix Knowledgebase article How to Configure Default Device Access Behavior of Receiver, XenDesktop and XenApp. Note: there is a bug stock-still in Receiver 4.2.100 and newer.

  1. Download the ADMX file from http://back up.citrix.com/article/CTX133565.
  2. Re-create the .admx and .adml files to PolicyDefinitions (Sysvol, or C:\Windows).
  3. The.adml file goes in theen-US folder.
  4. Edit a GPO that applies to the endpoint devices that are running Receiver.
  5. Go to Reckoner Configuration | Policies | Authoritative 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, run into 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

Employ 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 Offset Menu and Desktop. Use group policy to hide the common program groups and then employ Workspace app to place published applications back on the Kickoff Menu and Desktop based on user'due south grouping 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 store (due east.g. /Citrix/Store) and and so /discovery on the finish of the URL. The full URL would be similar to https://citrix.corp.com/Citrix/Store/discovery. Click OK.
  4. Edit a Delivery Group that has a published desktop and Citrix Workspace app installed.
  5. On the StoreFront page, alter the pick to Automatically, using the StoreFront servers selected beneath, and so check the box next to the StoreFront URL. Click OK. Now when users launch the published desktop, Workspace app will exist automatically configured with this URL.

Published Desktop – use Workspace app to control Shortcuts

If yous 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'southward published desktop Starting time Menu and Desktop. This is an alternative to using a User Feel Management product to control shortcut placement.

Note: Workspace app tends to exist slow to create Start Card shortcuts, so brand sure you lot perform a Proof of Concept to determine how this functionality impacts logon times.

Configuration of Workspace app inside a published desktop is simplified if you lot have the following minimum versions:

  • Workspace app installed inside the VDA
  • VDA 7.17 or newer
  • StoreFront 3.14 or newer

If you meet these minimum version requirements, and so 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 different VDA (aka double-hop). This feature is called vPrefer.

  • If yous don't see these minimum version requirements, then y'all'll need to employ the older Prefer Keyword method of handling Workspace app shortcuts as detailed later.
  • For a detailed explanation of vPrefer, see Citrix Blog Post VPrefer: Session Sharing Between a Published Desktop and a Published Awarding Made Easy

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

  1. Make certain Workspace app or Receiver version 4.11 or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if you oasis't already. For vPrefer, make sure they are the ADMX files from Workspace app.
  3. Enable the Group Policy settingRemove common program groups from Start Menu and apply it to non-administrators.
    • This removes all Public (aka All Users) Beginning Menu shortcuts. Workspace app will re-add the shortcuts based on user group membership.
  4. On the VDA, configure the post-obit 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 y'all're already running.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\SelfServiceMode to Simulated. This turns off the Workspace app Self-Service GUI and acts like all icons are subscribed. Otherwise, only subscribed (favorited) icons would be placed on the Showtime Card and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True. This creates a Start Menu folder based on the published app'south configured Category.
  5. Configure each desired published app to Add shortcut to user'due south desktop.
    • Or, configure HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop = True 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 place published applications in a sub-binder. Note: Windows Server 2012 and Windows x and newer only supports a single level of Start Menu folders, and then setting this effectively turns off published app categories.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\DesktopDir to place 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 ready Local user name and password to Enabled. Cheque the box next to Allow laissez passer-through hallmark for all ICA connections.
    2. If yous're using Gateway internally, and if Workspace app 1808 or newer, and then also 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. Make sure information technology is not in the Trusted Sites zone, or enable Automatic logon with current user name and password for the Trusted Sites zone.
    4. Make 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 not excluded from roaming.
  9. In Citrix Studio, configure a Delivery Group with commitment type = Desktop and Applications. Assign users to the delivery group, and the individual published applications (if visibility is express).
    1. In Citrix Studio, edit each published awarding, and on the Commitment tab, specify a category. This will become the Start Menu folder 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 clarification. This forces the applications to be subscribed/favorited. Just subscribed (or Favorite) apps are displayed in the Showtime Carte and Desktop. Unless you disable Workspace app'southward SelfService interface as described earlier.
    3. Some other option is to go to the StoreFront Console, click Stores on the left, and on the right, click Configure Store Settings, and click Disable User Subscriptions. This causes all apps to announced on the Start Carte and/or Desktop depending on Workspace app configuration.
  10. Create a group policy that applies to VDAs, and configure the group policy to ascertain the Store URL for Workspace app similar to https://citrix.corp.com/Citrix/Store/discovery. Replace the FQDN with your load balanced StoreFront FQDN. As well replace the path to the store with your store path. Brand sure in that location is /discovery on the terminate. By default, Workspace app and Receiver only back uphttps.
    1. Your StoreFront shop probably delivers both awarding and desktop icons. If you want to filter out the desktop icons, so 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 page, in the Filter resources by type row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA 7.17 (or newer), and StoreFront 3.14 (or newer), edit a GPO that applies to the VDAs.
    1. Go to Reckoner Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is simply in Workspace app ADMX templates from Workspace app.
    3. Set it toPermit all apps. Source = seven.17 vPrefer – non working with 32Bit Apps at Citrix Discussions.
  12. On your Delivery Controller, in PowerShell, run set up-brokersite -TrustRequestsSentToTheXmlServicePort $true
    • This is required for Pass-through Authentication from Workspace app.
  13. Configure your client devices to connect to the published desktop.
    1. When users connect to the published desktop, Workspace app volition auto-launch and hopefully machine-login.
    2. If Workspace app Cocky-Service Mode is disabled, all published applications should automatically appear in the Get-go Menu and Desktop.
    3. If Workspace app Self-Service Mode is enabled, then only applications with KEYWORDS:Automobile and/or KEYWORDS:Mandatory in the published awarding description will be displayed. Users can open the systray icon to subscribe to more than applications.
    4. Users can copy icons from the Starting time Menu to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    5. Users can then launch applications straight from the Start Menu, from the Desktop, or from the Workspace app (if the Self-Service interface is enabled).
    6. If Workspace app four.xi (or newer), VDA 7.17 (or newer), and StoreFront three.14 (or newer), sovPrefer is enabled by default. When launching an app icon that came from Workspace app, Workspace app checks the local VDA automobile to run into if the awarding can 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 speedily. If the application is on a different delivery group then a second (double-hop) Citrix HDX/ICA connectedness volition exist established.
    8. If the user deletes Workspace app shortcuts from the Get-go Menu, you tin go 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 iv.11, VDA 7.17, and StoreFront iii.14, then you'll need to configure theadopt keyword to go Receiver delivered icons to launch on the local VDA instead of in a new double-hop Citrix connection.

  1. Enable the Grouping Policy settingRemove common program groups from Starting time Menu and apply it to non-administrators.
    1. For applications that are installed on the aforementioned VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Agile Directory grouping membership. Applications on other delivery groups are handled by Receiver.
    2. Or use the prefer keyword to re-create shortcuts from the PreferTemplateDirectory.
  2. On the VDA, configure the following Receiver Registry keys (or corresponding settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PreferTemplateDirectory = a UNC path or local path containing shortcuts to exist copied by the prefer keyword. This tin can point to C:\ProgramData\Microsoft\Windows\Start Bill of fare.
  3. In Citrix Studio, configure a Delivery Group with delivery type = Desktop and Applications. Assign users to the Delivery Group and the applications (if visibility is limited).
    1. In Studio, edit each awarding and change KEYWORDS:Adopt to KEYWORDS:adopt. Notice the lower case p. It doesn't work with uppercase P.
      • With the prefer keyword, if y'all publish an awarding that is also created using Group Policy Preferences, the Grouping Policy Preferences icon will accept precedence. This is good. Otherwise the Receiver published application icon would event in a new Citrix double-hop session.
      • See Ralph Jansen Citrix Receiver 4.1 Prefer keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter it as KEYWORDS:prefer=shortcutname where shortcutname is the name of the shortcut that is copied from the Template directory.
  4. Configure your customer 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 volition automobile-launch and hopefully auto-login.
    3. If Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Carte du jour and Desktop.
    4. If Receiver Self-Service Mode is enabled then only applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application clarification will be displayed. Users tin open the systray icon to subscribe to more applications.
    5. For published applications with KEYWORDS:prefer=shortcutname, Receiver should copy icons from the template directory to the Start Menu and/or Desktop. Run into below for considerations.
    6. Users tin copy icons from the Start Card to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    7. Users can then launch applications directly from the Kickoff Menu, from the Desktop, or from the Receiver (if Cocky-Service interface is enabled).
    8. If a local shortcut (e.g. Group Policy Preferences shortcut, or copied from template directory) matches a published application withKEYWORDS:prefer then the local shortcut will override the published awarding icon.
    9. If the application is installed locally on the VDA then the local awarding shortcut should launch rapidly. If the application is on a different commitment group 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 dorsum by going to the systray icon and refreshing the applications. Or sometimes y'all take to reset Receiver.

Notes regarding Adopt Template Directory

  • Prefer Template Directory tin bespeak toC:\ProgramData\Microsoft\Windows\Start Menu, which is the All Users First Menu.
  • The shortcuts copied from the Prefer Template Directory are renamed to match the published app name.
  • For prefer local apps, any command line parameters specified in the published app are ignored. If you need these command line parameters, add them to the shortcut in the Prefer Template Directory.
  • If you have multiple published apps pointing to the same prefer local shortcut, and so only one re-create volition be made, and information technology will have the proper name of only one of the published apps. To workaround this, in the Prefer Template Directory, create split shortcuts for each published app, and adapt the published app prefer keyword accordingly.
  • Jan Hendrik Meier Automatic Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp 7.ten environs has a script that can create shortcuts based on the published apps withprefer keyword. These shortcuts can then be copied to your Prefer Template Directory.

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

From Citrix Knowledgebase article Driving the Citrix Receiver Cocky-Service Plug-in Programmatically: by default, Workspace app Self-Service (SSP) activities are driven past user interaction. Nonetheless, SSP exposes sufficient data for its activities to be scripted.

When SSP builds a shortcut, information technology builds information technology to a small stub application in a file %appdata%\Citrix\SelfService\app-name-with-spaces-removed.exe for each resource. These files let 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, set up HKLM\Software\Wow6432Node\Citrix\Dazzle\AlwaysUseStubs (REG_SZ) = true.

If yous want to drive SSP directly for launch instead of through an .exe stub, look at the keys nether HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall. At that place will be keys in in that location named farm-name@@server-subcontract-proper noun.app-friendly-proper name. In these keys y'all'll find a LaunchString value that shows the relevant parameters. These parameters are user-independent and can therefore be cloned from a reference user to a general example. You tin can copy and reuse these parameters without interpretation.

Running the command selfservice.exe –init –ipoll –exit 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 Connection Director SDK. You can employ the CCM SDK to exercise the following:

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

Citrix was kind enough 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 1 or more than Published Applications from Citrix Storefront ii.10 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 information.

Citrix Solutions Lab StoreFront Launcher Script at Github. It attempts to closely resemble what an bodily user would do by:

  1. Opening Internet Explorer.
  2. Navigating directly to the Receiver for Web site or NetScaler Gateway portal.
  3. Completing the fields.
  4. Logging in.
  5. Clicking on the resource.
  6. Logging off the StoreFront site.

David Ott StoreFront App/Desktop Launch Testing Script uses Internet Explorer to login to StoreFront and launch a resources. Sends e-mail with the result. 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 (similar 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 characteristic is based on Browser Content Redirection so don't exclude that feature when installing the VDA.

Approachable screensharing is not supported.

See Citrix Docs Optimization for Microsoft Teams.

Skype for Business

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

  • Version 2.nine 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 than details at CTX200466 Lifecycle Information for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the ii.three release can be establish in Citrix Blog Mail The Only Virtualization Solution for Skype Meetings Just Got Even Improve!

The HDX RealTime Optimization Pack comes in two pieces: the Connector (on the VDA), and the Media Engine (on the Workspace app machine). Commonly both pieces must be the same version, simply versions 2.3 and higher now allow version mixing.

  • Connector 2.9 LTSR
    • Connector two.4.3000 LTSR
  • Media Engine 2.ix LTSR
    • Media Engine two.4.3000 LTSR

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

For Skype for Business concern Location Based Routing, you'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 concern 2022 client (and HDX RTOP 2.1 and above) in the Click-to-Run (C2R) download quite a long time ago, only it hasn't yet been introduced in the MSI packet.
  • Information technology requires setting IsLBRInVDIEnabled on the Skype for Business Server to Truthful: 
    $10 = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "true" Set-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add=$x}

When offloading voice and video to Workspace app machines, don't forget to configure QoS on the client machines. Meet Citrix Blog 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 audio and video. The tool is independent of RealTime Optimization Pack version and runs any Windows automobile.

Citrix CTX214237 LOPper – Lync Optimization Pack Log Parser: parses log files generated past Citrix HDX RealTime Optimization Pack (HROP) when an audio/video 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 you launch Citrix sessions directly from a Controller without needing StoreFront.

You enter a Controller address, credentials, and and then information technology shows you the published resources. You can pick a resource, edit properties on the other tabs, and and then Connect. This allows you to easily endeavour different connection properties.

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

Troubleshooting – Workspace app Logging

In that location 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 be 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 Key.

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

Windows Registry Editor Version five.00  ;but 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 environment 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 Manager logging ;****************************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\AuthManager [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\AuthManager] "LoggingMode"="verbose" "TracingEnabled"="True" "SDKTracingEnabled"="True"  ;Self Service logging ;******************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle] "Tracing"="Truthful" "AuxTracing"="True" "DefaultTracingConfiguration"="global all –item"  ;save launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables allowed) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Avant-garde\Modules\Logging] "LogConfigurationAccess"="truthful" "LogConnectionAuthorisation"="true" "LogEvidence"="true" "LogICAFile"="true" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="truthful"  ;Receiver Always 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://support.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, particularly if you are running Workspace app inside a VDA. (h/t Dan High)

StoreFront URLs can be defined in several places:

  1. In Studio, go to Configuration > StoreFront and delete all URLs configured here.
  2. Expect in GPOs for Computer Configuration > Authoritative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts List. Remove any URLs configured here.
  3. In the customer-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you 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 exist treated equally a separate Workspace app site. This can be prevented past doing the following. 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\spider web.config. Make sure to propagate changes to other servers in the group.
    3. Match the Delivery Controller names under "Manage Delivery Controllers" – The XML brokers can exist different, just the actual name of the Commitment Controller/Farm must be identical.

If you are running Workspace app on a VDA, once you've removed the configured URLs shown in a higher place, do the following to clean up 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\Concluding 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'due south registry, HKEY_CURRENT_USER or the profile registry hive. Possible profile reset.
    1. Nether Software\Citrix\Dazzle\Sites – Delete all entries.
    2. Under Software\Citrix\Receiver\ctxaccount – delete all entries.
    3. Under Software\Citrix\SR\Store – delete the entries.
  7. Verify no cached profile folders for user on server.

hughesblith1971.blogspot.com

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

0 Response to "Internet Explorer Youtube an Error Occurred Please Try Again Later Citrix"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel