The users discuss ways to get a report on CVAD sessions that reconnect after 2 hours of disconnect time. One suggestion is to create a trigger on idle time and another is to use the session activity reports for more specific information. However, the reporting process may be slow in larger environments. Resource usage information is also shared.
Read the entire ‘Report on Reconnecting CVAD Sessions Longer Than 2 Hours’ thread below:
OK, lesson 1, dont press enter till finished. Anyone have any ideas how to get a report/data on CVAD sessions that are disconnected longer than 2 hours but then reconnect before our timeout of 6 hours? Looking for affected users if we drop the disconnection timeout for sessions to 2 hours. Thanks for any info. BTW, can get this in reports-session activity, but need to drill down into each session for the info, looking to get summary info really.
Just create a trigger on idle time > 2 hours. Do nothing with it and then get a count of triggers fired by using the incidents panel or audit log in dex
Ohh. List of affected users… More difficult.
Yeah how many of those actually reconnect is the question
Oof. Um maybe session adv trigger? From state disconnected >=2 hours and
Shouldnt post that, sorry.
redacted lol
Nah, all good. I think the logic above should work.
Pretty confident the adv trigger with disconnect time in the from and active in the to will do the trick.
Awesome, I will look into that today, appreciate it!
The reporting of it will be the painful part.
Incidents panel in the console has the data but is painfully slow.
Not knowing your environment size I can’t comment more. It may be fine, might not.
~5000 sessions start every 24 hours
127 Win2019 server desktop hosts
May be a bit slow
2000-3000 concurrent
Ok, that’s relevantly small. You should be fine.
Continue reading and comment on the thread ‘Report on Reconnecting CVAD Sessions Longer Than 2 Hours’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI, ControlUp Scripts & Triggers