Welcome to our community!

[Backstage] workflow, please restore back previous version workflow

raylund lai

1 week ago
updated 1 week ago
Pending Review

The current new version (25.5.3.9368) changed the way [Backstage] working. Previously, we could join into [Backstage] whenever "normal" user is connecting to ScreenConnect guest console. With the new version, we need to kick out user's session to join into [Backstage]. If the user was kicked out, then we could just join to console "frontstage" and sign in as admin! This logic of backstage is meaningless.

Please restore the [Backstage] logic and workflow as previous version.

Replies 2

Oldest first
Newest first Oldest first

Sean White Team Member

1 week ago

Hi there. We have not made any changes to the workflow. I just tested to verify:
1-Connected to a guest machine where user was logged and working

2- Switched to backstage

3- At this point I (host) was in backstage and user (guest) remained in their console session and were not interuppted.

If you are seeing different behavior, please contact our support team for assistance.

Contact Support

Reply Link

raylund lai

1 week ago

Previously, we could join (right click and select "Join with Options") into [Backstage] (there are options to connect to [Backstage] or Console) whenever "normal" user is connecting to ScreenConnect guest console. With the new version, when join (with active normal user connection to console), message saying "A Host is already connected to this session. Join options are limited". Not anymore "options" to be selected (for [Backstage]).

In addition, if clicked on "JOIN SESSION", both the user and me/admin are joined to the session on the guest. This already interrupted user working.

Furthermore, if I use the top menu to switch the connection from "Console" to "[Backstage]", the already connected user's session will be frozen (user cannot click or do anything). Even I disconnected, user's session still frozen. User needs to disconnect and reconnect to regain the control / working.

Hence, [Backstage] virtually doesn't mean working at the back stage. And needs to interrupt user's working during support (frozen, disconnect and reconnect).

Thanks

Raylund