Top List Top

Citrix Desktop Viewer toolbar registry

As far as I know there is no “official” way to set the width, height and screen position of Citrix Desktop Viewer in window mode. It can be done easily by changing a few registry values, though.

To set the window size [including title bar, borders, etc.] modify the following registry values:

[HKEY_CURRENT_USER\Software\Citrix\XenDesktop\DesktopViewer\SUBKEY] "WindowedBoundsLocationX"=dword:00000000 "WindowedBoundsLocationY"=dword:00000000 "WindowedBoundsSizeWidth"=dword:00000500 "WindowedBoundsSizeHeight"=dword:000002d0

Above values will put the Desktop Viewer window in the top left corner and set an outer size of 1280×720.

Notes: You need to replace SUBKEY with the internal name of the published resource. The easiest way to do that is check the registry of a user who has already connected to that resource. And yes, this works for XenApp and XenDesktop.

To find the screen resolution of the XenApp/XenDesktop session right-click the desktop and select Screen resolution. The dialog that comes up shows you the net size that remains after the Desktop Viewer window borders have been subtracted [1264×656 in this case]:

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.

💡 = Recently Updated

Change Log

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 [e.g. Browser Content Redirection, App Protection].

Workspace app uses a YYMM [year/month] versioning format, of which version 2202 [21.12.1] is the newest.

Workspace app 2009 and newer have the new Citrix logo.

Workspace app 1912 and newer support App Protection. It’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 contain many Teams optimization enhancements. 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.

Workspace app Modules

The Workspace app 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] – gets icons from StoreFront and displays them in a Window. When an icon is clicked, Self-service passes the ICA file to the ICA Engine to establish a connection.
Single Sign-on [SSON] for ICA [ssonsvr.exe] – captures user credentials and submits them to VDAs after an ICA connection is established
Workspace Auto-Update [CitrixReceiverUpdater.exe] – Notifies users of Workspace app updates. The most recent name for this component is Citrix Workspace Update.

The PNAgent module is not included in Workspace app. The older Receiver Enterprise includes the PNAgent module, but does not include Self-Service. The last version of Receiver Enterprise is 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.

Workspace app Discovery and Beacon Process

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

The Citrix logo changed in Workspace app 2009 and newer.

The Add Account wizard changed in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Cloud Workspace FQDN. Just enter the FQDN. There’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 entered a StoreFront FQDN, then Workspace app will download the Provisioning File directly from the StoreFront server.
If you entered a Gateway FQDN, then Gateway will first prompt the user to authenticate. After authentication, Gateway will connect to its configured 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 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 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:
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 Workspace app 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 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 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.

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 Workspace app.

The Receiver Clean-Up utility for Receiver 4.3 and older 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 Workspace app and Receiver.

Links:

Workspace app 1912 CU5 and Workspace app 2105 and newer fix security vulnerabilities.

CitrixWorkspaceApp.exe version 2202 [Current Release], or CitrixWorkspaceApp.exe version 1912 CU6 [aka 19.12.6000] [LTSR], 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, 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 or CitrixReceiver.exe is installed using an administrator account. then the Workspace app only needs to be installed once.
- Administrator installations are installed to C:\Program Files [x86]\Citrix\ICA Client.
- 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 is performed on a machine that has non-administrator installs of Workspace app, then the two installations will conflict. Best option 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.

Workspace app supports 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 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, Workspace app GUI, installer command line. See Configuring Citrix Workspace Updates at Citrix Docs.
Workspace app 2107 and later let users select an Update channel.
See George Spiers Citrix Receiver for Windows Auto-Update.

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

Auto-update is broken in Receiver for Windows 4.11 and older, and Receiver for Mac 12.9 and older. To fix it, manually upgrade to the next version [e.g. Workspace app for Mac], or install the Fix that can be downloaded from the Receiver download page [Source = CTX234657 Receiver Updater stops working with “Problem Checking for updates” error]

Auto-update is configured using Workspace app group policy under the Citrix Workspace Updates, Receiver Updates or Auto-Update node.

Workspace app Splash Screen

Workspace app shows a Splash Screen on first launch with the text “Citrix Workspace app extends the capabilities of Citrix Receiver”.

To prevent this splash screen, set the following registry value: [source = Dennis Span on Twitter]

Key = HKEY_CURRENT_USER\SOFTWARE\Citrix\Splashscreen
- Value [REG_SZ] = SplashscreenShown = 1

Add Account Wizard

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

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]

Rename CitrixReceiver.exe to CitrixReceiverWeb.exe.
Rename CitrixWorkspaceApp.exe to CitrixWorkspaceAppWeb.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 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 How to configure Receiver to a Store that is not 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 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. CitrixWorkspaceApp.exe /includeSSON CitrixReceiver.exe /includeSSON
/ALLOWADDSTORE=A – by 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;//Citrix.corp.com/Citrix/MyStore/discovery;on;App Store" CitrixReceiver.exe STORE0="AppStore;//Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"
- Workspace App and Receiver 4.10 and newer can discover the Store through NetScaler Gateway. CitrixWorkspaceApp.exe STORE0="AppStore;//gateway.corp.com#MyStore;On;App Store" CitrixReceiver.exe STORE0="AppStore;//gateway.corp.com#MyStore;On;App Store"
/SELFSERVICEMODE=False – 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 it to LTSR Branch only. AutoUpdateCheck can also be set to manual or disabled. AutoUpdateStream can also be set to Current. See Configuring Citrix Workspace Updates at Citrix Docs. CitrixWorkspaceApp.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR CitrixReceiver.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR
/ENABLEPRELAUNCH=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. Note: 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 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 Workspace app is running inside a VDA published desktop, set it to 0.
AlwaysUseStubs [REG_SZ] = True. Workspace app and Receiver 4.3.100 and newer don’t create .exe stubs by default. Set this to create .exe stubs. Also 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.
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 non-HTTPS stores to Workspace app:

HKLM\Software\Wow6432Node\Citrix\AuthManager
- ConnectionSecurityMode [REG_SZ] = Any

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

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

To prevent beacon probing from using proxy, set:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Citrix\Receiver\inventory
- BeaconProxyEnabled [REG_DWORD] = 0

To enable foreground progress bar, set:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client
- ForegroundProgressBar [REG_DWORD] = 1

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

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 Workspace app ADMX template [C:\Program Files [x86]\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 Workspace [or Receiver] and configure the following:

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| 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.
- 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 //support.citrix.com/article/CTX133565.
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 Workspace app using Active Directory

To deploy Workspace app using Active Directory, configure a GPO with a computer startup script that runs the Workspace app installer executable. Citrix provides sample scripts that can be downloaded from one of the Workspace app download pages [Workspace app 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.

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

You can change Workspace app’s / Receiver’s 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 //storefront.corp.com/Citrix/Store/discovery

It is sometimes necessary to Reset Citrix Workspace or Reset Receiver by right-clicking the Workspace app 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: Policies > Administrative Templates > Citrix Components > Citrix Workspace

Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver

For example, you can disable Customer Experience Improvement Program [CEIP] from here.

See //www.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip for additional places where CEIP is enabled.

Workspace app 1905 and newer has a setting to Disable sending data to 3rd party [e.g. Google Analytics].

Workspace app 1905 and newer let you disable embedded browser caching.

Workspace app 1905 and newer have NetScaler LAN Proxy under Network routing > Proxy.

Workspace app 1808 and newer have User authentication | Single Sign-on for NetScaler Gateway.

Receiver 4.12 adds Network Routing | Deprecated cipher suites to configure deprecated ciphers.

Citrix Workspace Updates, [aka AutoUpdate] can be configured using group policy. See Configuring Citrix Workspace Updates at Citrix Docs.

Workspace app 1912 and newer can be configured to require in-memory ICA files only. The setting called Secure ICA file session launch is under the Client Engine node. See Citrix Docs for details on in-memory ICA files instead of writing ICA files to disk.

Workspace app has settings to hide Advanced Preferences, enable/disable DPI, and enable/disable H265.

Workspace app 4.8 and newer have SplitDevices GPO setting under Citrix 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 Pass-Through Authentication with XenDesktop 7.5

Run the command
Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on a Delivery Controller.
- In XenApp 6.5, this is a Citrix Policy > Computer > Trust XML Requests.
Login to the PC as an administrator.
If installing Workspace app, as an administrator, during installation, on the Enable Single Sign-on page, check the box next to Enable Single Sign-on. Then finish the installation.
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 .
4. 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 is installed.
Go to Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace.
Expand Citrix Workspace and click User authentication.
On the right, double-click Local user name and password.
Select Enabled and then check the box next to Allow pass-through authentication for all ICA connections. Click OK.
In Workspace app 1808 and newer, you can enable Single Sign-on for NetScaler Gateway.
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.
Local Intranet zone should have Automatic logon only in Intranet zone enabled.
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.
If Workspace app won’t connect or is slow to enumerate icons, then you might have to disable Automatically detect settings in IE.
Right-click the Workspace app icon and click Advanced Preferences.
Click Configuration Checker.
Check the box next to SSONChecker and click Run.
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 Workspace app Self-Service.

Install the receiver.admx [and .adml] template into PolicyDefinitions if you haven’t already.
Edit a GPO that applies to endpoint devices that have Citrix Workspace app installed.
Go to Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
On the right, double-click NetScaler Gateway URL/StoreFront Accounts List.
Select Enabled, and then click Show.
Enter a store path based on the example shown in the Help box. Workspace app lets you enter a Gateway path. Then click OK.
Note: Gateway paths 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 then click Shortcuts and Reconnect, or Settings Option.

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

Workspace app Registry values
receiver.admx GPO Template
From StoreFront in C:\inetpub\wwwroot\Citrix\Roaming\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 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 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 Workspace [or Receiver] is a node called SelfService.

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

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

Workspace app and Receiver 4.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 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.

Download the ADMX file from //support.citrix.com/article/CTX133565.
Copy the .admx and .adml files to PolicyDefinitions [Sysvol, or C:\Windows].
The .adml file goes in the en-US folder.
Edit a GPO that applies to the endpoint devices that are running Receiver.
Go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace [or Receiver] | Citrix Client Selective Trust [x64].
Enable the setting Create Client Selective Trust Keys.
Then expand the regions, and configure the permission settings as desired.

Desktop Lock

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

External links:

Use Studio to configure Workspace app Accounts in Published Desktop

In published desktops, Workspace app can be used for placement of shortcuts on the user’s Start Menu and Desktop. Use group policy to hide the common program groups and then use Workspace app 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 //citrix.corp.com/Citrix/Store/discovery. Click OK.
Edit a Delivery Group that has a published desktop and Citrix Workspace app 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 will be automatically configured with this URL.

Published Desktop – use Workspace app to control Shortcuts

If you install Workspace app inside a published desktop [Workspace app on a VDA], then Workspace app can get icons from StoreFront and put those icons on the user’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 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 inside a published desktop is simplified if you have the following minimum versions:

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

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

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

Make sure Workspace app or Receiver version 4.11 or newer is installed on the VDA.
Install the Workspace app ADMX files if you haven’t already. For vPrefer, make sure they are the ADMX files from Workspace app.
Enable the Group Policy setting Remove common program groups from Start Menu and apply it to non-administrators.
- This removes all Public [aka All Users] Start Menu shortcuts. Workspace app will re-add the shortcuts based on user group membership.
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 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 Server 2012 and Windows 10 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:
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. If you’re using Gateway internally, and if Workspace app 1808 or newer, then also enable Single 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 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].
1. In Citrix Studio, edit each published application, and on the Delivery tab, specify a category. This will become the Start Menu folder name.
2. If Workspace app Self Service Mode [GUI] is enabled, in Studio, edit each application, and add KEYWORDS:Auto and/or KEYWORDS:Mandatory to the published application 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’s SelfService interface as described earlier.
3. 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 configuration.
Create a group policy that applies to VDAs, and configure the group policy to define the Store URL for Workspace app similar to //citrix.corp.com/Citrix/Store/discovery. Replace the FQDN with your load balanced StoreFront FQDN. Also replace the path to the store with your store path. Make sure there is /discovery on the end. By default, Workspace app and Receiver only support https.
1. Your StoreFront store probably delivers both application and desktop icons. If you want to filter out the desktop icons, then create a new StoreFront store, and configure the Workspace app on the VDA to connect to the new Store.
2. In StoreFront 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.
For vPrefer in Workspace app, VDA 7.17 [or newer], and StoreFront 3.14 [or newer], edit a GPO that applies to the VDAs.
On your Delivery Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $true
- This is required for Pass-through Authentication from Workspace app.
Configure your client devices to connect to the published desktop.
1. When users connect to the published desktop, Workspace app will auto-launch and hopefully auto-login.
2. If Workspace app Self-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.
3. If Workspace app 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.
4. Users can copy icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn’t Move it.
5. Users can then launch applications directly from the Start Menu, from the Desktop, or from the Workspace app [if the Self-Service interface is enabled].
6. If Workspace app 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, Workspace app 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.
7. 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.
8. If the user deletes Workspace app 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.

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.

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 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.
2. Or use the prefer keyword to copy shortcuts from the PreferTemplateDirectory.
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].
1. 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.
  - See Ralph Jansen Citrix Receiver 4.1 Prefer keyword examples
2. If using the prefer keyword with the PreferTemplateDirectory, enter it as KEYWORDS:prefer=shortcutname where shortcutname is the name of the shortcut that is copied from the Template directory.
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/Automate Workspace app and Receiver Self-Service

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

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

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

Citrix Workspace app and Receiver come with a .dll file that implements the Citrix Common Connection 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.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 actual user would do by:

Opening Internet Explorer.
Navigating directly to the Receiver for Web site or NetScaler Gateway portal.
Completing the fields.
Logging in.
Clicking on the resource.
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 support the delivery of Microsoft Teams from Citrix Virtual Apps and Desktops using optimization for Microsoft Teams.

Microsoft Teams optimization/offloading [similar to Skype optimization/offloading] requires the following:

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

The redirection components are built into VDA and Workspace app. There is no need to install anything separately. The 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 available versions:

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

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 "” -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 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 – Workspace app Logging

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

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 Workspace app and Receiver logging ;************************ ;logpath: %USERPROFILE%\Appdata\Local\Citrix\Receiver [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix] "ReceiverVerboseTracingEnabled"=dword:00000001 ;Authentication Manager logging ;****************************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\AuthManager [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\AuthManager] "LoggingMode"="verbose" "TracingEnabled"="True" "SDKTracingEnabled"="True" ;Self Service logging ;******************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle] "Tracing"="True" "AuxTracing"="True" "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] "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 ;Single Sign-on Logging ;************************** ;//support.citrix.com/article/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="true" "LogPath"="C:\\Temp"

Troubleshooting – Duplicate Stores

Stores are sometimes duplicated in Workspace app, especially if you are running Workspace app inside a VDA. [h/t Dan High]

StoreFront URLs can be defined in several places:

In Studio, go to Configuration > StoreFront and delete all URLs configured here.
Look in GPOs for Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront > NetScaler Gateway URL/StoreFront Accounts List. Remove any URLs configured here.
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.
When Citrix Workspace app switches between StoreFront servers in multiple datacenters, it’s possible for each datacenter to be treated as a separate Workspace app 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.

If you are running Workspace app 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.
1. Under \receiver\ctxaccount delete all entries.
2. 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.
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.
Verify no cached profile folders for user on server.