{"id":1775,"date":"2025-08-04T08:05:53","date_gmt":"2025-08-04T08:05:53","guid":{"rendered":"http:\/\/neu.koetzingit.de\/citrix-es-ist-an-der-zeit-drei-hdx-dinge-zu-beheben\/"},"modified":"2026-06-02T13:31:57","modified_gmt":"2026-06-02T13:31:57","slug":"citrix-es-ist-an-der-zeit-drei-hdx-dinge-zu-beheben","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/citrix-es-ist-an-der-zeit-drei-hdx-dinge-zu-beheben\/","title":{"rendered":"Citrix, it's time to fix three HDX things!"},"content":{"rendered":"

C<\/span>Citrix HDX is critical to the user experience in Virtual Apps and Desktops environments. This article highlights three areas where default settings and misconceptions can impact performance and complicate administration: Enlightened Data Transport (EDT), outdated legacy graphics policies, and the often misconfigured HDX 3D Pro acceleration. The goal is to provide actionable insights for proactive HDX optimization.<\/p>\n

<\/p>\n

The EDT Dilemma \u2013 Re-evaluating UDP as a Standard<\/span><\/h3>\n

Understanding Enlightened Data Transport (EDT)
<\/strong>EDT is a proprietary Citrix transport protocol built on UDP that was designed to improve the user experience over \u201edemanding long-distance connections\u201c and \u201eunreliable networks.\u201c The Adaptive Transport mechanism used by EDT is set to \u201ePreferred\u201c by default in Citrix policies, making EDT the primary protocol with automatic fallback to TCP.<\/p>\n

\u00a0<\/p>\n

The arguments for disabling it by default in LAN\/WAN
<\/b>In typical enterprise LAN or WAN environments with latencies below 100 ms, enabling EDT by default often results in performance degradation, which manifests as \u201eblack screens\u201c or \u201efragmented screen displays.\u201c These issues are often due to Maximum Transmission Unit (MTU) fragmentation, as UDP does not inherently handle fragmentation. This is particularly common with VPN connections, Wi-Fi access points, and mobile networks, where the effective MTU may be lower than the standard 1,500 bytes. EDT is \u201emuch more sensitive\u201c to MTU issues than the classic ICA protocol over TCP.<\/p>\n

Although EDT MTU Discovery is enabled by default and is designed to automatically determine the optimal MTU, it has limitations. It requires that Session Reliability be enabled and may fail in scenarios with asymmetric network paths or DS-Lite networks. A failed MTU Discovery can result in an overly high detected MTU, causing fragmentation and poor performance. The TCP fallback mechanism can also increase the session startup time by up to five seconds. The default \u201ePreferred\u201c setting for Adaptive Transport is problematic for most corporate networks<\/strong>, since the EDT implementation is sensitive to MTU issues.<\/p>\n

\u00a0<\/p>\n

\"Blog<\/p>\n

\u00a0<\/p>\n

Table: Comparison of HDX Adaptive Transport (EDT vs. TCP) Performance in Common Network Scenarios<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n
Network scenario<\/strong><\/td>\nDefault EDT behavior<\/strong><\/td>\nObserved performance issues (EDT)<\/strong><\/td>\nMain cause (EDT issues)<\/strong><\/td>\nRecommended protocol for the scenario<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Typical corporate LAN\/WAN (<100 ms)<\/td>\nPreferred, Active<\/td>\nBlack screens, fragmented display<\/td>\nMTU fragmentation, UDP sensitivity<\/td>\nTCP<\/strong><\/td>\n<\/tr>\n
VPN connection<\/td>\nPreferred, Active<\/td>\nBlack screens, fragmented display<\/td>\nMTU fragmentation, lower effective MTU<\/td>\nTCP<\/strong><\/td>\n<\/tr>\n
Long-distance WAN (>100 ms)<\/td>\nPreferred, Active<\/td>\nIdeal, but MTU issues are possible<\/td>\nMTU Discovery Restrictions<\/td>\nEDT<\/td>\n<\/tr>\n
Unreliable Wi-Fi\/cellular network<\/td>\nPreferred, Active<\/td>\nBlack screens, fragmented display<\/td>\nMTU fragmentation, unstable connection<\/td>\nTCP<\/strong>\u00a0<\/td>\n<\/tr>\n
Connection via Citrix Gateway<\/td>\nTCP (often enforced)<\/td>\nNo EDT issues (since UDP ports are often closed)<\/td>\nUDP ports not open\/EDT not enabled on the gateway<\/td>\nTCP <\/strong>(often forced)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\n

The standard for HDX connections and error detection
<\/strong>I often hear from customers that connections via the No issues with Citrix Gateway<\/strong> show, and this is because either EDT is not enabled on the gateway, or the UDP ports 1494\/2598 (inbound) and 443 (outbound) for Citrix Gateway have not been opened, meaning that only TCP connections<\/strong> come about.\u00a0<\/p>\n

Other indicators of UDP issues may include the previously mentioned \u201eblack screens<\/strong>\u201c or the \u201efragmented screen display<\/strong>\u201c be. If you are unsure which transport protocol is being used, you can check this via Citrix Director or using the command CtxSession.exe -v<\/code> check.<\/p>\n

Given that most customers do not use transatlantic connections, the default setting for HDX Adaptive Transport should be reevaluated. I recommend that Citrix set to \u201eOff\u201c by default.<\/strong><\/p>\n

\u00a0<\/b><\/p>\n

Citrix Legacy Graphics Policies\u00a0<\/span><\/h3>\n

The Purpose and Pitfalls of Legacy Graphics Mode
<\/b>The legacy graphics mode was designed for older operating systems such as Windows 7 and Windows 2008 R2. However, it is not supported or tested on modern operating systems (Windows 8, 8.1, 10, Server 2012\/2012 R2\/2016). The long-term presence<\/strong> The presence of numerous settings that are explicitly tied to \u201elegacy graphics mode\u201c (e.g., Extra color compression, Heavyweight compression, Lossy compression level, Progressive compression) causes considerable confusion among administrators. Although legacy graphics mode itself is used by administrators is not enabled<\/strong>, they often configure many of the policies that depend on it because these\u201elisten carefully<\/strong>\u201c, without realizing they are incompatible. Although a \u201eLegacy settings only\u201c filter is available in Web Studio, on-premise administrators currently make little use of this tool, which makes it difficult to identify and prevent these misconfigurations. This confusion has been an ongoing issue for many years. In a conversation with the then-HDX product manager Derek Thorslund<\/strong> I have expressed the need for a filter to manage these policies, but a comprehensive solution has never been fully implemented.<\/p>\n

\u00a0<\/b><\/p>\n

Overview of Legacy Graphic Guidelines
<\/b>The following images list policies that are either explicitly tied to \u201eLegacy Graphics Mode\u201c or were primarily relevant to older graphics rendering methods. Modern Citrix environments predominantly use Thinwire, which adapts dynamically and utilizes video codecs (H.264, H.265, AV1), rendering many of these legacy settings obsolete or ineffective.\u00a0<\/p>\n\n\n\n\n
Including legacy graphic guidelines<\/strong><\/td>\n\u00a0<\/td>\nCurrent Graphic Guidelines<\/strong><\/td>\n<\/tr>\n
\"Blog<\/td>\n\u00a0<\/td>\n\"Blog<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Citrix should speed up the cleanup of the Policy Console, by removing legacy policies<\/strong> and will no longer provide warnings or filters for legacy policies.<\/p>\n

\"Blo<\/p>\n

\u00a0<\/p>\n

Optimize HDX 3D Pro \u2013 Enable GPU Acceleration<\/span><\/h3>\n

Basics of HDX 3D Pro and GPU Usage
<\/b>HDX 3D Pro, now known as HDX Graphics, delivers a high-performance user experience for demanding graphics workloads by leveraging GPUs to hardware-accelerate DirectX and OpenGL applications. It uses adaptive H.264 or H.265-based depth compression for optimal WAN and wireless performance. Hardware encoding with H.264 and H.265 is supported on NVIDIA, Intel, and AMD cards that support NVENC.28 H.265 and AV1 offer superior compression and image quality. Proper installation of GPU drivers and hypervisor configuration are critical for the effective use of vGPUs.<\/p>\n

\u00a0<\/b><\/p>\n

Key Guidelines for Optimal HDX 3D Pro Performance<\/b><\/p>\n

Optimizing HDX 3D Pro requires precise configuration of Citrix policies:<\/p>\n