This message was deleted.
# citrix-vad
s
This message was deleted.
c
I presume for VDI you have configured the idle/disconnect values in a policy in studio as its different for SBC where you set it through the RDS policies. Also take a look at the DG settings you got peak/off peak settings for disconnected sessions so you could say when disconnected 20 mins action = shutdown you can also view the same settings via powershell get-brokerdesktopgroup -name "W10 VDI" and look for the disconnected action timeouts for peak/offpeak
n
Yeah, we use Studio for the W10 VDAs:
Never set anything in the DG:
ShutdownDesktopsAfterUse is True (which is default, IIRC)
So this is taking a weird turn. I'm testing this in QA, and if I disconnect from the session using the custom Disconnect shortcut that I created, which just runs C:\Windows\System32\tsdiscon.exe, nothing happens. It will remain in the Disconnected state. If I disconnect using the button in the Citrix toolbar, it obeys the policy and logs the user off. This makes no damn sense.
r
Curious, if these VDA were upgraded or Fresh install? I have seen some VDA upgrades not honor the disconnect timers.
n
Fresh install. This kind of makes sense, though, as I currently have an issue in WEM where using tsdiscon.exe doesn't work properly. Reconnecting will throw a 'single instance' error if I have the option selected to run the WEM agent on reconnect. I'm trying to pin down what command Citrix is running when you click on Disconnect in the toolbar in ProcMon.
Using tsdiscon.exe is Citrix's own workaround for the lack of the Disconnect option in W10, so I don't understand why it's treating this differently.
Anyone ever use CTXDiscon (http://www.florisvanderploeg.com/disconnecting-a-citrix-session-with-ctxdiscon/)? This actually works. I may replace tsdiscon with it.
r
Never used that. Cool to know though