Jump Clients

What are Jump Clients?

Jump Clients are software agents installed on remote systems, enabling secure, unattended access to those systems for support or administrative tasks.

How are Jump Clients useful to my organization?

Jump Clients provide reliable, always-available access to remote systems, improving efficiency by allowing teams to resolve issues without requiring user intervention. They enhance security through encrypted connections and customizable access controls.

How do I access the Jump Clients page?

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.
  2. From the main menu, click Privileged Remote Access > Jump.
    The Jump page opens and the Jump Clients tab displays by default.

The Jump Clients page

An image of the Jump Client Installer List interface in a remote access management software. The interface includes sections for adding and managing Jump Clients, downloading generic installers, configuring usage statistics, upgrading clients, maintaining inactive clients, and miscellaneous settings.
  1. Left menu: Easy access to all pages in Privilege Remote Access, including Status, Consoles & Downloads, My Account, Configuration, Jump, Vault, Console Settings, Users & Security, Reports, Management, and Appliance pages.
  2. Status: Opens the Status page.
  3. Header: Change your tenant site, manage your profile, and access documentation.
  1. Add: Adds a new Jump Client.

  2. Jump Clients columns- The list of Jump Clients columns. Not all the columns display in the image above.

    Jump Clients columns
    • Connection Type: Displays whether the connection is active or not.
    • Jump Group: Select what Jump Group you want the client to participate in.
    • Jump Policy: Select the Jump Policy you want the Jump Client to belong in.
    • Expires: Defines how long the installer is valid. This is determined by the This Installer Is Valid For setting.
  3. Jump Client options: You can download, show key information, extend the installer expiration, or delete a Jump Client installer.

  4. Generic Jump Client Installer Download:Downloads a generic installer.

  5. Installer Usage: Command line help for large deployments.

  6. Jump Client Statistics: Settings to gather statistics for Jump Clients.

  7. Upgrade: Settings to control automatic upgrade of Jump Clients.

  8. Maintenance: Settings to control maintenance of Jump Clients.

  9. Miscellaneous:Setting to wake up Jump Clients via Wake on LAN (WOL).

Jump Client installer list

The Jump Client installer list shows existing Jump Client installers and the ability to add a new Jump Client. To add a new Jump Client, see Jump Client Mass Deployment Wizard

A warning appears at the top of the list:

Installing more than one Jump Client as the same user or more than one Jump Client as a service 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 hide the message.

Delete an installer

To delete an installer, click the trash can To delete an existing group, click the trash can..

Extend an expiration

To extend the expiration on how long the installer is valid, click the clock To extend the installer expiration, click the trash can..

Download an installer

To either download, email or copy the direct link to the Jump Client installer, click Use to copy or download link to installer .

Show Key information

To show key information for installer, click the key Click the key to show installer information.

Generic Jump Client installer download

The generic installer allows you to download a Jump Client installer package that is not tied to a specific Jump Client installer. Generic installers can be used for automated or ephemeral deployments on Virtual Machine (VM) images and do not require authenticating and downloading the Jump Client-specific installer once deployed.

To use the Generic Jump Client installer, do the following steps:

  1. Select your desired platform and click Download.
  2. Copy the provided command into your command line interface (CLI), or click Download to download the .msi installer file.
  3. From the Jump Client installer list, select an installer and click the download icon to copy the key. If using a CLI, replace the text insert key info here with the key; otherwise, if running the Windows MSI through the user interface, enter the key when prompted.

Jump Client Mass Deployment Wizard

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

The only field that is required is Jump Group. After all fields have been completed, click Create.

The Jump Client Mass Deployment Wizard includes the following fields:

Jump Client Mass Deployment Wizard fields
Field NameDescription
Jump GroupFrom the Jump Group dropdown box, 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 (and higher ranking roles on your team, such as Team Lead and Team Manager if you are a Team Member, and Team Manager if you are a Team Lead) 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.
Allow override during installationSome 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.
This installer is Valid ForThe 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 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 logged-in admin user with appropriate permissions, 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 Remote Support admin.
Jump PolicyYou can 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. If no Jump Policy is applied, this Jump Client can be accessed at any time.
Session PolicyChoose session policies to assign to this Jump Client. Session policies assigned to this Jump Client have the highest priority when setting session permissions.
Jumpoint ProxyWhen a Jump Client is first deployed, if it cannot connect to the Appliance, it searches the local network for a Jumpoint or Jumpoint cluster serving as a Jump Zone Proxy. This allows a Jump Client installed on a system without a native internet connection to use the Jumpoint to connect back to the Appliance.

In the special case where the Jump Client and Jumpoint are not on the same local network or where a firewall blocks the Jump Client's attempt to connect to the Jumpoint, the Jumpoint Proxy setting allows you to set which Jumpoint the Jump Client should try to use as a proxy. This setting is used by Jump Clients that cannot use multicast DNS to retrieve proxy information from a Jumpoint.
Maximum Offline Minutes Before DeletionThe maximum number of minutes a Jump Client will be offline before it is deleted from the system. This setting will override the global setting if specified.
Attempt an Elevated Install If the Client Supports ItIf 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 in user mode, installing the Jump Client in user mode.

ℹ️ Note

User mode Jump Clients are deprecated and will be removed in a future release. This setting applies only to MacOS Desktop and Linux Desktop deployments. It does not apply to Windows deployments.

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 .
Prompt for Elevation Credentials If NeededIf 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.

ℹ️ Note

User mode Jump Clients are deprecated and will be removed in a future release. This setting applies only to MacOS Desktop deployments. It does not apply to Linux or Windows deployments.



Mass deployment help

For system administrators who need to push out the Jump Client installer to a large number of systems, the Windows MSI, the Mac DMG, or the Linux BIN can be used with your systems management tool of choice.

When using a command line or system management tool to install, you can override certain installation parameters. For any setting with Allow override during installation checked, you can modify the Jump Client installer with the following parameters for each installation.

ℹ️

Note

If a parameter is passed on the command line but the setting is not marked for override in the administrative interface, the installation fails. View the operating system event log for installation errors.

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-name<name...>If override is allowed, this command line parameter sets the Jump Client's name.
--jc-jump-groupuser:
jumpgroup:
If override is allowed, this command line parameter overrides the Jump Group specified in the Mass Deployment Wizard.
--jc-session-policyIf 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-policyIf override is allowed, this command line parameter sets the Jump Policy that controls how users are allowed to Jump to the Jump Client.
--jc-tagIf 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.
--jc-max-offline-minutesIf override is allowed, this command line parameter sets the number of minutes the Jump Client can be offline before being considered lost.
--jc-ephemeralNoneIf override is allowed on Maximum Offline Minutes, this command line parameter sets the Jump Client to ephemeral mode, marking it as uninstalled if it goes offline for more than 5 minutes. This is the same as setting --jc-max-offline-minutes 5.
--silentNoneIf specified, the Jump Client performs a silent installation. No user interaction is requested and no user interface is displayed during the process.

ℹ️

Note

When you deploy an MSI installer on Windows using the msiexec command:

  • The installation folder may be specified by passing a variable: INSTALLDIR=<path>
  • The KEY_INFO= is optional as it is built into the filename.
  • If you specify ONLINE_INSTALL=1, the installation fails if it cannot immediately reach the appliance. The default is blank.
  • A silent installation can be done by specifying /quiet to the msiexec command.
  • All of the --jc… parameters listed above may be specified as variables by:
    • Removing leading dashes (-)
    • Converting remaining dashes to underscores (_)
    • Assigning a value using an equals sign (=)

Example:

msiexec /i sra-pin-win_x64.msi jc_tag=servers

ℹ️

Note

For more information, see Mass deploy on macOS.


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 representative console and include the following items:

  • CPU
  • Console user
  • Disk usage
  • Remote screen
  • Uptime

Upgrade

Automatic Jump Client upgrades

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

  • Disabled: Permanently disable Jump Client upgrades.
  • Enabled for this version only: Temporarily enable Jump Client upgrades for the current upgrade cycle.
  • Enabled always: Permanently enable Jump Client upgrades.

ℹ️

Note

To manually update Jump Clients in the Web Rep Console, you must first disable Automatic Jump Client Upgrades.

Maintenance

Field NameDescription
Number of days before Jump Clients that have not connected are automatically deletedThis setting determines when the system should remove Jump Clients that have failed to connect to the site for the configured number of days. This setting is also shared with the client itself during normal operation so that even if it cannot communicate with the site, it will uninstall itself at the configured time.

This setting must be configured for 15 days or more.
Number of days before Jump Clients that have not connected are considered lostThis setting determines when a Jump Client is considered lost by the system, which means that it has not connected in the configured number of days. No specific action is taken on that client, but it is labeled as lost for identification purposes. If the Jump Client cannot contact the Appliance at the time it is uninstalled, the affected item remains in its offline state. To identify lost Jump Clients before they are automatically deleted, set this field to a smaller number than the Number of days before Jump Clients that have not connected are automatically deleted field.

This setting must be configured for 15 days or more.
Uninstalled Jump Client BehaviorIf a user uninstalls a Jump Client at the endpoint, the Access Console can either keep the Jump Client in the list and mark it as Uninstalled or remove it from the list entirely. When changed, this setting only affects Jump Clients that will be uninstalled in the future.

Miscellaneous

Allow representatives to attempt to wake up Jump Clients

Allow Representatives 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.


©2003-2025 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.