Workspace 1911



The Refinitiv Workspace Advanced IT-Managed Installation Guide is intended for IT specialists that are responsible for the installation of Workspace and Messenger standalone. Software releases and obsolescence You should be familiar with the Workspace Obsolescence Policy, which can be found in the Workspace section of MyRefinitiv. Workspace app for Windows Current Release Subscribe to RSS notifications of new downloads. Workspace app for Windows. Citrix Workspace app 2103.1 for Windows. Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software deployments. Run the following tool: CTX137494 - Receiver Clean-Up Utility After uninstalling Receiver and restarting the system, the following steps guide to remove any unnecessary files manually that might have been left on the client system.

downloadWhy can't I download this file?EDT MTU Discovery. If using these versions (or newer) of the VDA and Workspace app for Windows, this workaround is not required. Please review the documentation for more details.
This workaround is needed if using VDA 1909 (or older), Workspace app for Windows 1910 (or older), or Workspace app for Mac, Linux, or iOS.
The workaround involves lowering the EDT MTU to a value that will not cause fragmentation.
This MTU value needs to be determined for each network. A tool like mturoute.exe can help determine the appropriate MTU for a network.
When using Azure:
  • If ICA traffic has to traverse an Azure Gateway, the EDT MTU must be set to 1350 since Azure limits the MTU on the Azure Gateway to 1400.
  • If using an Azure-hosted Citrix Gateway, the EDT MTU must be set to a value lower than 1500 (e.g. 1480).

Steps

Citrix Workspace 1911

1. Define the EDT MTU and Output Buffers Length in the ICA file template in the Storefront server:
Open the default.ica file for editing (by default it is located in C:inetpubwwwrootCitrix<StoreName>App_Datadefault.ica)
Add the following options under the [Application] section:
OutBufLength=1480
udtMSS=1480 (add this line if using Receiver for Windows 4.9 - 4.9 CU3, Workspace app for Linux 1808 - 1903, Workspace app 1808+ for Mac or iOS)
edtMSS=1480 (add this line if using Receiver for Windows 4.9 CU4+, Workspace app for Windows 1808+, Workspace app for Linux 1906+)
Notes:
If unsure whether to use 'udtMSS' or 'edtMSS', add both. The client will use the appropriate setting and ignore the one that does not apply.
edtMSS and OutBufLength should be set to the same value.
1480 was used as an example. Replace 1480 with the value that's appropriate for your network.
The client and server will agree on sizes during the connection negotiation.

Workspace2. Enable Receiver/Workspace app to read the custom EDT MTU and Output Buffers Length values.
NOTE: If using Receiver for Windows 4.9 CU4+, Workspace app for Windows 1808+, or Workspace app for Mac 1809+, the configuration described below is NOT required, so step 2 can be omitted.
Create UDPStackParameters registry key, which is missing by default:
HKCUSOFTWARECitrixICA ClientEngineConfigurationAdvancedModulesUDPUDPStackParameters
There is a legacy issue in these Receivers for Windows where OutbufLength, when passed in an ICA file, is ignored.
Even if the registry value is modified to '*', meaning accept everything from the ICA file, the ICA file setting is still ignored.
For this to work, in addition to creating the 'UDPStackParameters' key as mentioned above, it is also necessary to modify the OutbufLength value in the registry and set it to the desired value determined above (1480 in the example):
  • 64-bit Windows
Workspace 1911
HKLMSOFTWAREWow6432NodeCitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength
  • 32-bit Windows
HKLMSOFTWARE CitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength
Modify the appropriate App Property to allow Receiver to read the customer parameters in the ICA file. This property is set to NO by default.
To do this, open Terminal and run:
defaults write com.citrix.receiver.nomas UDPStackParameters -bool YES
Toggle the the 'Read EDT stack parameter' option, which is disabled by default:
Settings > Advanced > Adaptive Transport Settings > Read EDT stack parameter
Enable the 'EDT Stack Parameters' option, which is disabled by default:
Settings > Advanced > EDT Stack Parameters

Problem Cause

Citrix Workspace 1911 Free Download

MTU alteration not accounted dynamically by EDT, and IP Fragmentation not handled properly by network appliances.

Citrix Workspace 1911 Known Issues

Additional Resources

downloadWhy can't I download this file?

Citrix Workspace 1911 Download

This article is intended for Citrix administrators and technical teams only.
Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.
Citrix Workspace app is the new universal app for all workspace services, that will encompass all Citrix clients and app capabilities over time.

Under certain circumstances, uninstalling older versions of Receiver for Windows may leave some files behind on the computer and in the registry.This article can also be used as reference to completely clean a system after uninstalling a legacy ICA Client or Citrix Online Plug-in version.
Note: If you plan to install a currently supported version of Receiver for Windows on the system (version 4.4 or later) then there is no need to perform these manual steps or run the clean-up utility. As per article CTX136410, Receiver for Windows 4.4 and later no longer require the separate Clean-Up Utility before installing or upgrading over a previously installed version of Receiver for Windows.

Instructions

Run the following tool: CTX137494 - Receiver Clean-Up Utility

After uninstalling Receiver and restarting the system, the following steps guide to remove any unnecessary files manually that might have been left on the client system.

It is important to remember that certain items mentioned in the following section might not exist on your system depending on the Receiver package used for the installation and how the package was deployed, for example per-machine against per-user installation.
More information on this is available in the Receiver and Plug-ins section of the Citrix eDocs for your version.

Following are the steps for cleaning up the file system:

  1. On the system in use, show all hidden system files and folders (Explorer’s Tools > Folder Options menu item).

  2. In the %userprofile%AppData folder

    • Delete the ICAClient folder if it exists.

    • If the Program Neighborhood Agent was present on the system, the following folder might also exist and should be deleted:
      CitrixPNAgent

    • For more recent Citrix Receiver releases, remove the following folders in AppData if they exist:

      • CitrixReceiver
      • CitrixAuthManager
      • CitrixSelfService
    • On Windows 7, the files and folders mentioned in the preceding must be deleted in both of the following locations:

      • AppDataLocal
      • AppDataRoaming
  3. Repeat everything mentioned in preceding Step 2 for the C:UsersDefault folder as well (C:Documents and SettingsDefault User on Windows XP).

  4. If they exist, ensure the following folders are removed from the directory in which the Receiver was installed. For example, the default install directory is %programfiles%Citrix (%programfiles(x86)%Citrix on 64-bit systems).

    • %programfiles%CitrixICA Client
    • %programfiles%CitrixAuthManager
    • %programfiles%CitrixSelfServicePlugin

Complete the following steps to clean up the system registry:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

  1. Using Registry Editor, navigate to the HKEY_CLASSES_ROOT key and delete the following keys if they exist:

    • Citrix.ICAClient* (delete all instances that exist – such as Citrix.ICAClient.2 or Citrix.ICAClient.2.1)
    • Citrix.ICAClientProp* (delete all instances – such as Citrix.ICAClientProp.2 or Citrix.ICAClientProp.2.1 might exist)
    • ica
    • In the CLSID key, delete any keys whose names begin with 238F
    • InstallerUpgradeCodes9B123F490B54521479D0EDD389BCACC1
    • MimeDatabaseContent Typeapplication/x-ica
    • Wfica
    • WinFrameICA
    • ICA Client
  2. Navigate to HKEY_CURRENT_USER and delete the following in SOFTWARECitrix if they exist:
    • ICA Client
    • PNAgent
    • Dazzle
    • PrinterProperties
    • Receiver
    • XenDesktopDesktopViewer
  3. Navigate to HKEY_LOCAL_MACHINESOFTWARE and delete the following keys if they exist (these keys are located in HKEY_LOCAL_MACHINESOFTWAREWow6432Node on 64-bit systems):

    • CitrixAuthManager
    • CitrixCitrixCAB
    • CitrixDazzle
    • CitrixICA Client
    • CitrixReceiverInside
    • CitrixPNAgent
    • CitrixPluginPackagesXenAppSuite
    • CitrixXenDesktopDesktopViewer
    • In CitrixInstall, delete the following keys if they exist:
      • {94F321B9-45B0-4125-970D-DE3D98CBCA1C}
      • ICA Client
      • PNAgent
      • DesktopViewer
      • ReceiverInsideForOnline
      • MUI
    • Depending on the Receiver package installed, delete one of the following keys in MicrosoftWindowsCurrentVersionUninstall if they exist:
      • CitrixOnlinePluginFull
      • CitrixOnlinePluginPackWeb
  4. After uninstalling the Receiver software, any custom Receiver-side registry keys that icaclient.adm created remain in the registry as well. If you reinstall Receiver, these policies might be enforced possibly causing unexpected behavior. If you want to remove these customizations as well, delete the following ICA Client keys:

    • HKEY_LOCAL_MACHINESoftwarePoliciesCitrixICA Client
    • HKEY_CURRENT_USERSoftwarePoliciesCitrixICA Client
    • On 64-bit systems, ensure that the HKEY_LOCAL_MACHINESoftwareWow6432NodePoliciesCitrixICA Client key does not exist either.
  5. For each user’s registry hive in HKEY_USERS, delete the following keys in SOFTWARECitrix if they exist (example HKEY_USERSS-1-5-18SoftwareCitrix):

    • ICA Client
    • Dazzle
    • Receiver
    • PrinterProperties
    • PNAgent
    • Program Neighborhood Agent
  6. Repeat everything in Step 5 in the key: HKEY_USERS.DEFAULTSoftwareCitrix

Additional Resources

Citrix recommends you to restart the system after editing the registry.

The number of items, their locations and names mentioned in this article might change in subsequent releases of the Receiver for Windows.

CTX121917 - How to Remove Legacy ICA Clients for Windows Using MSI or EXE Command-line Parameters

Refer Receiver and Plug-ins section of the Citrix eDocs.

Disclaimer

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.