Backstage option to prevent auto lock just for Backstage
Added in Version 23.2If Lock on Disconnect is enabled,
If Lock on Connect is enabled,
We have started looking into this requirement and would like to know How are you joining backstage when problem occurs 1.Starting a regular session and then swapping to backstage or 2. via 'Join with Options'?
Can you please help us with a use case?
Hey Rishikesh, It would just be beneficial if the Screen knows not to lock after using Backstage. if say we need to do background work on a machine, so it does not affect the user's screen while they are working. Say I just need to run a quick script in the background, I cant do that without it interfering with the user currently on the machine we are remoting into. let me know if that clarifies
@Rishikesh, the issue happens regardless of the join method.
This is not a feature request. This has been the functional implementation for almost 2 years, no matter how it was retroactively "intended" to work.
Ours broke recently after upgrading control to version 22.6 from 22.5 and it only locked when ending console sessions, which is how we need it to occur.
Customer support service by UserEcho