Deploy Jump Clients During a Connect Support Session or Prior to Support

There are two ways to install a Jump Client. During a Bomgar support session, a Jump Client can be installed ad-hoc by the representative. Alternatively, an administrator can mass-deploy Jump Clients for a larger rollout. These two methods of installation are outlined below.

During a Support Session

A Jump Client may be installed ad-hoc during a support session. This will allow the support representative to access this computer at a later time, even if the computer is unattended. This method of installation is also known as session pinning and is achieved by clicking the Pin as Jump Client button.

Note: A Jump Client pinned in user mode is available only when that user is logged in. In contrast, a Jump Client pinned in service mode, with elevated rights, will allow that system to always be available, regardless of which user is logged in.

Note: Support representatives can access unattended Android devices through session pinning. To learn more, please see Initiate an Android Support Session

Pin Jump Client

  1. From within a support session, click the Pin as Jump Client button in the session toolbar at the top right corner of the representative console.

 

Jump Client Properties

  1. From the dropdown, you may select to customize the Jump Client before deploying it.
    1. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
    2. Move Jump Clients from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Clients to or from other users' Jump Groups depends upon your account permissions.
    3. Further organize Jump Clients by entering the name of a new or existing Tag. While the selected Jump Clients are grouped together under the tag, they are still listed under the Jump Group where each is pinned. To move a Jump Client back into its top-level Jump Group, leave this field blank.
    4. Jump Clients include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Clients faster and easier.
    5. If necessary, click the Reset button clears all entries.
  2. Depending on the session permissions, the customer may receive a message that you are requesting to install a Jump Client. The customer will be asked to allow or refuse the request.
  3. Once the Jump Client is installed, the remote computer will appear in the Jump interface of the representative console. You may have to refresh the interface to see the new Jump Client.

Prior to Support

Jump Clients can be pre-installed on remote computers in anticipation of the need for remote access. This method of installation may be applied to one system or multiple systems simultaneously. The Jump Client command line installer has switches which allow a script to modify a variety of Jump Client parameters when executed. This allows you to create custom mass deployment scripts to pull in variables from other sources and use the variables to modify the Jump Client parameters at install time.

  1. From the /login administrative interface, go to Jump Clients and click Create Jump Client Installer

Jump > Jump Clients

Jump Client Mass Deployment Wizard

  1. You can download the Jump Client installer immediately if you plan to distribute it using a systems management tool or if you are at the computer that you need to later access. You can also email the installer to one or more remote users. Multiple recipients can install the client from the same link. The Platform option defaults to the appropriate installer for your operating system. You can select a different platform if you plan to deploy the Jump Client on a different operating system.
  2. Run the downloaded installer. No other action is required.

Note: To install a Jump Client in service mode on a Linux system, the Jump Client must be installed as root. This will NOT cause the Jump Client to run as root. A service mode Jump Client allows the user to start a session even if no remote user is logged on, as well as to log off the current remote user and log on with different credentials. A Linux Jump Client installed in user mode cannot be elevated within a session.

Mass Deploy Help

For system administrators who need to push out the Jump Client installer to a large number of systems, the Windows, Mac, or Linux executable or the Windows MSI can be used with your systems management tool of choice. You can include a valid custom install directory path where you want the Jump Client to install. You can also set certain installation parameters specific to your needs. These parameters can be specified for both the MSI and the EXE using a systems administration tool or the command line interface. If the installation fails, view the operating system event log for installation errors.

Command Line Parameter Value Description
--install-dir <directory_path> Specifies a new writable directory under which to install the Jump Client. This is supported only on Windows and Linux. When defining a custom install directory, ensure that the directory you are creating does not already exist and is in a location that can be written to.
--jc-jump-group

user:<username>

This command line parameter sets the Jump Client's group to a specific user.
--jc-tag <tag-name> This command line parameter sets the Jump Client's tag.
--jc-comments <comments ... > This command line parameter sets the Jump Client's comments.
--silent   If included, the installer shows no windows, spinners, errors, or other visible alerts.

Note: When deploying an MSI installer on Windows using an msiexec command, the above parameters can be specified by:

  1. Removing leading dashes (-)
  2. Converting remaining dashes to underscores (_)
  3. Assigning a value using an equal sign (=)

Example:

  • msiexec /i bomgar-scc-win32.msi KEY_INFO=w0dc3056g7ff8d1j68ee6wi6dhwzfefggyezh7c40jc90 jc_jump_group=user:admin jc_tag=servers

There are two exceptions to this rule:

  • installdir has a dash in the EXE version but no dashes in the MSI version.
  • /quiet is used for the MSI version in place of --silent in the EXE version.

Installation on Headless Linux Systems

To install a Jump Client on a remote Linux system with no graphical user interface, be sure you have downloaded the headless Linux Jump Client installer, and then follow these additional steps:

  1. Using your preferred method, push the Jump Client installer file to each headless Linux system you wish to access.
  1. Once the installer file is on the remote system, use a command interface to install the file and specify any desired parameters.
    1. Install the Jump Client in a location to which you have write permission, using --install-dir <path>. You must have permission to write to this location, and the path must not already exist. Any additional parameters must also be specified at this time, as described below.
      • sh ./bomgar-scc-{uid}.bin --install-dir /home/username/jumpclient
    2. If you wish to install under a specific user context, you can pass the --user <username> argument. The user must exist and have rights to the directory where the Jump Client is being installed. If you do not pass this argument, the Jump Client installs under the user context that is currently running.
      • sh ./bomgar-scc-{uid}.bin --install-dir /home/username/jumpclient --user jsmith

      IMPORTANT!

      It is not recommended to install the Jump Client under the root context. If you attempt to install when the current user is root, you receive a warning message and are required to pass --user <username> to explicitly specify the user that the process should run as.

    3. You can also set certain installation parameters specific to your needs. These parameters can be specified for both the MSI and the EXE using a systems administration tool or the command line interface. If the installation fails, view the operating system event log for installation errors.
      • sh ./bomgar-scc-{uid}.bin --install-dir /home/username/jumpclient --jc-jump-group "Linux Admins" --jc-tag "Headless Linux Systems"

       

      Command Line ParameterValueDescription
      --install-dir<directory_path>Specifies a new writable directory under which to install the Jump Client. This is supported only on Windows and Linux. When defining a custom install directory, ensure that the directory you are creating does not already exist and is in a location that can be written to.
      --jc-jump-group

      user:<username>

      This command line parameter sets the Jump Client's group to a specific user.
      --jc-tag <tag-name>This command line parameter sets the Jump Client's tag.
      --jc-comments<comments ... >This command line parameter sets the Jump Client's comments.
      --silent If included, the installer shows no windows, spinners, errors, or other visible alerts.
  2. After installing the Jump Client, you must start its process. The Jump Client must be started for the first time within the time frame specified by This Installer Is Valid For.
    • /home/username/jumpclient/init-script start

    This init script also accepts the stop, restart, and status arguments. You can use ./init-script status to make sure the Jump Client is running.

    IMPORTANT!

    You must also arrange for init-script start to run at boot in order for the Jump Client to remain available whenever the system restarts.

  3. If you wish to uninstall the Jump Client, you must run its uninstall script.
    • /home/username/jumpclient/uninstall

    Note: Separately and in addition to running the uninstall script, you must remove the Jump Client via the representative console. Otherwise, the Jump Client will remain in the representative console, though it will not be accessible. Likewise, removing the Jump Client only via the representative console prevents it from being accessed but leaves the Jump Client files on the Linux system.

Use Jump Clients to Access Unattended Android Devices

Beginning with Bomgar 16.1, a persistent connection can be established with an Android device by pinning a Jump Client to the device. This provides the ability to have unattended support sessions with Android devices. You can deploy Jump Clients using either of the methods below.

Note: Bandwidth usage and battery life are minimally affected by establishing a persistent connection.

Note: Persistent connections to an unattended Android device can occur only when the devices have both the Bomgar Support Client App 2.2.7 and Bomgar Jump Client App 2.2.0 installed from the Google Play Store. To learn more, please see Download the Bomgar Support Client and Bomgar Jump Client Apps for Bomgar Connect.

Pin an Android Jump Client from the Representative Console

Pin Jump Client

  1. While in a support session with the Android device, click on the Pin a Jump Client icon.
  2.  

    Persistent Android Jump Client

  3. After pinning, click the Refresh option located above the Jump Items list, and the Android device appears as a Jump Item in the Jump Item list. If the Pin a Jump Client icon is gray, the Android Jump Client has not been installed on the Android device.
  4. Meanwhile, the Bomgar Jump Client app on the device should show the client as pinned with a date and timestamp.

Note: Options are available for the Jump Client to be disabled if the device is relying on battery power or on data to connect.

Persistent Pinned Android Session

Email a Link from the /login Interface to Install and Android Jump Client

Jump Clients

  1. From the /login interface, navigate to Jump Clients and click Create Jump Client Installer.
  2. Jump Client Mass Deploy for Android

  3. From the Download or Install the Client Now section, choose Android as your platform.
  4. Verify that the Bomgar Jump Client app is installed on the Android device. If not, navigate to the Google Play App store to download the app.
  5. To download the Jump Client to the device, open a browser on the Android device and go to the URL provided by the mass deployment wizard.

Note: You can also email the URL to the Android device by clicking on the Email link located in the Deploy to Email Recipients section.