This message was deleted.
# citrix-vad
s
This message was deleted.
p
We get this occasionally. Have a filtered view in director to find them. Note they won’t appear in director immediately, usually takes a half hour.
j
Wow, that shows up for me too under filtered. Thanks @Paul Brown
👍 1
t
Are you doing EDT to both DGs? If she connects via hot spot does it work? We've seen weird things like this for EDT with certain broadband carriers.
d
Tim is right! I guess EDT is causing the problem. You could disable EDT on one DG with a Citrix policy filtered by a tag. Tag the DG and apply the policy with EDT disabled on the tag. Restart the machine or execute gpupdate. You can check with netstat if the server still listens to UDP 2598/1494.
j
Turned out to be that brokered desktop, failed at logon, never fully associated with them. Used the filter in director above to find a desktop assigned to N/A, force rebooted that desktop so it could reregister with broker with no user on.
👍 1
p
We’re not using EDT, have it actively disabled. Still have 4 or 5 of these issues a day.
r
same here
t
All on XD? Or XA as well?
j
All XD
p
Same. We have two farms. Only the desktop farm has this issue, and only with more recent releases of XD.
c
I disabled edt too. Too many issues
r
I often wonder what the % is that disable EDT now.
d
with EDT you need to make use of MTU discovery and lower the MTU in the default.ica for reliable connections from networks not under your control. There are lots of carriers/providers/VPN users running below the default 1500 MTU size.
💯 1
d
It’s only a regkey to enable MTU discovery. Give it a try!
s
Do you find that setting the storefront side change is good enough? Or is the endpoint reg change necessary too?
r
I do both
My remind on notes for me. Just pasted it all here. 4. Add the MTU discovery Registry setting to Fix packet fragmentation. I originally did this with GPO, But from what Citrix and slack member are saying. It needs to be baked in the Golder Image. What this key does…. This key stop the packet fragmentation from happing on version of Citrix workspace the can use this key and support MTU discovery to adjust the MTU size of the ICA session. If we find that we have version that can't work. Then you must edit the Storefront default ICA file. So in a nutshell, MTU discovery works on Clients that support it. Clients that doesn't support it. You need to modify the defaul.ica file to make it work fully https://support.citrix.com/article/CTX231821 a. 1912VDA, add this DWORD: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\icawd Name: MtuDiscovery Type: DWORD Data: 00000001 • If you enable it on the VDA it works WITHOUT changing the default.ica. It is controlled by: Registry key on the VDA (set it in registry on GM, not with GPO) • Client (Windows CWA 1911 and later) Example of not have the key and using default MTU setting which is 1500.
t
Our users with problems were all internal accessing Citrix desktops across SD-WAN. All of our external users work with EDT without problem. My thought is it's either client related (Citrix Receiver/WSA version), or a problem with the SD-WAN config.
s
Another change on the vda too?!?!? That ping command is nifty
d
You can use my BGInfo script to check the client MTU size inside a VDA Session among many other things https://github.com/Mohrpheus78/Citrix/tree/main/BGInfo
r
I need to deploy this.
d
I updated the script. Added WEM cache date and free size of FSL in percent 😁 Script is now on GitHub
t
Your staff don't have a problem with BGInfo running in their session? Ours would probably flip. Plus, we have an organization mandated background within our desktop, so we'd have to work around that (there is a graphic in the bottom right corner)
r
yea I wish we add it. Users would FLIP out
d
Just use the BGInfo Taskbar script! No change of the background wallpaper, just a tray icon.
If you click on the tray icon you see all the informations 👍🏼
r
That would actually work.
Now I have to go lookup how to add it. Been years since I looked at this.
d
Very simple. Start BGInfo-Taskbar.ps1 with WEM external task on logon. Just read the example notes in the script.
r
oh thats it. Well that simple
p
How does wem cope with PS execution modes being pushed by corporate policy?
r
It will choke
I run a CMD file to set the exuction policies, then call the .PS1 files
p
i was worried it would do.
r
Dennis might have a simpler way
d
WEM external task: Path: powershell.exe Arguments: -executionpolicy bypass -file “C:\Program Files (x86)\Scripts\BGInfo\BGInfo-Taskbar-Taskbar.ps1”
r
I had that at one time, and it wouldnt work. But I can try that again
d
Works 100 %. Make sure you don’t block powershell.exe with WEM (Security tab)
BGInfo Taskbar looks like this (after clicking on the systray icon):
r
I cant get it to load for me. Script runs, but I dont see the icon yet.
j
@Paul Brown, if you don't want to wait for Director to show up at the +30m mark and need to find the VDA that has the Brokered by not fully logged on session try this. It'll show desktops in the process of logging on, from there you can infer if one is stuck in that state by running it again + your average logon time.
Get-BrokerSession -DesktopGroupName "DGName" -SessionState Connected | select Brokering*,DNS*