banner



Home  ›  Why Use A Vpn For Client-to-server Connections Over The Internet?

Why Use A Vpn For Client-to-server Connections Over The Internet?

Written By Wednesday, April 27, 2022 Add Comment Edit

Navigation

Workspace app is the new name for Receiver. This post applies to all Workspace app versions, including the Electric current Release version 2204.1, and the LTSR versions 2203.i and 1912.7000.

  • Modify Log
  • Workspace app versions
  •  Overview
    • Workspace app Modules
    • Workspace app Discovery and Beacon Procedure
    • Virtual Monitors
  • Uninstall Old Receiver Clients
  • Installation and Configuration
    • Administrator vs non-administrator
    • Workspace app Auto-Update
    • Splash Screen
    • Add Business relationship Magician
    • CitrixWorkspaceApp.exe Command line switches
    • Workspace app Registry values
    • Workspace app Group Policy settings
    • Client-side Registry for Microsoft Edge
  • Workspace app ADMX GPO Template
  • Laissez passer-through Authentication
  • Automatically add StoreFront Accounts to Workspace app
  • Control Shortcut placement on Desktop and Start Carte – and Workspace Control (Session Reconnect)
  • Enable Prelaunch
  • Command Device Mapping Prompts
  • Desktop Lock
  • Use Studio to configure Workspace app Accounts in Published Desktop
  • Published Desktop – configure Workspace app to place shortcuts
  • Script / Automate Workspace app and Receiver Self-Service
  • Microsoft Teams
  • Skype for Business
  • Troubleshoot:
    • Citrix QuickLaunch
    • Workspace app Logging
    • Make clean up Duplicate Stores

💡 = Recently Updated

Modify Log

  • 2022 Apr 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update seven Hotfix one
  • 2022 Apr seven – Versions – updated for Workspace app 2203.i LTSR
  • 2022 April 7 – updated entire article for Workspace app 2204.i
  • 2022 Mar 17 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7
  • 2022 Feb 7 – updated entire article for Workspace app 2202
  • 2021 December nine – Versions – updated for Workspace app 1912 LTSR Cumulative Update 6
  • 2021 Dec 8 – updated entire article for Workspace app 2112.1
  • 2021 Oct 4 – updated entire article for Workspace app 2109.1
  • 2021 Sep 29 – updated entire commodity for Workspace app 2109
  • 2021 Aug thirty – updated unabridged commodity for Workspace app 2108
  • 2021 Aug eleven – Versions – updated for Workspace app 1912 LTSR Cumulative Update 5
  • 2021 July 29 – updated unabridged article for Workspace app 2107
  • 2021 June 16 – updated unabridged article for Workspace app 2106
  • 2021 May 11 – Workspace app 1912 CU4 and Workspace app 2105 and newer prepare security vulnerabilities
  • 2021 May 10 – updated unabridged article for Workspace app 2105
  • 2021 May 10 – Versions – updated for Workspace app 1912 LTSR Cumulative Update four
  • 2021 Mar 23 – updated entire article for Workspace app 2103.i
  • 2021 Mar 16 – updated entire article for Workspace app 2103
  • 2021 Feb 1 – updated unabridged commodity for Workspace app 2102
  • 2021 Jan 20 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 Dec xviii – updated entire article for Workspace app 2012.one
  • 2020 Dec viii – updated entire article for Workspace app 2012
  • 2020 Nov 2 – updated entire article for Workspace app 2010
  • 2020 Oct 15 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct 1 – updated entire article for Workspace app 2009.6
  • 2020 Sep 24 – updated entire article for Workspace app 2009.5
  • 2020 Sep xv – updated entire article for Workspace app 2009

Workspace app Versions

Workspace app is the new proper name for Receiver.

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

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

Workspace app 2009 and newer take the new Citrix logo.

Workspace app 1912 and newer support App Protection. It's available in both the LTSR versions (1912 and 2203) and the Current Release 2204.i version.

In that location are two LTSR (Long Term Service Release) versions of Workspace app: 2203.one, and 1912 Cumulative Update vii (aka nineteen.12.7000) (or 1912 Cumulative Update 7 Hotfix 1). 1912 CU5 and newer contain many Teams optimization enhancements. The LTSR versions of Workspace app do not back up Browser Content Redirection (BCR) considering the embedded browser is non included in the LTSR Workspace app.


Workspace app Modules

The Workspace app installer deploys multiple modules. Here are the of import 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 constitute a connexion.
  • Single Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs later on an ICA connectedness is established
  • Workspace Motorcar-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The nigh recent proper 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 non include Self-Service. The concluding version of Receiver Enterprise is 3.4.

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

Workspace app Discovery and Beacon Process

If you are using Workspace app'due south built-in user interface (instead of a web browser), and so Workspace app first prompts you to perform discovery, which is also chosen Add Business relationship.

The Citrix logo changed in Workspace app 2009 and newer.

The Add together Account wizard changed in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Deject 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 yous entered a StoreFront FQDN, so Workspace app volition download the Provisioning File direct from the StoreFront server.
  • If you entered a Gateway FQDN, then Gateway will first prompt the user to authenticate. Afterward authentication, Gateway will connect to its configured Business relationship 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 strength a particular shop.

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

The Provisioning File downloaded from StoreFront is an XML document containing values for several items configured in the StoreFront panel. 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:

Workspace app reads the Provisioning File, and configures itself past 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 yous performed discovery through NetScaler Gateway, discover that the internal Base of operations URL is added to the user's registry.

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

  1. Attempt to connect to the Internal Beacon.
  2. If the Internal Buoy is reachable, connect directly to the StoreFront Base of operations URL (Address).
  3. If the Internal Beacon is not reachable:
    1. Attempt to connect to the External Beacons. If the External Beacons are not reachable, then finish attempting to connect.
    2. Connect to the Gateway address configured in the Provisioning File. If there is more than than one Gateway, connect to the Gateway that is marked as the Default.

Here are some interesting notes on this connection process:

  • The FQDN you entered during Discovery has absolutely goose egg to exercise with how Workspace app connects to StoreFront or Gateway. The actual connection procedure is controlled by the contents of the Provisioning File, non the Discovery address.
  • If the Provisioning File has multiple Gateways defined, Workspace app uses whichever Gateway is marked equally 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'southward Avant-garde Preferences.

In StoreFront Console, if any configuration changes are performed that touch 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) and then the updated Provisioning File is imported?

Hither are some boosted methods of performing Workspace app Discovery:

Virtual Monitors

In Workspace app 1812 and newer, when connected to a published desktop on a unmarried monitor, you can split the screen into virtual monitors. This feature is intended for large 4K monitors.

Uninstall Old Clients

Workspace app and Receiver 4.4 and newer includes Receiver Clean-Upwardly, and then, in theory, it'due south 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 information technology silently, run CitrixWorkspaceApp.exe /RCU /Silent orCitrixReceiver.exe /RCU /Silent.
  • In Workspace app 1909 and newer, /forceinstall switch is the replacement for /rcu switch.

For a reliable upgrade feel, write a script to remove the old clients, make clean up the registry and file system, then deploy the new Workspace app.

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

The Receiver Clean-Up utility for Receiver four.three 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 operation is experienced after upgrade from an earlier Receiver or Online Plug-in
  • If Receiver upgrade is non possible due to feature incompatibility and/or a make clean uninstall is required
  • The Receiver Clean-Up Utility removes components, files, and registry values of Online Plug-in 11.ten, 12.x, and Receiver for Windows iii.x, 4.x (Online Plugin-in thirteen.ten, fourteen.10). This includes the Offline Plug-in component if installed.

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

Blog posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Client and Install Citrix Receiver 3.x
  • Full list of Citrix Client Uninstall Strings

Installation and Configuration

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

Links:

  • Citrix Web log Post: Optimizing Citrix Receiver for Pre-launch and Single Sign-On
  • Citrix CTX202002 How To Deploy Citrix Receiver for Windows Using SCCM 2012 R2

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

CitrixWorkspaceApp.exe electric current release version 2204.one, LTSR version 2203.1, or LTSR version 1912 CU7 (aka 19.12.7000) (or 1912 CU7 Hotfix 1) can exist installed by simply double-clicking it. Note: LTSR Workspace app does not support Browser Content Redirection. Workspace app 2006 and newer practice not back up Windows 7.



Ambassador vs not-administrator

  • Non-administrator – If a non-administrator installs Workspace app, and so each non-ambassador that logs in to the same workstation will have to reinstall Workspace app.
    • Non-administrator installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Customer for each user.
  • Administrator – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator business relationship. then the Workspace app just needs to be installed once.
    • Administrator installations are installed to C:\Plan Files (x86)\Citrix\ICA Client.
    • Administrator installations of Workspace app 1912 and newer can be manually upgraded by non-administrators by clicking Cheque for Updates. Older versions cannot be upgraded by not-administrators.
  • Conflicts – If an administrator install of Workspace app is performed on a machine that has non-ambassador installs of Workspace app, then the two installations will conflict. Best choice is to uninstall not-admin Workspace app and Receiver before installing admin Workspace app. Otherwise, the user's contour probably has to be reset before Workspace app is functional again.
    • Citrix commodity CTX249920 Workspace App for Windows – Your apps are not available at this fourth dimension – Event when installing Citrix Receiver in non elevated/per-user install style describes the HKEY_CURRENT_USER registry keys that must be deleted to prepare this outcome.
    • For a script to clean-up the per-user installs, run across Marker DePalma at Citrix Receiver Per-User Install Cleanup.

Auto-Update

Workspace app supports auto-update.

Some notes:

To troubleshoot Motorcar-update, meet 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 adjacent version (east.g. Workspace app for Mac), or install the Fix that tin can be downloaded from the Receiver download folio (Source = CTX234657 Receiver Updater stops working with "Problem Checking for updates" error)

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




Workspace app Splash Screen

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

To prevent this splash screen, set the post-obit registry value: (source = Dennis Span on Twitter)

  • Cardinal = 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 volition launch and ask you to add together an business relationship. If Workspace app, notice the checkboxPractice not evidence this window automatically at logon.

For Workspace app and Receiver 4.4 and newer, FTU (First Fourth dimension Employ aka Add Account Magician) will exist displayed simply if a store is not configured. If a store is already configured via command line, GPO, or Citrix Studio, and then FTU screen will not exist 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.
  • RenameCitrixWorkspaceApp.exe toCitrixWorkspaceAppWeb.exe.
  • Install using a command line switch:
    • CitrixWorkspaceApp.exe/ALLOWADDSTORE=North
    • CitrixReceiver.exe/ALLOWADDSTORE=Due north
  • Set the registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\EnableFTU=dword:00000000 (or EnableX1FTU =dword:0)
  • Disable the EnableFTU policy setting inReceiver.admx.
  • Change Registry values postal service installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, fix AllowAddStore value to N.
  • Set the registry value: HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\NeverShowConfigurationWizard (REG_SZ) = true
  • Also see Suppressing Add together Account dialog at Citrix Docs.

Find Hidden Stores

When Receiver is first launched, it must perform Discovery, which is the procedure of downloading the .xml provisioning file from StoreFront. Discovery is performed past entering a StoreFront FQDN or Gateway FQDN. To discover a subconscious store (a shop that'southward not advertised), add ?StoreName to the end of the FQDN. CTX214819 How to configure Receiver to a Store that is not advertised.

CitrixWorkspaceApp.exe / CitrixReceiver.exe Control line switches

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

For unattended installation of Workspace app, run across CTA Dennis Bridge Citrix Workspace App unattended installation with PowerShell or Citrix Receiver unattended installation with PowerShell.

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

  • /silent
  • /includeSSON – enables laissez passer-through hallmark. GPO configuration is as well 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 control line: 
    CitrixWorkspaceApp.exe STORE0="AppStore;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"  CitrixReceiver.exe STORE0="AppStore;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"
    • Workspace App and Receiver 4.10 and newer tin can discover the Store through NetScaler Gateway. 
      CitrixWorkspaceApp.exe STORE0="AppStore;https://gateway.corp.com#MyStore;On;App Store"  CitrixReceiver.exe STORE0="AppStore;https://gateway.corp.com#MyStore;On;App Store"
  • /SELFSERVICEMODE=False – disables the Cocky-Service interface and enables shortcut-only mode: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=False  CitrixReceiver.exe /SELFSERVICEMODE=Imitation
  • /AutoUpdateCheck=car /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets it to LTSR Branch only. AutoUpdateCheck can likewise be set to manual or disabled. AutoUpdateStream can likewise be gear up to Electric 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=i

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'due south / Receiver'south 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) = Truthful or Imitation
  • StartMenuDir (REG_SZ) = name of folder on Start Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = proper noun of folder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = Truthful – If SSON is enabled then PreLaunch is already enabled by default.
  • AllowAddStore (REG_SZ) = A – Just if using http (instead of https) to connect to StoreFront.
  • AllowSavePwd (REG_SZ) = A – Only if using http (instead of https) to connect to StoreFront.
  • UserDomainName (REG_SZ) = pre-filled domain name
  • InitialRefreshMinMs (REG_SZ) = one – 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.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Hallmark Window Periodically When Receiver is Not Opened
  • MaxSimultaneousFetches (REG_DWORD) = 6  – improves the fourth dimension of loading icons in Start Menu
  • MaxSimultaneousSubscribes (REG_DWORD) = half-dozen – improves the time of loading icons in Start Carte du jour
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server. (or False)
  • SilentlyUninstallRemovedResources (REG_SZ) = True – prevents dialog boxes when resources are removed from the server
  • PreferTemplateDirectory (REG_SZ) = UNC path or local path containing shortcuts copied past the prefer keyword. Give the shortcuts a short name.
  • PnaSSONEnabled (REG_SZ) = Truthful – Enables Single Sign-on for PNAgent (Spider web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Workspace app is running inside a VDA published desktop, fix it to 0.
    • If yous're having trouble getting sessions to reconnect, see Receiver 4.3 Desktop will non machine-reconnect when logging into a machine at Citrix Discussions
  • AlwaysUseStubs (REG_SZ) = True. Workspace app and Receiver 4.3.100 and newer don't create .exe stubs by default. Fix this to create .exe stubs. As well run across Citrix CTX211893 Controlling Shortcut beliefs in Receiver iv.3.100.
  • DontCreateAddRemoveEntry (REG_SZ) = True – don't create "Delivered by Citrix" entries in Programs and Features
  • DesktopNameFormatString = format string for shortcut names – For case "{0}_{one}_{2}_{iii}". Come across the link for details.
  • SelfServiceFlags (REG_DWORD) = 4 – prevents duplicate shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = 5 to stop external SSON from prompting for authentication
  • ReEvaluateNetwork (REG_SZ) = true – for Buoy detection with Unmarried 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) = Whatever

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

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\TCP/IP
    • OutBufCountClient2 = Number of OutBufs (default is 44)
    • OutBufCountHost2 = Number of OutBufs (default is 44)
    • Encounter CTX125027 How to Optimize HDX Bandwidth Over High Latency Connections for some recommended values (multiples of 44)

To forestall buoy 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) = ane

For client-to-server file type redirection, prepare:

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

To prevent "USB Hub Power Exceeded" bulletin, set up (not needed in 4.2.100 and newer):

  • HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB (aforementioned path for 32-flake 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 Customer\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). Also re-create receiver.adml to C:\Windows\PolicyDefinitions\en-united states of america (or Sysvol).

Edit a GPO that applies to customer machines, go to Calculator Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) and configure the following:

  • To enable pass-through authentication: go to | User Authentication |.
    • Local Username and Password – Check the summit two boxes.
    • Also add the StoreFront FQDN to the Local Intranet zone in Net Explorer.
    • Unmarried Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add a store, get to | StoreFront |
    • StoreFront Accounts List – see the help text
  • To enable Machine-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 Feel |
    • Local App Access Settings
  • To configure the Self-Service interface, become to | SelfService |
    • Set Manage SelfServiceMode to Disabled to completely disable the Cocky-Service window. This causes all icons to be placed on the First Card.
    • Enable Manage App Shortcut and configure it as desired.
      • To permit the Self-Service window, but forestall it from automatically opening (reside in systray), tickPrevent Citrix Workspace (or Receiver) performing a refresh of the application list when opened. Source
    • Enable Control when Workspace (or Receiver) attempts to reconnect to existing sessions. If this is a VDA published desktop, set information technology to Disabled. Otherwise configure it as desired.
    • Ready Enable FTU to Disabled  to foreclose the Add Account wizard from displaying.
    • EnableLet/Prevent users to publish dangerous 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 http://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 than of the regions.

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

  • Computer Configuration | Policies | Administrative Templates | Windows Components | File Explorer
    • Permit 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 reckoner startup script that runs the Workspace app installer executable. Citrix provides sample scripts that can be downloaded from one of the Workspace app download pages (Workspace app current release version 2204.ane, LTSR version 2203.1, or LTSR version 1912 CU7 (aka 19.12.7000), past expanding Downloads for Admins (Deployment Tools).

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

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

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

"C:\Programme Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -deleteproviderbyname Corporate  "C:\Plan Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -init -createprovider Corporate https://storefront.corp.com/Citrix/Store/discovery

Information technology is sometimes necessary toReset Citrix Workspace orReset Receiver by correct-clicking the Workspace app systray icon, clickingAvant-garde Preferences, and clicking theReset link. You tin exercise this from the command line by running "C:\Programme 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 feel in Microsoft Edge is not ideal. Every time a user clicks an icon, the user has the click theOpen button afterward the .ica file is downloaded.

Citrix Blog Mail service Providing Full Receiver for Web Experience for Microsoft Edge has instructions for enabling the Receiver Launcher for Edge. Apply your preferred text editor to open spider 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[three-9]|[6789][0-9])|\d\d\d))|(Chrome/((iv[2-9]|[56789][0-9])|\d\d\d)))(?!.*Border)". Remove (?!.*Border) and save the file.

Only once you do that, you get a new switch apps prompt every fourth dimension you launch an icon from Border.

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

Workspace app Group Policy ADMX Template

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

  1. From a machine that has Workspace app installed, discover the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • Y'all can also download the ADMX files from i of the Workspace app download pages (Workspace app electric current release version 2204.i, LTSR version 2203.1, or LTSR version 1912 CU7 (aka 19.12.7000), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. Also copy theen-Usa folder. In Workspace app, the files are still namedreceiver.admx.
  3. Go to your domain'south SYSVOL share and in the Policies folder expect for a PolicyDefinitions folder. If one exists, paste the .admx file directly into the PolicyDefinitions binder. If this folder doesn't exist in SYSVOL, instead re-create the .admx file to C:\Windows\PolicyDefinitions. Overwrite any existing Receiver ADMX files.
  4. The GPO settings can then be plant at one of the following:
    • Computer Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Workspace
    • Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For instance, yous tin disable Customer Experience Improvement Program (CEIP) from here.
  6. See https://www.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip for additional places where CEIP is enabled.
  7. Workspace app 1905 and newer has a setting toDisable sending data to tertiary political party (e.g. Google Analytics).
  8. Workspace app 1905 and newer let you disable embedded browser caching.
  9. Workspace app 1905 and newer have NetScaler LAN Proxy underNetwork routing > Proxy.
  10. Workspace app 1808 and newer takeUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver four.12 adds Network Routing | Deprecated cypher suites to configure deprecated ciphers.

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

Pass-through Hallmark

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

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

  4. If installing an older version of Receiver:
    1. Go to the downloaded Citrix Receiver. Shift-correct-click CitrixReceiver. exe, and click Copy equally path.
    2. Open up a command prompt.
    3. Correct-click to paste the path in the control prompt and so add together /includeSSON to the cease of the command. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, go to C:\Plan Files (x86)\Citrix\ICA Client and expect for the file ssonsvr. exe.
  6. And if you open regedit and go to HKLM\System\CurrentControlSet\Control\NetworkProvider\Guild, you should see PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if y'all haven't already.
  8. Edit a GPO that is applied to the client PCs where the Workspace app is installed.
  9. Go to Reckoner Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace.
  10. Expand Citrix Workspace and click User authentication.
  11. On the right, double-click Local user proper noun and password.
  12. Select Enabled and and so check the box adjacent to Permit pass-through hallmark for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, you can enableSingle Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Internet Explorer. You can use a GPO to configure this on the client side.
  15. Local Intranet zone should have Automatic logon simply in Intranet zone enabled.
  16. Logoff Windows and log back on. In Task Manager you should now see ssonsvr. exe. This won't announced unless you logoff and log back on.
  17. If Workspace app won't connect or is slow to enumerate icons, then you might accept to disable Automatically observe settings in IE.
  18. Right-click the Workspace app icon and click Advanced Preferences.
  19. ClickConfiguration Checker.
  20. Check the box adjacent toSSONChecker and clickRun.
  21. The lines with scarlet x volition indicate the issue and cosmetic action.

StoreFront Accounts

You lot tin can employ a customer-side GPO to add a store (Account) to Workspace app Self-Service.

  1. Install the receiver.admx (and .adml) template into PolicyDefinitions if you lot haven't already.
  2. Edit a GPO that applies to endpoint devices that have Citrix Workspace app installed.
  3. Go to Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
  4. On the right, double-click NetScaler Gateway URL/StoreFront Accounts Listing.
  5. Select Enabled, and then clickEvidence.
  6. Enter a store path based on the example shown in the Help box. Workspace app lets you enter a Gateway path. And so click OK.
  7. 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 Avant-garde Preferences, then clickShortcuts and Reconnect, orSettings Option.


From Citrix Docs Configuring application delivery: At that place are several methods of controlling how Workspace app displays shortcuts on the Showtime Menu and Desktop equally detailed beneath:

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

Nether HKLM\Software\Wow6432Node\Citrix\Dazzle (or HKCU\Software\Wow6432Node\Citrix\Dazzle) are several registry values related to shortcuts. Some of the settings only apply if SelfServiceMode is set to Imitation. Here are some common options:

  • SelfServiceMode – ready to False so Receiver disables the Self-Service interface and automatically places all published shortcuts on the First Menu and/or Desktop. More details in Configuring application delivery at Citrix Docs.
  • PutShortcutsOnDesktop– set toTrue to identify 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 at that place is potentially a disharmonize between local apps and remote apps, then yous should place the Kickoff Carte du jour shortcuts in a folder.
  • PreferTemplateDirectory (with KEYWORDS:prefer=shortcutname) – copies the shortcutname from the template directory to the Offset Menu and/or Desktop.

If you lot 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.two.100 and newer have the power to configure (or disable) Workspace Control using group policy. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure information technology 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 Showtime 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 Customer\Prelaunch

  • Proper name: Land
    • REG_SZ: 0 = disable, 1 = just-in-fourth dimension 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. G:T:W:Thursday:F:S:SU are the days of the week. For case, to enable scheduled pre-launch on Monday, Wednesday, and Friday at 1:45 p.1000., set Schedule as Schedule=13:45|ane:0:1:0:1:0:0 . The session actually launches between 1:fifteen p.m. and 1:45 p.m.
  • Name: UserOverride
    • REG_SZ: 0  = HKLM overrides HKCU, ane = HKCU overrides HKLM

Device Access Behavior (Client Selective Trust)

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

To configure the default behavior, run into the Citrix Knowledgebase commodity How to Configure Default Device Access Beliefs of Receiver, XenDesktop and XenApp. Note: there is a bug stock-still in Receiver 4.2.100 and newer.

  1. Download the ADMX file from http://support.citrix.com/commodity/CTX133565.
  2. Re-create the .admx and .adml files to PolicyDefinitions (Sysvol, or C:\Windows).
  3. The.adml file goes in theen-US folder.
  4. Edit a GPO that applies to the endpoint devices that are running Receiver.
  5. Become to Reckoner Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) |Citrix Customer Selective Trust (x64).
  6. Enable the setting Create Customer Selective Trust Keys.

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

Desktop Lock

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

External links:

  • Dale Scriven YouTube video – Citrix Desktop Lock installation and configuration
  • Jarian Gibson and Andrew Morgan – Citrix Receiver Desktop Lock
  • An culling to Desktop Lock – ThinKiosk

Use Studio to configure Workspace app Accounts in Published Desktop

In published desktops, Workspace app can exist used for placement of shortcuts on the user's Start Carte du jour and Desktop. Use group policy to hibernate the common plan groups and then use Workspace app to place published applications back on the Starting time Card and Desktop based on user's group membership and subscription preference.

  1. In Citrix Studio, on the left, aggrandize the Configuration node, correct-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.thou. /Citrix/Store) and then /discovery on the end of the URL. The full URL would be similar to https://citrix.corp.com/Citrix/Store/discovery. Click OK.
  4. Edit a Commitment Grouping that has a published desktop and Citrix Workspace app installed.
  5. On the StoreFront page, alter 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 – utilize Workspace app to control Shortcuts

If yous install Workspace app inside a published desktop (Workspace app on a VDA), then Workspace app tin can go icons from StoreFront and put those icons on the user's published desktop Start Carte du jour 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, then make sure y'all perform a Proof of Concept to make up one's mind how this functionality impacts logon times.

Configuration of Workspace app inside a published desktop is simplified if y'all accept the post-obit minimum versions:

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

If yous run across 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.

  • If you don't meet these minimum version requirements, then you'll need to utilize the older Prefer Keyword method of treatment Workspace app shortcuts as detailed later.
  • For a detailed explanation of vPrefer, run across Citrix Blog Post VPrefer: Session Sharing Between a Published Desktop and a Published Application Made Easy

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

  1. Make sure Workspace app or Receiver version four.11 or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if you haven't already. For vPrefer, make sure they are the ADMX files from Workspace app.
  3. Enable the Group Policy settingRemove common plan groups from First Menu and utilize it to non-administrators.
    • This removes all Public (aka All Users) Start Carte du jour shortcuts. Workspace app will re-add together the shortcuts based on user group membership.
  4. On the VDA, configure the post-obit Workspace app Registry keys (or corresponding settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\WSCReconnectMode="0″ then Workspace app doesn't try to reconnect to the published desktop you're already running.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\SelfServiceMode to Faux. This turns off the Workspace app Self-Service GUI and acts like all icons are subscribed. Otherwise, just subscribed (favorited) icons would be placed on the Start Menu and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True. This creates a Showtime Bill of fare folder based on the published app'southward configured Category.
  5. Configure each desired published app to Add shortcut to user'south desktop.
    • Or, configure HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PutShortcutsOnDesktop = Truthful to place all icons on the desktop.
  6. To control icon placement, configure the post-obit registry values:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to identify published applications in a sub-folder. Note: Windows Server 2012 and Windows 10 and newer only supports a single level of Start Menu folders, then setting this effectively turns off published app categories.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\DesktopDir to place published applications in a sub-folder on the desktop.
  7. Pass-through authentication:
    1. In a GPO that applies to the VDA, import the receiver.admx file, and set Local user name and password to Enabled. Cheque the box next to Let pass-through authentication for all ICA connections.
    2. If you lot're using Gateway internally, and if Workspace app 1808 or newer, then as well enableSingle Sign-on for NetScaler Gateway.
    3. In a user-level GPO that applies to the VDA, add the StoreFront FQDN to the Local Intranet zone. Brand sure it is not in the Trusted Sites zone, or enable Automatic logon with current user proper noun and password for the Trusted Sites zone.
    4. Make sure ssonsvr. exe is running after you login to the VDA. If not, troubleshoot it.
  8. When configuring Citrix Profile Management, make sure !ctx_startmenu! is non excluded from roaming.
  9. In Citrix Studio, configure a Delivery Group with delivery blazon = Desktop and Applications. Assign users to the delivery group, and the private published applications (if visibility is limited).
    1. In Citrix Studio, edit each published awarding, and on the Delivery tab, specify a category. This will become the Kickoff Card folder name.
    2. If Workspace app Self Service Mode (GUI) is enabled, in Studio, edit each awarding, and add KEYWORDS:Auto and/or KEYWORDS:Mandatory to the published application clarification. This forces the applications to exist subscribed/favorited. But subscribed (or Favorite) apps are displayed in the Commencement Card and Desktop. Unless you disable Workspace app'south SelfService interface every bit described earlier.
    3. Another pick is to go to the StoreFront Panel, click Stores on the left, and on the right, click Configure Store Settings, and click Disable User Subscriptions. This causes all apps to appear on the Start Menu and/or Desktop depending on Workspace app configuration.
  10. Create a group policy that applies to VDAs, and configure the group policy to ascertain the Shop URL for Workspace app similar to https://citrix.corp.com/Citrix/Store/discovery. Supplant the FQDN with your load balanced StoreFront FQDN. Likewise replace the path to the store with your store path. Make sure at that place is /discovery on the end. Past default, Workspace app and Receiver only supporthttps.
    1. Your StoreFront store probably delivers both application and desktop icons. If you want to filter out the desktop icons, then create a new StoreFront shop, and configure the Workspace app on the VDA to connect to the new Store.
    2. In StoreFront Panel, click the store for VDAs, and click Configure Shop Settings. On the Advanced Settings page, in the Filter resources by type row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA 7.17 (or newer), and StoreFront iii.14 (or newer), edit a GPO that applies to the VDAs.
    1. Go to Estimator Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is only in Workspace app ADMX templates from Workspace app.
    3. Set it toAllow all apps. Source = seven.17 vPrefer – non working with 32Bit Apps at Citrix Discussions.
  12. On your Delivery Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $truthful
    • This is required for Pass-through Authentication from Workspace app.
  13. Configure your client devices to connect to the published desktop.
    1. When users connect to the published desktop, Workspace app volition auto-launch and hopefully car-login.
    2. If Workspace app Cocky-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, and so only applications with KEYWORDS:Automobile and/or KEYWORDS:Mandatory in the published application description will be displayed. Users tin open the systray icon to subscribe to more than applications.
    4. Users can copy icons from the Start Menu to the desktop. Brand certain the user Copies the icon and doesn't Motionit.
    5. Users tin can then launch applications direct from the Start Menu, from the Desktop, or from the Workspace app (if the Self-Service interface is enabled).
    6. If Workspace app iv.eleven (or newer), VDA 7.17 (or newer), and StoreFront 3.14 (or newer), thenvPrefer is enabled by default. When launching an app icon that came from Workspace app, Workspace app checks the local VDA automobile 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 and so the local application shortcut should launch quickly. If the application is on a unlike commitment group then a second (double-hop) Citrix HDX/ICA connection will exist established.
    8. If the user deletes Workspace app shortcuts from the Kickoff Carte, you tin can get them back past going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app.

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

  1. Enable the Group Policy settingRemove common program groups from Start Carte du jour and employ information technology 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.
  2. On the VDA, configure the post-obit Receiver Registry keys (or corresponding settings in the receiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PreferTemplateDirectory = a UNC path or local path containing shortcuts to be copied by the prefer keyword. This tin can betoken to C:\ProgramData\Microsoft\Windows\Commencement Card.
  3. In Citrix Studio, configure a Delivery Grouping with delivery blazon = Desktop and Applications. Assign users to the Commitment Grouping and the applications (if visibility is limited).
    1. In Studio, edit each application and change KEYWORDS:Prefer to KEYWORDS:prefer. Detect the lower case p. It doesn't work with capital letter P.
      • With the prefer keyword, if y'all publish an application that is likewise 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.
      • Run across Ralph Jansen Citrix Receiver 4.one Adopt keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter it every bit KEYWORDS:prefer=shortcutname where shortcutname is the proper name of the shortcut that is copied from the Template directory.
  4. Configure your customer devices to connect to the published desktop.
    1. When users connect to the published desktop, Group Policy Preferences volition create shortcuts to local applications.
    2. Receiver volition auto-launch and hopefully auto-login.
    3. If Receiver Cocky-Service Fashion is disabled, all published applications should automatically appear in the Commencement Carte du jour and Desktop.
    4. If Receiver Self-Service Style is enabled and then simply applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published awarding clarification will be displayed. Users can open the systray icon to subscribe to more than applications.
    5. For published applications with KEYWORDS:adopt=shortcutname, Receiver should re-create icons from the template directory to the Kickoff Menu and/or Desktop. Meet below for considerations.
    6. Users can copy icons from the Start Menu to the desktop. Make certain the user Copies the icon and doesn't Moveit.
    7. Users can and then launch applications directly from the Outset Bill of fare, 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 withKEYWORDS:prefer then the local shortcut will override the published application icon.
    9. If the awarding is installed locally on the VDA and so the local application shortcut should launch speedily. If the awarding is on a different delivery group and then a 2d (double-hop) Citrix HDX/ICA connection volition be established.
    10. If the user deletes Receiver shortcuts from the Offset Menu, you lot can become them back past going to the systray icon and refreshing the applications. Or sometimes you have to reset Receiver.

Notes regarding Prefer Template Directory

  • Prefer Template Directory tin indicate toC:\ProgramData\Microsoft\Windows\Start Menu, which is the All Users Kickoff 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 y'all need these control line parameters, add them to the shortcut in the Prefer Template Directory.
  • If y'all have multiple published apps pointing to the same prefer local shortcut, and so only i copy will be made, and information technology volition have the proper name of only one of the published apps. To workaround this, in the Prefer Template Directory, create split shortcuts for each published app, and adjust the published app prefer keyword appropriately.
  • Jan Hendrik Meier Automatic Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp vii.ten environment has a script that can create shortcuts based on the published apps withprefer keyword. These shortcuts tin can then exist copied to your Adopt Template Directory.

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

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

When SSP builds a shortcut, it builds it to a small stub awarding in a file %appdata%\Citrix\SelfService\app-proper noun-with-spaces-removed.exe for each resource. These files allow SSP to create a faux 'install' tape for Add together/Remove Software. Running these .exe files causes the application to launch. Annotation: Workspace app and Receiver 4.3.100 and newer don't create stubs by default. To enable, fix HKLM\Software\Wow6432Node\Citrix\Dazzle\AlwaysUseStubs (REG_SZ) = truthful.

If you want to bulldoze 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-proper name.app-friendly-proper noun. In these keys y'all'll notice 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 instance. You tin re-create and reuse these parameters without interpretation.

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

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

Citrix Workspace app and Receiver come up with a .dll file that implements the Citrix Common Connection Manager SDK. You can use the CCM SDK to practise the following:

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

Citrix was kind plenty to develop a PowerShell module that calls functions from the .dll. Go 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. Encounter 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. Information technology 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 resources.
  6. Logging off the StoreFront site.

David Ott StoreFront App/Desktop Launch Testing Script uses Cyberspace Explorer to login to StoreFront and launch a resource. Sends email with the upshot. Uses wficalib.dll to become session data.

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. In that location is no need to install annihilation separately. The feature is based on Browser Content Redirection so don't exclude that feature when installing the VDA.

Outgoing screensharing is non supported.

Encounter Citrix Docs Optimization for Microsoft Teams.

Skype for Business organization

Citrix has a HDX RealTime Optimization Pack for Workspace app that enables offloading of Skype for Business concern media protocols to the client device. Here are the available versions:

  • Version ii.9 is a Long Term Service Release (LTSR). See HDX RealTime Optimization Pack 2.ix LTSR at Citrix Docs.
  • Version 2.4.3000 (Cumulative Update 3) is a Long Term Service Release (LTSR). More than details at CTX200466 Lifecycle Information for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the 2.3 release tin can be found in Citrix Blog Mail The Only Virtualization Solution for Skype Meetings Just Got Even Better!

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, simply versions 2.iii and higher now allow version mixing.

  • Connector 2.9 LTSR
    • Connector 2.4.3000 LTSR
  • Media Engine 2.nine LTSR
    • Media Engine 2.4.3000 LTSR

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

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

  • Microsoft added back up for Location Based Routing (LBR) with the virtualized Skype for Business concern 2016 client (and HDX RTOP ii.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 parcel.
  • It requires setting IsLBRInVDIEnabled on the Skype for Business organisation Server to True: 
    $x = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "truthful" Prepare-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add together=$ten}

When offloading vocalization and video to Workspace app machines, don't forget to configure QoS on the customer machines. See Citrix Blog Mail service Implementing the Citrix HDX RealTime Optimization Pack: Don't Forget Nearly QoS/DSCP.

Citrix CTX222459 RealTime Optimization Pack Adequacy Checker: It will listing out endpoint hardware/software information which volition be used to process audio and video. The tool is independent of RealTime Optimization Pack version and runs whatever 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 Awarding and Desktop Launch) lets yous launch Citrix sessions directly from a Controller without needing StoreFront.

You enter a Controller accost, credentials, so it shows y'all the published resources. You tin can pick a resource, edit backdrop on the other tabs, and so 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 style (/debug switch).

Troubleshooting – Workspace app Logging

There are a couple methods of logging Workspace app for Windows operations. 1 method is CTX141751 Citrix Receiver Diagnostics Tool – For Windows, which creates a CDF trace that tin 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 Primal.

Instead of creating the registry keys manually,  you can apply the post-obit .reg file provided by Wolfgang Thürr:

Windows Registry Editor Version v.00  ;merely for x64 windows os ;import with admin rights ;restart your figurer to activate the logging and tracing settings ;create C:\TEMP for the launch ICA log and SSON logn (no environment variables tin can be used)  ;general Workspace app and Receiver logging ;************************ ;logpath: %USERPROFILE%\Appdata\Local\Citrix\Receiver [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix] "ReceiverVerboseTracingEnabled"=dword:00000001  ;Hallmark Managing director logging ;****************************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\AuthManager [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\AuthManager] "LoggingMode"="verbose" "TracingEnabled"="True" "SDKTracingEnabled"="True"  ;Self Service logging ;******************** ;logpath: %USERPROFILE%\Appdata\Local\Citrix\SelfService [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle] "Tracing"="Truthful" "AuxTracing"="True" "DefaultTracingConfiguration"="global all –detail"  ;salve launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables immune) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Advanced\Modules\Logging] "LogConfigurationAccess"="true" "LogConnectionAuthorisation"="true" "LogEvidence"="true" "LogICAFile"="true" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="true"  ;Receiver E'er On Tracing ;************************** ;generates ETL Files for analyzing with CDFControl meet CTX111961 for details ;can be configured or overruled past GPOs (icaclient.admx) ;path %USERPROFILE%\AppData\Local\Temp\CTXReceiverLogs [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\ICA Customer\AoLog] "EnableTracing"=dword:00000001  ;Single Sign-on Logging ;************************** ;https://support.citrix.com/article/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="true" "LogPath"="C:\\Temp"

Troubleshooting – Indistinguishable Stores

Stores are sometimes duplicated in Workspace app, particularly if yous are running Workspace app inside a VDA. (h/t Dan High)

StoreFront URLs can be defined in several places:

  1. In Studio, go to Configuration > StoreFront and delete all URLs configured here.
  2. Wait in GPOs for Estimator Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts List. Remove any URLs configured hither.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you might meet store addresses that were specified during a command line installation of Workspace app.
  4. When Citrix Workspace app switches betwixt StoreFront servers in multiple datacenters, it's possible for each datacenter to be treated equally a separate Workspace app site. This tin be prevented past doing the post-obit. From Juan Zevallos at Citrix Discussions:
    1. Friction match the Base URL 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 grouping.
    3. Match the Delivery Controller names under "Manage Delivery Controllers" – The XML brokers tin can be different, but the actual name of the Delivery Controller/Subcontract 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:

  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\Last Server\Install\Software\Citrix – Remove the entries for storefront in the following folders.
    1. Under \receiver\ctxaccount delete all entries.
    2. Under \SR\Shop delete the entries.
  3. On the VDA, C:\ProgramData\CitrixCseCache – Delete all files
  4. On the VDA, C:\ProgramData\Citrix\GroupPolicy – Delete all folders and files.
  5. Run gpupdate and logoff.
  6. In the user's registry, HKEY_CURRENT_USER or the profile registry hive. Possible profile reset.
    1. Under Software\Citrix\Dazzle\Sites – Delete all entries.
    2. Nether Software\Citrix\Receiver\ctxaccount – delete all entries.
    3. Under Software\Citrix\SR\Store – delete the entries.
  7. Verify no cached contour folders for user on server.

Why Use A Vpn For Client-to-server Connections Over The Internet?,

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

Posted by: reavesothopel.blogspot.com

0 Response to "Why Use A Vpn For Client-to-server Connections Over The Internet?"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel