This message was deleted.
# citrix-vad
s
This message was deleted.
n
Does that registry key require it to be baked into the image, or can it be deployed via GPO?
r
i do not know. All I know is all my systems that are using published apps on high-DPI monitors can now no longer read the txt....
Ah, in that case, add it via the registry and report back your findings... 😄
r
This is with VDA 1912 LTSR CU3
n
That's what we're on.
r
it changed all the settings from "Let the OS scale" to "yes"
which changed the resolution of all the published apps
AND, they removed the "High DPI" section from the freaking WSA, so users can't even set it anymore
i mean WTF?!?!
n
I just noticed that myself. I guess if it means that all you have to do is add this registry key and it should work automatically, that would be good.
r
That's what bothers me the most.. change something without giving any fucks about the ramifications of millions of users, while removing the section in the GUI...
/rant
Just got the count in... 900 systems were updated on our side...
n
So your options are either uninstall/reinstall an older client, or disable DPI matching via GPO.
r
So, GPO.. that 900 is probably across 80+ environments. lol.
yeah, i'm in a tough spot
need to stop it before it rolls out to the other 3000.... haha
n
"Sorry, CWA 2206 has finished deployment. We should just upgrade the infrastructure now."
r
hahaha
well, the VDAs are all above 1912LTSR, that should have nothing to do with it?
DPI matching is disabled by default on 1912 LTSR Multi-session OS VDAs for all Virtual Apps (aka seamless or published apps) sessions. As a result, the VDA ignores the DPI scale settings of the client for all Virtual Apps sessions. This can be an issue for Windows clients with high-resolution monitors (above 1920x1080) where DPI scaling is generally used, with the main symptoms displaying very small graphics and text.
oh, nm....
n
Yeah, you could try adding that registry key to one of your VDAs. That would be an easy fix if it works.
r
yeah, fun... ok team, make a bunch of GPO changes, STAT
yeah, will test
n
We still have a 7.15 environment, so that rules out this entire client and will now prevent me from upgrading CWA for a while.
r
yeah, dang
ha, no wrong number.. it's actually 2000...
😞
r
I often wonder when they remove things like this, was the amount of customers wanting it vs leaving it as an option. I don't understand why they remove things like this.
💯 1
n
It's a catch 22 for us. All of our sites are LTSR, but we have to use the CR build of CWA because of the browser being removed from the LTSR build of CWA. So right now, our entire environment will be stuck with CWA 2112.1 until our Epic VDAs are upgraded to 1912 (I know, I know...).
r
It happens man. As many environments I have been in, there is always something that you have to work around.
n
I'm more annoyed that we are waiting until literally the last month to upgrade that environment to 1912. There's no excuse.
k
We've upgraded 2 persistent VDAs and clients with the latest VDA and Workspace app and both of them render the session wrong on our displays. (Microsoft Surface Laptops with 1440P external monitors.) We're trying a RDS host to see if we see the same thing, but so far we're 0 for 2. Funny part is we had opened a case on this 2+ years ago and Citrix was able to repro in their lab, you'd think they would've done some testing there.
r
QA? lmfao
🤣 1
Confirmed the registry key works fine. Tested with my Surfacebook, with 2206, with VDA 1912 LTSR CU3
👍 1
n
I wonder how it affects devices that did set DPI to one of the other options, assuming they're on an old CWA but connect to a VDA with that reg key.
r
i can test that too
It honors the setting on WSA...
Which, I guess is good to hear
k
That's what we noticed as well. Whatever setting it's set to prior to upgrading Workspace app is what sticks. As far as RDS goes, with 2206 VDA and 2206 WSA, only 1 out of 4 of us had issues with how the screens rendered. Really perplexed as to why they removed the DPI settings, especially if they're not standardizing on setting it 1 way when this new WSA is installed.
r
@keislij Can you explain your last comment a bit more? So you see issues when you upgrade a CWA and the DPI setting was prior the upgrade set to any other value?
k
@Rody Kossen In our environment, we utilize Surface devices which have a bit higher DPI/resolution than our external monitors. This made the environment a bit challenging as the DPI setting in Workspace App would have to be configured a certain way depending on if the user just uses Surfaces vs if they use external monitors. Almost all of our "laptop" fleet had the DPI set to "Yes" vs No or Let the OS decide. After updating to the latest WSA (not using clean-up utility or uninstall/reinstall), we've found that whatever value that was set in the DPI screen that was removed was what "stuck" if you will in the latest CWA. We verified this by checking the regkey in HKCU:\Software\Citrix\ICA Client\DPI registry key. If Citrix's intent was to "standardize" to DPI matching, it's not swapping the DPI setting if the user had already set it to client-side scaling or DPI unaware. We've found that once we update to the 2206 VDA (from 2203), suddenly sessions render a bit weird. Part of the display from the Surface monitor bleeds over to the external monitors.
d
Workspace 2210 Tech Preview, the High DPI menu under Advanced Preferences is reintroduced.
💥 1
r
SWEET
r
heh, that's nice to hear.. I was wondering if this was going to be the case.
We have locked ours to 2205 until something changed
💯 1
n
I patiently await CWA 2210 2210.1
😂 2