Skip to content Skip to sidebar Skip to footer
Home / Citrix Access Management Console an Error Occurred Try Performing the Task Again

Citrix Access Management Console an Error Occurred Try Performing the Task Again

Post a Comment

Navigation

Workspace app is the new name for Receiver. This mail applies to all Workspace app versions, including the Current Release version 2204.1, and the LTSR versions 2203.ane and 1912.7000.

  • Change Log
  • Workspace app versions
  •  Overview
    • Workspace app Modules
    • Workspace app Discovery and Beacon Process
    • Virtual Monitors
  • Uninstall Old Receiver Clients
  • Installation and Configuration
    • Ambassador vs non-ambassador
    • Workspace app Auto-Update
    • Splash Screen
    • Add Account Wizard
    • CitrixWorkspaceApp.exe Control line switches
    • Workspace app Registry values
    • Workspace app Group Policy settings
    • Customer-side Registry for Microsoft Border
  • Workspace app ADMX GPO Template
  • Laissez passer-through Authentication
  • Automatically add StoreFront Accounts to Workspace app
  • Control Shortcut placement on Desktop and Outset Menu – 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
    • Clean up Duplicate Stores

💡 = Recently Updated

Change Log

  • 2022 Apr 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7 Hotfix i
  • 2022 Apr 7 – Versions – updated for Workspace app 2203.i LTSR
  • 2022 April 7 – updated entire commodity for Workspace app 2204.1
  • 2022 Mar 17 – Versions – updated for Workspace app 1912 LTSR Cumulative Update vii
  • 2022 Feb vii – updated entire article for Workspace app 2202
  • 2021 Dec nine – Versions – updated for Workspace app 1912 LTSR Cumulative Update 6
  • 2021 Dec 8 – updated entire article for Workspace app 2112.1
  • 2021 Oct 4 – updated entire article for Workspace app 2109.1
  • 2021 Sep 29 – updated entire commodity for Workspace app 2109
  • 2021 Aug xxx – updated unabridged article for Workspace app 2108
  • 2021 Aug eleven – Versions – updated for Workspace app 1912 LTSR Cumulative Update five
  • 2021 July 29 – updated unabridged article for Workspace app 2107
  • 2021 June 16 – 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 article for Workspace app 2105
  • 2021 May 10 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 4
  • 2021 Mar 23 – updated unabridged article for Workspace app 2103.ane
  • 2021 Mar 16 – updated entire commodity for Workspace app 2103
  • 2021 February 1 – updated unabridged article for Workspace app 2102
  • 2021 Jan xx – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 December 18 – updated unabridged article for Workspace app 2012.ane
  • 2020 Dec 8 – updated unabridged article for Workspace app 2012
  • 2020 Nov 2 – updated unabridged article for Workspace app 2010
  • 2020 Oct 15 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct one – updated entire article for Workspace app 2009.6
  • 2020 Sep 24 – updated entire article for Workspace app 2009.5
  • 2020 Sep 15 – updated entire article for Workspace app 2009

Workspace app Versions

Workspace app is the new proper name for Receiver.

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

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

Workspace app 2009 and newer have the new Citrix logo.

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

There are two LTSR (Long Term Service Release) versions of Workspace app: 2203.1, and 1912 Cumulative Update 7 (aka 19.12.7000) (or 1912 Cumulative Update 7 Hotfix 1). 1912 CU5 and newer contain many Teams optimization enhancements. The LTSR versions of Workspace app do not support Browser Content Redirection (BCR) because the embedded browser is non 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) – 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 connection.
  • Single Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs after an ICA connection is established
  • Workspace Auto-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The nearly 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 concluding version of Receiver Enterprise is 3.four.

Custom ICA files are no longer supported. Notwithstanding, 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 built-in user interface (instead of a web browser), then Workspace app kickoff prompts you to perform discovery, which is also called Add Business relationship.

The Citrix logo changed in Workspace app 2009 and newer.

The Add Account magician inverse in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Deject Workspace FQDN. Simply enter the FQDN. There'southward no need to enter https or a path.

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

  • If you entered a StoreFront FQDN, then Workspace app will download the Provisioning File directly from the StoreFront server.
  • If you entered a Gateway FQDN, then Gateway will first prompt the user to authenticate. After authentication, Gateway will connect to its configured Business relationship Services address, and download the Provisioning File from StoreFront. The Business relationship 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 exist prompted to select a store. Unfortunately, there's no configuration pick in NetScaler Gateway to forcefulness a particular store.

  • Ane workaround is to hide the store that you don't desire visible externally. Come across How to configure Receiver to a Store 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 lot 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 by inserting the file's contents into the user'southward registry. The values are located under HKCU\Software\Citrix\Dazzle\Sites and HKCU\Software\Citrix\Receiver\SR. If you lot performed discovery through NetScaler Gateway, notice that the internal Base URL is added to the user's registry.

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

  1. Effort to connect to the Internal Beacon.
  2. If the Internal Beacon is reachable, connect direct 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 non reachable, then stop attempting to connect.
    2. Connect to the Gateway address configured in the Provisioning File. If in that location is more than than ane Gateway, connect to the Gateway that is marked as the Default.

Here are some interesting notes on this connectedness process:

  • The FQDN y'all entered during Discovery has absolutely cypher to do with how Workspace app connects to StoreFront or Gateway. The actual connexion 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 as Default. Workspace app and Receiver completely ignore any Gateway FQDN you entered during Discovery. To apply 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 touch on 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 then the updated Provisioning File is imported?

Here are some additional methods of performing Workspace app Discovery:

Virtual Monitors

In Workspace app 1812 and newer, when connected to a published desktop on a unmarried monitor, you can split 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-Upwardly, so, in theory, it's not necessary to uninstall former clients first. For more than details, run across 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 old clients, clean up the registry and file system, and then deploy the new Workspace app.

Citrix Blog Mail service Cookbook to Upgrade from Receiver iii.iv for Windows to Receiver 4.ii.100 and Citrix Article CTX135933 Upgrading to Citrix Receiver for Windows contains footstep-by-step procedure to use Group Policy to uninstall Receiver Enterprise iii.4 and install/configure Workspace app.

The Receiver Clean-Upward utility for Receiver four.3 and older is designed to assistance with the post-obit scenarios:

  • When errors occur during upgrade from an earlier version of Receiver, or Online Plug-in
  • When unexpected behavior or performance is experienced afterward upgrade from an earlier Receiver or Online Plug-in
  • If Receiver upgrade is non possible due to feature incompatibility and/or a clean uninstall is required
  • The Receiver Clean-Upwardly 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 thirteen.10, 14.ten). This includes the Offline Plug-in component if installed.

Citrix CTX325140: How to Remove Customer Files Remaining on System after Uninstalling Receiver for Windows.

Blog posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Customer and Install Citrix Receiver 3.ten
  • Full list 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 set security vulnerabilities.

CitrixWorkspaceApp.exe electric current release version 2204.1, LTSR version 2203.1, or LTSR version 1912 CU7 (aka nineteen.12.7000) (or 1912 CU7 Hotfix i) can be installed past just double-clicking it. Note: LTSR Workspace app does non support Browser Content Redirection. Workspace app 2006 and newer practise not back up Windows vii.



Administrator vs non-ambassador

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

Car-Update

Workspace app supports motorcar-update.

Some notes:

To troubleshoot Motorcar-update, see Citrix CTX226779 Troubleshooting Citrix Receiver Updates.

Car-update is cleaved in Receiver for Windows 4.11 and older, and Receiver for Mac 12.ix and older. To fix it, manually upgrade to the next version (e.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 group 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 foreclose this splash screen, prepare the following registry value: (source = Dennis Span on Twitter)

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

Add Account Wizard

From Citrix CTX135438 How to Suppress the Add together Business relationship Window in Citrix Receiver for Windows: Subsequently installation, Workspace app volition launch and ask you to add an account. If Workspace app, notice the checkboxPractise non bear witness this window automatically at logon.

For Workspace app and Receiver iv.4 and newer, FTU (Starting time Time Utilize aka Add together Business relationship Wizard) will be displayed only if a shop is non configured. If a store is already configured via command line, GPO, or Citrix Studio, then FTU screen volition not be available after installation. Otherwise, FTU can be suppressed by doing one of the following:  (Note: Receiver iv.4.1000 and newer has a fix for preventing the Add Account magician)

  • Rename CitrixReceiver.exe to CitrixReceiverWeb.exe.
  • RenameCitrixWorkspaceApp.exe toCitrixWorkspaceAppWeb.exe.
  • Install using a command line switch:
    • CitrixWorkspaceApp.exe/ALLOWADDSTORE=Due north
    • CitrixReceiver.exe/ALLOWADDSTORE=N
  • 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 post installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, prepare AllowAddStore value to N.
  • Set the registry value: HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\NeverShowConfigurationWizard (REG_SZ) = truthful
  • Too see Suppressing Add together Account dialog at Citrix Docs.

Discover Hidden Stores

When Receiver is commencement launched, information technology must perform Discovery, which is the process of downloading the .xml provisioning file from StoreFront. Discovery is performed by inbound a StoreFront FQDN or Gateway FQDN. To detect a hidden store (a shop that'southward not advertised), add ?StoreName to the end of the FQDN. CTX214819 How to configure Receiver to a Store that is not advertised.

CitrixWorkspaceApp.exe / CitrixReceiver.exe Control line switches

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

For unattended installation of Workspace app, see 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 equally detailed below. 
    CitrixWorkspaceApp.exe /includeSSON  CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A – by default, just SSL (HTTPS) stores are accepted. To let 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 iv.x and newer can 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-merely manner: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=False  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=car /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets it to LTSR Branch just. AutoUpdateCheck can as well be prepare to manual or disabled. AutoUpdateStream can 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=True  CitrixReceiver.exe /ENABLEPRELAUNCH=Truthful
  • /ALLOW_CLIENTHOSTEDAPPSURL=1 – enables Local App Access: 
    CitrixWorkspaceApp.exe /ALLOW_CLIENTHOSTEDAPPSURL=ane  CitrixReceiver.exe /ALLOW_CLIENTHOSTEDAPPSURL=1

Registry values

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

  • SelfServiceMode (REG_SZ) = Simulated – Turns off Workspace app'south / Receiver's Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = Truthful – If Cocky-Service interface is disabled, places all shortcuts on desktop.
  • UseDifferentPathsforStartmenuAndDesktop (REG_SZ) = Truthful
    • UseCategoryAsStartMenuPath (REG_SZ) = True or Faux
    • UseCategoryAsDesktopPath (REG_SZ) = True or False
  • StartMenuDir (REG_SZ) = proper name of binder on Offset Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = name of folder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = Truthful – If SSON is enabled so PreLaunch is already enabled by default.
  • AllowAddStore (REG_SZ) = A – Just 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 proper noun
  • InitialRefreshMinMs (REG_SZ) = 1 – minimizes the launch delay before contacting store
  • InitialRefreshMaxMs (REG_SZ) = 1 – minimizes the launch delay earlier contacting store
  • RefreshMs (REG_SZ) = 3600000 (1 hour) – interval for Receiver icon refreshes. 1 hr is the default value.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Authentication Window Periodically When Receiver is Not Opened
  • MaxSimultaneousFetches (REG_DWORD) = 6  – improves the time of loading icons in Start Menu
  • MaxSimultaneousSubscribes (REG_DWORD) = 6 – improves the time of loading icons in Start Carte du jour
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server. (or False)
  • SilentlyUninstallRemovedResources (REG_SZ) = Truthful – 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 curt name.
  • PnaSSONEnabled (REG_SZ) = True – Enables Single Sign-on for PNAgent (Web Interface).
  • WSCReconnectMode (REG_SZ) = iii (default) – If this Workspace app is running inside a VDA published desktop, fix it to 0.
    • If you're having trouble getting sessions to reconnect, run across Receiver 4.three Desktop volition not automobile-reconnect when logging into a car at Citrix Discussions
  • AlwaysUseStubs (REG_SZ) = True. Workspace app and Receiver 4.3.100 and newer don't create .exe stubs by default. Set this to create .exe stubs. Also run into Citrix CTX211893 Controlling Shortcut behavior in Receiver four.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}_{ii}_{3}". Encounter the link for details.
  • SelfServiceFlags (REG_DWORD) = four – prevents duplicate shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = 5 to cease external SSON from prompting for authentication
  • ReEvaluateNetwork (REG_SZ) = true – for Buoy detection with Single FQDN

To prevent the Win+M 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 increase 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)
    • Run into CTX125027 How to Optimize HDX Bandwidth Over High Latency Connections for some recommended values (multiples of 44)

To prevent buoy probing from using proxy, prepare:

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

To enable foreground progress bar, set up:

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

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

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Avant-garde\Modules\ClientDrive
    • NativeDriveMapping="Truthful"

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

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

To prevent "USB Hub Power Exceeded" message, fix (not needed in iv.2.100 and newer):

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

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

Grouping Policy Settings

Re-create the Workspace app ADMX template (C:\Programme Files (x86)\Citrix\ICA Client\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). Also copy receiver.adml to C:\Windows\PolicyDefinitions\en-the states (or Sysvol).

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

  • To enable pass-through authentication: go to | User Authentication |.
    • Local Username and Countersign – Check the top 2 boxes.
    • Also add together the StoreFront FQDN to the Local Intranet zone in Net Explorer.
    • Single Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add together a shop, get to | StoreFront |
    • StoreFront Accounts List – see the assistance text
  • To enable Auto-Update, go to|AutoUpdate| or|Receiver Updates| or|Citrix Workspace Updates|. (the node was renamed in 4.xi 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, get to | SelfService |
    • Set Manage SelfServiceMode to Disabled to completely disable the Self-Service window. This causes all icons to exist placed on the Commencement Menu.
    • Enable Manage App Shortcut and configure information technology as desired.
      • To let the Self-Service window, but foreclose it from automatically opening (reside in systray), tickPrevent Citrix Workspace (or Receiver) performing a refresh of the application listing when opened. Source
    • Enable Command when Workspace (or Receiver) attempts to reconnect to existing sessions. If this is a VDA published desktop, fix it to Disabled. Otherwise configure it as desired.
    • Set Enable FTU to Disabled  to prevent the Add together Account sorcerer from displaying.
    • EnablePermit/Prevent users to publish unsafe content if publishing content that's opens a file or file share.

Enable automatic customer drive and client microphone mapping.

  • In a customer-side GPO, add the GPO ADM template from http://back up.citrix.com/commodity/CTX133565.
  • Enable the setting Create Client Selective Trust Keys. Run into Below for details.
  • Configure the FileSecurityPermission setting in 1 or more of the regions.
  • Configure the MicrophoneAndWebcamSecurityPermission setting in i or more of the regions.

Citrix CTX203658 Get-go Menu Icons Set to Default (Blank Document) Afterward Update to Receiver 4.three.100 – Windows eight and newer

  • Computer Configuration | Policies | Authoritative Templates | Windows Components | File Explorer
    • Allow the apply 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 computer 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.1, LTSR version 2203.1, or LTSR version 1912 CU7 (aka nineteen.12.7000), by expanding Downloads for Admins (Deployment Tools).

Also come across CTA Dennis Bridge Citrix Receiver unattended installation with PowerShell.

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

You tin can change Workspace app's / Receiver'due south configured Store/Account with a couple control lines:

"C:\Programme Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -deleteproviderbyname Corporate  "C:\Plan 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 past right-clicking the Workspace app systray icon, clickingAdvanced Preferences, and clicking theReset link. You tin can exercise this from the command line by running "C:\Program Files (x86)\Citrix\ICA Customer\SelfServicePlugin\CleanUp.exe" -cleanUser -silent. Run across CTX140149 How to Reset Receiver Using the Command Line.


Receiver for Border

The Receiver for Web experience in Microsoft Edge is not ideal. Every time a user clicks an icon, the user has the click theOpen button afterward 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. Use your preferred text editor to open web.config for the RfWeb site you 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-9]|[6789][0-9])|\d\d\d))|(Chrome/((4[2-nine]|[56789][0-9])|\d\d\d)))(?!.*Edge)". Remove (?!.*Edge) and save the file.

But once you practise that, you go a new switch apps prompt every time you launch an icon from Border.

To cease 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 set it to 0 (cypher). You can use 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 just bachelor after 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 tin can besides download the ADMX files from one of the Workspace app download pages (Workspace app electric current release version 2204.one, LTSR version 2203.ane, or LTSR version 1912 CU7 (aka 19.12.7000), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. Also copy theen-US binder. In Workspace app, the files are nonetheless namedreceiver.admx.
  3. Go to your domain's SYSVOL share and in the Policies binder wait for a PolicyDefinitions folder. If i exists, paste the .admx file directly into the PolicyDefinitions folder. If this folder doesn't exist in SYSVOL, instead copy the .admx file to C:\Windows\PolicyDefinitions. Overwrite any existing Receiver ADMX files.
  4. The GPO settings can then be constitute at ane of the post-obit:
    • Figurer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace
    • Calculator Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For case, you can disable Customer Experience 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 data to 3rd party (due east.g. Google Analytics).
  8. Workspace app 1905 and newer let you disable embedded browser caching.
  9. Workspace app 1905 and newer have NetScaler LAN Proxy underNetwork routing > Proxy.
  10. Workspace app 1808 and newer haveUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver iv.12 adds Network Routing | Deprecated cypher suites to configure deprecated ciphers.

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

Pass-through Hallmark

Citrix blog mail service – A Comprehensive Guide to Enabling Laissez passer-Through Authentication with XenDesktop 7.v

  1. Run the command
    Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $Truthful from a Windows PowerShell control prompt on a Delivery Controller.
    • In XenApp vi.5, this is a Citrix Policy > Computer > Trust XML Requests.
  2. Login to the PC as an administrator.
  3. If installing Workspace app, as an administrator, during installation, on the Enable Single Sign-on page, check the box next to Enable Single Sign-on. Then stop the installation.

  4. If installing an older version of Receiver:
    1. Go to the downloaded Citrix Receiver. Shift-correct-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. Press <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, go to C:\Plan Files (x86)\Citrix\ICA Client and wait for the file ssonsvr. exe.
  6. And if you open regedit and become to HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order, y'all should see PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if you 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 authentication.
  11. On the right, double-click Local user name and password.
  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, you can enableSingle Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Internet Explorer. You can use a GPO to configure this on the customer side.
  15. Local Intranet zone should have Automatic logon just in Intranet zone enabled.
  16. Logoff Windows and log back on. In Chore Manager y'all should now encounter 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, and then you lot might have to disable Automatically detect settings in IE.
  18. Correct-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 10 will betoken the issue and corrective action.

StoreFront Accounts

Y'all can use a client-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 Estimator Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
  4. On the right, double-click NetScaler Gateway URL/StoreFront Accounts List.
  5. Select Enabled, and so clickShow.
  6. Enter a store path based on the case 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 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 so clickShortcuts and Reconnect, orSettings Option.


From Citrix Docs Configuring application commitment: There are several methods of controlling how Workspace app displays shortcuts on the Start Carte du jour and Desktop equally detailed below:

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

Nether 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 set to False. Here are some common options:

  • SelfServiceMode – set to False and so Receiver disables the Self-Service interface and automatically places all published shortcuts on the Start Carte and/or Desktop. More than details in Configuring application delivery at Citrix Docs.
  • PutShortcutsOnDesktop– gear up toTrue to place every app on the desktop
  • DesktopDir – Workspace app places every shortcut on the desktop then information technology's probably best to place them in a folder.
  • StartMenuDir – If there is potentially a conflict between local apps and remote apps, so you should place the Commencement 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 lot import the receiver.admx (and .adml) into the PolicyDefinitions folder, under Computer Configuration > Authoritative 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.ii.100 and newer have the ability to configure (or disable) Workspace Control using group policy. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure information technology equally desired.

Prelaunch

Staring with Receiver 4.2, 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 Commencement Bill of fare.

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

Boosted customizations can exist configured at:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Prelaunch

  • Proper noun: Country
    • REG_SZ: 0 = disable, 1 = simply-in-time pre-launch, 2 = scheduled pre-launch
  • Name: Schedule
    • REG_SZ: HH:MM|M:T:Westward:Thursday:F:Due south:SU where HH and MM are hours and minutes. 1000:T:W:Thursday:F:S:SU are the days of the week. For example, to enable scheduled pre-launch on Monday, Wednesday, and Fri at 1:45 p.k., set Schedule as Schedule=13:45|ane:0:1:0:i:0:0 . The session really launches betwixt 1:15 p.m. and ane:45 p.m.
  • Proper name: UserOverride
    • REG_SZ: 0  = HKLM overrides HKCU, one = HKCU overrides HKLM

Device Access Behavior (Client Selective Trust)

When connecting to a XenApp/XenDesktop session, you might see the post-obit:

To configure the default beliefs, see the Citrix Knowledgebase article How to Configure Default Device Access Behavior of Receiver, XenDesktop and XenApp. Note: there is a bug fixed in Receiver 4.ii.100 and newer.

  1. Download the ADMX file from http://support.citrix.com/article/CTX133565.
  2. Copy the .admx and .adml files to PolicyDefinitions (Sysvol, or C:\Windows).
  3. The.adml file goes in theen-U.s. binder.
  4. Edit a GPO that applies to the endpoint devices that are running Receiver.
  5. Go to Computer 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 expand the regions, and configure the permission settings as desired.

Desktop Lock

Equally an alternative to Workspace app Desktop Lock, run into Transformer in Citrix Workspace Environs 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

Apply Studio to configure Workspace app Accounts in Published Desktop

In published desktops, Workspace app tin can be used for placement of shortcuts on the user's Start Carte du jour and Desktop. Use group policy to hide the mutual program groups and then use Workspace app to identify published applications back on the Start Menu and Desktop based on user's group membership and subscription preference.

  1. In Citrix Studio, on the left, expand the Configuration node, correct-click StoreFront and click Add together StoreFront.
  2. Enter a descriptive proper noun for the StoreFront server.
  3. Enter the internal https URL of the load counterbalanced StoreFront servers. Add the path to your shop (e.g. /Citrix/Store) then /discovery on the finish of the URL. The full URL would exist similar to https://citrix.corp.com/Citrix/Store/discovery. Click OK.
  4. Edit a Commitment Group that has a published desktop and Citrix Workspace app installed.
  5. On the StoreFront page, modify the selection to Automatically, using the StoreFront servers selected beneath, and then check the box adjacent to the StoreFront URL. Click OK. Now when users launch the published desktop, Workspace app will exist automatically configured with this URL.

Published Desktop – employ Workspace app to command Shortcuts

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

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

Configuration of Workspace app inside a published desktop is simplified if yous have the post-obit minimum versions:

  • Workspace app installed inside the VDA
  • VDA 7.17 or newer
  • StoreFront 3.fourteen 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 chosen vPrefer.

  • If y'all don't meet these minimum version requirements, and so you'll need to use the older Prefer Keyword method of handling Workspace app shortcuts as detailed subsequently.
  • For a detailed explanation of vPrefer, meet Citrix Weblog Post VPrefer: Session Sharing Between a Published Desktop and a Published Awarding Made Easy

Do the post-obit for all versions of Workspace app, VDA, and StoreFront, whether using the Prefer keyword or not:

  1. Make sure Workspace app or Receiver version 4.xi or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if you lot haven't already. For vPrefer, make certain they are the ADMX files from Workspace app.
  3. Enable the Group Policy settingRemove common programme groups from Start Carte du jour and apply it to not-administrators.
    • This removes all Public (aka All Users) Offset Card 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″ and 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 False. 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 Start Menu and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True. This creates a Start Menu folder based on the published app's configured Category.
  5. Configure each desired published app to Add together shortcut to user's desktop.
    • Or, configure HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop = True to identify all icons on the desktop.
  6. To control icon placement, configure the post-obit registry values:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to place published applications in a sub-folder. Note: Windows Server 2012 and Windows 10 and newer only supports a single level of Beginning Menu folders, so 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 set Local user name and countersign to Enabled. Bank check the box next to Allow laissez passer-through authentication for all ICA connections.
    2. If you're using Gateway internally, and if Workspace app 1808 or newer, then as well enableSingle Sign-on for NetScaler Gateway.
    3. In a user-level GPO that applies to the VDA, add together the StoreFront FQDN to the Local Intranet zone. Brand sure information technology is non in the Trusted Sites zone, or enable Automatic logon with current user name and password 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 delivery group, and the individual published applications (if visibility is express).
    1. In Citrix Studio, edit each published application, and on the Commitment tab, specify a category. This volition go the Start Carte folder name.
    2. If Workspace app Self Service Style (GUI) is enabled, in Studio, edit each application, and add together KEYWORDS:Machine and/or KEYWORDS:Mandatory to the published application description. This forces the applications to be subscribed/favorited. But subscribed (or Favorite) apps are displayed in the Start Menu and Desktop. Unless you disable Workspace app's SelfService interface every bit described earlier.
    3. Another option is to go to the StoreFront Panel, click Stores on the left, and on the right, click Configure Store 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 group policy that applies to VDAs, and configure the group policy to define the Shop URL for Workspace app like 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 store path. Make sure there is /discovery on the end. By default, Workspace app and Receiver only supporthttps.
    1. Your StoreFront store probably delivers both application and desktop icons. If you want to filter out the desktop icons, then create a new StoreFront store, and configure the Workspace app on the VDA to connect to the new Store.
    2. In StoreFront Panel, click the store for VDAs, and click Configure Store Settings. On the Advanced Settings page, in the Filter resources past blazon row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA 7.17 (or newer), and StoreFront iii.xiv (or newer), edit a GPO that applies to the VDAs.
    1. Go to Computer Configuration | Policies | Authoritative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is only in Workspace app ADMX templates from Workspace app.
    3. Set information technology toAllow all apps. Source = vii.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 client devices to connect to the published desktop.
    1. When users connect to the published desktop, Workspace app will auto-launch and hopefully auto-login.
    2. If Workspace app Self-Service Way is disabled, all published applications should automatically announced in the First Menu and Desktop.
    3. If Workspace app Self-Service Way is enabled, then only applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application clarification will exist displayed. Users tin can open up the systray icon to subscribe to more applications.
    4. Users tin re-create icons from the Kickoff Bill of fare to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    5. Users tin then launch applications directly from the Kickoff Carte du jour, from the Desktop, or from the Workspace app (if the Self-Service interface is enabled).
    6. If Workspace app iv.11 (or newer), VDA seven.17 (or newer), and StoreFront 3.14 (or newer), thenvPrefer is enabled by default. When launching an app icon that came from Workspace app, Workspace app checks the local VDA car to run across if the application tin can be launched on the local VDA instead of past creating a new Citrix double-hop session.
    7. If the application is installed locally on the VDA and so the local application shortcut should launch quickly. If the awarding is on a different delivery group then a second (double-hop) Citrix HDX/ICA connection volition be established.
    8. If the user deletes Workspace app shortcuts from the Showtime Carte du jour, you tin get them back past going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app.

If you are running components older than Receiver four.xi, VDA seven.17, and StoreFront 3.14, then y'all'll need to configure theprefer 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 use it to non-administrators.
    1. For applications that are installed on the same VDA that is publishing the desktop, configure Grouping Policy Preferences to recreate the application shortcuts based on Agile Directory group membership. Applications on other delivery groups are handled by Receiver.
    2. Or use the adopt 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 prefer keyword. This 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:Prefer to KEYWORDS:adopt. Notice the lower case p. Information technology doesn't work with upper-case letter P.
      • With the prefer keyword, if you publish an application that is also created using Group Policy Preferences, the Group Policy Preferences icon will have precedence. This is good. Otherwise the Receiver published application icon would result in a new Citrix double-hop session.
      • Run across Ralph Jansen Citrix Receiver 4.i Prefer keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter information technology as KEYWORDS:prefer=shortcutname where shortcutname is the 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 volition create shortcuts to local applications.
    2. Receiver will auto-launch and hopefully auto-login.
    3. If Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.
    4. If Receiver Self-Service Mode is enabled and then only applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application description will be displayed. Users can 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 Carte du jour and/or Desktop. See below for considerations.
    6. Users can copy icons from the Start Menu to the desktop. Brand certain the user Copies the icon and doesn't Movementit.
    7. Users tin so launch applications directly from the Start 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 awarding 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 quickly. If the application is on a unlike delivery group and so a second (double-hop) Citrix HDX/ICA connection volition exist established.
    10. If the user deletes Receiver shortcuts from the Start Carte, y'all can go them dorsum by going to the systray icon and refreshing the applications. Or sometimes you have to reset Receiver.

Notes regarding Prefer Template Directory

  • Prefer Template Directory can point toC:\ProgramData\Microsoft\Windows\Kickoff Menu, which is the All Users Start Menu.
  • The shortcuts copied from the Prefer Template Directory are renamed to match the published app proper name.
  • For prefer local apps, any command line parameters specified in the published app are ignored. If you lot need these control line parameters, add together them to the shortcut in the Adopt Template Directory.
  • If you have multiple published apps pointing to the aforementioned prefer local shortcut, then simply 1 copy will exist made, and it will have the proper name of simply 1 of the published apps. To workaround this, in the Prefer Template Directory, create dissever shortcuts for each published app, and adjust the published app prefer keyword accordingly.
  • Jan Hendrik Meier Automatic 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 withadopt keyword. These shortcuts can and so 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 by user interaction. However, SSP exposes sufficient information for its activities to be scripted.

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

If you want to drive SSP straight for launch instead of through an .exe stub, look at the keys nether HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall. There volition exist keys in there named subcontract-name@@server-farm-name.app-friendly-proper name. In these keys you'll find a LaunchString value that shows the relevant parameters. These parameters are user-independent and can therefore exist cloned from a reference user to a general case. Y'all can re-create 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 control 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 Managing director SDK. You can use 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. Get the CCMPowershellModule from Github. The PowerShell module contains functions like the post-obit:

  • 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 ane or more Published Applications from Citrix Storefront 2.x through iii.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 brandish session information.

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

  1. Opening Net Explorer.
  2. Navigating direct 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 email with the issue. Uses wficalib.dll to become 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 post-obit:

  • 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 so don't exclude that feature when installing the VDA.

Outgoing screensharing is not supported.

See Citrix Docs Optimization for Microsoft Teams.

Skype for Business concern

Citrix has a HDX RealTime Optimization Pack for Workspace app that enables offloading of Skype for Business organisation 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 3) is a Long Term Service Release (LTSR). More details at CTX200466 Lifecycle Data for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the two.iii release can exist found in Citrix Blog Post The Only Virtualization Solution for Skype Meetings Only Got Even Better!

The HDX RealTime Optimization Pack comes in ii pieces: the Connector (on the VDA), and the Media Engine (on the Workspace app machine). Usually both pieces must exist the same version, only versions two.3 and higher now allow version mixing.

  • Connector two.9 LTSR
    • Connector 2.4.3000 LTSR
  • Media Engine 2.9 LTSR
    • Media Engine 2.4.3000 LTSR

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

For Skype for Business Location Based Routing, you'll need the post-obit: (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.one and higher up) in the Click-to-Run (C2R) download quite a long time ago, but it hasn't yet been introduced in the MSI package.
  • It requires setting IsLBRInVDIEnabled on the Skype for Business Server to True: 
    $x = New-CsClientPolicyEntry -Proper noun "IsLBRInVDIEnabled" -Value "true" Set-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add=$10}

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

Citrix CTX222459 RealTime Optimization Pack Adequacy Checker: It will list 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 whatsoever Windows machine.

Citrix CTX214237 LOPper – Lync Optimization Pack Log Parser: parses log files generated by Citrix HDX RealTime Optimization Pack (HROP) when an sound/video call is fabricated using Lync 2013/Skype for Business organization (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 then information technology shows you the published resources. You lot can choice a resource, edit properties on the other tabs, and so Connect. This allows you lot to hands effort unlike connection backdrop.

If you run into issues launching a session, use Sysinternals DebugView while running CQL in Debug mode (/debug switch).

Troubleshooting – Workspace app Logging

There 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.

Some other 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 Fundamental.

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

Windows Registry Editor Version v.00  ;just 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 be 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"="True"  ;Cocky Service logging ;******************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle] "Tracing"="True" "AuxTracing"="Truthful" "DefaultTracingConfiguration"="global all –detail"  ;relieve launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables immune) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Advanced\Modules\Logging] "LogConfigurationAccess"="true" "LogConnectionAuthorisation"="truthful" "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 ;tin can exist 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/commodity/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 you are running Workspace app inside a VDA. (h/t Dan Loftier)

StoreFront URLs tin be defined in several places:

  1. In Studio, become to Configuration > StoreFront and delete all URLs configured here.
  2. Look in GPOs for Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts List. Remove any URLs configured here.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you might see 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, information technology's possible for each datacenter to be treated every bit a split 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. Lucifer the SRID in all datacenters – The SRID can exist safely edited in the C: \inetpub\wwwroot\Citrix\Roaming\web.config. Make sure to propagate changes to other servers in the group.
    3. Friction match the Delivery Controller names under "Manage Delivery Controllers" – The XML brokers tin be different, but the actual proper noun of the Delivery Controller/Subcontract must be identical.

If you lot are running Workspace app on a VDA, one time you lot've removed the configured URLs shown in a higher place, do the following to make 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\Terminal Server\Install\Software\Citrix – Remove the entries for storefront in the post-obit folders.
    1. Nether \receiver\ctxaccount delete all entries.
    2. Under \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'south registry, HKEY_CURRENT_USER or the profile registry hive. Possible profile reset.
    1. Under Software\Citrix\Dazzle\Sites – Delete all entries.
    2. Nether Software\Citrix\Receiver\ctxaccount – delete all entries.
    3. Under Software\Citrix\SR\Store – delete the entries.
  7. Verify no cached contour folders for user on server.

butleryouspe.blogspot.com

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

Post a Comment for "Citrix Access Management Console an Error Occurred Try Performing the Task Again"