Make this group a member of the -bomgar group described above.
They cannot use the jump client method described above or the unattended method described below. TSPs who are members of the no-jump group have only one level of access: they can initiate interactive sessions beginning with the end user downloading and installing the Bomgar mini-client, and where the end user is present to respond to the TSP's requests for permissions to copy files, get system information, elevate privileges, etc. The three remaining groups (described below) should all be made members of this group. The end user must still be present for these future sessions, and must respond to TSP prompts asking for additional permissions. This allows the TSP to start another session at a future time without the need for the client to walk through the steps of downloading and installing the client.
#Bomgar jump client install install#
Members of this group are able to initiate interactive sessions (where the end user is present) by inviting the end user to download and install the Bomgar mini-client. Typically the mini-client is removed when the support session ends, but, with the end user's permission, they can "pin" the client (which is then called the Jump Client) to the user's computer where it will remain, inactive, after the session ends. This is the example we'll use in the descriptions in this article. For instance, the department of limnology might have the prefix LIM. Group names include the prefix for the OU where they reside. See the exception noted under the Managers group below. An individual should be made a member of only one of the groups described here.