Μετάβαση στο κύριο περιεχόμενο
  • Υποβάλετε παραγγελίες γρήγορα και εύκολα
  • Δείτε τις παραγγελίες και παρακολουθήστε την κατάσταση αποστολής
  • Δημιουργήστε μια λίστα με τα προϊόντα σας για να έχετε πρόσβαση σε αυτή
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Wyse ThinOS Release 8.3.1 Administrator’s Guide

PDF

Basic Operations for Citrix HDX Flash Redirection

  1. To disable flash version compatibility check, perform the following tasks:

    1. ThinOS client built-in Flash player version is 11.1. If the version installed on VDA/XenApp machines is higher than 11.1, then user needs to disable flash version compatibility check for the HDX Flash redirection feature to work.

    2. User can disable the version check by modifying Windows Registry Key on VDA/XenApp named “FlashPlayerVersionComparisonMask” which is a DWORD that must be set to zero.
    3. This needs to be set on each and every VDA/XenApp where the user needs the checking disabled.

    The following action need to be set on d every VDA/XenApp and you need the checking disabled on.
    • For a 32-bit operating system:

      HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\HdxMediaStreamForFlash\Server\PseudoServer

    • Add the entry named FlashPlayerVersionComparisonMask with a DWORD value = 00000000 and ClientFlashPlayerVersionMinimum"="11.0.0.

    • For a 64-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\HdxMediaStreamForFlash\Server\PseudoServer
    • Add the entry named FlashPlayerVersionComparisonMask with a DWORD value = 00000000 and ClientFlashPlayerVersionMinimum"="11.0.0.

    • After making the modification you must restart IE on VDA/XenApp.

  2. To modify maximum Internet Explorer version that HDX Flash supports:
    1. HDX Flash client side rendering feature does not work with Internet Explorer 11 with HDX Flash redirection enabled on XenApp 6.5 and XenDesktop 5.6 VDA.
    2. The registry key value IEBrowserMaximumMajorVersion is queried by the HDX Flash service to check for maximum Internet Explorer version that HDX Flash supports. For Flash Redirection to work with Internet Explorer 11, set the registry key value IEBrowserMaximumMajorVersion to 11 on the machine where HDX flash service is running. In case of XenApp it would be the XenApp Server and in case of XenDesktop it would be the machine where VDA is installed.

    3. For a 32-bit operating system:

      • HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\HdxMediaStreamForFlash\Server\PseudoServer.

      • Add the entry named IEBrowserMaximumMajorVersion with a DWORD value = 0000000b.

    4. For a 64-bit operating system:

      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\HdxMediaStreamForFlash\Server\PseudoServer.
      • Add the entry named IEBrowserMaximumMajorVersion with a DWORD value = 0000000b.

    • NOTE: This is applicable for XenApp 6.5 and XenDesktop 5.6 VDA.
  3. Use the following guidelines to create a new policy:

    1. Launch the XenApp/XenDesktop manage console, and then go to Polices node pane.

    2. User can edit ‘Unfiltered’ User Policy directly that applies to all connections. User can also view a personal policy, such as ‘FlashTest’ policy, and assign this policy to user’s own computer OU and domain user.

  4. To view the list of Flash policies:

    Go to Settings tab, and then select Flash Redirection. All the Flash Redirection policies are listed as shown in the following screenshot.

  5. To activate a policy:

    After modifying any Citrix policy, run the CMD command ‘gpupdate /force’ in the XenApp/VDA machine, and then reconnect the session. The policy will be updated immediately.

  6. To verify if Flash is getting client rendered OR HDX Flash redirection is working:

    1. Right-click on the Flash Region to view the Flash context menu. If the Flash context menu is same as native Linux menu, the ThinOS built-in Adobe Flash Player version is 11.1. The following screenshot shows that the Flash is getting client rendered.

    2. When flash is client rendered, the event log will display “FR”.

  7. To delete the dynamic blacklist manually:

    In Registry Editor, right-click HKEY_CURRENT_USER to find entries with Keywords ‘DynamicBlacklist’, and then delete all the Backlist keys/records.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\