This message was deleted.
# citrix-vad
s
This message was deleted.
n
Can confirm, you need to enable the policy in Studio and either set it to Enabled or Disabled.
Set the policy beforehand and you're all good.
By default, the VDA makes the call, and since by default in 2203 everything is blocked, that'd be the result without telling it to open.
r
I need to see if the policy even exist in 1912. I have no idea.
Been a while since I touched 1912
You running 1912 anywhere in your enviroment?
n
Sure am... getting you a screenshot right now
r
Cool, thanks man
Ahh I see in the 1912 docs "By default, the Virtual channel allow list feature is disabled."
n
Yeah, everything allowed by default in 1912. Reversed in 2203.
From one of our 1912 CU5 environments:
r
Thanks man
n
Anytime.
I still think the decision to reverse this by default is dumb.
r
yea, it can be a strange one.
d
Until 1912 cu4 it’s open by default. With cu 4 citrix changed this in 1912 and the Virtual Channel are closed by default 😓
r
Good to know that. I thought they would not make any changes lol oh well.
n
Is that accurate? I thought the policies were created as of like CU2, but not the functionality change.
d
Yep I know what u mean. We were all very surprised, because this change was a very little note in the readme of cu 4 😓
n
We're on 1912 CU5, don't have this policy configured, but Webex and ControlUp VCs work fine...
d
Yep 2006 cr and 1912 cu 4. trust me. I had so much customer with this update and they all gone nuts because the third party tools (controlup, Devicetrust and so on) doesn’t work after the update. Nobody had a glue at this time, because we all had in our minds that in ltsr that changes are not allowed 👏
n
lol, jesus Citrix
d
Maybe u configured it. If u have it not configured. The default changed from allow to deny.
Oh sry it was 2109 current release and cu 4 1912 ltsr
This was my default article for my customer 😂
n
So weird