Citrix Workspace 1911

Posted on  by



downloadWhy can't I download this file?

  • Navigate to the Application Compatibility Flags portion of the registry:

    For a 32-bit application:
    HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionTerminal ServerCompatibilityApplications

    For an x64-but application:
    KEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionTerminal ServerCompatibilityApplications

  • Create a Key and name it the same as the name for the application’s executable (that is ADOBEREADER)

  • Create the REG_DWORD value of Flags=0x00000408

    • 0x00000008 = 32 bit application

    • 0x00000400 = refer to system Windows directory

    • that is for an application called Scanner Companion which is 32 bits and on an x64 Windows 2008 R2 XenApp server create the following key

      HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionTerminal ServerCompatibilityApplicationsSCANNERCOMPANION

    • Value

    • Instructions

    To Test scanning in XenApp 6.5

    1. On the local device, navigate to the local services panel (Control Panel|Administrative Tools) and disable the Windows Image Acquisition (WIA) service. This is done to ensure that the scanner will be using the TWAIN device driver.

    2. Scan a document locally using the scanner manufacturer’s scanning software to ensure that local scanning functions as expected.

    3. If scanning locally works successfully, log on to the XenApp 6.5 published desktop.

    4. Open a TWAIN compliant application to see if scanning functions as expected within the XenApp session.

    5. If the application does not see the scanner and scanning within XenApp fails, refer to the following troubleshooting section:

    Troubleshooting Information

    Desktop Experience Pack

    • For Windows 2008 R2 servers only
    • Some TWAIN devices require the XenApp server to have the Desktop Experience Pack which contains STI.inf, the default INF file for still image devices, as well as the core imaging system binaries including the STI/WIA service and the TWAIN Data Source Manager. To enable this on the server do the following:

    1. Start Server Manager.

    2. In the details pane, locate the Features Summary area, and then click Add Features.

    3. In the Add Features Wizard, click to select the Desktop Experience check box, and then click Next.

    4. Click Install.

    5. After the Desktop Experience feature is installed, click Close to exit the Add Features Wizard, and then click Yes to restart the computer.

    TWAIN testing tool

    Install Twacker – a third party TWAIN testing tool - to the XenApp server and to the local client device to test TWAIN scanning within a XenApp desktop session.

    Download from here.

    1. Install Twacker.

    2. Within a XenApp published desktop session:

    1. Launch Twacker (32 bit version).

    2. Click File > Select Source and select your scanner from the list.

    3. Click File > Acquire.

    4. Click the Scan button to test your scanner.

    If the Twacker application is able to scan successfully then the XenApp environment is configured properly for USB redirection and to use TWAIN devices, and states all of the requirements have been met on the local client device. In case of further scanning issues within a particular application it is likely to be a software issue.

    downloadWhy can't I download this file?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.
    Mac
    2. 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

    Citrix Workspace 1911 Download Windows

    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
    HKLMSOFTWAREWow6432NodeCitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength
    • 32-bit Windows
    HKLMSOFTWARE CitrixICA ClientEngineConfigurationAdvancedModulesTCP/IPOutbufLength

    Citrix Workspace 1911 Mac

    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​
    Citrix Workspace 1911

    Citrix Workspace App 1911 For Windows

    Enable the 'EDT Stack Parameters' option, which is disabled by default:
    Settings > Advanced > EDT Stack Parameters

    Citrix Workspace Desktop Lock 1911

    Problem Cause

    Citrix Workspace 1911 Windows

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

    Additional Resources