Home  ›  Could Not Log on Please Try Again Citrix Receiver Iphone

Could Not Log on Please Try Again Citrix Receiver Iphone

Written By segunda-feira, 16 de maio de 2022 Add Comment Edit

Navigation

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

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

💡 = Recently Updated

Change Log

  • 2022 Apr 11 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 7 Hotfix 1
  • 2022 Apr 7 – Versions – updated for Workspace app 2203.1 LTSR
  • 2022 April 7 – updated entire commodity for Workspace app 2204.1
  • 2022 Mar 17 – Versions – updated for Workspace app 1912 LTSR Cumulative Update seven
  • 2022 Feb 7 – updated entire article for Workspace app 2202
  • 2021 December 9 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 6
  • 2021 Dec eight – updated entire article for Workspace app 2112.1
  • 2021 Oct iv – updated entire article for Workspace app 2109.1
  • 2021 Sep 29 – updated entire article for Workspace app 2109
  • 2021 Aug 30 – updated entire article 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 sixteen – updated entire article for Workspace app 2106
  • 2021 May 11 – Workspace app 1912 CU4 and Workspace app 2105 and newer set up security vulnerabilities
  • 2021 May 10 – updated entire article for Workspace app 2105
  • 2021 May 10 – Versions – updated for Workspace app 1912 LTSR Cumulative Update 4
  • 2021 Mar 23 – updated entire article for Workspace app 2103.1
  • 2021 Mar 16 – updated unabridged article for Workspace app 2103
  • 2021 Feb 1 – updated entire commodity for Workspace app 2102
  • 2021 January twenty – Versions – updated for Workspace app 1912 LTSR Cumulative Update 3
  • 2020 December 18 – updated entire article for Workspace app 2012.i
  • 2020 Dec 8 – updated entire article for Workspace app 2012
  • 2020 Nov ii – updated entire article for Workspace app 2010
  • 2020 October fifteen – Versions – updated for Workspace app 1912 LTSR Cumulative Update 2
  • 2020 Oct i – updated entire article for Workspace app 2009.6
  • 2020 Sep 24 – updated entire article for Workspace app 2009.5
  • 2020 Sep 15 – updated entire commodity for Workspace app 2009

Workspace app Versions

Workspace app is the new name for Receiver.

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

Workspace app uses a YYMM (year/month) versioning format, of which version 2204,1 (22.4.one) 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 versions (1912 and 2203) and the Electric current Release 2204.1 version.

There are two LTSR (Long Term Service Release) versions of Workspace app: 2203.one, and 1912 Cumulative Update seven (aka 19.12.7000) (or 1912 Cumulative Update vii Hotfix 1). 1912 CU5 and newer contain many Teams optimization enhancements. The LTSR versions of Workspace app do not support Browser Content Redirection (BCR) considering 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) – procedure that uses the ICA protocol to connect to published apps and desktops.
  • Cocky-Service (selfservice.exe) – gets icons from StoreFront and displays them in a Window. When an icon is clicked, Self-service passes the ICA file to the ICA Engine to constitute a connection.
  • Unmarried Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs later on an ICA connexion is established
  • Workspace Automobile-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The near 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 concluding version of Receiver Enterprise is 3.four.

Custom ICA files are no longer supported. All the same, 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 Procedure

If you are using Workspace app's built-in user interface (instead of a web browser), and then Workspace app first prompts yous to perform discovery, which is as well chosen Add together Account.

The Citrix logo changed in Workspace app 2009 and newer.

The Add together Account sorcerer inverse in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Deject Workspace FQDN. But enter the FQDN. There'southward no demand to enter https or a path.

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

  • If you lot entered a StoreFront FQDN, then Workspace app will download the Provisioning File directly from the StoreFront server.
  • If you entered a Gateway FQDN, then Gateway will first prompt the user to cosign. 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 Contour on the Published Applications tab.

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

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

The Provisioning File downloaded from StoreFront is an XML document containing values for several items configured in the StoreFront panel. You tin export the Provisioning File from the StoreFront panel 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 by inserting the file's contents into the user's registry. The values are located nether HKCU\Software\Citrix\Dazzle\Sites and HKCU\Software\Citrix\Receiver\SR. If you lot performed discovery through NetScaler Gateway, find that the internal Base URL is added to the user'southward 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 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, and then stop attempting to connect.
    2. Connect to the Gateway address configured in the Provisioning File. If in that location is more one Gateway, connect to the Gateway that is marked as the Default.

Hither are some interesting notes on this connection process:

  • The FQDN you lot entered during Discovery has admittedly nothing to practice with how Workspace app connects to StoreFront or Gateway. The actual connection process is controlled past the contents of the Provisioning File, not the Discovery accost.
  • 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's Advanced Preferences.

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

Here are some boosted methods of performing Workspace app Discovery:

Virtual Monitors

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

Uninstall Old Clients

Workspace app and Receiver 4.iv and newer includes Receiver Clean-Up, so, in theory, information technology's not necessary to uninstall old clients first. For more than details, meet Citrix CTX135933 Upgrading to Citrix Receiver for Windows.

  • In Workspace app 1908 and older (including Receiver), to run it silently, run CitrixWorkspaceApp.exe /RCU /Silent orCitrixReceiver.exe /RCU /Silent.
  • In Workspace app 1909 and newer, /forceinstall switch is the replacement for /rcu switch.

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

Citrix Blog Post Cookbook to Upgrade from Receiver three.4 for Windows to Receiver iv.2.100 and Citrix Commodity CTX135933 Upgrading to Citrix Receiver for Windows contains step-by-stride process to utilize Group Policy to uninstall Receiver Enterprise 3.four 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 functioning is experienced later upgrade from an earlier Receiver or Online Plug-in
  • If Receiver upgrade is not possible due to feature incompatibility and/or a clean uninstall is required
  • The Receiver Clean-Upward Utility removes components, files, and registry values of Online Plug-in xi.10, 12.10, and Receiver for Windows 3.10, 4.x (Online Plugin-in 13.ten, fourteen.x). This includes the Offline Plug-in component if installed.

Citrix CTX325140: How to Remove Customer Files Remaining on System subsequently Uninstalling Receiver for Windows.

Blog posts from Shaun Ritchie:

  • PowerShell Script to Uninstall all Versions of Citrix Client and Install Citrix Receiver 3.10
  • Full list of Citrix Customer Uninstall Strings

Installation and Configuration

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

Links:

  • Citrix Blog Mail: 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 set security vulnerabilities.

CitrixWorkspaceApp.exe electric current release version 2204.1, LTSR version 2203.1, or LTSR version 1912 CU7 (aka 19.12.7000) (or 1912 CU7 Hotfix 1) tin can be installed by just double-clicking information technology. Note: LTSR Workspace app does not support Browser Content Redirection. Workspace app 2006 and newer do not back up Windows seven.



Ambassador vs non-administrator

  • Non-ambassador – If a non-administrator installs Workspace app, so each non-ambassador that logs in to the same workstation will have to reinstall Workspace app.
    • Non-ambassador installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Customer for each user.
  • Administrator – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator account. so the Workspace app merely needs to be installed in one case.
    • Administrator installations are installed to C:\Programme Files (x86)\Citrix\ICA Client.
    • Ambassador installations of Workspace app 1912 and newer can exist manually upgraded by not-administrators by clicking Cheque 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 not-administrator installs of Workspace app, then the 2 installations volition disharmonize. Best option is to uninstall non-admin Workspace app and Receiver before installing admin Workspace app. Otherwise, the user's profile probably has to exist reset before Workspace app is functional again.
    • Citrix commodity CTX249920 Workspace App for Windows – Your apps are not available at this time – Issue when installing Citrix Receiver in non elevated/per-user install manner describes the HKEY_CURRENT_USER registry keys that must be deleted to set this issue.
    • For a script to clean-upwards the per-user installs, see Marker DePalma at Citrix Receiver Per-User Install Cleanup.

Auto-Update

Workspace app supports machine-update.

Some notes:

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

Motorcar-update is broken in Receiver for Windows 4.eleven and older, and Receiver for Mac 12.nine and older. To fix it, manually upgrade to the next version (e.yard. Workspace app for Mac), or install the Set up that can exist downloaded from the Receiver download page (Source = CTX234657 Receiver Updater stops working with "Problem Checking for updates" mistake)

Auto-update is configured using Workspace app grouping policy under the Citrix Workspace Updates,Receiver Updates or Motorcar-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 Bridge on Twitter)

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

Add Business relationship Magician

From Citrix CTX135438 How to Suppress the Add Business relationship Window in Citrix Receiver for Windows: Afterwards installation, Workspace app volition launch and ask y'all to add together an account. If Workspace app, find the checkboxDo not show this window automatically at logon.

For Workspace app and Receiver four.4 and newer, FTU (Starting time Time Use aka Add Account Wizard) will be displayed just 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 be available later on installation. Otherwise, FTU tin be suppressed by doing ane of the following:  (Note: Receiver 4.4.1000 and newer has a fix for preventing the Add Business relationship wizard)

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

Find Subconscious Stores

When Receiver is start 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'southward non advertised), add ?StoreName to the end of the FQDN. CTX214819 How to configure Receiver to a Shop 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 command line.

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

Installer Control 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;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Store"  CitrixReceiver.exe STORE0="AppStore;https://Citrix.corp.com/Citrix/MyStore/discovery;on;App Shop"
    • Workspace App and Receiver four.10 and newer 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-but mode: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=Fake  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=auto /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets information technology to LTSR Branch only. AutoUpdateCheck tin can also be set to manual or disabled. AutoUpdateStream can too exist set up to Current. See Configuring Citrix Workspace Updates at Citrix Docs. 
    CitrixWorkspaceApp.exe /AutoUpdateCheck=motorcar /AutoUpdateStream=LTSR  CitrixReceiver.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR
  • /ENABLEPRELAUNCH=Truthful – enables prelaunch: 
    CitrixWorkspaceApp.exe /ENABLEPRELAUNCH=True  CitrixReceiver.exe /ENABLEPRELAUNCH=True
  • /ALLOW_CLIENTHOSTEDAPPSURL=ane – enables Local App Admission: 
    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 blazon REG_SZ (cord) 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'southward Self-Service interface.
  • PutShortcutsOnDesktop (REG_SZ) = Truthful – If Self-Service interface is disabled, places all shortcuts on desktop.
  • UseDifferentPathsforStartmenuAndDesktop (REG_SZ) = True
    • UseCategoryAsStartMenuPath (REG_SZ) = Truthful or False
    • UseCategoryAsDesktopPath (REG_SZ) = Truthful or False
  • StartMenuDir (REG_SZ) = name of folder on Showtime Carte du jour 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 – Merely 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 filibuster before contacting store
  • InitialRefreshMaxMs (REG_SZ) = i – minimizes the launch delay before contacting shop
  • RefreshMs (REG_SZ) = 3600000 (1 hr) – interval for Receiver icon refreshes. 1 hour is the default value.
    • RefreshMs (REG_SZ) = 18000000 – Citrix CTX213755 Citrix Receiver Shows Authentication Window Periodically When Receiver is Not Opened
  • MaxSimultaneousFetches (REG_DWORD) = 6  – improves the fourth dimension of loading icons in Outset Card
  • MaxSimultaneousSubscribes (REG_DWORD) = half-dozen – improves the fourth dimension of loading icons in Commencement Menu
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server. (or Simulated)
  • SilentlyUninstallRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server
  • PreferTemplateDirectory (REG_SZ) = UNC path or local path containing shortcuts copied by the adopt keyword. Give the shortcuts a brusque name.
  • PnaSSONEnabled (REG_SZ) = True – Enables Unmarried Sign-on for PNAgent (Web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Workspace app is running within a VDA published desktop, set it to 0.
    • If yous're having trouble getting sessions to reconnect, see Receiver four.3 Desktop will non auto-reconnect when logging into a car at Citrix Discussions
  • AlwaysUseStubs (REG_SZ) = True. Workspace app and Receiver 4.3.100 and newer don't create .exe stubs past default. Set up this to create .exe stubs. Also encounter 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 case "{0}_{1}_{2}_{3}". Run 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 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 permit calculation non-HTTPS stores to Workspace app:

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

To increase ICA bandwidth consumption over high latency links, gear up:

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

To forestall beacon probing from using proxy, set up:

  • 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) = one

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

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Avant-garde\Modules\ClientDrive
    • NativeDriveMapping="TRUE"

To fix USB devices that emulate a keyboard, set:

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

To forbid "USB Hub Ability Exceeded" message, gear up (non needed in four.2.100 and newer):

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

To override the devices that are mapped using optimized channels instead of generic USB, come across 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 copy receiver.adml to C:\Windows\PolicyDefinitions\en-united states (or Sysvol).

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

  • To enable laissez passer-through authentication: go to | User Authentication |.
    • Local Username and Password – Check the top two boxes.
    • Too add the StoreFront FQDN to the Local Intranet zone in Internet Explorer.
    • Single Sign-on for NetScaler Gateway (Workspace app 1808 and newer)
  • To add a shop, go to | StoreFront |
    • StoreFront Accounts List – see the aid text
  • To enable Auto-Update, get 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 Admission, go to | User Experience |
    • Local App Access Settings
  • To configure the Self-Service interface, go to | SelfService |
    • Fix 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 permit the Self-Service window, but prevent it from automatically opening (reside in systray), tickForestall Citrix Workspace (or Receiver) performing a refresh of the awarding 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.
    • Gear up Enable FTU to Disabled  to forestall the Add Account wizard from displaying.
    • EnableAllow/Prevent users to publish unsafe content if publishing content that's opens a file or file share.

Enable automated client bulldoze 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. Run into 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 Commencement Carte du jour Icons Ready to Default (Bare Document) After Update to Receiver 4.3.100 – Windows 8 and newer

  • Estimator Configuration | Policies | Authoritative 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 Agile 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 current release version 2204.one, LTSR version 2203.1, or LTSR version 1912 CU7 (aka xix.12.7000), by expanding Downloads for Admins (Deployment Tools).

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

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

Yous can change Workspace app's / Receiver's configured Store/Business relationship with a couple command lines:

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

Information technology is sometimes necessary toReset Citrix Workspace orReset Receiver by right-clicking the Workspace app systray icon, clickingAdvanced Preferences, and clicking theReset link. You can exercise this from the command line past 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 theOpen push button after the .ica file is downloaded.

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

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

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

Workspace app Group Policy ADMX Template

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

  1. From a machine that has Workspace app installed, notice the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • Yous tin as well download the ADMX files from i of the Workspace app download pages (Workspace app 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'due south SYSVOL share and in the Policies folder look for a PolicyDefinitions folder. If i exists, paste the .admx file directly into the PolicyDefinitions folder. If this folder doesn't exist in SYSVOL, instead copy the .admx file to C:\Windows\PolicyDefinitions. Overwrite whatsoever existing Receiver ADMX files.
  4. The GPO settings tin can then be found at one of the following:
    • Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace
    • Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For example, you can disable Client Experience Improvement Program (CEIP) from here.
  6. Run into https://world wide web.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip for boosted places where CEIP is enabled.
  7. Workspace app 1905 and newer has a setting toDisable sending data to 3rd political party (due east.g. Google Analytics).
  8. Workspace app 1905 and newer let you disable embedded browser caching.
  9. Workspace app 1905 and newer have NetScaler LAN Proxy netherNetwork routing > Proxy.
  10. Workspace app 1808 and newer haveUser authentication |Unmarried Sign-on for NetScaler Gateway.
  11. Receiver 4.12 adds Network Routing | Deprecated cipher suites to configure deprecated ciphers.

  12. Citrix Workspace Updates, (akaAutoUpdate) can be 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 called Secure ICA file session launch is under the Client Engine node. Come across Citrix Docs for details on in-memory 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 4.viii and newer accept SplitDevices GPO setting underCitrix Workspace | Remoting customer 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 vii.v

  1. Run the control
    Ready-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on a Commitment Controller.
    • In XenApp 6.five, this is a Citrix Policy > Calculator > Trust XML Requests.
  2. Login to the PC as an administrator.
  3. If installing Workspace app, every bit an administrator, during installation, on the Enable Single Sign-on page, check the box adjacent to Enable Unmarried Sign-on. Then stop the installation.

  4. If installing an older version of Receiver:
    1. Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver. exe, and click Re-create equally path.
    2. Open a command prompt.
    3. Correct-click to paste the path in the command prompt and and then add /includeSSON to the end of the command. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, go to C:\Program Files (x86)\Citrix\ICA Client and look for the file ssonsvr. exe.
  6. And if you open regedit and go to HKLM\Arrangement\CurrentControlSet\Command\NetworkProvider\Gild, you should see PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if you haven't already.
  8. Edit a GPO that is practical to the client PCs where the Workspace app is installed.
  9. Become to Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace.
  10. Aggrandize Citrix Workspace and click User authentication.
  11. On the right, double-click Local user name and password.
  12. Select Enabled and and so check the box next to Allow pass-through authentication for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, yous 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 accept Automated logon only in Intranet zone enabled.
  16. Logoff Windows and log back on. In Chore Manager you should now meet ssonsvr. exe. This won't appear unless yous logoff and log back on.
  17. If Workspace app won't connect or is slow to enumerate icons, and then you might have to disable Automatically detect settings in IE.
  18. Right-click the Workspace app icon and click Avant-garde Preferences.
  19. ClickConfiguration Checker.
  20. Check the box next toSSONChecker and clickRun.
  21. The lines with red x will signal the event and cosmetic activity.

StoreFront Accounts

You tin can use a client-side GPO to add a store (Account) to Workspace app Self-Service.

  1. Install the receiver.admx (and .adml) template into PolicyDefinitions if you haven't already.
  2. Edit a GPO that applies to endpoint devices that have Citrix Workspace app installed.
  3. Get to Computer Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront.
  4. On the right, double-click NetScaler Gateway URL/StoreFront Accounts List.
  5. Select Enabled, and then clickShow.
  6. Enter a store path based on the example shown in the Assist box. Workspace app lets you enter a Gateway path. Then click OK.
  7. Note: Gateway paths work in GPO, just might non work when specified in the CitrixWorkspaceApp.exe installation control 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 clickShortcuts and Reconnect, orSettings Option.


From Citrix Docs Configuring application delivery: There are several methods of controlling how Workspace app displays shortcuts on the Beginning Carte du jour and Desktop as detailed beneath:

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

Under HKLM\Software\Wow6432Node\Citrix\Dazzle (or HKCU\Software\Wow6432Node\Citrix\Dazzle) are several registry values related to shortcuts. Some of the settings simply utilize if SelfServiceMode is set to False. Hither are some common options:

  • SelfServiceMode – prepare to Fake so Receiver disables the Self-Service interface and automatically places all published shortcuts on the Get-go Menu and/or Desktop. More details in Configuring awarding delivery at Citrix Docs.
  • PutShortcutsOnDesktop– set toTrue to place every app on the desktop
  • DesktopDir – Workspace app places every shortcut on the desktop and so it's probably best to place them in a binder.
  • StartMenuDir – If at that place is potentially a conflict betwixt local apps and remote apps, and so 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 > Authoritative Templates > Citrix Components > Citrix Workspace (or Receiver) is a node called SelfService.

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

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

Workspace app and Receiver 4.ii.100 and newer have the ability to configure (or disable) Workspace Control using grouping policy. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure it as desired.

Prelaunch

Staring with Receiver 4.two, prelaunch is automatically enabled if Workspace app is installed with SSON enabled. Otherwise, prepare registry values to enable prelaunch. Receiver 4.2.100 prevents the prelaunch icon from appearing on the Kickoff Menu.

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

Additional customizations can be configured at:

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

  • Name: Land
    • REG_SZ: 0 = disable, one = just-in-time pre-launch, ii = scheduled pre-launch
  • Proper noun: Schedule
    • REG_SZ: HH:MM|Chiliad:T:West:Th:F:S:SU where HH and MM are hours and minutes. M:T:W:TH:F:S:SU are the days of the calendar week. For example, to enable scheduled pre-launch on Monday, Wednesday, and Friday at 1:45 p.grand., set Schedule as Schedule=13:45|1:0:1:0:1:0:0 . The session actually launches betwixt ane:fifteen p.m. and 1:45 p.chiliad.
  • 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 lot might run into the following:

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

  1. Download the ADMX file from http://support.citrix.com/article/CTX133565.
  2. Copy 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. Go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) |Citrix Client Selective Trust (x64).
  6. Enable the setting Create Client Selective Trust Keys.

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

Desktop Lock

As an alternative to Workspace app Desktop Lock, run into Transformer in Citrix Workspace Environs 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

Utilize 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 Outset Menu and Desktop. Use group policy to hibernate the common program groups and then apply Workspace app to place published applications back on the Start Card and Desktop based on user'south group membership and subscription preference.

  1. In Citrix Studio, on the left, expand the Configuration node, right-click StoreFront and click Add together StoreFront.
  2. Enter a descriptive proper name for the StoreFront server.
  3. Enter the internal https URL of the load balanced StoreFront servers. Add the path to your store (due east.grand. /Citrix/Store) and and so /discovery on the end of the URL. The total URL would exist similar to https://citrix.corp.com/Citrix/Store/discovery. Click OK.
  4. Edit a Delivery Group that has a published desktop and Citrix Workspace app installed.
  5. On the StoreFront page, change the 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 volition be automatically configured with this URL.

Published Desktop – employ Workspace app to control Shortcuts

If you lot 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'due south published desktop Start Bill of fare and Desktop. This is an alternative to using a User Experience Management product to command shortcut placement.

Annotation: Workspace app tends to be slow to create Start Carte shortcuts, and then make sure yous 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 take 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.

  • If you don't meet these minimum version requirements, so you'll need to use the older Prefer Keyword method of handling Workspace app shortcuts as detailed after.
  • For a detailed explanation of vPrefer, meet Citrix Blog Post VPrefer: Session Sharing Between a Published Desktop and a Published Awarding Made Easy

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

  1. Brand sure Workspace app or Receiver version 4.11 or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if yous haven't already. For vPrefer, brand sure they are the ADMX files from Workspace app.
  3. Enable the Grouping Policy settingRemove common program groups from Get-go Menu and apply information technology to non-administrators.
    • This removes all Public (aka All Users) Start Bill of fare shortcuts. Workspace app will re-add 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″ 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 Imitation. This turns off the Workspace app Self-Service GUI and acts like all icons are subscribed. Otherwise, only subscribed (favorited) icons would exist placed on the Start Menu and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = Truthful. This creates a Starting time Menu folder based on the published app's configured Category.
  5. Configure each desired published app to Add shortcut to user's 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 place published applications in a sub-folder. Annotation: Windows Server 2012 and Windows x and newer only supports a single level of Get-go Card 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-binder 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. Check the box next to Allow laissez passer-through authentication for all ICA connections.
    2. If you're using Gateway internally, and if Workspace app 1808 or newer, then too enableUnmarried Sign-on for NetScaler Gateway.
    3. In a user-level GPO that applies to the VDA, add together the StoreFront FQDN to the Local Intranet zone. Make certain it is not in the Trusted Sites zone, or enable Automated logon with current user proper name and password for the Trusted Sites zone.
    4. Brand 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 not excluded from roaming.
  9. In Citrix Studio, configure a Delivery Grouping 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 volition become the First 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 awarding description. This forces the applications to exist subscribed/favorited. Merely subscribed (or Favorite) apps are displayed in the Start Menu and Desktop. Unless you disable Workspace app's SelfService interface as described before.
    3. Some other pick 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 Kickoff Menu and/or Desktop depending on Workspace app configuration.
  10. Create a group policy that applies to VDAs, and configure the group policy to define the Store URL for Workspace app similar to https://citrix.corp.com/Citrix/Store/discovery. Supervene upon the FQDN with your load balanced StoreFront FQDN. Likewise supplant the path to the store with your store path. Make sure there is /discovery on the terminate. By default, Workspace app and Receiver only supporthttps.
    1. Your StoreFront store probably delivers both application and desktop icons. If you desire 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 Panel, click the store for VDAs, and click Configure Store Settings. On the Avant-garde Settings page, in the Filter resources by type row, cull Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA 7.17 (or newer), and StoreFront iii.fourteen (or newer), edit a GPO that applies to the VDAs.
    1. Become to Computer Configuration | Policies | Authoritative Templates | Citrix Components | Citrix Workspace (or Receiver) | SelfService.
    2. Edit the settingvPrefer. This setting is but in Workspace app ADMX templates from Workspace app.
    3. Gear up it toAllow all apps. Source = 7.17 vPrefer – not working with 32Bit Apps at Citrix Discussions.
  12. On your Commitment Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $truthful
    • This is required for Pass-through Authentication from Workspace app.
  13. Configure your customer devices to connect to the published desktop.
    1. When users connect to the published desktop, Workspace app will motorcar-launch and hopefully auto-login.
    2. If Workspace app Self-Service Mode is disabled, all published applications should automatically announced in the Start Card and Desktop.
    3. If Workspace app Self-Service Mode is enabled, and then but applications with KEYWORDS:Automobile and/or KEYWORDS:Mandatory in the published application description will be displayed. Users can open up the systray icon to subscribe to more applications.
    4. Users can re-create icons from the Offset Carte to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    5. Users can and so launch applications directly from the Start Carte, from the Desktop, or from the Workspace app (if the Self-Service interface is enabled).
    6. If Workspace app 4.xi (or newer), VDA 7.17 (or newer), and StoreFront iii.fourteen (or newer), thenvPrefer 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 tin can exist 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 so the local application shortcut should launch apace. If the awarding is on a different delivery group and then a second (double-hop) Citrix HDX/ICA connexion will exist established.
    8. If the user deletes Workspace app shortcuts from the Offset Carte, you can get them back by going to the systray icon and refreshing the applications. Or sometimes y'all have to reset Workspace app.

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

  1. Enable the Group Policy settingRemove common program groups from Get-go Menu and apply information technology to not-administrators.
    1. For applications that are installed on the aforementioned VDA that is publishing the desktop, configure Grouping Policy Preferences to recreate the application shortcuts based on Active Directory group membership. Applications on other delivery groups are handled by Receiver.
    2. Or employ the prefer keyword to re-create 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 past the prefer keyword. This can betoken to C:\ProgramData\Microsoft\Windows\Beginning Carte.
  3. In Citrix Studio, configure a Commitment 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 alter KEYWORDS:Prefer to KEYWORDS:adopt. Discover the lower example p. It doesn't work with majuscule P.
      • With the prefer keyword, if you publish an application that is besides created using Group Policy Preferences, the Grouping Policy Preferences icon will have precedence. This is good. Otherwise the Receiver published application icon would outcome in a new Citrix double-hop session.
      • See Ralph Jansen Citrix Receiver iv.1 Prefer keyword examples
    2. If using the prefer keyword with the PreferTemplateDirectory, enter it equally KEYWORDS:prefer=shortcutname where shortcutname is the name of the shortcut that is copied from the Template directory.
  4. Configure your client devices to connect to the published desktop.
    1. When users connect to the published desktop, Grouping Policy Preferences will create shortcuts to local applications.
    2. Receiver will auto-launch and hopefully auto-login.
    3. If Receiver Cocky-Service Mode is disabled, all published applications should automatically appear in the Start Menu and Desktop.
    4. If Receiver Self-Service Mode is enabled and so simply applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published application description will be displayed. Users can open up the systray icon to subscribe to more applications.
    5. For published applications with KEYWORDS:adopt=shortcutname, Receiver should copy icons from the template directory to the Start Card and/or Desktop. See beneath for considerations.
    6. Users can re-create icons from the Start Menu to the desktop. Make sure the user Copies the icon and doesn't Moveit.
    7. Users can and then launch applications directly from the Start Carte du jour, from the Desktop, or from the Receiver (if Self-Service interface is enabled).
    8. If a local shortcut (e.m. 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 application is installed locally on the VDA so the local awarding shortcut should launch quickly. If the awarding is on a different commitment grouping then a second (double-hop) Citrix HDX/ICA connectedness will be established.
    10. If the user deletes Receiver shortcuts from the Starting time Menu, you lot 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 tin can signal toC:\ProgramData\Microsoft\Windows\Starting time Menu, which is the All Users Outset Carte du jour.
  • The shortcuts copied from the Prefer Template Directory are renamed to match the published app name.
  • For prefer local apps, any control line parameters specified in the published app are ignored. If yous need these control line parameters, add together them to the shortcut in the Adopt Template Directory.
  • If you accept multiple published apps pointing to the same prefer local shortcut, then only one copy volition exist made, and it will have the name of simply ane 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 accordingly.
  • Jan Hendrik Meier Automatic Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp vii.x environs has a script that can create shortcuts based on the published apps withprefer keyword. These shortcuts tin then be 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 Cocky-Service (SSP) activities are driven by user interaction. However, SSP exposes sufficient data for its activities to be scripted.

When SSP builds a shortcut, it builds it to a pocket-sized stub application in a file %appdata%\Citrix\SelfService\app-proper 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) = truthful.

If y'all want to bulldoze SSP directly for launch instead of through an .exe stub, wait 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 yous'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 tin 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 get out.

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 Mutual Connexion Managing director SDK. Y'all can apply the CCM SDK to do 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. 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. Run into Create an ICA File from Storefront using PowerShell or JavaScript for more than info.

Stan Czerno – Powershell Script to launch 1 or more Published Applications from Citrix Storefront two.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 past:

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

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

Microsoft Teams

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

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

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

The redirection components are built into VDA and Workspace app. At that place 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 non supported.

Run across 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. Hither are the available versions:

  • Version 2.9 is a Long Term Service Release (LTSR). Run into HDX RealTime Optimization Pack 2.nine LTSR at Citrix Docs.
  • Version 2.4.3000 (Cumulative Update iii) is a Long Term Service Release (LTSR). More than details at CTX200466 Lifecycle Data for Citrix XenApp/XenDesktop HDX RealTime Optimization Pack
  • Details on the 2.iii release can be found in Citrix Blog Post The Only Virtualization Solution for Skype Meetings Just Got Even Amend!

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 exist the same version, only versions 2.three and higher now permit version mixing.

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

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

For Skype for Concern Location Based Routing, you'll need the post-obit: (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 organization 2016 client (and HDX RTOP ii.one and to a higher place) in the Click-to-Run (C2R) download quite a long fourth dimension ago, simply it hasn't still been introduced in the MSI bundle.
  • It requires setting IsLBRInVDIEnabled on the Skype for Business Server to True: 
    $x = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "true" Set-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add=$x}

When offloading voice and video to Workspace app machines, don't forget to configure QoS on the customer machines. Come across Citrix Weblog Post Implementing the Citrix HDX RealTime Optimization Pack: Don't Forget Nearly QoS/DSCP.

Citrix CTX222459 RealTime Optimization Pack Capability Checker: It will list out endpoint hardware/software information which will be used to process sound 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 phone 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 direct from a Controller without needing StoreFront.

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

If you run into problems launching a session, use Sysinternals DebugView while running CQL in Debug way (/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 exist 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 utilise the following .reg file provided by Wolfgang Thürr:

Windows Registry Editor Version 5.00  ;only for x64 windows bone ;import with admin rights ;restart your reckoner 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  ;Hallmark 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"="Truthful" "DefaultTracingConfiguration"="global all –detail"  ;salvage launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables allowed) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Avant-garde\Modules\Logging] "LogConfigurationAccess"="truthful" "LogConnectionAuthorisation"="true" "LogEvidence"="true" "LogICAFile"="truthful" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="truthful"  ;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 Customer\AoLog] "EnableTracing"=dword:00000001  ;Unmarried Sign-on Logging ;************************** ;https://support.citrix.com/commodity/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="truthful" "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 Loftier)

StoreFront URLs tin can exist defined in several places:

  1. In Studio, go to Configuration > StoreFront and delete all URLs configured here.
  2. Expect in GPOs for Computer 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 see shop addresses that were specified during a command line installation of Workspace app.
  4. When Citrix Workspace app switches between StoreFront servers in multiple datacenters, it's possible for each datacenter to exist treated as a split up Workspace app site. This can be prevented by doing the post-obit. From Juan Zevallos at Citrix Discussions:
    1. 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 group.
    3. Lucifer the Delivery Controller names under "Manage Delivery Controllers" – The XML brokers tin can be dissimilar, but the bodily 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 to a higher place, do the post-obit to clean up the VDAs:

  1. On the VDA, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix – Delete the number folders representing policy entries.
  2. On session host VDAs, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Citrix – Remove the entries for storefront in the post-obit folders.
    1. Under \receiver\ctxaccount delete all entries.
    2. Under \SR\Store delete the entries.
  3. On the VDA, C:\ProgramData\CitrixCseCache – Delete all files
  4. On the VDA, C:\ProgramData\Citrix\GroupPolicy – Delete all folders and files.
  5. Run gpupdate and logoff.
  6. In the user's registry, HKEY_CURRENT_USER or the profile registry hive. Possible contour reset.
    1. Under Software\Citrix\Dazzle\Sites – Delete all entries.
    2. Under Software\Citrix\Receiver\ctxaccount – delete all entries.
    3. Under Software\Citrix\SR\Shop – delete the entries.
  7. Verify no cached profile folders for user on server.

pasillassoming.blogspot.com

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

0 Response to "Could Not Log on Please Try Again Citrix Receiver Iphone"

Postar um comentário

Assinar: Postar comentários (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel