Workspace app and Receiver Versions

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 1912 and newer support App Protection. It’s available in both the LTSR 1912 version and the Current Release 2006.1 version.

The LTSR (Long Term Service Release) version of Workspace app is version 1912. The LTSR version of Workspace app does not support Browser Content Redirection (BCR) because the embedded browser is not included in the LTSR Workspace app. 💡

The PNAgent module is not included in Workspace app or Receiver 4.0 and newer. The older Receiver Enterprise includes the PNAgent module, but does not include Self-Service. The last version of Receiver Enterprise is 3.4.

Workspace app and Receiver Discovery and Beacon Process

If you are using Workspace app’s / Receiver’s built-in user interface (instead of a web browser), then Workspace app and Receiver first prompts you to perform discovery, which is also called Add Account.

Enter either a StoreFront FQDN, or a NetScaler Gateway FQDN. Just enter the FQDN. There’s no need to enter https or a path.

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

If you entered a StoreFront FQDN, then Workspace app or Receiver 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 Account Services address, and download the Provisioning File from StoreFront. The Account Services address is configured in the NetScaler Gateway Session Profile on the Published Applications tab.

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

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

The ReceiverConfig.cr Provisioning File looks something like this:

Here are the values in the Provisioning File:

Address – the Base URL configured in StoreFront Console

Internal Beacon – as configured in StoreFront Console. This can be the Base URL, or a manually specified URL.

External Beacons – as configured in StoreFront Console

Gateways – as configured in StoreFront Console. If there are multiple Gateways, when enabling Remote Access on the Store, then only one Gateway is selected as Default

SRID – Store ID. An important value to consider for multi-datacenter configurations. The SRID is set when the Store is created. It can also be changed by editing C:\inetpub\wwwroot\Citrix\Roaming\web.config.

Workspace app or Receiver 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’s registry.

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

Attempt to connect to the Internal Beacon.

If the Internal Beacon is reachable, connect directly to the StoreFront Base URL (Address).

If the Internal Beacon is not reachable:

Attempt to connect to the External Beacons. If the External Beacons are not reachable, then stop attempting to connect.

Connect to the Gateway address configured in the Provisioning File. If there is more than one Gateway, connect to the Gateway that is marked as the Default.

Here are some interesting notes on this connection process:

The FQDN you entered during Discovery has absolutely nothing to do with how Workspace app or Receiver connects to StoreFront or Gateway. The actual connection process is controlled by the contents of the Provisioning File, not the Discovery address.

If the Provisioning File has multiple Gateways defined, Workspace app or Receiver uses whichever Gateway is marked as Default. Workspace app and Receiver completely ignore whatever Gateway FQDN you entered during Discovery. To use a non-default Gateway, the user must manually select the other Gateway in Workspace app’s / Receiver’s Advanced Preferences.

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

Here are some additional methods of performing Workspace app or Receiver Discovery:

After exporting the Provisioning File from StoreFront Console, distribute it to users, and ask them to double-click it.

After logging in to Receiver for Web (StoreFront), at the top right, click the user name, and click Activate. This downloads the receiverconfig.cr file, which is identical to the one you can export from StoreFront Console. The user then must run the downloaded file.

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 feature is intended for large 4K monitors.

In the desktop toolbar at the top of the screen, click Preferences.

Switch to the Monitor Layout tab.

On the bottom, select Horizontal or Vertical, then click somewhere in the blue box to draw a line. The single monitor will be split along this line. You can set different DPI for each portion of the virtual display.

Right-clicking one of the split sections changes that section to the primary display.

Click OK when done.

In the toolbar, click Window to resize it to a window, and then click Full Screen to cause your virtual monitor configuration to take effect.

Uninstall Old Clients

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

In Workspace app 1908 and older (including Receiver), to run it silently, run CitrixWorkspaceApp.exe /RCU /Silent or CitrixReceiver.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 or Receiver.

CitrixWorkspaceApp.exe version 2006.1 (Current Release), or CitrixWorkspaceApp.exe version 1912 (LTSR), or CitrixReceiver.exe version 4.9.9000 (Long Term Service Release), can be installed by simply 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 or Receiver, then each non-administrator that logs in to the same workstation will have to reinstall Workspace app or Receiver.

Non-administrator installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.

Administrator – If CitrixWorkspaceApp.exe or CitrixReceiver.exe is installed using an administrator account. then the Workspace app or Receiver only needs to be installed once.

Administrator installations of Workspace app 1912 and newer can be manually upgraded by non-administrators by clicking Check for Updates. Older versions cannot be upgraded by non-administrators.

Conflicts – If an administrator install of Workspace app or Receiver is performed on a machine that has non-administrator installs of Workspace app or Receiver, then the two installations will conflict. Best option is to uninstall non-admin Workspace app and Receiver before installing admin Workspace app or Receiver. Otherwise, the user’s profile probably has to be reset before Workspace app or Receiver is functional again.

Auto-Update

Auto-Update is broken in Receiver 4.11 and older. You’ll have to manually install Workspace app 2006.1.

Workspace app and Receiver 4.8 and newer support auto-update.

Some notes:

If Workspace app 1912 or newer is installed as administrator, then non-administrators can click Check for Updates to manually update Workspace app. To prevent this, use group policy to disable Citrix Workspace Updates.

Older versions of Workspace app cannot be upgraded by non-administrators.

If Workspace app or Receiver is installed on a VDA, auto-update is automatically disabled. This includes Remote PC.

For Workspace app and Receiver 4.4 and newer, FTU (First Time Use aka Add Account Wizard) will be displayed only 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 one of the following: (Note: Receiver 4.4.1000 and newer has a fix for preventing the Add Account wizard)

Discover Hidden Stores

When Receiver is first launched, it must perform Discovery, which is the process of downloading the .xml provisioning file from StoreFront. Discovery is performed by entering a StoreFront FQDN or Gateway FQDN. To discover a hidden store (a store that’s not advertised), add %StoreName to the end of the FQDN. CTX214819 Unable to add account from Receiver dialog If the store is hidden in storefront.

Registry values

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

To enable Auto-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, go 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, but prevent it from automatically opening (reside in systray), tick Prevent 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.

Deploy Workspace app or Receiver using Active Directory

To deploy Workspace app or Receiver using Active Directory, configure a GPO with a computer startup script that runs the Workspace app or Receiver installer executable. Citrix provides sample scripts that can be downloaded from one of the Workspace app or Receiver download pages (Workspace app version 2006.1 (Current Release), or Workspace app version 1912 (LTSR), Receiver version 4.9.9000 (LTSR) by expanding Downloads for Admins (Deployment Tools). An enhanced version of the installation script can be found in Citrix Discussions.

It is sometimes necessary to Reset Citrix Workspace or Reset Receiver by right-clicking the Workspace app or Receiver systray icon, clicking Advanced Preferences, and clicking the Reset link. You can do this from the command line by running "C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\CleanUp.exe" -cleanUser -silent. See CTX140149 How to Reset Receiver Using the Command Line.

Receiver for Edge

The Receiver for Web experience in Microsoft Edge is not ideal. Every time a user clicks an icon, the user has the click the Open 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. 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 like this: <protocolHandler enabled="true" platforms="(Macintosh|Windows NT).*((Firefox/((5[3-9]|[6789][0-9])|\d\d\d))|(Chrome/((4[2-9]|[56789][0-9])|\d\d\d)))(?!.*Edge)". Remove (?!.*Edge) and save the file.

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

To stop the switch apps pop-up, on the client side, edit the registry, go toHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ProtocolExecute\receiver (create missing registry keys), create DWORD value WarnOnOpen, and set it to 0 (zero). You can use Group Policy Preferences to deploy this registry value.

Workspace app or Receiver Group Policy ADMX Template

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

From a machine that has Workspace app or Receiver installed, find the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.

You can also download the ADMX files from one of the Workspace app or Receiver download pages (Workspace app version 2006.1 (Current Release), or Workspace app version 1912 (LTSR), or Receiver version 4.9.9000 (LTSR)) by expanding Downloads for Admins (Deployment Tools).

Copy the CitrixBase.admx and receiver.admx files. Also copy the en-US folder. In Workspace app, the files are still named receiver.admx.

Go to your domain’s SYSVOL share and in the Policies folder look for a PolicyDefinitions folder. If one 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.

If installing Workspace app or Receiver for Windows 4.4 or newer, as an administrator, during installation, on the Enable Single Sign-on page, check the box next to Enable Single Sign-on. Then finish the installation.

If installing an older version of Receiver:

Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver.exe, and click Copy as path.

Open a command prompt.

Right-click to paste the path in the command prompt and then add /includeSSON to the end of the command. Press <Enter>.

Click Install when prompted.

To verify that SSON is installed, go to C:\Program Files (x86)\Citrix\ICA Client and look for the file ssonsvr.exe.

And if you open regedit and go to HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order, you should see PnSson in the ProviderOrder.

Install the receiver.admx (and .adml) template into PolicyDefinitions if you haven’t already.

Edit a GPO that is applied to the client PCs where the Workspace app or Citrix Receiver is installed.

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.

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

SelfServiceMode – set to False so Receiver disables the Self-Service interface and automatically places all published shortcuts on the Start Menu and/or Desktop. More details in Configuring application delivery at Citrix Docs.

PutShortcutsOnDesktop – set to True to place every app on the desktop

DesktopDir – Workspace app or Receiver places every shortcut on the desktop so it’s probably best to place them in a folder.

StartMenuDir – If there is potentially a conflict between local apps and remote apps, then you should place the Start Menu shortcuts in a folder.

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

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

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

Workspace app and Receiver 4.2.100 and newer have the ability to configure (or disable) Workspace Control 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 or Receiver is installed with SSON enabled. Otherwise, set registry values to enable prelaunch. Receiver 4.2.100 prevents the prelaunch icon from appearing on the Start Menu.

REG_SZ: HH:MM|M:T:W:TH:F:S:SU where HH and MM are hours and minutes. M:T:W:TH:F:S:SU are the days of the week. For example, to enable scheduled pre-launch on Monday, Wednesday, and Friday at 1:45 p.m., set Schedule as Schedule=13:45|1:0:1:0:1:0:0 . The session actually launches between 1:15 p.m. and 1:45 p.m.

Name: UserOverride

REG_SZ: 0 = HKLM overrides HKCU, 1 = HKCU overrides HKLM

Device Access Behavior (Client Selective Trust)

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

Use Studio to configure Workspace app or Receiver Accounts in Published Desktop

In published desktops, Workspace app or Receiver can be used for placement of shortcuts on the user’s Start Menu and Desktop. Use group policy to hide the common program groups and then use Workspace app or Receiver to place published applications back on the Start Menu and Desktop based on user’s group membership and subscription preference.

In Citrix Studio, on the left, expand the Configuration node, right-click StoreFront and click Add StoreFront.

Enter a descriptive name for the StoreFront server.

Enter the internal https URL of the load balanced StoreFront servers. Add the path to your store (e.g. /Citrix/Store) and then /discovery on the end of the URL. The full URL would be similar to https://citrix.corp.com/Citrix/Store/discovery. Click OK.

Edit a Delivery Group that has a published desktop and Citrix Workspace app or Receiver installed.

On the StoreFront page, change the selection to Automatically, using the StoreFront servers selected below, and then check the box next to the StoreFront URL. Click OK. Now when users launch the published desktop, Workspace app or Receiver will be automatically configured with this URL.

Published Desktop – use Workspace app or Receiver to control Shortcuts

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

Note: Workspace app or Receiver tends to be slow to create Start Menu shortcuts, so make sure you perform a Proof of Concept to determine how this functionality impacts logon times.

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

Workspace app or Receiver 4.11 or newer installed inside the VDA

VDA 7.17 or newer

StoreFront 3.14 or newer

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

If you don’t meet these minimum version requirements, then you’ll need to use the older Prefer Keyword method of handling Workspace app or Receiver shortcuts as detailed later.

This removes all Public (aka All Users) Start Menu shortcuts. Workspace app or Receiver will re-add the shortcuts based on user group membership.

On the VDA, configure the following Workspace app or Receiver Registry keys (or corresponding settings in the receiver.admx GPO template):

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\WSCReconnectMode=”0″ so Workspace app or Receiver 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 or Receiver 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.

Configure each desired published app to Add shortcut to user’s desktop.

Or, configure HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop = True to place all icons on the desktop.

To control icon placement, configure the following registry values:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to place published applications in a sub-folder. Note: Windows 2012 and newer only supports a single level of Start Menu folders, so setting this effectively turns off published app categories.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\DesktopDir to place published applications in a sub-folder on the desktop.

Pass-through authentication:

In a GPO that applies to the VDA, import the receiver.admx file, and set Local user name and password to Enabled. Check the box next to Allow pass-through authentication for all ICA connections.

If you’re using Gateway internally, and if Workspace app 1808 or newer, then also enable Single Sign-on for NetScaler Gateway.

Make sure ssonsvr.exe is running after you login to the VDA. If not, troubleshoot it.

When configuring Citrix Profile Management, make sure !ctx_startmenu! is not excluded from roaming.

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 limited).

In Citrix Studio, edit each published application, and on the Delivery tab, specify a category. This will become the Start Menu folder name.

If Workspace app or Receiver Self Service Mode (GUI) is enabled, in Studio, edit each application, and add KEYWORDS:Auto and/or KEYWORDS:Mandatory to the published application description. This forces the applications to be subscribed/favorited. Only subscribed (or Favorite) apps are displayed in the Start Menu and Desktop. Unless you disable Workspace app or Receiver’s SelfService interface as described earlier.

Another option is to go to the StoreFront Console, click Stores on the left, and on the right, click Configure Store Settings, and click Disable User Subscriptions. This causes all apps to appear on the Start Menu and/or Desktop depending on Workspace app or Receiver configuration.

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 or Receiver on the VDA to connect to the new Store.

In StoreFront Console, click the store for VDAs, and click Configure Store Settings. On the Advanced Settings page, in the Filter resources by type row, choose Citrix.MPS.Desktop.

On your Delivery Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $true

This is required for Pass-through Authentication from Workspace app or Receiver.

Configure your client devices to connect to the published desktop.

When users connect to the published desktop, Workspace app or Receiver will auto-launch and hopefully auto-login.

If Workspace app or Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.

If Workspace app or Receiver Self-Service Mode is enabled, 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.

Users can copy icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn’t Move it.

Users can then launch applications directly from the Start Menu, from the Desktop, or from the Workspace app or Receiver (if the Self-Service interface is enabled).

If Workspace app or Receiver 4.11 (or newer), VDA 7.17 (or newer), and StoreFront 3.14 (or newer), then vPrefer is enabled by default. When launching an app icon that came from Workspace app or Receiver, Workspace app or Receiver checks the local VDA machine to see if the application can be launched on the local VDA instead of by creating a new Citrix double-hop session.

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 will be established.

If the user deletes Workspace app or Receiver shortcuts from the Start Menu, you can get them back by going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app or Receiver.

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

For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory group membership. Applications on other delivery groups are handled by Receiver.

On the VDA, configure the following Receiver Registry keys (or corresponding settings in the receiver.admx GPO template):

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PreferTemplateDirectory = a UNC path or local path containing shortcuts to be copied by the prefer keyword. This can point to C:\ProgramData\Microsoft\Windows\Start Menu.

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

In Studio, edit each application and change KEYWORDS:Prefer to KEYWORDS:prefer. Notice 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 take precedence. This is good. Otherwise the Receiver published application icon would result in a new Citrix double-hop session.

If using the prefer keyword with the PreferTemplateDirectory, enter it as KEYWORDS:prefer=shortcutname where shortcutname is the name of the shortcut that is copied from the Template directory.

Configure your client devices to connect to the published desktop.

When users connect to the published desktop, Group Policy Preferences will create shortcuts to local applications.

Receiver will auto-launch and hopefully auto-login.

If Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.

If Receiver Self-Service Mode is enabled 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.

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.

Users can copy icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn’t Move it.

Users can then launch applications directly from the Start Menu, from the Desktop, or from the Receiver (if Self-Service interface is enabled).

If a local shortcut (e.g. Group Policy Preferences shortcut, or copied from template directory) matches a published application with KEYWORDS:prefer then the local shortcut will override the published application icon.

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 will be established.

If the user deletes Receiver shortcuts from the Start Menu, you can get them back 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 to C:\ProgramData\Microsoft\Windows\Start Menu, which is the All Users Start Menu.

The shortcuts copied from the Prefer Template Directory are renamed to match the published app name.

For prefer local apps, any command line parameters specified in the published app are ignored. If you need these command line parameters, add them to the shortcut in the Prefer Template Directory.

If you have multiple published apps pointing to the same prefer local shortcut, then only one copy will be made, and it will have the name of only one of the published apps. To workaround this, in the Prefer Template Directory, create separate shortcuts for each published app, and adjust the published app prefer keyword accordingly.

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

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

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

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.

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

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 support for Location Based Routing (LBR) with the virtualized Skype for Business 2016 client (and HDX RTOP 2.1 and above) 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:

Citrix CTX222459 RealTime Optimization Pack Capability 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 any Windows machine.

Troubleshooting – Citrix QuickLaunch

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

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

In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you might see store addresses that were specified during a command line installation of Workspace app or Receiver.

When Citrix Workspace app or Receiver switches between StoreFront servers in multiple datacenters, it’s possible for each datacenter to be treated as a separate Workspace app or Receiver site. This can be prevented by doing the following. From Juan Zevallos at Citrix Discussions:

Match the BaseURL in all datacenters.

Match the SRID in all datacenters – The SRID can be safely edited in the C:\inetpub\wwwroot\Citrix\Roaming\web.config. Make sure to propagate changes to other servers in the group.

Match the Delivery Controller names under “Manage Delivery Controllers” – The XML brokers can be different, but the actual name of the Delivery Controller/Farm must be identical.

If you are running Workspace app or Receiver on a VDA, once you’ve removed the configured URLs shown above, do the following to clean up the VDAs:

On the VDA, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix – Delete the number folders representing policy entries.

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.

Under \receiver\ctxaccount delete all entries.

Under \SR\Store delete the entries.

On the VDA, C:\ProgramData\CitrixCseCache – Delete all files

On the VDA, C:\ProgramData\Citrix\GroupPolicy – Delete all folders and files.

Run gpupdate and logoff.

In the user’s registry, HKEY_CURRENT_USER or the profile registry hive. Possible profile reset.

511 thoughts on “Citrix Workspace app 2006.1”

Comment navigation

Hi! We have a customer having issues with blurry fonts. If the users log off, and reset Workspace client, the fonts looks good. Have tried different versions of the client, and installed the latest 2006 yesterday, but no solution. They are running on 7.15 cu5. They are also using 4K monitors. Yo have any idea how to resolve this? Thanks!

Hi I hope anyone can help me with my current issue with Citrix workspace 1907. Any application disable/enable changes i make on cloud console is not getting refreshed automatically on citrix workspace installed when i restart the server.

Workspace app 2002 throwing error while click on VDA desktop “error number 2308:. The citrix workspace received a corrupt ICA file. The key (coding]) has no associated value.”
Tried Citrix receiver cleanup tool, cleared app data, registry Citrix folders , created new windows profile and installed it still no luck.
Any advice?
Even version 19xx workspace app throws the same. But 18xx and receiver works fine.
Impacted version can work in browser HMTL 5 and downloadable ICA file from browser.

Hi Carl,
I have an issue in my Citrix environment. We have Citrix VDA Terminal session hosts with Win 2012 R2 (VDA 7.6) with 13 session hosts and 120 users logs in everyday. Users facing slowness throughout the Citrix, mouse clicking takes time, app switching takes time (alt tab or mouse click). But it is better in Citrix light version, problem only in full version. CPU & memory utilization is 60%.
Any suggestions from your side.

Sure, thanks for the response. I will turn off the legacy mode. I have one more doubt that our session performance is better in HTML5 but not in full ICA version. even some application works fine in HTML5 session and the same getting crashed in full mode ICA session (app launches fine but when click on selected button in the app crashes the app but this works fine in HMTL 5) what could be the cause, what is the difference between HTML5 based session and ICA based full mode session.

Hey Carl…..I need a little help if possible. My customer is looking to install SSO with the Citrix Workspace App from a GPO. Users do not have any administrative rights. I placed the CitrixWorkSpaceApp.exe on a file share. I modified the Citrix provided startup scripts to create a BAT file and kicked that off in the GPO Startup Script. Commandline options I entered included /includeSSON and /ENABLE_SSON=yes. SSO is not getting installed. Keep in mind when I install the application on a machine logged in as admin, it works. I read where the startup script runs as LocalSystem which has full administrative rights but it doesn’t work in my scenario. I’m wondering if its because I put the application on a share. I also read that if I use a fileshare, the startup script doesn’t run as LocalSystem anymore but runs as ComputerAccount which is a regular user. I added ComputerAccount to local administrators group on system to see if that would work but it doesn’t. If I move the WorkSpaceApp off of a share, will it continue to install with LocalSystem account. And if it does, where would i move it to? A mapped drive that isn’t mapped yet? Is there a share I can put it on so it gets copied to the local system first? Any idea on how I can add SSO to Workspace using a GPO Windows Startup Script? Thanks, Todd.

Hello Carl, after I install Windows 10 Enterprise LTSC with Workspace app, I see only white screen. Meanwhile I have my citrix resource in start menu, have you any idea ? on every PC with other Windows 10 like LTSB version, no problem.

I’m having conflicting experience with the installation of Workspace App installed as Admin vs non-admin and the claim that installing as Admin puts the citrix files into C:\Program Files (x86)\Citrix\ICA Client vs in AppData when a user installs.

I checked 3 environments and all have Citrix files in both C:\Program Files (x86)\Citrix\ICA Client. and AppData. AppData is not populated until a user launches a Citrix app.

We’ve been spending time troubleshooting sudden breaking citrix clients that all get the “This version of Citrix Workspace does not support selected encryption. Please contact your administrator.”

The users profile is broken and no RCU or DePalma’s PS script can resolve it. The user profile has to be deleted and recreated to get Citrix to work again. Then in breaks in 4-8 weeks for dozens of users. This sounds like something in our environment that we inherited that is updating a Appdata dll or HKCU reg key and corrupting it.

Is this environment the only one still experiencing the “This version of Citrix Workspace does not support selected encryption. Please contact your administrator.” error?

no – no resolution – its been going on for 7 months, I found this post 2 months ago. My experience is that once there are many files in the AppData, Citrix will break. Reading this post led me to believe that most of my users attempted Per-user installs and thats why AppData was populated and also why it broke. I’ve since cleaned out some profiles, cleared out Workspace App , then installed at Admin ONLY – it breaks within 2 months anyhow.

It most likely something in our environment, as a small amount of users are getting mic issues and only clearing out the profiles fixes that too – again pointing to my environments….