Receiver for Windows 4.10.1

Last Modified: Feb 4, 2018 @ 6:31 am


This post applies to all Receiver versions 4.0 and newer, including the LTSR versions.

ūüí° = Recently Updated

Change Log

Receiver Modules

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

  • ICA Engine (wfica.exe) ‚Äď process that uses the ICA protocol to connect to published apps and desktops.
  • Self-Service (selfservice.exe)¬†‚Äď local GUI that gets icons from StoreFront. When icon is clicked, ICA Engine performs the connection.
  • Single Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs
  • Receiver Auto-Update (CitrixReceiverUpdater.exe) – Receiver 4.8 and newer – Notifies users of Receiver updates

The PNAgent module is no longer included in 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.

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

Receiver Discovery and Beacon Process

If you are using Receiver’s built-in user interface (instead of ¬†a web browser), then 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.

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

  • If you entered a StoreFront FQDN, then 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 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.

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 Receiver is configured, it then performs the following steps:

  1. Attempt to connect to the Internal Beacon.
  2. If the Internal Beacon 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 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 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, Receiver uses whichever Gateway is marked as Default. Receiver completely ignores whatever Gateway FQDN you entered during Discovery. To use a non-default Gateway, the user must manually select the other Gateway in Receiver’s Advanced Preferences.

In StoreFront Console, if any configuration changes are performed that affect the Provisioning File, do the Receivers reconfigure themselves automatically? Or do users have to remove Accounts and re-add so the updated Provisioning File is imported?

Here are some additional methods of performing 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, at the top right, click the user name, and click¬†Activate. This downloads the¬† file, which is identical to the one you can export from StoreFront Console. The user then must run the downloaded file.

Uninstall Old Clients

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. To run it silently, run CitrixReceiver.exe /RCU /Silent¬†

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

Citrix Blog Post Cookbook to Upgrade from Receiver 3.4 for Windows to Receiver 4.2.100 and Citrix Article CTX135933 Upgrading to Citrix Receiver for Windows contains step-by-step procedure to use Group Policy to uninstall Receiver Enterprise 3.4 and install/configure Receiver 4.x.

The Receiver Clean-Up utility is designed to assist with the following scenarios:

  • When errors occur during upgrade from an earlier version of Receiver or Online Plug-in
  • When unexpected behavior or performance 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-Up Utility removes components, files, and registry values of Online Plug-in 11.x, 12.x, and Receiver for Windows 3.x, 4.x (Online Plugin-in 13.x, 14.x). This includes the Offline Plug-in component if installed.

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

Blog posts from Shaun Ritchie:

Installation and Configuration

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


CitrixReceiver.exe version 4.10.1 (Current Release), or version 4.9.1000 (Long Term Service Release), or version 4.4.5000 (LTSR), can be installed by simply double-clicking it.

Administrator vs non-administrator

  • Non-administrator – If a non-administrator installs Receiver, then each non-administrator that logs in to the workstation will have to reinstall Receiver. Non-administrator installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.
  • Administrator – If CitrixReceiver.exe is installed using an administrator account. then the Receiver only needs to be installed once. Administrator installations are installed to C:\Program Files (x86)\Citrix\ICA Client. Administrator installations cannot be upgraded by non-administrators.
  • Conflicts – If an administrator install of Receiver is performed on a machine that has non-administrator installs of Receiver, then the two Receivers will conflict. Best option is to uninstall non-admin Receiver before installing admin Receiver. Otherwise, the user’s profile probably has to be reset before Receiver is functional again.


Receiver 4.8 and newer support auto-update. Some notes:

  • If Receiver is installed as administrator, then only administrators can install the auto-update.
  • If Receiver is installed on a VDA, auto-update is automatically disabled. This includes Remote PC.
  • Auto-update can be limited to LTSR updates only.
  • Auto-update is configurable through several mechanisms: group policy, StoreFront, Receiver GUI, installer command line. See¬†Configuring auto-update at Citrix Docs.
  • See George Spiers¬†Citrix Receiver for Windows Auto-Update.

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

Add Account Wizard

From Citrix CTX135438 How to Suppress the Add Account Window in Citrix Receiver for Windows: After installation, Receiver will launch and ask you to add an account. If Receiver 4.4.1000 or newer, notice the new checkbox Do not show this window automatically at logon.

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

  • Rename CitrixReceiver.exe to CitrixReceiverWeb.exe.
  • Install using a command line switch: 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 in¬†Receiver.admx.
  • Change Registry values post installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, set AllowAddStore value to N.
  • Set the registry value:¬†HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\NeverShowConfigurationWizard (REG_SZ) = true
  • Also see¬†Suppressing Add Account dialog at Citrix Docs.

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

CitrixReceiver.exe Command line switches

Citrix Blog Post Citrix Receiver Command Line Helper Tool¬†contains a GUI tool to build your installer command line.¬† ūüí°

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

  • /silent
  • /includeSSON ‚Äď enables pass-through authentication. GPO configuration is also required as detailed below.
    CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A ‚Äď by default, only SSL (HTTPS) stores are accepted. To allow non-SSL stores:
    CitrixReceiver.exe /ALLOWADDSTORE=A
  • /STORE0 ‚Äď To add a store from the installation command line:
    CitrixReceiver.exe STORE0="AppStore;;on;App Store"
    • Receiver 4.10 and newer can discover the Store through NetScaler Gateway.
      CitrixReceiver.exe STORE0="AppStore;;On;App Store"
  • /SELFSERVICEMODE=False ‚Äď disables the Self-Service interface and enables shortcut-only mode:
    CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=auto – enables Receiver auto-update¬†notifications
    CitrixReceiver.exe /AutoUpdateCheck=auto
  • /ENABLEPRELAUNCH=True ‚Äď enables prelaunch:
    CitrixReceiver.exe /ENABLEPRELAUNCH=True
  • /ALLOW_CLIENTHOSTEDAPPSURL=1 ‚Äď enables Local App Access:

Registry values

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

  • SelfServiceMode¬†(REG_SZ) = False¬†–¬†Turns off Receiver’s Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = True¬†–¬†If Self-Service interface is disabled, places all shortcuts on desktop.
  • UseDifferentPathsforStartmenuAndDesktop (REG_SZ) = True
    • UseCategoryAsStartMenuPath (REG_SZ) = True or False
    • UseCategoryAsDesktopPath¬†(REG_SZ) = True or False
  • StartMenuDir (REG_SZ) = name of folder on Start Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = name of folder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = True¬†–¬†If SSON is enabled then PreLaunch is already enabled by 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) = 1 – minimizes the launch delay before contacting store
  • InitialRefreshMaxMs (REG_SZ) = 1¬†– minimizes the launch delay before contacting store
  • RefreshMs (REG_SZ) =¬†3600000 (1 hour) – interval for Receiver icon refreshes. 1 hour is the default value.
  • MaxSimultaneousFetches (REG_DWORD) = 6¬† –¬†improves the time of loading icons in Start Menu
  • MaxSimultaneousSubscribes (REG_DWORD) = 6¬†–¬†improves the time of loading icons in Start Menu
  • DontWarnOfRemovedResources (REG_SZ) = True –¬†prevents dialog boxes when resources are removed from the server. (or False as mentioned at Citrix Discussions?)
  • SilentlyUninstallRemovedResources (REG_SZ) = True –¬†prevents dialog boxes when resources are removed from the server
  • PreferTemplateDirectory (REG_SZ) = UNC path or local path containing shortcuts copied by the prefer keyword. Give the shortcuts a short name.
  • PnaSSONEnabled (REG_SZ) = True –¬†Enables Single Sign-on for PNAgent (Web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Receiver is running inside a VDA published desktop, set it to 0.
  • AlwaysUseStubs (REG_SZ) = True. Receiver 4.3.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 4.3.100.
  • DontCreateAddRemoveEntry¬†(REG_SZ) = True – don’t create “Delivered by Citrix” entries in Programs and Features
  • DesktopNameFormatString¬†= format string for shortcut names – For example¬†“{0}_{1}_{2}_{3}”. See the link for details.
  • SelfServiceFlags¬†(REG_DWORD) = 4¬†– prevents duplicate shortcuts when roaming and Desktop is redirected.

Registry value at HKLM\Software\Wow6432Node\Citrix\AuthManager on the Receiver machine:

  • ConnectionSecurityMode = Any. Only if using http (instead of https) to connect to StoreFront.

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

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\TCP/IP

To prevent beacon probing from using proxy, set:

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

To enable foreground progress bar, set:

    • ForegroundProgressBar = 1 (DWORD)

For client-to-server file type 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, set:

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

To prevent ‚ÄúUSB Hub Power Exceeded‚ÄĚ message, set (not needed in 4.2.100¬†and newer):

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

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

Group Policy Settings

Copy the Receiver ADMX template (C:\Program Files\Citrix\ICA Client\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). Also copy receiver.adml to C:\Windows\PolicyDefinitions\en-us (or Sysvol). Edit a GPO that applies to client machines, go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Receiver.

  • To enable pass-through authentication: go to | User Authentication |.
  • To add a store, go to | StoreFront |
    • StoreFront Accounts List ‚Äď see the help text
  • To enable Auto-Update, go to¬†|AutoUpdate|.
    • Enable or Disable AutoUpdate
  • 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 Receiver performing a refresh of the application list when opened. Source¬† ūüí°
    • Enable Control when 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.
    • Enable¬†Allow/Prevent users to publish unsafe content¬†if publishing content that’s opens a file or file share.

Enable automatic client drive and client microphone mapping.

  • In a client-side GPO, add the GPO ADM template from
  • Enable the setting Create Client Selective Trust Keys. See Below¬†for details.
  • Configure the FileSecurityPermission setting in one or more of the regions.
  • Configure the MicrophoneAndWebcamSecurityPermission setting in one or more of the regions.

Citrix CTX203658 Start Menu Icons Set to Default (Blank Document) After Update to Receiver 4.3.100 РWindows 8 and newer

  • Computer Configuration | Policies | Administrative Templates | Windows Components |¬†File Explorer
    • Allow the use of remote paths in file shortcut icons = enabled

Deploy Receiver using Active Directory

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

Change Receiver Store Configuration, including Reset Receiver

You can change Receiver’s configured Store/Account with a couple command lines: (from 4.4 LTSR store configuration per user at Citrix Discussions)

"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


It is sometimes necessary to reset Receiver settings by right-clicking the Receiver icon, clicking¬†Advanced Preferences, and clicking¬†Reset Receiver. 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 to
HKEY_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.

Receiver Group Policy ADMX Template

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

  1. From a machine that has Receiver installed, find the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    1. You can also download the ADMX files from one of the Receiver download pages (version 4.10.1 (Current Release), version 4.9.1000 (LTSR), or version 4.4.5000 (LTSR)) by expanding Downloads for Admins (Deployment Tools).
  2. Copy the CitrixBase.admx and receiver.admx files. Also copy the en-US folder.
  3. 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.
  4. The GPO settings can then be found at Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver.
  5. For example, you can disable Customer Experience Improvement Program (CEIP) from here.
  6. See for additional places where CEIP is enabled.
  7. Receiver AutoUpdate can be configured using group policy. See Configuring auto-update at Citrix Docs.
  8. Receiver 4.10 and newer have settings to hide Advanced Preferences, enable/disable DPI, and enable/disable H265.
  9. Receiver 4.8 and newer have SplitDevices GPO setting under Citrix Receiver | 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 Pass-Through Authentication with XenDesktop 7.5

From Citrix Knowledgebase article How to Configure Desktop Pass-Through with Storefront and Receiver 3.x: To enable Single Sign-on with StoreFront, you must install CitrixReceiver.exe using the /includeSSON switch. This will only be successful for administrators.

  1. Run the command
    Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on a Delivery Controller.

  2. Login to the PC as an administrator.
  3. If installing Receiver for Windows 4.4 or newer, as an administrator, on the Enable Single Sign-on page, check the box next to Enable Single Sign-on. Then finish the installation.
  4. If installing an older version of Receiver:
    1. Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver.exe, and click Copy as path.
    2. Open a command prompt.
    3. Right-click to paste the path in the command prompt and then add /includeSSON to the end of the command. Press <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 you open regedit and go to HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order, you should see PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if you haven’t already.
  8. Edit a GPO that is applied to the client PCs where the Citrix Receiver is installed.
  9. Go to Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver.
  10. Expand Citrix Receiver and click User authentication.
  11. On the right, double-click Local user name and password.
  12. Select Enabled and then check the box next to Allow pass-through authentication for all ICA connections. Click OK.
  13. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Internet Explorer. You can use a GPO to configure this on the client side.
  14. Local Intranet zone should have Automatic logon only in Intranet zone enabled.
  15. Logoff Windows and log back on. In Task Manager you should now see ssonsvr.exe. This won’t appear unless you logoff and log back on.
  16. If Receiver won’t connect or is slow to enumerate icons, then you might have to disable Automatically detect settings in IE.
  17. In Receiver 4.5 and newer, right-click the Receiver icon and click Advanced Preferences.
  18. Click Configuration Checker.
  19. Check the box next to SSONChecker and click Run.
  20. The lines with red x will indicate the issue and corrective action.

StoreFront Accounts

You can use a client-side GPO to add a store (Account) to Receiver 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 Receiver Self-Service installed.
  3. Go to Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Receiver > StoreFront.
  4. On the right, double-click NetScaler Gateway URL/StoreFront Accounts List.
  5. Select Enabled, and then click Show.
  6. Enter a store path based on the example shown in the Help box. Receiver 4.5 lets you enter a Gateway path. Then click OK.
  7. Note: Gateway paths work in GPO, but don’t seem to work when specified in the CitrixReceiver.exe installation command line.

Published Shortcuts and Reconnect

Citrix CTX200924 How to Customize App Shortcuts with Receiver for Windows

Receiver 4.5 and newer has a user interface for setting Shortcut Paths. Right-click the Receiver icon, click Advanced Preferences, and then click Settings Option.

From Citrix Docs Configuring application delivery: There are several methods of controlling how Receiver displays shortcuts on the Start Menu and Desktop as detailed below:

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 ‚Äď 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.
  • 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 folder, under Computer Configuration > Administrative Templates > Citrix Components > Citrix Receiver is a new node called SelfService.

Disable the Manage SelfServiceMode setting to hide the Receiver Window.

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

Receiver 4.2.100 and newer has the ability to configure (or disable) Workspace Control using group policy. Enable the setting Control when Receiver attempts to reconnect to existing sessions and configure it as desired.


Staring with Receiver 4.2, prelaunch is automatically enabled if 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.

  • 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, 2 = scheduled pre-launch
  • Name: Schedule
    • 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:

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

  1. Download the ADMX file from
  2. Copy the .admx and .adml files to PolicyDefinitions (Sysvol, or C:\Windows).
  3. The .adml file goes in the en-US folder.
  4. Edit a GPO that applies to the endpoint devices that are running Receiver.
  5. Go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Receiver |  Citrix Client Selective Trust (x64).
  6. Enable the setting Create Client Selective Trust Keys.

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

Desktop Lock

As an alternative to Receiver Desktop Lock, see Transformer in Citrix Workspace Environment Manager.

External links:

Use Studio to configure Receiver Accounts in Published Desktop

In published desktops, the 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 Receiver to place published applications back on the Start Menu and Desktop based on user’s group membership and subscription preference.

  1. In Citrix Studio, on the left, expand the Configuration node, 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 (e.g. /Citrix/Store) and then /discovery on the end of the URL. The full URL would be similar to Click OK.
  4. Edit a Delivery Group that has a published desktop and Citrix Receiver installed.
  5. 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, Receiver will be automatically configured with this URL.

Published Desktop – Shortcuts

Here is a summary of steps to use Receiver to control shortcuts on a published desktop. The source of this complexity is that there is no session sharing between published apps and published desktop, so instead we must use some other means of creating shortcuts.

  1. Make sure Receiver (version 4.10.1 (Current Release), version 4.9.1000 (LTSR), or version 4.4.5000 (LTSR)) is installed on the VDA.
  2. Enable the Group Policy setting Remove common program groups from Start Menu and apply it to non-administrators.
    1. For applications that are installed on the same server that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory group membership. Applications on other delivery groups are handled by Receiver.
    2. Or use the prefer keyword to copy shortcuts from the PreferTemplateDirectory.
  3. 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\WSCReconnectMode=”0″ so 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 separate Self-Service GUI and assumes all icons are subscribed.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop¬†= True¬†to¬†place icons on the desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to place published¬†applications in a sub-folder.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\DesktopDir to place published applications in a sub-folder on the desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True.
    • 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.
  4. Pass-through authentication:
    1. In a GPO that applies to the VDA, import the receiver.admx file and set Local user name and password to Enabled. Check the box next to Allow pass-through authentication for all ICA connections.
    2. 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 zone.
    3. Make sure ssonsvr.exe is running after you login to the VDA. If not, troubleshoot it.
  5. When configuring Citrix Profile Management, make sure !ctx_startmenu! is not excluded. You can do one of the following: edit the Studio policy, edit the GPO, or edit the .ini file.
  6. In Studio, configure a delivery group with delivery type = Desktop and Applications. Assign users to the delivery group and the applications (if visibility is limited).
    1. In Studio, edit each published application and on the Delivery tab specify a category. This will become the Start Menu folder name.
    2. If Receiver Self Service Mode 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.
    3. Another option is to go to the StoreFront Console, click Stores on the left, and on the right click Disable User Subscriptions. This causes all apps to appear on the Start Menu and/or Desktop depending on Receiver configuration.
    4. 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 session.  See Ralph Jansen Citrix Receiver 4.1 Prefer keyword examples
    5. 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.
  7. The default Windows 2012 Start Menu has limitations for nested folders, duplicate icons, etc. Consider installing a Start Menu Replacement.
  8. In Studio, create a StoreFront object with a URL similar to Replace the FQDN with your load balanced StoreFront FQDN. Also replace the path to the store with your store path. Make sure there is /discovery on the end. By default, Receiver only supports https
    1. In Studio, assign the StoreFront object to the delivery group from which the desktop is published.
    2. Instead of Studio, you could use group policy to define the Store.
  9. On your Delivery Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $true
  10. 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 auto-launch and hopefully auto-login.
    3. If Receiver Self-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.
    4. If Receiver Self-Service Mode is enabled then only applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application description will be displayed. Users can open the systray icon to subscribe to more applications.
    5. For published applications with KEYWORDS:prefer=shortcutname, Receiver should copy icons from the template directory to the Start Menu and/or Desktop. See below for considerations.
    6. Users can copy icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn’t Move it.
    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 (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.
    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 will be established.
    10. 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.
  • Jan Hendrik Meier Automatic Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp 7.x environment¬†has a script that can create shortcuts based on the published apps with¬†prefer keyword. These shortcuts can then be copied to your Prefer Template Directory.

How to Script Receiver Self-Service

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

When SSP builds a shortcut, it builds 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: 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 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.

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


Citrix Receiver comes with a .dll file that implements the Citrix Common Connection Manager SDK. You can use the CCM SDK to do the following:

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

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

  • CCMTerminateApplication
  • CCMLaunchApplication
  • CCMGetActiveSessionCount
  • CCMDisconnectAllSessions

Launcher Scripts

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

Stan Czerno – Powershell Script to launch one or more Published Applications from Citrix Storefront 2.x through 3.6: 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 Receiver to display session information.

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

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

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

Skype for Business

Citrix has a HDX plug-in (HDX RealTime Optimization Pack) for Receiver that enables offloading of Skype for Business media protocols to the client device. The latest version is 2.4.

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

Receiver and HDX RealTime Media Engine are also available as a bundle at Citrix Receiver 4.9 and HDX RealTime Media Engine 2.3 for Windows

24-page Citrix PDF Delivering Microsoft Skype for Business 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 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:
    $x = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "true"
    Set-CsClientPolicy -Identity "<ClientPolicyName>‚ÄĚ -PolicyEntry @{Add=$x}

When offloading voice and video to Receiver 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 be used to process audio and video. The tool is independent of RealTime Optimization Pack version and runs any Windows machine.

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

Troubleshooting – Citrix QuickLaunch

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

You enter a Controller address, credentials, and 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).

Troubleshooting – Receiver Logging

There are a couple methods of logging Receiver for Windows operations. One method is CTX141751 Citrix Receiver Diagnostics Tool РFor Windows, which creates a CDF trace that can be parsed by CDFControl.

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

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

Windows Registry Editor Version 5.00

;only for x64 windows os
;import with admin rights
;restart your computer to activate the logging and tracing settings
;create C:\TEMP for the launch ICA log and SSON logn (no environment variables can be used)

;general Receiver logging
;logpath: %USERPROFILE%\Appdata\Local\Citrix\Receiver

;Authentication Manager logging
;logpath: %USERPROFILE%\Appdata\Local\Citrix\AuthManager

;Self Service logging
;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService
"DefaultTracingConfiguration"="global all ‚Äďdetail"

;save launch ICA
;logpath: C:\TEMP\ica.log (no environemnt variables allowed)
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Logging]

;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

;Single Sign-on Logging

Troubleshooting – Duplicate Stores

Stores are sometimes duplicated in Receiver, especially if you are running Receiver 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. Look in GPOs for Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Receiver > StoreFront > NetScaler Gateway URL/StoreFront Accounts List. Remove any URLs configured here.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you might see store addresses that were specified during a command line installation of Receiver.
  4. When Citrix Receiver switches between StoreFront servers in multiple datacenters, it’s possible for each datacenter to be treated as a separate Receiver site. This can be prevented by doing the following. From Juan Zevallos at Citrix Discussions:
    1. Match the BaseURL in all datacenters.
    2. Match the SRID in all datacenters – The SRID can be safely edited in the C:\inetpub\wwwroot\Citrix\Roaming\web.config. Make sure to propagate changes to other servers in the group.
    3. 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. Here’s the exact setting I’m referring to:¬†

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

  1. On the VDA, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix ‚Äď Delete the number folders representing policy entries.
  2. On session host VDAs, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Citrix ‚Äď Remove the entries for storefront in the following folders.
    1. Under \receiver\ctxaccount delete all entries.
    2. Under \SR\Store delete the entries.
  3. On the VDA, C:\ProgramData\CitrixCseCache ‚Äď Delete all files
  4. On the VDA, C:\ProgramData\Citrix\GroupPolicy ‚Äď Delete all folders and files.
  5. Run gpupdate and logoff.
  6. In the user’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 profile folders for user on server.

402 thoughts on “Receiver for Windows 4.10.1”

  1. G’day Carl, I’ve got a problem with Receiver 4.10 and 4.10.1 where if a user does a ‘Send to Desktop’ on an app published to a start menu folder, the resultant icon is removed when the receiver is refreshed. This behavior doesn’t occur in 4.9 and before however. Any ideas?

    1. Just following up re: this. The shortcuts disappear when the user accesses a Citrix application, and this behavior does occur with Receiver 4.9, but only when clean installed. If I installed 4.6, logged in to the Receiver, and then installed 4.9 over the top, the icons would remain. Trying this same method with 4.10 and 4.10.1 didn’t work. Receiver 4.6 has no problems at all.

  2. Hi Carl,
    Does Local App Access integrate with Citrix Desktop Lock ? I am able to get LAA and Desktop Lock work separately but not together. Is there something I am doing wrong or is it by design? Thank you for anticipated answer, I just have a client requirement to allow LAA into win7 with Desktop lock installed for their 6.5 environment.

  3. Carl,
    Just ran into an issue with, it appears to break access to Legacy Xenapp 5 Servers. Was wondering if you have heard or ran into this issue. (Yes I know this has been EOL since 2013)

  4. Anyone had first hand experience of this fixing the authentication popup box which appears randomly. Citrix support have reported it does, don’t want to waste my time testing as I have multiple SDP’s to work on. Thanks.

  5. We have exactly the same problem in our published apps. Combo boxes drop down their list but nothing happens when you click on them while using Receiver 4.10. This is a critical problem for us. We are advising our customers to roll back to Receiver 4.9 but some of them have been receiving automatic updates and are not technically minded enough to handle the rollback well.

  6. Hello Carl,

    We have found a bug in 4.10.

    Office 2010 document with dropdown select boxes.
    Clicking on the box opens the dropdown list but clicking on an item does nothing. You can highlight an item then press “Enter” on the keyboard.

    I’m having to rollback to 4.9 as this is not an issue there. I don’t know what other application will be affected by this issue.

Leave a Reply