We have set up a triggered task to run tsdiscon.exe at workstation lock on our Windows 10 VDI (We're using DEM 2111) . It works properly when you lock the workstation, but if you manually disconnect the session, then try try to reconnect, tsdicon.exe runs a second time, so you get into a loop and can't reconnect the session.
We set the triggered task to run CMD.exe for testing purposes, when we manually disconnect / reconnect there are 2 command prompts open on the desktop
It seems that when you reconnect, Horizon issues a second lock that kicks off the triggered task again.
Can anyone think of a different way to do this? Is there some way for DEM to recognize that the lock is coming from Horizon and if it is, don't run the task?
I am currently working on a way of letting users get disconnected after a certain time period. Would you like me to share with you how i've done this if i have reached a conclusion?