Automating Logoff of Old Horizon Sessions with ControlUp

Some users discuss using ControlUp to automate the logoff of old sessions in Horizon. One user suggests using a trigger pack with adjustable time to log off sessions after a certain period. Another user recommends building an sba that uses the invoke-cuaction for the horizon forced log off action.

Read the entire ‘Automating Logoff of Old Horizon Sessions with ControlUp’ thread below:

Is anyone using ControlUp to automate the logoff of old sessions in Horizon? I was hoping to use HZ Session Create Time greater > 28 days to run the Message Schedule and Logoff script but it doesn’t look like that’s possible (can only choose specific dates). Curious to see what others are doing.

We have some clients using it but use 8 hours

using session state changed from connected to disconnected , wait 8 hours then log off

We have a trigger in our trigger packs that will help with this use case. You can adjust the time to your preference.

https://support.controlup.com/docs/trigger-packs?highlight=triggers#general

that one probably won’t work in some of those cases as logoff in horizon often doesn’t work when the desktop is locked. In that case I would recommend to build an sba that uses the invoke-cuaction for the horizon forced logoff action. This one comes from the horizon api’s but is not available in the horizon admin and for me always manages to logoff the most stubborn horizon sessions

Continue reading and comment on the thread ‘Automating Logoff of Old Horizon Sessions with ControlUp’.  Not a member? Join Here!