Jump

Jump Clients: Manage Settings and Install Jump Clients for Endpoint Access

Jump

Jump Clients

Jump Client Installer List

This list shows all previously installed active Jump Client installers. Administrators and privileged users can view, download, delete, or extend Jump Client installers.

A warning message appears at the top of the list: Installing more than one Jump Client on the same system is being phased out in a future release. In the Access Console you may use the copy action on a Jump Client to apply different policies to the same endpoint. Click Dismiss to remove the warning message.

Generic Jump Client Installer Download

The generic installer allows you to create Jump Client and Jumpoint installers that are not tied to a specific Jump Client or Jumpoint. Generic installers can be used for automated or ephemeral deployments on VM images, and do not require authenticating and downloading the Jump Client or Jumpoint-specific installer once deployed.

To use the generic Jump Client installer, select your desired platform, and click Download. When prompted, copy the Jump Client-specific key to complete the installation.

Jump Client Mass Deployment Wizard

To access the Jump Client Mass Deployment Wizard, click Add at the top of the Jump Client Installer List.

The Mass Deployment Wizard enables administrators and privileged users to deploy Jump Clients to one or more remote computers for later unattended access.

For more information, please see Privileged Remote Access Jump Client Guide: Unattended Access to Systems in Any Network.

Jump Group

From the Jump Group dropdown, select whether to pin the Jump Client to your personal list of Jump Items or to a Jump Group shared by other users. Pinning to your personal list of Jump Items means that only you can access this remote computer through this Jump Client. Pinning to a shared Jump Group makes this Jump Client available to all members of that Jump Group.

Name

Add a name for the Jump Client.

Some Mass Deployment Wizard settings allow override, enabling you to use the command line to set parameters that are specific to your deployment, prior to installation.

Jump Policy

You may apply a Jump Policy to this Jump Client. Jump Policies are configured on the Jump > Jump Policies page and determine the times during which a user can access this Jump Client. A Jump Policy can also send a notification when it is accessed or can require approval to be accessed. If no Jump Policy is applied, this Jump Client can be accessed without restriction.

Jumpoint Proxy

If you have one or more Jumpoints set up as proxies, you can select a Jumpoint to proxy these Jump Client connections. That way, if these Jump Clients are installed on computers without native internet connections, they can use the Jumpoint to connect back to your B Series Appliance. The Jump Clients must be installed on the same network as the Jumpoint selected to proxy the connections.

Attempt an Elevated Install if the Client Supports It

If Attempt an Elevated Install if the Client Supports It is selected, the installer attempts to run with administrative rights, installing the Jump Client as a system service. If the elevated installation attempt is unsuccessful or if this option is deselected, the installer runs with user rights, installing the Jump Client as an application. This option applies only to Windows and Mac operating systems.

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, allows that system to always be available, regardless of which user is logged in.

This Installer Is Valid For

The installer remains usable only as long as specified by the This Installer is Valid For dropdown. Be sure to leave adequate time for installation. If someone should attempt to run the Jump Client installer after this time, installation fails, and a new Jump Client installer must be created. Additionally, if the installer is run within the allotted time but the Jump Client is unable to connect to the B Series Appliance within that time, the Jump Client uninstalls, and a new installer must be deployed. The validity time can be set for anywhere from 10 minutes to 1 year. This time does NOT affect how long the Jump Client remains active.

Once a Jump Client has been installed, it remains online and active until it is uninstalled from the local system either by a user from the Jump interface or by an uninstall script. It can also be uninstalled, or extended, from the Jump Client Installer List. A user cannot remove a Jump Client unless the user is given appropriate permissions by their admin from the /login interface.

Comments

Add Comments, which can be helpful in searching for and identifying remote computers. Note that all Jump Clients deployed via this installer have the same comments set initially, unless you check Allow Override During Installation and use the available parameters to modify the installer for individual installations.

Session Policy

You may choose a session policy to assign to this Jump Client. Session policies are configured on the Users & Security > Session Policies page. A session policy assigned to this Jump Client has the highest priority when setting session permissions.

For more information, please see at Session Policies: Set Session Permission and Prompting Rules.

Maximum Offline Minutes Before Deletion

You can set the Maximum Offline Minutes Before Deletion of a Jump Client from the system. This setting overrides the global setting, if specified.

Prompt for Elevation Credentials if Needed

If Prompt for Elevation Credentials if Needed is selected, the installer prompts the user to enter administrative credentials if the system requires that these credentials be independently provided; otherwise, it installs the Jump Client with user rights. This applies only if an elevated install is being attempted.

Tag

Adding a Tag helps to organize your Jump Clients into categories within the access console.

Allow Override During Installation

Some Mass Deployment Wizard settings allow override, enabling you to use the command line to set parameters that are specific to your deployment, prior to installation.

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.

It is common for receive an error message during the install, regarding a layout or appearance issue. This can be disregarded.

Duplicate installations of Jump Clients or large numbers of installations can lead to installation failures or degraded performance. Please see Review Best Practices for Jump Client Mass Deployment — Windows.

You can also override certain installation parameters specific to your needs. When you mark specific installation options for override during installation, you can use the following optional parameters to modify the Jump Client installer for individual installations. Note that if a parameter is passed on the command line but not marked for override in the /login administrative interface, the installation fails. 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-name <name...> If override is allowed, this command line parameter sets the Jump Client's name.
--jc-jump-group

user:<username>jumpgroup:<jumpgroup-code-name>

If override is allowed, this command line parameter overrides the Jump Group specified in the Mass Deployment Wizard.

--jc-session-policy <session-policy-code-name>

If override is allowed, this command line parameter sets the Jump Client's session policy that controls the permission policy during an access session.

--jc-jump-policy <jump-policy-code-name>

If override is allowed, this command line parameter sets the Jump Policy that controls how users are allowed to Jump to the Jump Client.

--jc-max-offline-minutes <minutes> The maximum number of minutes a Jump Client can be offline before it is deleted from the system. This setting overrides the global setting if specified.
--jc-ephemeral  

Sets the maximum number of minutes a Jump Client will be offline before it is deleted from the system to 5 minutes. This is a convenience option that specifies the Jump Client as being ephemeral and is functionally equivalent to specifying --jc-max-offline-minutes 5

--jc-tag <tag-name>

If override is allowed, this command line parameter sets the Jump Client's tag.

--jc-comments <comments ... >

If override is allowed, this command line parameter sets the Jump Client's comments.

--silent  

If included, the installer shows no windows, spinners, errors, or other visible alerts.

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 (=)

MSI Example:

msiexec /i bomgar-pec-win32.msi KEY_INFO=w0dc3056g7ff8d1j68ee6wi6dhwzfefggyezh7c40jc90 jc_jump_group=jumpgroup:server_support jc_tag=servers

When deploying an EXE installer, the above parameters can be specified by:

  • Adding dashes
  • Adding a space between the parameter and the value

EXE Example:

bomgar-pec-[unique id].exe --jc-jump-group jumpgroup:servers --jc-tag servers

Other rules to consider:

  • 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.

Jump Client Statistics

An administrator can choose which statistics to view for all Jump Clients on a site-wide basis. These statistics are displayed in the access console and include CPU, console user, disk usage, a thumbnail of the remote screen, and uptime.

Upgrade

Maximum bandwidth of concurrent Jump Client upgrades

You can regulate the bandwidth used during upgrades by setting Maximum bandwidth of concurrent Jump Client upgrades.

Maximum number of concurrent Jump Client upgrades

Also set the maximum number of Jump Clients to upgrade at the same time. Note that if you have a large number of Jump Clients deployed, you may need to limit this number to regulate the amount of bandwidth consumed.

This setting does not affect access console upgrades.

Automatic Jump Client Upgrades

Use the radio buttons below to control automatic Jump Client upgrades. You can:

  • Permanently disable Jump Client upgrades.
  • Temporarily enable Jump Client upgrades for the current upgrade cycle.
  • Permanently enable Jump Client upgrades.

In order to manually update Jump Clients in the privileged web access console, you must first disable Automatic Jump Client Upgrades.

Maintenance

Number of days before Jump Clients that have not connected are automatically deleted

If a Jump Client goes offline and does not reconnect to the B Series Appliance for the number of days specified by the Number of days before Jump Clients that have not connected are automatically deleted setting, it is automatically uninstalled from the target computer and is removed from the Jump interface of the access console.

This setting is shared with the Jump Client during normal operation so that even if it cannot communicate with the site, it uninstalls itself at the configured time. If this setting is changed after the Jump Client loses connection with the B Series Appliance, it uninstalls itself at the previously configured time.

Number of days before Jump Clients that have not connected are considered lost

If a Jump Client goes offline and does not reconnect to the B Series Appliance for the number of days specified by the Number of days before Jump Clients that have not connected are automatically deleted setting, it is labeled as lost in the access console. No specific action is taken on the Jump Client at this time. It is labeled as lost only for identification purposes, so that an administrator can diagnose the reason for the lost connection and take action to correct the situation.

To allow you to identify lost Jump Clients before they are automatically deleted, this field should be set to a smaller number than the deletion field above.

Uninstalled Jump Client Behavior

Uninstalled Jump Client Behavior determines how a Jump Client deleted by an end user is handled by the access console. Depending on dropdown option selected, the deleted item can either be marked as uninstalled and kept in the list or actually be removed from the Jump Items list in the access console. If the Jump Client cannot contact the B Series Appliance at the time it is uninstalled, the affected item remains in its offline state.

Miscellaneous

Allow Representative to attempt to wake up Jump Clients

Allow users to attempt to wake up Jump Clients provides a way to wake up a selected Jump Client by broadcasting Wake-on-LAN (WOL) packets through another Jump Client on the same network. Once a WOL is attempted, the option becomes unavailable for 30 seconds before a subsequent attempt can be made. WOL must be enabled on the target computer and its network for this function to work. The default gateway information of the Jump Client is used to determine if other Jump Clients reside on the same network. When sending a WOL packet, the user has an advanced option to provide a password for WOL environments that require a secure WOL password.

You can set Jump Clients to allow or disallow simultaneous Jumps from the Jump > Jump Items > Jump Settings section. If allowed, multiple users can gain access to the same Jump Client without an invitation to join an active session by another user. If disallowed, only one user can Jump to a Jump Client at a time. Only an invitation by the user who originated the session can allow for a second user to access the session.

For more information, please see .

Use screen state to detect Customer Presence

When enabled, a customer will be considered present only if a user is logged in, the system is not locked, and a screen saver is not running. When disabled, a customer will be considered present if a user is logged in, regardless of the screen state. Customer Presence affects the session policy used for sessions started from a Jump Client.

Global connection rate for Jump Clients

The global connection rate setting is used by disconnected Jump Clients as a clue to know how aggressively to try to reconnect.