Jump to content
Welcome to our new Citrix community!
  • 0

Advanced setting DPI scaling on Server 2022 build 2108


Question

We've migrated from Server 2019 to 2022 (same VDA (2203 LTSR CU2)) and same GPOs. Now setting DPI scaling from 100 to 125 or 150 does not have any effect.
Logon to the "old" Server 2019 DPI scaling works again.

 

Our users connecting via IGEL client (CWA 2209) to the Citrix farm. So no client-scaling should be the issue.

I've checked all registry settings:

HKEY_CURRENT_USER\Control Panel\Desktop
LogPixels = 144 (for 150%)
Win8DpiScaling = 1

But after new logon the RegKey:
HKEY_CURRENT_USER\Control Panel\Desktop\WindowsMetrics
AppliedDPI = 60 (100%)
is again 100% default 96 DPI.

 

Is this an known issue with Server 2022 ?

Link to comment

11 answers to this question

Recommended Posts

  • 0

Here the answer from Microsoft (issue can't be resolved - looking forward to next server edition):

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Windows Server 2022 ignores the set DPI's because the function of changing from the scaling factor for the RDP session is no longer supported on Windows Server 2022.  
 

The detailed evaluation that can be shared with your client:  

  

The reason for the different behavior in Server OS 2019 and 2022 is that different technologies were used. In Server OS 2019, icardd was used.  

  

Icardd.dll (vdtw30.dll legacy) - Graphics redirection driver for Terminal Sever based session.   

  

However, in 2022, icardd was no longer used and IDD was used - Indirect display driver.  

  

The indirect display driver (IDD) model provides a simple user mode driver model to support monitors that are not connected to traditional GPU display outputs. An example is a dongle connected via USB to a normal (VGA, VGA, HDMI, DP, etc.) connected PC. 

 

IDD implementation 

An IDD is the UMDF Driver driver for the device provided by third-party vendors. It is developed using the functions made available by the Iddcx.h header  (Indirect Display Driver Class eXtension) to interface with the Windows graphics subsystems in the following ways: 
 

·         -Creating the graphics card adapter that represents the indirect display device.  

·         -Reporting monitors that are connected and disconnected from the system  

·         -Providing descriptions of the connected monitors  

·         -Providing available display modes  

·         -Support other display features, such as hardware mouse cursors, gamma, I2C communication, and protected content  

·         -Process desktop images displayed on the monitor 

Since an IDD is a UMDF driver, it is also responsible for implementing all UMDF functions  Overview of UMDF -  such as device communication, power management, plug and play, and so on.  

The IDD is executed in Session Zero without any components running in the user session. Therefore, any driver instability does not affect the stability of the system as a whole.  

The following diagram provides an architecture-based overview. 

An IDD is the third-party UMDF Driver for the device. It is developed using the functions made available by the  Iddcx.h header (Indirect Display Driver Class eXtension) to interface with the Windows graphics subsystems in the following ways. 
 
Ref:Indirect display driver model overview - Windows drivers | Microsoft Learn 
Display/Graphics overview - Windows drivers | Microsoft Learn 
 

After it was forwarded and discussed internally by Dev Teams, the Microsoft was added docs under: 

https://learn.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server-2022#features-were-no-longer-developing 
  

And yes, that's why it doesn't work with Dual screen!
 

As a last attempt to fix the issue try to add this Regkey in: 
 
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm 
 
"OverlayTestMode"=dword:00000005
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  • Like 1
Link to comment
  • 0

Here the answer from Citrix:

 

The reason results in the different behaviors in server OS 2019 and 2022 is that different technologies were used. In server OS 2019, the icardd was used.

 

But in 2022, icardd was deprecated and IDD was used

 

From our code, we always use the DPI and resolution of the client to set the monitor layout when starting an ICA session. The "Custom Scaling" is a Windows OS setting, we don't use this value in our code. I've also confirmed that the same issue in RDP session in server OS 2022. So, I would recommend involving Microsoft to investigate.

 

As of now, citrix doesn't has any case logged with MS on this.
Customers are requested to engage the MS team to check on the issue.
We are not jointly working with MS as of now on this issue.

 

As discussed, please log a case with MS and get this issue analyzed, you can give them the reference i told on my first email.
If upon analysis done by MS, if any of the citrix component is involved in the issue, please revert to this email and i will take it forward.
As told, i will be closing this case for now, let us know if any assistance is required from our side.

 

Great support! I don't know why I have to open a case @MS to get a bug of Citrix getting fixed ?

Link to comment
  • 0

@stefan wielers : I've an answer by Microsoft, but it doesn't work in our environment. Could you try to check it, if it works in yours ?

 

As you mentioned, the reason for the different behavior in Server OS 2019 and 2022 is that different technologies were used. In Server OS 2019, icardd was used and IDD in Windows Server 2022


Icardd.dll (vdtw30.dll legacy) - Graphics redirection driver for Terminal Sever based session. 

Starting with XA 7.0 and XD7.0, the virtual graphics channel is hosted in ctxgfx.exe for both workstation and terminal server based sessions. Ctxgfx hosts platform-specific modules that interact with the appropriate driver (icardd.dll for RDSH and vd3dk.sys for Workstation).

 

However, in 2022 icardd was no longer used and IDD was used - Indirect display driver.
An IDD is the UMDF Driver for the device provided by third parties. It is developed using the features made available by the Iddcx (Indirect display driver class eXtension) to interface with the Windows graphics subsystems in the following ways:

 

-Indirect display driver model overview - Windows drivers | Microsoft Learn
-Display/Graphics overview - Windows drivers | Microsoft Learn

 

Our recommended Solution:
Disabling GPO for The Windows Display Driver Model (WDDM) is the graphics display driver architecture WDDM could therefore solve the existing problem under Win_Ser _2022, even if the GPO was not configured at all. 

(Group policy path:
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Remote Session Environment)
-"Use WDDM graphics display driver for remote desktop connections" to Disable

 

Please reboot for this change to take effect.

Alternatively you can execute the following statement via CMD/PowerShell with administrator rights:

 

REG ADD “HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services” /v “fEnableWddmDriver” /t REG_DWORD /d 0 /f

 

And here is the normal changing for the DPI scaling since Server 2012 r2: 

  

Change registry settings and reboot 

HKEY_CURRENT_USER\Control Panel\Desktop\Win8DpiScaling 

  

– Type in Decimal Value: 

Turn on = 1 

  

HKEY_CURRENT_USER\Control Panel\Desktop\LogPixels 

  

– If LogPixels does not exist then create a new DWORD value 

– Type in Decimal Value 

96 for Smaller 100% 

120 for Medium 125% 

144 for Larger 150% 

192 for 200% 

  

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\IgnoreClientDesktopScaleFactor 

– Type in Decimal Value: 

Turn on = 1 

Link to comment
  • 0

Upgrading from WS2019 to WS2022 we have found the same thing, Windows DPI scaling no longer works on our HP Linux thin clients on 2203 CU2. For now we have found that enabling the "Enable DPI matching" option in Citrix Workspace on our ThinPro machines follows the client system, so after setting the scaling to 125%, 150% etc. on the Linux thin client, when launching the VDA it now scales to the same percentage

 

Not ideal as its now on a per machine level instead of per user, but a temporary solution nonetheless until Citrix fixes this properly and hooks in correctly to however WS2022 is now doing this

Link to comment
  • 0
10 hours ago, Evan Ractivand said:

Upgrading from WS2019 to WS2022 we have found the same thing, Windows DPI scaling no longer works on our HP Linux thin clients on 2203 CU2. For now we have found that enabling the "Enable DPI matching" option in Citrix Workspace on our ThinPro machines follows the client system, so after setting the scaling to 125%, 150% etc. on the Linux thin client, when launching the VDA it now scales to the same percentage

 

Not ideal as its now on a per machine level instead of per user, but a temporary solution nonetheless until Citrix fixes this properly and hooks in correctly to however WS2022 is now doing this

Thanks for sharing this workaround. This is not an real option for us, because we have shared workplaces. But if there were an option for us -  how did you configure "Enable DPI matching" in the Linux CWA ? 

Link to comment
  • 0
11 hours ago, Jens Strohschnitter1709152492 said:

Thanks for sharing this workaround. This is not an real option for us, because we have shared workplaces. But if there were an option for us -  how did you configure "Enable DPI matching" in the Linux CWA ? 

 

Seems my previous comment didn't post properly, so I'll try again...

 

This is where the options exists on HP ThinPro, under the Xen connection settings. On Windows machines, see this article for DPI matching: https://support.citrix.com/article/CTX230017/configuration-of-dpi-matching-and-clientside-scaling-with-citrix-workspace-app-for-windows

DPIMatching.jpg

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...