Random Posts

Home  ›  Uncategorized

6".locate or Download the Software Installaion Files Updated FREE

6".locate or Download the Software Installaion Files

Navigation

Workspace app is the new name for Receiver. This post applies to all Workspace app versions, and all Receiver versions 4.0 and newer, versions 1808 and newer (e.g. 2202), and the LTSR versions.

  • Change Log
  • Workspace app versions
  •  Overview
    • Workspace app Modules
    • Workspace app Discovery and Beacon Procedure
    • Virtual Monitors
  • Uninstall Old Receiver Clients
  • Installation and Configuration
    • Ambassador vs not-administrator
    • Workspace app Machine-Update
    • Splash Screen
    • Add Business relationship Sorcerer
    • CitrixWorkspaceApp.exe Command line switches
    • Workspace app Registry values
    • Workspace app Group Policy settings
    • Client-side Registry for Microsoft Edge
  • Workspace app ADMX GPO Template
  • Pass-through Authentication
  • Automatically add StoreFront Accounts to Workspace app
  • Control Shortcut placement on Desktop and Commencement 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 identify shortcuts
  • Script / Automate Workspace app and Receiver Cocky-Service
  • Microsoft Teams
  • Skype for Business
  • Troubleshoot:
    • Citrix QuickLaunch
    • Workspace app Logging
    • Make clean upward Duplicate Stores

💡 = Recently Updated

Change Log

  • 2022 Feb 7 – updated entire article for Workspace app 2202
  • 2021 Dec nine – Versions – updated for Workspace app 1912 LTSR Cumulative Update vi
  • 2021 Dec viii – updated unabridged article for Workspace app 2112.one
  • 2021 Oct 4 – updated entire article for Workspace app 2109.i
  • 2021 Sep 29 – updated unabridged article for Workspace app 2109
  • 2021 Aug thirty – updated unabridged article for Workspace app 2108
  • 2021 Aug 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 5
  • 2021 July 29 – updated entire article for Workspace app 2107
  • 2021 June xvi – updated entire article for Workspace app 2106
  • 2021 May eleven – Workspace app 1912 CU4 and Workspace app 2105 and newer gear up security vulnerabilities
  • 2021 May ten – updated entire article for Workspace app 2105
  • 2021 May x – Versions – updated for Workspace app 1912 LTSR Cumulative Update 4
  • 2021 Mar 23 – updated entire commodity for Workspace app 2103.1
  • 2021 Mar sixteen – updated entire article for Workspace app 2103
  • 2021 February 1 – updated entire article for Workspace app 2102
  • 2021 Jan 20 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 Dec 18 – updated unabridged article for Workspace app 2012.1
  • 2020 Dec 8 – updated entire article for Workspace app 2012
  • 2020 Nov ii – updated entire article for Workspace app 2010
  • 2020 Oct 15 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct ane – updated entire article for Workspace app 2009.6
  • 2020 Sep 24 – updated entire article for Workspace app 2009.five
  • 2020 Sep xv – updated entire article for Workspace app 2009

Workspace app Versions

Workspace app is the new name for Receiver.

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

Workspace app uses a YYMM (year/month) versioning format, of which version 2202 (21.12.i) is the newest.

Workspace app 2009 and newer have the new Citrix logo.

Workspace app 1912 and newer support App Protection. Information technology's available in both the LTSR 1912 version and the Current Release 2202 version.

The LTSR (Long Term Service Release) version of Workspace app is version 1912 Cumulative Update 6 (aka 19.12.6000). CU5 and newer comprise many Teams optimization enhancements. The LTSR version of Workspace app does not back up 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. Hither are the important ones:

  • ICA Engine (wfica.exe) – procedure that uses the ICA protocol to connect to published apps and desktops.
  • Cocky-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 found a connection.
  • Unmarried Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs after an ICA connectedness is established
  • Workspace Auto-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The most recent name for this component is Citrix Workspace Update.

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

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

Workspace app Discovery and Beacon Process

If y'all are using Workspace app's built-in user interface (instead of a web browser), and then Workspace app showtime prompts you to perform discovery, which is also called Add together Business relationship.

The Citrix logo changed in Workspace app 2009 and newer.

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

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

  • If you lot entered a StoreFront FQDN, then Workspace app will download the Provisioning File direct from the StoreFront server.
  • If you entered a Gateway FQDN, and then Gateway will offset prompt the user to authenticate. After hallmark, Gateway will connect to its configured Business relationship Services accost, and download the Provisioning File from StoreFront. The Account Services address is configured in the NetScaler Gateway Session Contour on the Published Applications tab.

If your StoreFront server is configured with multiple stores, then the user will exist prompted to select a store. Unfortunately, there's no configuration option in NetScaler Gateway to force a particular store.

  • One workaround is to hide the store that you don't want visible externally. See How to configure Receiver to a Store that is non advertised for special syntax.

The Provisioning File downloaded from StoreFront is an XML certificate containing values for several items configured in the StoreFront console. You tin can export the Provisioning File from the StoreFront console past correct-clicking a Store.

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'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, information technology so performs the following steps:

  1. Attempt to connect to the Internal Beacon.
  2. If the Internal Buoy is reachable, connect directly to the StoreFront Base URL (Address).
  3. If the Internal Beacon is not reachable:
    1. Attempt to connect to the External Beacons. If the External Beacons are not reachable, then 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 nix to do with how Workspace app connects to StoreFront or Gateway. The actual connexion process is controlled past the contents of the Provisioning File, not the Discovery address.
  • If the Provisioning File has multiple Gateways divers, Workspace app uses whichever Gateway is marked as Default. Workspace app and Receiver completely ignore whatever Gateway FQDN you entered during Discovery. To use a not-default Gateway, the user must manually select the other Gateway in Workspace app'south / Receiver'due south Advanced Preferences.

In StoreFront Console, if whatsoever configuration changes are performed that affect the Provisioning File, do the Workspace apps / Receivers reconfigure themselves automatically? Or practice users accept to remove Accounts and re-add (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 can split the screen into virtual monitors. This characteristic is intended for large 4K monitors.

Uninstall Sometime Clients

Workspace app and Receiver 4.iv and newer includes Receiver Clean-Upward, so, in theory, information technology's not necessary to uninstall quondam clients showtime. For more details, run into 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 feel, write a script to remove the old clients, make clean upward the registry and file system, and then deploy the new Workspace app.

Citrix Blog Post Cookbook to Upgrade from Receiver three.4 for Windows to Receiver 4.two.100 and Citrix Article CTX135933 Upgrading to Citrix Receiver for Windows contains step-by-footstep procedure to use Group Policy to uninstall Receiver Enterprise 3.four and install/configure Workspace app.

The Receiver Make clean-Up utility for Receiver 4.three and older is designed to help with the post-obit scenarios:

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

Citrix CTX325140: How to Remove Client Files Remaining on System afterwards Uninstalling Receiver for Windows.

Blog posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Client and Install Citrix Receiver three.x
  • Full list of Citrix Client 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 prepare security vulnerabilities.

CitrixWorkspaceApp.exe version 2202 (Electric current Release), or CitrixWorkspaceApp.exe version 1912 CU6 (aka nineteen.12.6000) (LTSR), can be installed by just double-clicking it. Note: LTSR 1912 does not support Browser Content Redirection. Workspace app 2006 and newer do not support Windows 7.

Administrator vs non-administrator

  • Non-administrator – If a non-administrator installs Workspace app, then each non-administrator that logs in to the same workstation will have to reinstall Workspace app.
    • Non-administrator installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.
  • Administrator – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator account. then the Workspace app only needs to be installed once.
    • Ambassador installations are installed to C:\Program Files (x86)\Citrix\ICA Client.
    • Ambassador installations of Workspace app 1912 and newer tin can be manually upgraded past non-administrators by clicking Check for Updates. Older versions cannot be upgraded past non-administrators.
  • Conflicts – If an ambassador install of Workspace app is performed on a machine that has non-administrator installs of Workspace app, and so the 2 installations will disharmonize. All-time choice is to uninstall non-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 again.
    • Citrix article CTX249920 Workspace App for Windows – Your apps are non available at this time – Issue when installing Citrix Receiver in not elevated/per-user install mode describes the HKEY_CURRENT_USER registry keys that must be deleted to prepare this issue.
    • For a script to make clean-up the per-user installs, see Mark DePalma at Citrix Receiver Per-User Install Cleanup.

Car-Update

Workspace app supports automobile-update.

Some notes:

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

Auto-update is cleaved in Receiver for Windows four.11 and older, and Receiver for Mac 12.9 and older. To ready it, manually upgrade to the next version (e.k. Workspace app for Mac), or install the Fix 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 Car-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 up the following registry value: (source = Dennis Bridge on Twitter)

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

Add Account Wizard

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

For Workspace app and Receiver 4.4 and newer, FTU (First Time Use aka Add Business relationship Wizard) will exist displayed merely if a store is not configured. If a store is already configured via command line, GPO, or Citrix Studio, then FTU screen will not be available after installation. Otherwise, FTU can be suppressed by doing 1 of the following:  (Note: Receiver iv.4.1000 and newer has a set for preventing the Add Account sorcerer)

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

Discover Hidden Stores

When Receiver is offset 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 discover a hidden store (a store that's not 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, see CTA Dennis Span Citrix Workspace App unattended installation with PowerShell or Citrix Receiver unattended installation with PowerShell.

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

  • /silent
  • /includeSSON – enables laissez passer-through authentication. GPO configuration is also required every bit detailed below. 
    CitrixWorkspaceApp.exe /includeSSON  CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A – past default, only SSL (HTTPS) stores are accepted. To allow non-SSL stores: 
    CitrixWorkspaceApp.exe /ALLOWADDSTORE=A  CitrixReceiver.exe /ALLOWADDSTORE=A
  • / STORE0 – To add a store from the installation 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 Store"
    • Workspace App and Receiver 4.10 and newer can notice the Shop 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=Faux – disables the Self-Service interface and enables shortcut-only mode: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=False  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=auto /AutoUpdateStream=LTSR – enables Citrix Workspace (or Receiver) Update notifications and sets information technology to LTSR Branch only. AutoUpdateCheck can too be set to manual or disabled. AutoUpdateStream tin also exist ready to Electric current. See Configuring Citrix Workspace Updates at Citrix Docs. 
    CitrixWorkspaceApp.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR  CitrixReceiver.exe /AutoUpdateCheck=motorcar /AutoUpdateStream=LTSR
  • /ENABLEPRELAUNCH=True – enables prelaunch: 
    CitrixWorkspaceApp.exe /ENABLEPRELAUNCH=True  CitrixReceiver.exe /ENABLEPRELAUNCH=True
  • /ALLOW_CLIENTHOSTEDAPPSURL=1 – enables Local App Access: 
    CitrixWorkspaceApp.exe /ALLOW_CLIENTHOSTEDAPPSURL=1  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) = False – Turns off Workspace app's / Receiver's Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = True – If Cocky-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) = proper noun of folder on Start Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = name of binder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = Truthful – If SSON is enabled 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) = ane – minimizes the launch delay before contacting store
  • InitialRefreshMaxMs (REG_SZ) = 1 – minimizes the launch filibuster before contacting store
  • RefreshMs (REG_SZ) = 3600000 (1 60 minutes) – interval for Receiver icon refreshes. 1 hour is the default value.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Authentication Window Periodically When Receiver is Not Opened
  • MaxSimultaneousFetches (REG_DWORD) = half dozen  – improves the time of loading icons in Starting time Carte du jour
  • MaxSimultaneousSubscribes (REG_DWORD) = vi – improves the fourth dimension of loading icons in Kickoff Menu
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server. (or False every bit mentioned at Citrix Discussions?)
  • 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 adopt keyword. Give the shortcuts a short proper noun.
  • PnaSSONEnabled (REG_SZ) = Truthful – Enables Unmarried Sign-on for PNAgent (Spider web Interface).
  • WSCReconnectMode (REG_SZ) = iii (default) – If this Workspace app is running inside a VDA published desktop, fix it to 0.
    • If you lot're having trouble getting sessions to reconnect, come across Receiver 4.3 Desktop will not auto-reconnect when logging into a car at Citrix Discussions
  • AlwaysUseStubs (REG_SZ) = True. Workspace app and Receiver 4.iii.100 and newer don't create .exe stubs by default. Set this to create .exe stubs. Also see Citrix CTX211893 Controlling Shortcut behavior in Receiver iv.iii.100.
  • DontCreateAddRemoveEntry (REG_SZ) = True – don't create "Delivered by Citrix" entries in Programs and Features
  • DesktopNameFormatString = format string for shortcut names – For example "{0}_{1}_{2}_{iii}". See the link for details.
  • SelfServiceFlags (REG_DWORD) = iv – prevents duplicate shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = 5 to terminate external SSON from prompting for authentication
  • ReEvaluateNetwork (REG_SZ) = true – for Beacon detection with Single FQDN

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

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

To allow adding not-HTTPS stores to Workspace app:

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

To increase ICA bandwidth consumption over loftier latency links, ready:

  • 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, ready:

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

For customer-to-server file blazon redirection, set:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\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="x"

To preclude "USB Hub Ability Exceeded" message, fix (non needed in 4.ii.100 and newer):

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

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

Grouping Policy Settings

Re-create the Workspace app ADMX template (C:\Program Files (x86)\Citrix\ICA Client\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). Besides copy receiver.adml to C:\Windows\PolicyDefinitions\en-u.s.a. (or Sysvol).

Edit a GPO that applies to client machines, get to Computer 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 Countersign – Check the top two boxes.
    • Also add the StoreFront FQDN to the Local Intranet zone in Internet Explorer.
    • Single Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add together a store, go to | StoreFront |
    • StoreFront Accounts List – see the help text
  • To enable Motorcar-Update, go to|AutoUpdate| or|Receiver Updates| or|Citrix Workspace Updates|. (the node was renamed in 4.11 and Workspace app)
    • Enable or Disable AutoUpdate or
    • Receiver Updates or
    • Citrix Workspace Updates
  • To enable Local App Access, go to | User Experience |
    • Local App Access Settings
  • To configure the Self-Service interface, get to | SelfService |
    • Set Manage SelfServiceMode to Disabled to completely disable the Self-Service window. This causes all icons to be placed on the Start Menu.
    • Enable Manage App Shortcut and configure it as desired.
      • To allow the Self-Service window, merely prevent it 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, set it to Disabled. Otherwise configure it as desired.
    • Set Enable FTU to Disabled  to prevent the Add Account wizard from displaying.
    • EnableAllow/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 client-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 one or more of the regions.
  • Configure the MicrophoneAndWebcamSecurityPermission setting in i or more of the regions.

Citrix CTX203658 Start Menu Icons Set to Default (Blank Certificate) Afterward Update to Receiver iv.iii.100 – Windows 8 and newer

  • Computer Configuration | Policies | Administrative Templates | Windows Components | File Explorer
    • Let the utilize 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 version 2202 (Current Release), or Workspace app version 1912 CU6 (aka 19.12.6000) (LTSR), by expanding Downloads for Admins (Deployment Tools).

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

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

You can change Workspace app'southward / Receiver'southward configured Store/Account with a couple command lines:

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


Receiver for Edge

The Receiver for Spider web experience in Microsoft Border is non ideal. Every time a user clicks an icon, the user has the click theOpen button after the .ica file is downloaded.

Citrix Blog Post Providing Full Receiver for 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/((5[iii-9]|[6789][0-9])|\d\d\d))|(Chrome/((4[2-9]|[56789][0-9])|\d\d\d)))(?!.*Edge)". Remove (?!.*Edge) and save the file.

Just once you do that, yous 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 prepare information technology to 0 (zero). Y'all tin use Group Policy Preferences to deploy this registry value.

Workspace app Group Policy ADMX Template

Many of the Workspace app configuration settings must exist configured in group policy. These Workspace app settings are just available after installing the GPO templates.

  1. From a machine that has Workspace app installed, detect the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • You can also download the ADMX files from i of the Workspace app download pages (Workspace app version 2202 (Current Release), or Workspace app version 1912 CU6 (aka nineteen.12.6000) (LTSR), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. As well copy theen-The states folder. In Workspace app, the files are still namedreceiver.admx.
  3. Go to your domain'south SYSVOL share and in the Policies folder look for a PolicyDefinitions folder. If ane 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 any existing Receiver ADMX files.
  4. The GPO settings can then exist found at 1 of the post-obit:
    • Calculator Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace
    • Reckoner Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For example, you lot can disable Customer Feel Comeback Program (CEIP) from here.
  6. See https://www.carlstalhood.com/commitment-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 third party (e.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 netherNetwork routing > Proxy.
  10. Workspace app 1808 and newer haveUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver four.12 adds Network Routing | Deprecated goose egg suites to configure deprecated ciphers.

  12. Citrix Workspace Updates, (akaAutoUpdate) tin be configured using grouping policy. Encounter Configuring Citrix Workspace Updates at Citrix Docs.
  13. Workspace app 1912 and newer tin can be configured to require in-memory ICA files only. The setting chosen Secure ICA file session launch is under the Client Engine node. Meet Citrix Docs for details on in-retentivity ICA files instead of writing ICA files to disk.
  14. Workspace app has settings to hibernate Avant-garde Preferences, enable/disable DPI, and enable/disable H265.
  15. Workspace app iv.8 and newer accept SplitDevices GPO setting underCitrix Workspace | Remoting client devices | Generic USB Remoting. See Configuring composite USB device redirection at Citrix Docs.

Pass-through Authentication

Citrix blog post – A Comprehensive Guide to Enabling Laissez passer-Through Hallmark with XenDesktop 7.5

  1. Run the command
    Fix-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on a Delivery Controller.
    • In XenApp 6.5, this is a Citrix Policy > Reckoner > Trust XML Requests.
  2. Login to the PC as an administrator.
  3. If installing Workspace app, equally an administrator, during installation, on the Enable Single Sign-on page, check the box adjacent to Enable Unmarried Sign-on. So finish 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 up a command prompt.
    3. Correct-click to paste the path in the control prompt and and so add /includeSSON to the end of the command. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, go to C:\Program Files (x86)\Citrix\ICA Client and look for the file ssonsvr. exe.
  6. And if y'all open regedit and go to HKLM\Organisation\CurrentControlSet\Control\NetworkProvider\Lodge, you should see PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if you oasis't already.
  8. Edit a GPO that is applied to the client PCs where the Workspace app is installed.
  9. Go to Estimator Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Workspace.
  10. Expand Citrix Workspace and click User hallmark.
  11. On the right, double-click Local user name and password.
  12. Select Enabled and so check the box next to Allow pass-through authentication for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, you tin enableSingle Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Cyberspace Explorer. Y'all can use a GPO to configure this on the customer side.
  15. Local Intranet zone should accept Automated logon but in Intranet zone enabled.
  16. Logoff Windows and log back on. In Task Manager you lot should now run across ssonsvr. exe. This won't appear unless you logoff and log back on.
  17. If Workspace app won't connect or is ho-hum to enumerate icons, then you lot might have to disable Automatically discover settings in IE.
  18. Right-click the Workspace app icon and click Avant-garde Preferences.
  19. ClickConfiguration Checker.
  20. Cheque the box adjacent toSSONChecker and clickRun.
  21. The lines with scarlet ten volition point the issue and corrective action.

StoreFront Accounts

You can use a client-side GPO to add together a shop (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. Go to Figurer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
  4. On the correct, double-click NetScaler Gateway URL/StoreFront Accounts List.
  5. Select Enabled, so clickShow.
  6. Enter a store path based on the example shown in the Help box. Workspace app lets you enter a Gateway path. Then click OK.
  7. Note: Gateway paths piece of work in GPO, but might not work when specified in the CitrixWorkspaceApp.exe installation command line.

Published Shortcuts and Reconnect

Citrix CTX200924 How to Customize App Shortcuts with Receiver for Windows

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


From Citrix Docs Configuring application commitment: At that place are several methods of controlling how Workspace app displays shortcuts on the Showtime Menu 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 (e.g. prefer).
  • Workspace app and Receiver 4.2.100 and newer supports published app Delivery configuration for adding the shortcut to the desktop. This just 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 prepare to Simulated. Here are some common options:

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

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

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

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

Workspace app and Receiver iv.2.100 and newer accept the ability to configure (or disable) Workspace Command using group policy. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure it as 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.ii.100 prevents the prelaunch icon from actualization on the First Menu.

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

Additional customizations can be configured at:

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

  • Name: State
    • REG_SZ: 0 = disable, 1 = just-in-time pre-launch, ii = scheduled pre-launch
  • Proper name: Schedule
    • REG_SZ: HH:MM|M:T:W:Th:F:Southward:SU where HH and MM are hours and minutes. K:T:West:Thursday:F:South:SU are the days of the week. For example, to enable scheduled pre-launch on Monday, Wednesday, and Friday at i:45 p.m., ready Schedule as Schedule=xiii:45|1:0:1:0:1:0:0 . The session actually launches between 1:xv p.m. and i:45 p.m.
  • Name: UserOverride
    • REG_SZ: 0  = HKLM overrides HKCU, 1 = HKCU overrides HKLM

Device Admission Behavior (Customer Selective Trust)

When connecting to a XenApp/XenDesktop session, yous might come across the following:

To configure the default behavior, run across 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.2.100 and newer.

  1. Download the ADMX file from http://support.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. Get to Calculator Configuration | Policies | Authoritative Templates | Citrix Components | Citrix Workspace (or Receiver) |Citrix Customer Selective Trust (x64).
  6. Enable the setting Create Client Selective Trust Keys.

  7. And so expand the regions, and configure the permission settings as desired.

Desktop Lock

As an culling to Workspace app Desktop Lock, see 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 culling to Desktop Lock – ThinKiosk

Utilise Studio to configure Workspace app Accounts in Published Desktop

In published desktops, Workspace app can be used for placement of shortcuts on the user'southward Offset Carte du jour and Desktop. Use grouping policy to hide the common plan groups then utilize Workspace app to place published applications dorsum 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, 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 balanced StoreFront servers. Add the path to your store (due east.g. /Citrix/Store) then /discovery on the end of the URL. The full URL would exist 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, change the option to Automatically, using the StoreFront servers selected below, and then check the box next to the StoreFront URL. Click OK. At present when users launch the published desktop, Workspace app will be automatically configured with this URL.

Published Desktop – utilise Workspace app to control Shortcuts

If y'all install Workspace app inside a published desktop (Workspace app on a VDA), then Workspace app tin become icons from StoreFront and put those icons on the user's published desktop Commencement Bill of fare and Desktop. This is an alternative to using a User Experience Management product to command shortcut placement.

Note: Workspace app tends to exist slow to create Beginning Card shortcuts, so make 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 within the VDA
  • VDA 7.17 or newer
  • StoreFront 3.14 or newer

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

  • If you don't run across these minimum version requirements, then you'll need to use the older Prefer Keyword method of handling Workspace app shortcuts as detailed later on.
  • For a detailed explanation of vPrefer, see Citrix Blog Mail service VPrefer: Session Sharing Betwixt a Published Desktop and a Published Application Fabricated Easy

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

  1. Brand sure Workspace app or Receiver version 4.xi or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if you oasis't already. For vPrefer, make certain 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) Start Menu shortcuts. Workspace app volition re-add the shortcuts based on user group membership.
  4. On the VDA, configure the following Workspace app Registry keys (or corresponding settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\WSCReconnectMode="0″ so Workspace app doesn't try to reconnect to the published desktop you're already running.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\SelfServiceMode to False. This turns off the Workspace app Self-Service GUI and acts similar all icons are subscribed. Otherwise, but subscribed (favorited) icons would be placed on the Start Card and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = Truthful. 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 command 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 ten and newer only supports a single level of Commencement 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 authentication:
    1. In a GPO that applies to the VDA, import the receiver.admx file, and set Local user name and countersign to Enabled. Check the box next to Let pass-through hallmark for all ICA connections.
    2. If you're using Gateway internally, and if Workspace app 1808 or newer, 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 it 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 afterwards you login to the VDA. If non, 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 delivery type = Desktop and Applications. Assign users to the delivery group, and the private published applications (if visibility is express).
    1. In Citrix Studio, edit each published application, and on the Delivery tab, specify a category. This will get the Offset Menu folder name.
    2. If Workspace app Self Service Mode (GUI) is enabled, in Studio, edit each awarding, and add together KEYWORDS:Auto and/or KEYWORDS:Mandatory to the published application description. This forces the applications to be subscribed/favorited. Only subscribed (or Favorite) apps are displayed in the Get-go Menu and Desktop. Unless you disable Workspace app's SelfService interface as described earlier.
    3. Another choice is to go to the StoreFront Panel, click Stores on the left, and on the right, click Configure Shop Settings, and click Disable User Subscriptions. This causes all apps to appear on the Start Menu and/or Desktop depending on Workspace app configuration.
  10. Create a group policy that applies to VDAs, and configure the group policy to define the Store URL for Workspace app like to https://citrix.corp.com/Citrix/Store/discovery. Supplant the FQDN with your load balanced StoreFront FQDN. Also supplant the path to the store with your store path. Make certain there is /discovery on the finish. By default, Workspace app and Receiver only supporthttps.
    1. Your StoreFront store probably delivers both awarding and desktop icons. If you want to filter out the desktop icons, then create a new StoreFront store, and configure the Workspace app on the VDA to connect to the new Shop.
    2. In StoreFront Console, click the store for VDAs, and click Configure Store Settings. On the Avant-garde Settings page, in the Filter resource past type row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA seven.17 (or newer), and StoreFront 3.14 (or newer), edit a GPO that applies to the VDAs.
    1. Go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is only in Workspace app ADMX templates from Workspace app.
    3. Set information technology toLet all apps. Source = 7.17 vPrefer – not working with 32Bit Apps at Citrix Discussions.
  12. On your Commitment Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $true
    • This is required for Laissez passer-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 motorcar-login.
    2. If Workspace app Self-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 but applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application description will be displayed. Users can open up the systray icon to subscribe to more applications.
    4. Users tin re-create icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    5. Users tin can then launch applications directly from the Start Carte, from the Desktop, or from the Workspace app (if the Cocky-Service interface is enabled).
    6. If Workspace app 4.11 (or newer), VDA vii.17 (or newer), and StoreFront 3.14 (or newer), sovPrefer is enabled by default. When launching an app icon that came from Workspace app, Workspace app checks the local VDA machine to run across if the application tin be launched on the local VDA instead of by creating a new Citrix double-hop session.
    7. If the application is installed locally on the VDA and then the local application shortcut should launch quickly. If the application is on a different commitment group then a second (double-hop) Citrix HDX/ICA connection will be established.
    8. If the user deletes Workspace app shortcuts from the Beginning Menu, you can get them back by going to the systray icon and refreshing the applications. Or sometimes you accept to reset Workspace app.

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

  1. Enable the Group Policy settingRemove common program groups from Start Menu and utilise it to non-administrators.
    1. For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the awarding shortcuts based on Active Directory grouping membership. Applications on other delivery groups are handled by Receiver.
    2. Or utilise the adopt keyword to copy shortcuts from the PreferTemplateDirectory.
  2. On the VDA, configure the post-obit 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 be copied by the prefer keyword. This can betoken to C:\ProgramData\Microsoft\Windows\Commencement Menu.
  3. In Citrix Studio, configure a Delivery Grouping with delivery type = Desktop and Applications. Assign users to the Delivery Grouping and the applications (if visibility is limited).
    1. In Studio, edit each awarding and change KEYWORDS:Prefer to KEYWORDS:prefer. Find the lower case p. It doesn't work with uppercase P.
      • With the prefer keyword, if you publish an application that is also created using Group Policy Preferences, the Group Policy Preferences icon will have precedence. This is expert. Otherwise the Receiver published awarding icon would result in a new Citrix double-hop session.
      • Run across Ralph Jansen Citrix Receiver 4.1 Prefer keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter it equally 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 will create shortcuts to local applications.
    2. Receiver will motorcar-launch and hopefully motorcar-login.
    3. If Receiver Self-Service Way is disabled, all published applications should automatically announced in the Beginning Menu and Desktop.
    4. If Receiver Self-Service Style is enabled then only applications with KEYWORDS:Machine and/or KEYWORDS:Mandatory in the published awarding clarification will exist displayed. Users tin can open the systray icon to subscribe to more than applications.
    5. For published applications with KEYWORDS:prefer=shortcutname, Receiver should copy icons from the template directory to the Start Menu and/or Desktop. See below for considerations.
    6. Users tin copy icons from the Start Carte du jour to the desktop. Make sure the user Copies the icon and doesn't Moveinformation technology.
    7. Users can then launch applications directly from the Start Menu, from the Desktop, or from the Receiver (if Self-Service interface is enabled).
    8. If a local shortcut (east.k. Group Policy Preferences shortcut, or copied from template directory) matches a published application withKEYWORDS:adopt 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 different delivery group then a second (double-hop) Citrix HDX/ICA connection volition be established.
    10. If the user deletes Receiver shortcuts from the Showtime Bill of fare, yous tin get them back past going to the systray icon and refreshing the applications. Or sometimes you lot have to reset Receiver.

Notes regarding Prefer Template Directory

  • Prefer Template Directory can point toC:\ProgramData\Microsoft\Windows\Start Carte, which is the All Users Start Menu.
  • The shortcuts copied from the Adopt Template Directory are renamed to friction match the published app name.
  • For prefer local apps, any command line parameters specified in the published app are ignored. If you demand these control line parameters, add them to the shortcut in the Prefer Template Directory.
  • If you have multiple published apps pointing to the same adopt local shortcut, and then only one copy will exist made, and it will have the proper noun of only one 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 environment has a script that tin can create shortcuts based on the published apps withprefer keyword. These shortcuts can so be copied to your Prefer Template Directory.

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

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

When SSP builds a shortcut, information technology builds it to a small-scale stub application in a file %appdata%\Citrix\SelfService\app-name-with-spaces-removed.exe for each resource. These files let SSP to create a imitation 'install' record for Add/Remove Software. Running these .exe files causes the awarding to launch. Note: Workspace app and Receiver 4.iii.100 and newer don't create stubs by default. To enable, set up HKLM\Software\Wow6432Node\Citrix\Dazzle\AlwaysUseStubs (REG_SZ) = truthful.

If y'all desire to drive SSP directly for launch instead of through an .exe stub, wait at the keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall. There volition exist keys in there named farm-name@@server-farm-proper name.app-friendly-name. In these keys you'll discover a LaunchString value that shows the relevant parameters. These parameters are user-independent and can therefore exist cloned from a reference user to a full general case. You can copy and reuse these parameters without interpretation.

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

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

Citrix Workspace app and Receiver come with a .dll file that implements the Citrix Common Connection Manager SDK. Y'all tin employ the CCM SDK to exercise the following:

  • Launch Sessions
  • Disconnect Sessions
  • Logoff Sessions
  • Become 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 than Published Applications from Citrix Storefront 2.10 through 3.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 Net 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 resource. Sends email with the result. Uses wficalib.dll to get session information.

Microsoft Teams

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

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

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

The redirection components are congenital 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

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 bachelor versions:

  • Version 2.9 is a Long Term Service Release (LTSR). Meet HDX RealTime Optimization Pack 2.ix LTSR at Citrix Docs.
  • Version two.iv.3000 (Cumulative Update three) is a Long Term Service Release (LTSR). More details at CTX200466 Lifecycle Information for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the ii.3 release tin be found in Citrix Web log Post The Simply 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 motorcar). Usually both pieces must be the aforementioned version, but versions 2.3 and higher now allow version mixing.

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

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

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

  • Microsoft added back up for Location Based Routing (LBR) with the virtualized Skype for Business 2016 customer (and HDX RTOP 2.1 and above) in the Click-to-Run (C2R) download quite a long time agone, merely it hasn't yet been introduced in the MSI bundle.
  • Information technology requires setting IsLBRInVDIEnabled on the Skype for Business Server to True: 
    $x = 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. See Citrix Blog Post Implementing the Citrix HDX RealTime Optimization Pack: Don't Forget About QoS/DSCP.

Citrix CTX222459 RealTime Optimization Pack Capability Checker: It will list out endpoint hardware/software information which will exist used to process audio and video. The tool is independent of RealTime Optimization Pack version and runs whatever Windows car.

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 yous launch Citrix sessions directly from a Controller without needing StoreFront.

You enter a Controller address, credentials, and and so information technology shows y'all the published resources. Y'all can selection a resource, edit properties on the other tabs, and then Connect. This allows you to easily attempt dissimilar connection properties.

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

Troubleshooting – Workspace app Logging

In that location are a couple methods of logging Workspace app for Windows operations. 1 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 lot tin use the post-obit .reg file provided past Wolfgang Thürr:

Windows Registry Editor Version 5.00  ;only for x64 windows os ;import with admin rights ;restart your computer to actuate the logging and tracing settings ;create C:\TEMP for the launch ICA log and SSON logn (no surround 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  ;Hallmark Managing director 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"="True" "AuxTracing"="True" "DefaultTracingConfiguration"="global all –detail"  ;salvage launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables immune) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Avant-garde\Modules\Logging] "LogConfigurationAccess"="true" "LogConnectionAuthorisation"="true" "LogEvidence"="true" "LogICAFile"="true" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="true"  ;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  ;Unmarried Sign-on Logging ;************************** ;https://support.citrix.com/article/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="truthful" "LogPath"="C:\\Temp"

Troubleshooting – Indistinguishable 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. Await in GPOs for Computer Configuration > Authoritative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts Listing. Remove any URLs configured here.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you might see shop addresses that were specified during a command line installation of Workspace app.
  4. When Citrix Workspace app switches between StoreFront servers in multiple datacenters, it'due south possible for each datacenter to be treated every bit a dissever Workspace app site. This can be prevented by doing the post-obit. From Juan Zevallos at Citrix Discussions:
    1. Match the BaseURL in all datacenters.
    2. Lucifer the SRID in all datacenters – The SRID tin exist safely edited in the C: \inetpub\wwwroot\Citrix\Roaming\web.config. Make sure to propagate changes to other servers in the grouping.
    3. Match the Commitment Controller names under "Manage Delivery Controllers" – The XML brokers can be dissimilar, merely the bodily name of the Delivery Controller/Subcontract must be identical.

If you are running Workspace app on a VDA, one time you've removed the configured URLs shown above, 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 following folders.
    1. Nether \receiver\ctxaccount delete all entries.
    2. Under \SR\Shop delete the entries.
  3. On the VDA, C:\ProgramData\CitrixCseCache – Delete all files
  4. On the VDA, C:\ProgramData\Citrix\GroupPolicy – Delete all folders and files.
  5. Run gpupdate and logoff.
  6. In the user's registry, HKEY_CURRENT_USER or the profile registry hive. Possible profile reset.
    1. Under 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 contour folders for user on server.

6".locate or Download the Software Installaion Files

DOWNLOAD HERE

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

Posted by: dotsonwhadming.blogspot.com

Related Posts

There is no other posts in this category.
Subscribe Our Newsletter