This message was deleted.
# citrix-vad
s
This message was deleted.
d
are you using WEM - there’s the fast logoff setting
a
No, not WEM, but Liquidware ProfileUnity but they’ve said it’s not them controlling that behaviour..
j
ProcMon
a
I’ve been advised that the Citrix vda overlooks the gpo that’s set to show logoff scripts so I’m guessing this is back to Citrix to investigate!
a
you dont use controlup by chance, do you? i've used that to monitor a session that does this to see what processes are stuck. i know you're more wanting it to keep showing what is stuck before it disconnects but if you wanted to see what its doing you could open a console window on your hypervisor for the vm then after you log off the ICA session watch that console and it should show you where its stuck
o
sure sounds like Fast Logoff. Quite a few vendors had that setting
n
This is interesting. My W10 1809 VDAs on 7.15 LTSR CU2 logoff quickly (Fast Logoff is disabled in WEM), but on my new 1912 LTSR VDAs, logging off is slow, where the user sees the logoff screen for a solid 5-6 seconds.
a
Odd right! For our logoffs, we want to deliberately provide an informative status otherwise when the session disconnects, users just assume they can go ahead and launch a new desktop, but in reality the profile sync may still he happening or dropping disks. If they logon again too quickly, the last session may still have a disk locked or a profile sync in progress so it affects the success of their next logon. Checked the following : HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages which would normally ensure messages aren’t shown, but that’s not set! I’ve reviewed the VMware UEM forums and found that the splash screens on logon and logoff also don’t work so it seems to be a common issue from Windows 8 onwards regardless of brokering platform. Citrix or VMware..
n
I enabled Fast Logoff in QA, and now it hangs at logoff for up to 20 seconds. Good start to Friday.
a
More digging suggests that logoff progess visibility broke when the shutdown process was changed in 1703 (Windows 10)
n
The logoff process has been consistent for us in 1709 and 1809 on 7.15 LTSR. 1912 is where I'm seeing a change, unfortunately.
a
Ok, sounds like we have different challenges! We’re still only on 1906 VDAz
n
Well, maybe... 1906 and 1912 are much more similar, IMO. I'm pretty sure that 1912's development started with the 1906 source.
My issue may actually be FSLogix. If I disable Profile containers, logoff is 2-3 seconds max. Down the rabbit hole I go...