Random Posts

Home  ›  Uncategorized

Citrix Receiver 4.9 Download for Mac UPDATED Free

Citrix Receiver 4.9 Download for Mac

Navigation

Workspace app is the new name for Receiver. This post applies to all Workspace app versions, and all Receiver versions 4.0 and newer, versions 1808 and newer (e.k. 2204), and the LTSR versions 2203 and 1912.

💡 = Recently Updated

Alter Log

Workspace app Versions

Workspace app is the new name for Receiver.

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

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

Workspace app 2009 and newer accept 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 version.

In that location are two LTSR (Long Term Service Release) versions of Workspace app: 2203, and 1912 Cumulative Update 7 (aka 19.12.7000). 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. Hither are the important ones:

  • ICA Engine (wfica.exe) – procedure 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, Cocky-service passes the ICA file to the ICA Engine to plant a connection.
  • Unmarried Sign-on (SSON) for ICA (ssonsvr.exe) – captures user credentials and submits them to VDAs afterwards an ICA connection is established
  • Workspace Auto-Update (CitrixReceiverUpdater.exe) – Notifies users of Workspace app updates. The near contempo 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.4.

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

Workspace app Discovery and Beacon Procedure

If you are using Workspace app's congenital-in user interface (instead of a web browser), then Workspace app commencement prompts y'all to perform discovery, which is besides called Add together Business relationship.

The Citrix logo changed in Workspace app 2009 and newer.

The Add together Business relationship wizard changed in Workspace app 2108 and newer. Enter a StoreFront FQDN, a Citrix Gateway FQDN, or Citrix Cloud Workspace FQDN. Only enter the FQDN. At that place'due south no need to enter https or a path.

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

  • If you entered a StoreFront FQDN, then Workspace app will download the Provisioning File straight from the StoreFront server.
  • If you entered a Gateway FQDN, so Gateway will first prompt the user to authenticate. Later on authentication, Gateway will connect to its configured Account Services address, and download the Provisioning File from StoreFront. The Account Services address is configured in the NetScaler Gateway Session Profile on the Published Applications tab.

If your StoreFront server is configured with multiple stores, so the user volition be prompted to select a shop. Unfortunately, in that location's no configuration choice in NetScaler Gateway to force a particular store.

The Provisioning File downloaded from StoreFront is an XML document containing values for several items configured in the StoreFront panel. You can consign the Provisioning File from the StoreFront console past 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'south contents into the user's registry. The values are located under HKCU\Software\Citrix\Dazzle\Sites and HKCU\Software\Citrix\Receiver\SR. If you performed discovery through NetScaler Gateway, find that the internal Base URL is added to the user's registry.

In one case Workspace app is configured, it then performs the following steps:

  1. Attempt to connect to the Internal Beacon.
  2. If the Internal Beacon is reachable, connect straight to the StoreFront Base URL (Accost).
  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 ane Gateway, connect to the Gateway that is marked equally the Default.

Here are some interesting notes on this connection process:

  • The FQDN yous entered during Discovery has absolutely naught to practise with how Workspace app connects to StoreFront or Gateway. The actual connection process is controlled by the contents of the Provisioning File, not the Discovery address.
  • If the Provisioning File has multiple Gateways divers, Workspace app uses whichever Gateway is marked equally Default. Workspace app and Receiver completely ignore whatsoever Gateway FQDN you entered during Discovery. To use a not-default Gateway, the user must manually select the other Gateway in Workspace app's / Receiver's Advanced Preferences.

In StoreFront Console, if any configuration changes are performed that affect the Provisioning File, exercise 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?

Here are some additional 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 characteristic is intended for large 4K monitors.

Uninstall Old Clients

Workspace app and Receiver iv.4 and newer includes Receiver Make clean-Up, and then, in theory, it's not necessary to uninstall one-time clients starting time. For more details, run into Citrix CTX135933Upgrading 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 organization, and then deploy the new Workspace app.

Citrix Blog Mail Cookbook to Upgrade from Receiver three.four for Windows to Receiver 4.2.100 and Citrix Article CTX135933 Upgrading to Citrix Receiver for Windows contains step-by-step process to apply Group Policy to uninstall Receiver Enterprise 3.4 and install/configure Workspace app.

The Receiver Clean-Upwards utility for Receiver 4.iii and older is designed to help with the following scenarios:

  • When errors occur during upgrade from an before version of Receiver, or Online Plug-in
  • When unexpected behavior or performance is experienced afterwards upgrade from an before Receiver or Online Plug-in
  • If Receiver upgrade is not possible due to characteristic incompatibility and/or a clean uninstall is required
  • The Receiver Clean-Up Utility removes components, files, and registry values of Online Plug-in 11.x, 12.x, and Receiver for Windows 3.x, 4.x (Online Plugin-in xiii.ten, 14.x). This includes the Offline Plug-in component if installed.

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

Web log posts from Shaun Ritchie:

Installation and Configuration

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

Links:

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

CitrixWorkspaceApp.exe current release version 2204, LTSR version 2203, or LTSR version 1912 CU7 (aka 19.12.7000) can be installed by only double-clicking it. Notation: LTSR Workspace app does not support Browser Content Redirection. Workspace app 2006 and newer practice not support Windows 7.

Administrator vs not-administrator

  • Not-administrator – If a non-administrator installs Workspace app, then each non-administrator that logs in to the aforementioned workstation will take to reinstall Workspace app.
    • Non-ambassador installations are installed to %USERPROFILE%\AppData\Local\Citrix\ICA Client for each user.
  • Administrator – If CitrixWorkspaceApp.exe orCitrixReceiver. exe is installed using an administrator account. then the Workspace app simply needs to exist installed one time.
    • Administrator installations are installed to C:\Programme Files (x86)\Citrix\ICA Client.
    • Administrator installations of Workspace app 1912 and newer can be manually upgraded by not-administrators by clicking Bank check for Updates. Older versions cannot exist upgraded by non-administrators.
  • Conflicts – If an administrator install of Workspace app is performed on a machine that has non-administrator installs of Workspace app, then the two installations will conflict. Best selection is to uninstall non-admin Workspace app and Receiver before installing admin Workspace app. Otherwise, the user's profile probably has to be reset before Workspace app is functional again.

Motorcar-Update

Workspace app supports auto-update.

Some notes:

To troubleshoot Motorcar-update, come across Citrix CTX226779Troubleshooting Citrix Receiver Updates.

Auto-update is broken in Receiver for Windows 4.11 and older, and Receiver for Mac 12.ix and older. To fix information technology, manually upgrade to the next version (e.g.Workspace app for Mac), or install the Prepare that can be downloaded from the Receiver download page (Source = CTX234657Receiver Updater stops working with "Problem Checking for updates" fault)

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




Workspace app Splash Screen

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

To forbid this splash screen, ready the following registry value: (source = Dennis Span on Twitter)

  • Cardinal = HKEY_CURRENT_USER\SOFTWARE\Citrix\Splashscreen
    • Value (REG_SZ) =SplashscreenShown = ane

Add Account Magician

From Citrix CTX135438How to Suppress the Add Account Window in Citrix Receiver for Windows: After installation, Workspace app will launch and inquire you lot to add together an account. If Workspace app, notice the checkboxDo not evidence this window automatically at logon.

For Workspace app and Receiver 4.four and newer, FTU (Start Fourth dimension Utilize aka Add Account Wizard) will be displayed merely if a store is non configured. If a store is already configured via command line, GPO, or Citrix Studio, then FTU screen volition not be available after installation. Otherwise, FTU tin exist suppressed by doing one of the post-obit:  (Note: Receiver 4.4.1000 and newer has a prepare for preventing the Add Account wizard)

  • Rename CitrixReceiver.exe to CitrixReceiverWeb.exe.
  • RenameCitrixWorkspaceApp.exe toCitrixWorkspaceAppWeb.exe.
  • Install using a control line switch:
    • CitrixWorkspaceApp.exe/ALLOWADDSTORE=North
    • CitrixReceiver.exe/ALLOWADDSTORE=N
  • Set the registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\EnableFTU=dword:00000000 (or EnableX1FTU =dword:0)
  • Disable the EnableFTU policy setting in Receiver.admx .
  • Change Registry values post installation to suppress the Add Account window. Under HKLM\Software\Wow6432Node\Citrix\Dazzle, set AllowAddStore value to N.
  • Set the registry value: HKEY_LOCAL_MACHINE\Software\Citrix\Receiver\ NeverShowConfigurationWizard (REG_SZ) = truthful
  • Also seeSuppressing Add together Account dialog at Citrix Docs.

Discover Hidden Stores

When Receiver is kickoff 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 observe a hidden store (a store that's not advertised), add ?StoreName to the end of the FQDN. CTX214819How to configure Receiver to a Shop that is not advertised.

CitrixWorkspaceApp.exe / CitrixReceiver.exe Command line switches

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

For unattended installation of Workspace app, see CTA Dennis BridgeCitrix Workspace App unattended installation with PowerShell orCitrix Receiver unattended installation with PowerShell.

Installer Command Line Switches are detailed at Configure and install Receiver for Windows using control-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 beneath. 
    CitrixWorkspaceApp.exe /includeSSON  CitrixReceiver.exe /includeSSON
  • /ALLOWADDSTORE=A – by default, only SSL (HTTPS) stores are accepted. To let 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 Store"
    • Workspace App and Receiver four.ten and newer can find the Shop 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=Imitation – disables the Self-Service interface and enables shortcut-just mode: 
    CitrixWorkspaceApp.exe /SELFSERVICEMODE=False  CitrixReceiver.exe /SELFSERVICEMODE=False
  • /AutoUpdateCheck=auto /AutoUpdateStream=LTSR – enables Citrix Workspace Update notifications and sets it to LTSR Branch only. AutoUpdateCheck can besides be set to manual or disabled. AutoUpdateStream can besides be ready to Current. See Configuring Citrix Workspace Updates at Citrix Docs. 
    CitrixWorkspaceApp.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR  CitrixReceiver.exe /AutoUpdateCheck=auto /AutoUpdateStream=LTSR
  • /ENABLEPRELAUNCH=True – enables prelaunch: 
    CitrixWorkspaceApp.exe /ENABLEPRELAUNCH=Truthful  CitrixReceiver.exe /ENABLEPRELAUNCH=Truthful
  • /ALLOW_CLIENTHOSTEDAPPSURL=one – enables Local App Access: 
    CitrixWorkspaceApp.exe /ALLOW_CLIENTHOSTEDAPPSURL=1  CitrixReceiver.exe /ALLOW_CLIENTHOSTEDAPPSURL=1

Registry values

HKLM\Software\Wow6432Node\Citrix\Dazzle on the Workspace app auto. 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'southward / 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 False
  • StartMenuDir (REG_SZ) = name of folder on Start Menu where shortcuts are placed.
  • DesktopDir (REG_SZ) = name of folder on Desktop where shortcuts are placed
  • EnablePreLaunch (REG_SZ) = True – If SSON is enabled and so PreLaunch is already enabled by default.
  • AllowAddStore (REG_SZ) = A – Only if using http (instead of https) to connect to StoreFront.
  • AllowSavePwd (REG_SZ) = A – Only if using http (instead of https) to connect to StoreFront.
  • UserDomainName (REG_SZ) = pre-filled domain name
  • InitialRefreshMinMs (REG_SZ) = i – minimizes the launch delay earlier contacting shop
  • InitialRefreshMaxMs (REG_SZ) = i – minimizes the launch filibuster earlier contacting store
  • RefreshMs (REG_SZ) = 3600000 (1 hour) – interval for Receiver icon refreshes. one hour is the default value.
  • MaxSimultaneousFetches (REG_DWORD) = six  – improves the time of loading icons in Outset Menu
  • MaxSimultaneousSubscribes (REG_DWORD) = 6 – improves the time of loading icons in Outset Carte du jour
  • DontWarnOfRemovedResources (REG_SZ) = True – prevents dialog boxes when resource are removed from the server. (or False as mentioned at Citrix Discussions?)
  • SilentlyUninstallRemovedResources (REG_SZ) = True – prevents dialog boxes when resources are removed from the server
  • PreferTemplateDirectory (REG_SZ) = UNC path or local path containing shortcuts copied by the prefer keyword. Give the shortcuts a short proper name.
  • PnaSSONEnabled (REG_SZ) = True – Enables Unmarried Sign-on for PNAgent (Web Interface).
  • WSCReconnectMode (REG_SZ) = 3 (default) – If this Workspace app is running inside a VDA published desktop, prepare it to 0 .
  • AlwaysUseStubs (REG_SZ) = Truthful. Workspace app and Receiver 4.3.100 and newer don't create .exe stubs past default. Set up this to create .exe stubs. Also see Citrix CTX211893Controlling Shortcut beliefs in Receiver 4.3.100.
  • DontCreateAddRemoveEntry  (REG_SZ) = True – don't create "Delivered by Citrix" entries in Programs and Features
  • DesktopNameFormatString  = format string for shortcut names – For example "{0}_{1}_{two}_{3}". Come across the link for details.
  • SelfServiceFlags  (REG_DWORD) = four – prevents duplicate shortcuts when roaming and Desktop is redirected.
    • SelfServiceFlags = five to stop external SSON from prompting for authentication
  • ReEvaluateNetwork (REG_SZ) = true – for Buoy detection with Unmarried FQDN

To prevent the Win+Grand popup on Windows 10 machines:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GameDVR
    • AllowGameDVR (REG_DWORD) = 0

To permitadding non-HTTPS stores to Workspace app:

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

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

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Customer\Engine\Configuration\Avant-garde\Modules\TCP/IP

To prevent beacon probing from using proxy, set:

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

To enable foreground progress bar, set up:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client
    • ForegroundProgressBar (REG_DWORD) = i

For client-to-server file type redirection, set up:

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

To fixUSB devices that emulate a keyboard, set:

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

To foreclose "USB Hub Ability Exceeded" bulletin, gear up (non needed in 4.ii.100 and newer):

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

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

Group Policy Settings

Copy the Workspace app ADMX template (C:\Program Files (x86)\Citrix\ICA Client\Configuration\receiver.admx) to C:\Windows\PolicyDefinitions (or Sysvol). As well copy receiver.adml to C:\Windows\PolicyDefinitions\en-us (or Sysvol).

Edit a GPO that applies to client machines, become to Computer Configuration | Policies | Administrative Templates | Citrix Components | Citrix Workspace (or Receiver) and configure the post-obit:

  • To enable laissez passer-through authentication: go to | User Hallmark |.
  • To add together a store, go to | StoreFront |
    • StoreFront Accounts List – see the assist text
  • To enable Auto-Update, go to|AutoUpdate| or|Receiver Updates| or|Citrix Workspace Updates|. (the node was renamed in iv.xi and Workspace app)
    • Enable or Disable AutoUpdate or
    • Receiver Updates or
    • Citrix Workspace Updates
  • To enable Local App Access, go to | User Experience |
    • Local App Access Settings
  • To configure the Self-Service interface, go to | SelfService |
    • Gear up Manage SelfServiceMode to Disabled to completely disable the Cocky-Service window. This causes all icons to exist placed on the Start Menu.
    • Enable Manage App Shortcut and configure it as desired.
      • To let the Self-Service window, but forbid it from automatically opening (reside in systray), tickForbid Citrix Workspace (or Receiver) performing a refresh of the awarding listing when opened. Source
    • Enable Control when Workspace (or Receiver) attempts to reconnect to existing sessions. If this is a VDA published desktop, prepare it to Disabled . Otherwise configure it as desired.
    • Set Enable FTU to Disabled  to forestall the Add together Account wizard from displaying.
    • EnableAllow/Prevent users to publish unsafe content if publishing content that's opens a file or file share.

Enable automatic client bulldoze and customer microphone mapping.

  • In a client-side GPO, add the GPO ADM template from http://back up.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 CTX203658Start Carte Icons Set to Default (Bare Document) After Update to Receiver 4.3.100 – Windows 8 and newer

  • Reckoner Configuration | Policies | Authoritative Templates | Windows Components | File Explorer
    • Let the employ of remote paths in file shortcut icons = enabled

Deploy Workspace app using Agile Directory

To deploy Workspace app using Active Directory, configure a GPO with a computer startup script that runs the Workspace app installer executable. Citrix provides sample scripts that tin be downloaded from 1 of the Workspace app download pages (Workspace app current release version 2204, LTSR version 2203, or LTSR version 1912 CU7 (aka 19.12.7000), by expanding Downloads for Admins (Deployment Tools).

Also see CTA Dennis BridgeCitrix Receiver unattended installation with PowerShell.

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

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

"C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -deleteproviderbyname Corporate  "C:\Programme 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, clickingAvant-garde Preferences, and clicking theReset link. You can do this from the control line past running "C:\Plan Files (x86)\Citrix\ICA Client\SelfServicePlugin\CleanUp.exe" -cleanUser -silent. See CTX140149How to Reset Receiver Using the Command Line.


Receiver for Border

The Receiver for Spider 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 PostProviding Full Receiver for Spider web Experience for Microsoft Edge has instructions for enabling the Receiver Launcher for Border. Use your preferred text editor to open web.config for the RfWeb site you would like to configure (typically C:\inetpub\wwwroot\Citrix\StoreWeb\web.config). Locate the line like this: <protocolHandler enabled="true" platforms="(Macintosh|Windows NT).*((Firefox/((5[3-nine]|[6789][0-9])|\d\d\d))|(Chrome/((4[2-nine]|[56789][0-9])|\d\d\d)))(?!.*Edge)". Remove (?!.*Edge) and salvage the file.

But once you do that, you become a new switch apps prompt every fourth dimension you launch an icon from Edge.

To stop theswitch apps pop-upwards, on the client side, edit the registry, go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cyberspace Explorer\ProtocolExecute\receiver (create missing registry keys), create DWORD valueWarnOnOpen, and set it to 0 (naught). You lot tin use Grouping Policy Preferences to deploy this registry value.

Workspace app Grouping Policy ADMX Template

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

  1. From a machine that has Workspace app installed, detect the .admx and .adml files in the C:\Program Files (x86)\Citrix\ICA Client\Configuration.
    • Yous can also download the ADMX files from ane of the Workspace app download pages (Workspace app current release version 2204, LTSR version 2203, or LTSR version 1912 CU7 (aka xix.12.7000), by expanding Downloads for Admins (Deployment Tools).
  2. Copy theCitrixBase.admx andreceiver.admx files. Also copy theen-US binder. In Workspace app, the files are still namedreceiver.admx.
  3. Become to your domain's SYSVOL share and in the Policies folder await for a PolicyDefinitions folder. If 1 exists, paste the .admx file straight 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 can then exist found at ane of the post-obit:
    • Calculator Configuration > Policies > Authoritative Templates > Citrix Components > Citrix Workspace
    • Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver
  5. For example, you tin can disable Customer Experience Improvement Program (CEIP) from here.
  6. Seehttps://www.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 information to 3rd 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 haveUser authentication |Single Sign-on for NetScaler Gateway.
  11. Receiver four.12 adds Network Routing | Deprecated cipher suites to configure deprecated ciphers.

  12. Citrix Workspace Updates, (akaAutoUpdate) can be configured using group policy. MeetConfiguring Citrix Workspace Updates at Citrix Docs.
  13. Workspace app 1912 and newer can be configured to crave in-memory ICA files merely. The setting called Secure ICA file session launch is nether the Client Engine node. See Citrix Docs for details on in-memory ICA files instead of writing ICA files to deejay.
  14. Workspace app has settings to hide Advanced Preferences, enable/disable DPI, and enable/disable H265.
  15. Workspace app 4.8 and newer take SplitDevices GPO setting netherCitrix Workspace | Remoting client devices | Generic USB Remoting. Run intoConfiguring composite USB device redirection at Citrix Docs.

Pass-through Authentication

Citrix web log post – A Comprehensive Guide to Enabling Laissez passer-Through Hallmark with XenDesktop seven.v

  1. Run the command
    Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell control prompt on a Commitment Controller.
  2. Login to the PC as an administrator.
  3. If installing Workspace app, equally an ambassador, during installation, on the Enable Single Sign-on folio, check the box side by side to Enable Single Sign-on. And so finish the installation.

  4. If installing an older version of Receiver:
    1. Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver. exe, and click Copy as path.
    2. Open a command prompt.
    3. Right-click to paste the path in the control prompt and then add together /includeSSON to the terminate of the control. Printing <Enter>.
    4. Click Install when prompted.
  5. To verify that SSON is installed, get to C:\Programme Files (x86)\Citrix\ICA Client and look for the file ssonsvr. exe.
  6. And if y'all open regedit and go to HKLM\System\CurrentControlSet\Control\NetworkProvider\Guild, yous should meet PnSson in the ProviderOrder.
  7. Install the receiver.admx (and .adml) template into PolicyDefinitions if you lot haven't already.
  8. Edit a GPO that is practical to the client PCs where the Workspace app is installed.
  9. Go to Estimator Configuration > Policies > Administrative Templates > Citrix Components > Citrix Workspace.
  10. Aggrandize Citrix Workspace and click User authentication.
  11. On the correct, double-click Local user name and password.
  12. Select Enabled and and so bank check the box next to Allow pass-through authentication for all ICA connections. Click OK.
  13. In Workspace app 1808 and newer, y'all tin can enableSingle Sign-on for NetScaler Gateway.
  14. Ensure that the internal StoreFront FQDN is in the Local Intranet zone in Internet Explorer. Yous can use a GPO to configure this on the client side.
  15. Local Intranet zone should have Automatic logon only in Intranet zone enabled.
  16. Logoff Windows and log back on. In Task Manager y'all should at present run into ssonsvr. exe. This won't appear unless you lot logoff and log back on.
  17. If Workspace app won't connect or is slow to enumerate icons, then yous might have to disable Automatically detect settings in IE.
  18. Right-click the Workspace app icon and click Advanced Preferences.
  19. ClickConfiguration Checker.
  20. Bank check the box adjacent toSSONChecker and clickRun.
  21. The lines with cerise x will bespeak the issue and corrective action.

StoreFront Accounts

You can use 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 y'all oasis't already.
  2. Edit a GPO that applies to endpoint devices that accept Citrix Workspace app installed.
  3. Go to Figurer Configuration > Authoritative 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 Help box. Workspace app lets you enter a Gateway path. Then click OK.
  7. Notation: Gateway paths work in GPO, but might not work when specified in the CitrixWorkspaceApp.exe installation control line.

Published Shortcuts and Reconnect

Citrix CTX200924How 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 DocsConfiguring awarding delivery: At that place are several methods of controlling how Workspace app displays shortcuts on the Start Card and Desktop equally detailed below:

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

Under HKLM\Software\Wow6432Node\Citrix\Dazzle (or HKCU\Software\Wow6432Node\Citrix\Dazzle) are several registry values related to shortcuts. Some of the settings only utilise if SelfServiceMode is gear up to Imitation. Here are some mutual options:

  • SelfServiceMode – set to Simulated then Receiver disables the Cocky-Service interface and automatically places all published shortcuts on the Beginning 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 then information technology's probably best to place them in a folder.
  • StartMenuDir – If at that place is potentially a conflict between local apps and remote apps, and so you should place the Get-go Carte du jour shortcuts in a folder.
  • PreferTemplateDirectory (with KEYWORDS:prefer=shortcutname) – copies the shortcutname from the template directory to the Start Menu and/or Desktop.

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

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

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

Workspace app and Receiver 4.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 it every bit desired.

Prelaunch

Staring with Receiver iv.two, prelaunch is automatically enabled if Workspace app is installed with SSON enabled. Otherwise, gear up registry values to enable prelaunch. Receiver four.ii.100 prevents the prelaunch icon from actualization on the Get-go Menu.

  • HKLM\Software\[Wow6432Node\]Citrix\Dazzle
    • EnablePreLaunch (REG_SZ) = true or fake

Additional customizations tin be configured at:

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

  • Name: Land
    • REG_SZ: 0 = disable, 1 = just-in-time pre-launch, 2 = scheduled pre-launch
  • Name: Schedule
    • REG_SZ: HH:MM|M:T:W:TH:F:Due south:SU where HH and MM are hours and minutes. K:T:W:Th:F:South:SU are the days of the week. For example, to enable scheduled pre-launch on Monday, Wednesday, and Friday at 1:45 p.m., set Schedule as Schedule=xiii:45|i:0:1:0:i:0:0 . The session actually launches between 1:15 p.m. and 1:45 p.chiliad.
  • Proper noun: UserOverride
    • REG_SZ: 0  = HKLM overrides HKCU, 1 = HKCU overrides HKLM

Device Access Behavior (Client Selective Trust)

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

To configure the default behavior, come across the Citrix Knowledgebase article How to Configure Default Device Admission Beliefs of Receiver, XenDesktop and XenApp. Note: in that location is a bug fixed in Receiver 4.2.100 and newer.

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

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

Desktop Lock

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

External links:

Use Studio to configure Workspace app Accounts in Published Desktop

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

  1. In Citrix Studio, on the left, expand the Configuration node, right-click StoreFront and click Add StoreFront.
  2. Enter a descriptive name for the StoreFront server.
  3. Enter the internal https URL of the load counterbalanced StoreFront servers. Add the path to your store (e.g. /Citrix/Store) and then /discovery on the end of the URL. The total 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, change the selection to Automatically, using the StoreFront servers selected beneath, 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 – apply Workspace app to control Shortcuts

If you lot install Workspace app within a published desktop (Workspace app on a VDA), then Workspace app can go icons from StoreFront and put those icons on the user'south published desktop Start Carte and Desktop. This is an culling to using a User Experience Management production to control shortcut placement.

Note: Workspace app tends to be tiresome to create Start Menu shortcuts, so make sure you lot 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 lot have the post-obit minimum versions:

  • Workspace app installed within the VDA
  • VDA vii.17 or newer
  • StoreFront 3.14 or newer

If you meet these minimum version requirements, and so 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.

Practise the post-obit for all versions of Workspace app, VDA, and StoreFront, whether using the Prefer keyword or non:

  1. Make sure Workspace app or Receiver version4.11 or newer is installed on the VDA.
  2. Install the Workspace app ADMX files if you haven't already. For vPrefer, make certain they are the ADMX files from Workspace app.
  3. Enable the Group Policy setting Remove mutual program groups from Start Menu and apply information technology to non-administrators.
    • This removes all Public (aka All Users) Start Card shortcuts. Workspace app will re-add the shortcuts based on user group membership.
  4. On the VDA, configure the following Workspace app Registry keys (or respective settings in thereceiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\WSCReconnectMode="0″ so Workspace app doesn't effort to reconnect to the published desktop you lot're already running.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\SelfServiceMode to False. This turns off the Workspace app Cocky-Service GUI and acts like all icons are subscribed. Otherwise, just subscribed (favorited) icons would exist placed on the Start Menu and Desktop.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\UseCategoryAsStartMenuPath = True. This creates a Offset Menu folder based on the published app'due south 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 = True to place all icons on the desktop.
  6. To control icon placement, configure the following registry values:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\StartMenuDir to place published applications in a sub-folder. Note: Windows Server 2012 and Windows 10 and newer just supports a single level of Start Menu folders, and 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 fix Local user name and password to Enabled. Check the box next to Allow pass-through authentication for all ICA connections.
    2. If y'all're using Gateway internally, and if Workspace app 1808 or newer, then besides enableUnmarried Sign-on for NetScaler Gateway.
    3. In a user-level GPO that applies to the VDA, add the StoreFront FQDN to the Local Intranet zone. Make sure information technology 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 y'all 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 commitment type = Desktop and Applications. Assign users to the commitment group, and the individual published applications (if visibility is limited).
    1. In Citrix Studio, edit each published application, and on the Commitment tab, specify a category. This will become the First Menu 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 be subscribed/favorited. Only subscribed (or Favorite) apps are displayed in the Start Bill of fare and Desktop. Unless yous disable Workspace app's SelfService interface as described earlier.
    3. Another pick is to go to the StoreFront Panel, click Stores on the left, and on the right, click Configure Shop Settings, and click Disable User Subscriptions. This causes all apps to announced on the Start Menu and/or Desktop depending on Workspace app configuration.
  10. Create a grouping 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. Replace the FQDN with your load balanced StoreFront FQDN. As well replace the path to the store with your store path. Make certain there 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 yous want to filter out the desktop icons, and then create a new StoreFront store, and configure the Workspace app on the VDA to connect to the new Store.
    2. In StoreFront Console, click the store for VDAs, and click Configure Store Settings. On the Advanced Settings page, in the Filter resources past type row, choose Citrix.MPS.Desktop.
  11. For vPrefer in Workspace app, VDA seven.17 (or newer), and StoreFront 3.fourteen (or newer), edit a GPO that applies to the VDAs.
    1. Go to Computer Configuration | Policies | Authoritative 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 – not working with 32Bit Apps at Citrix Discussions.
  12. On your Delivery Controller, in PowerShell, run set-brokersite -TrustRequestsSentToTheXmlServicePort $true
    • This is required for Laissez passer-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 will auto-launch and hopefully auto-login.
    2. If Workspace app Self-Service Fashion is disabled, all published applications should automatically appear in the Outset Menu and Desktop.
    3. If Workspace app Cocky-Service Fashion is enabled, 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.
    4. Users can copy icons from the First Card to the desktop. Brand certain the user Copies the icon and doesn't Motilityit.
    5. Users can and so launch applications directly from the Outset 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 car to see if the application 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 then the local application shortcut should launch quickly. If the application is on a different commitment group then a second (double-hop) Citrix HDX/ICA connexion will exist established.
    8. If the user deletes Workspace app shortcuts from the Start Card, you lot can get them back by going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app.

If you are running components older than Receiver 4.11, VDA 7.17, and StoreFront 3.14, then yous'll need to configure theadopt 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 setting Remove common program groups from Kickoff Card and apply it to non-administrators.
    1. For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory grouping 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 following Receiver Registry keys (or corresponding settings in thereceiver.admx GPO template):
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle\PreferTemplateDirectory = a UNC path or local path containing shortcuts to exist copied by the adopt keyword. This can point to C:\ProgramData\Microsoft\Windows\Commencement Menu.
  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 change KEYWORDS:Prefer to KEYWORDS:adopt. Notice the lower case p. It doesn't work with uppercase P.
      • With the prefer keyword, if you publish an application that is also created using Grouping Policy Preferences, the Group Policy Preferences icon will take precedence. This is skillful. Otherwise the Receiver published application icon would result 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 as 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 volition create shortcuts to local applications.
    2. Receiver volition automobile-launch and hopefully car-login.
    3. If Receiver Self-Service Fashion is disabled, all published applications should automatically announced in the Beginning Menu and Desktop.
    4. If Receiver Self-Service Mode is enabled then but applications with KEYWORDS:Auto and/or KEYWORDS:Mandatory in the published awarding description volition be displayed. Users can open the systray icon to subscribe to more applications.
    5. For published applications with KEYWORDS:prefer=shortcutname, Receiver should copy icons from the template directory to the Outset Bill of fare and/or Desktop. See below for considerations.
    6. Users tin copy icons from the Start Menu to the desktop. Make certain the user Copies the icon and doesn't Moveit.
    7. Users tin so launch applications directly from the Start Menu, from the Desktop, or from the Receiver (if Self-Service interface is enabled).
    8. If a local shortcut (e.g. Group Policy Preferences shortcut, or copied from template directory) matches a published application withKEYWORDS:prefer then the local shortcut volition override the published awarding icon.
    9. If the application is installed locally on the VDA then the local application shortcut should launch rapidly. If the awarding is on a different delivery group then a second (double-hop) Citrix HDX/ICA connexion volition be established.
    10. If the user deletes Receiver shortcuts from the Start Carte, y'all can get them back by going to the systray icon and refreshing the applications. Or sometimes you accept to reset Receiver.

Notes regarding Prefer Template Directory

  • Prefer Template Directory can point toC:\ProgramData\Microsoft\Windows\Start Card, which is the All Users Kickoff Menu.
  • The shortcuts copied from the Adopt Template Directory are renamed to match the published app proper name.
  • For prefer local apps, any control line parameters specified in the published app are ignored. If y'all demand these command line parameters, add them to the shortcut in the Adopt Template Directory.
  • If y'all have multiple published apps pointing to the same prefer local shortcut, then only one re-create will be fabricated, and it will have the proper name of but ane of the published apps. To workaround this, in the Prefer Template Directory, create split up shortcuts for each published app, and adjust the published app prefer keyword accordingly.
  • Jan Hendrik Meier Automatic Shortcut generation for local installed applications in a Citrix XenDesktop / XenApp 7.x environs has a script that can create shortcuts based on the published apps withprefer keyword. These shortcuts tin can then be copied to your Prefer Template Directory.

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

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

When SSP builds a shortcut, it builds information technology to a small-scale stub application in a file %appdata%\Citrix\SelfService\app-proper noun-with-spaces-removed.exe for each resource. These files let SSP to create a false 'install' record for Add together/Remove Software. Running these .exe files causes the application to launch. Notation: Workspace app and Receiver 4.three.100 and newer don't create stubs past default. To enable, set HKLM\Software\Wow6432Node\Citrix\Dazzle\AlwaysUseStubs (REG_SZ) = true.

If you desire to drive SSP straight for launch instead of through an .exe stub, await at the keys nether HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall. There will be keys in in that location named subcontract-name@@server-farm-name.app-friendly-name. In these keys you'll detect a LaunchString value that shows the relevant parameters. These parameters are user-contained and can therefore be cloned from a reference user to a general case. You can re-create and reuse these parameters without interpretation.

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

Additional control 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 theCitrix Common Connection Director SDK. You can use the CCM SDK to do the post-obit:

  • 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 theCCMPowershellModule 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. EncounterCreate an ICA File from Storefront using PowerShell or JavaScript for more info.

Stan Czerno – Powershell Script to launch i 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 data.

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

  1. Opening Cyberspace Explorer.
  2. Navigating straight to the Receiver for Spider 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 Net Explorer to login to StoreFront and launch a resource. Sends email with the result. Uses wficalib.dll to get session information.

Microsoft Teams

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

Microsoft Teams optimization/offloading (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. There is no demand to install annihilation separately. The feature is based on Browser Content Redirection and so don't exclude that feature when installing the VDA.

Approachable screensharing is not supported.

Come 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. Here are the available versions:

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

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

For Skype for Business Location Based Routing, yous'll demand the post-obit: (Source = Citrix Derek Thorslund atLocation based routing at Citrix Discussions)

  • Microsoft added back up for Location Based Routing (LBR) with the virtualized Skype for 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 notwithstanding been introduced in the MSI package.
  • It requires setting IsLBRInVDIEnabled on the Skype for Business Server to True: 
    $x = New-CsClientPolicyEntry -Name "IsLBRInVDIEnabled" -Value "truthful" Set-CsClientPolicy -Identity "<ClientPolicyName>" -PolicyEntry @{Add=$10}

When offloading vocalisation and video to Workspace app machines, don't forget to configure QoS on the client machines. Run into Citrix Web log Post Implementing the Citrix HDX RealTime Optimization Pack: Don't Forget About QoS/DSCP.

Citrix CTX222459RealTime Optimization Pack Capability Checker: It volition listing out endpoint hardware/software information which volition be used to process sound and video. The tool is independent of RealTime Optimization Pack version and runs any Windows machine.

Citrix CTX214237LOPper – 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 organization (SfB) and shows relevant information in a UI.

Troubleshooting – Citrix QuickLaunch

Citrix CTX219718 QuickLaunch Tool (Testing Awarding and Desktop Launch) lets y'all launch Citrix sessions straight from a Controller without needing StoreFront.

You enter a Controller address, credentials, and and then information technology shows you the published resources. You can selection a resources, edit properties on the other tabs, and so Connect. This allows you to easily endeavor different connexion backdrop.

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

Troubleshooting – Workspace app Logging

In that location are a couple methods of logging Workspace app for Windows operations. One method is CTX141751Citrix Receiver Diagnostics Tool – For Windows, which creates a CDF trace that tin be parsed by CDFControl.

Some other 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 CTX206102Enable SSON Logging Using Registry Cardinal.

Instead of creating the registry keys manually,  you tin can use the following .reg file provided by Wolfgang Thürr:

Windows Registry Editor Version 5.00  ;simply for x64 windows os ;import with admin rights ;restart your computer to activate the logging and tracing settings ;create C:\TEMP for the launch ICA log and SSON logn (no environment variables tin can be used)  ;full general Workspace app and Receiver logging ;************************ ;logpath: %USERPROFILE%\Appdata\Local\Citrix\Receiver [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix] "ReceiverVerboseTracingEnabled"=dword:00000001  ;Authentication 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"="True" "AuxTracing"="True" "DefaultTracingConfiguration"="global all –detail"  ;salve launch ICA ;*************** ;logpath: C:\TEMP\ica.log (no environemnt variables allowed) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Avant-garde\Modules\Logging] "LogConfigurationAccess"="true" "LogConnectionAuthorisation"="truthful" "LogEvidence"="truthful" "LogICAFile"="true" "LogFile"="C:\\TEMP\\ica.log" "LogStartup"="true"  ;Receiver Ever On Tracing ;************************** ;generates ETL Files for analyzing with CDFControl see CTX111961 for details ;can exist configured or overruled by GPOs (icaclient.admx) ;path %USERPROFILE%\AppData\Local\Temp\CTXReceiverLogs [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\ICA Client\AoLog] "EnableTracing"=dword:00000001  ;Single Sign-on Logging ;************************** ;https://support.citrix.com/article/CTX206102 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\SSON] "DebugEnabled"="true" "LogPath"="C:\\Temp"

Troubleshooting – Duplicate Stores

Stores are sometimes duplicated in Workspace app, especially if you are running Workspace app within a VDA. (h/t Dan High)

StoreFront URLs tin can be defined in several places:

  1. In Studio, go to Configuration > StoreFront and delete all URLs configured here.
  2. Look in GPOs for Reckoner Configuration > Administrative Templates > Policies > Citrix Components > Citrix Workspace > StoreFront >NetScaler Gateway URL/ StoreFront Accounts List. Remove any URLs configured here.
  3. In the client-side registry, at HKLM\Software\Wow6432Node\Citrix\Dazzle\Sites, you lot might see shop addresses that were specified during a command line installation of Workspace app.
  4. When Citrix Workspace app switches betwixt StoreFront servers in multiple datacenters, information technology's possible for each datacenter to be treated as a separate Workspace app site. This can exist prevented past doing the following. From Juan Zevallos at Citrix Discussions:
    1. Match the BaseURL in all datacenters.
    2. Friction match the SRID in all datacenters – The SRID tin can be safely edited in the C: \inetpub\wwwroot\Citrix\Roaming\spider web.config. Make sure to propagate changes to other servers in the group.
    3. Match the Commitment Controller names under "Manage Commitment Controllers" – The XML brokers can be dissimilar, only the actual name of the Delivery Controller/Farm must be identical.

If you are running Workspace app on a VDA, once yous've removed the configured URLs shown above, exercise the following to clean upwards 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\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'due south 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. Nether Software\Citrix\SR\Store – delete the entries.
  7. Verify no cached profile folders for user on server.

Citrix Receiver 4.9 Download for Mac UPDATED Free

Posted by: jaimiegrous1946.blogspot.com

Related Posts

There is no other posts in this category.
Subscribe Our Newsletter