Sessions

Administrators can view ongoing remote connections in the Management Console and disconnect sessions when needed.

Overview

What Is a Session?

When a member uses a Controller to remotely connect to a Controlled device, a session is created.

Sessions can be divided by entry point into types such as Remote Support, Device List, File Transfer, and Monitor Wall.

Administrators can view who is connecting, when the connection started, which Controller is being used, and which Controlled device is being connected.

What Is the Relationship Between Sessions, Controllers, Controlled Devices, and Members?

Members can use different Controllers to connect to different Controlled devices. Each connection from a Controller to a Controlled device is an independent session.

Disconnect Sessions

Disconnect a Session as Administrator

1. Select Ongoing Sessions in the left navigation bar of the Management Console;
2. Expand more actions in the actions column of the specified session;
3. Click Disconnect Session;
4. Or, select multiple sessions in the list and click Disconnect Session under Batch Operations.

In addition, administrators can also disconnect all sessions initiated by a specified Controller from the Controllers list, and batch operations are also supported.

Disconnect a Session on the Controlled Device

On the Controlled device, open the Connected Devices floating window in the lower-right corner of the screen and click the X button.

After completion, the connection between the corresponding Controller and the current Controlled device is disconnected.

Disconnect a Session as a Member on the Controller

Directly close the session tab to disconnect the session.

Or, click the drop-down button above the remote control screen in the AskLink Business Controller, then click End in the expanded menu.

After completion, the current remote session ends.

Disconnect a Session as a Member in Member Security Center

1. Open Member Security Center in the AskLink Business Controller;
2. Click the relevant Controller in the Authorized Controllers list;
3. Click Disconnect All Sessions.

After completion, the corresponding remote sessions initiated by this Controller are disconnected.

Notes

• Disconnecting a session immediately interrupts the corresponding remote connection. Before performing the operation, confirm that ongoing work will not be affected;
• If an abnormal session is found, disconnect the session first, then check member, Controller authorization, and device permissions;
• Revoking Controller authorization is different from disconnecting a session: revoking authorization prevents the Controller from continuing to access enterprise devices later.