Configure and Install a PRA Jumpoint

Setup of a Jumpoint on a remote network is a multi-step process that includes configuration on the /login interface, downloading the installer, and running the installation wizard.


  1. From the /login administrative interface, go to Jump > Jumpoint.

Jumpoint Management

Add Jumpoint

  1. Click Add
  2. Create a unique name to help identify this Jumpoint. This name should help users locate this Jumpoint when they need to start a session with a computer on its same network.
  3. Set a code name for integration purposes. If you do not set a code name, one is created automatically.
  4. Add comments to help identify this Jumpoint.
  5. Leave the Disabled check box unchecked.
  6. A Clustered Jumpoint allows you to install multiple, redundant nodes of the same Jumpoint on different host systems. If this option is selected, the Jumpoint will be available as long as at least one of the installed nodes is online. This provides redundancy, preventing the failure of all Jump Items associated with the failure of a single, standalone Jumpoint, and improves load balancing across the system. All configuration of clustered Jumpoints is done in /login, with no local configuration available during the install. Once created, a clustered Jumpoint cannot be converted to standalone, nor a standalone Jumpoint converted to clustered.



Jumpoint cluster nodes must be installed on hosts residing in the same local area network.

  1. If you want users to be able to connect to SSH-enabled and Telnet-enabled network devices through this Jumpoint, check Enable Shell Jump Method.
  2. If Enable Protocol Tunnel Jump Method is checked, users may make TCP connections from their systems to remote endpoints through this Jumpoint.
  3. From the Jumpoint edit page, you may authorize users to start sessions through this Jumpoint. After the Jumpoint has been created, you can also grant access to groups of users from Users & Security > Group Policies.S
  4. Save the configuration. Your new Jumpoint should now appear in the list of configured Jumpoints.

Once you have installed the Jumpoint, the table will populate the hostname of the system it is installed on, as well as that system's public and private IP addresses. This information can help you locate the Jumpoint's host system in case you need to change the Jumpoint's configuration.


Now that your Jumpoint is configured, you will need to install the Jumpoint on a single system in the remote network you wish to access. This system will serve as the gateway for Jump sessions with other computers on the remote network. You can either install the Jumpoint directly to the host or email the installer to a user at the remote system. If this is to be a clustered Jumpoint, you will be able to add nodes later.

  1. From the table, find the appropriate Jumpoint and click the link to download either the 32-bit or 64-bit installer file (bomgar-jpt-{uid}.exe).
  2. If you are at the system you want to use as the Jumpoint host, you can run the installation file immediately.
  3. Otherwise, save the file and then email it to the remote user to deploy on the system that will serve as the Jumpoint host.

If you need to change the Jumpoint's host system, click Redeploy. The Jumpoint uninstalls from its current location, and the download links become available. You can now install the Jumpoint on a new host. The new Jumpoint replaces the old one for any existing Jump shortcuts that are associated with it. The new Jumpoint does not copy over the configuration from the old Jumpoint and must be reconfigured during installation.


BeyondTrust Jumpoint Setup

  1. From the system that will host the Jumpoint, run the installation package. When the installation wizard appears, click Next.


Jumpoint Installer Waiver Agreement

  1. Read and accept the waiver agreement. You must accept the agreement to be able to proceed with the installation.


Jumpoint Installer Disclaimer

  1. Read and agree to the disclaimer.


Jumpoint Installer Choose Install Location

  1. Choose where you would like the Jumpoint to install. The default location is C:\Program Files\Bomgar \Jumpoint or C:\Program Files (x86)\Bomgar \Jumpoint.
  2. Click Install. If you are installing a single Jumpoint, the BeyondTrust Jumpoint Configuration window will open after a moment. If you are installing a clustered Jumpoint node, the installation will finish.



In the case of clustered Jumpoints, keep in mind that there is no customization available at the local level. As a result, you will not see the configuration window that allows for Proxy and other configuration items available for standalone Jumpoints. If you are installing a clustered Jumpoint, you may skip the following steps and go directly to Clustered Jumpoint Setup: Adding Nodes.

For a Jumpoint to be deployed on a remote network that is behind a proxy, appropriate proxy information may be necessary for the Jumpoint to connect back to the Secure Remote Access Appliance.

    Basic options for configuring a Jumpoint Proxy.

  1. From the dropdown on the Proxy tab, select Basic or NTLM to configure proxy settings.
  2. Enter the Proxy Host, Proxy Port, Username and Password. The Jumpoint will supply this proxy information whenever Jumping to another system on the remote network, providing the credentials necessary to download and run the endpoint client on the target system.


  1. You also can set up this Jumpoint to function as a proxy itself by selecting Jump Zone Proxy Server from the dropdown on the Proxy tab. With Jump Zone Proxy Server selected, this Jumpoint can be used to proxy connections for clients on the network that do not have a native internet connection, such as POS systems. Using a Jumpoint as a proxy will route traffic only to the appliance. A Jumpoint can also be used to proxy Jump Client connections. For more information on deploying Jump Clients, see the Jump Client Guide.

In order for a Jumpoint to function as a Jump Zone Proxy Server, its host system cannot reside behind a proxy. The Jumpoint must be able to access the Internet without having to supply proxy information for its own connection.

  1. Enter the hostname to use at the listening interface, and set which port to use.


Host and port fields should be set carefully since any Jump Client deployed using this Jumpoint as a proxy server will use the settings available to it at the time of deployment and will not be updated should the host or port change. If the host or port must be changed, the Jump Client would need to be redeployed.

  1. Set whether to allow all IP addresses or to limit the IPs that can connect through this proxy.
  2. If allowing or denying access, enter one IP address or CIDR subnet range per line.

It is a best practice to make an exception in the Windows firewall for the port on which the proxy server will listen for the process which will be accepting connections.

Jumpoint Setup Completion and Revision

BeyondTrust Jumpoint Setup Complete

After installing the Jumpoint, you will receive a confirmation message. Click Finish.

Once the Jumpoint has been installed, the configuration options can be modified by locating the BeyondTrust folder in the Windows All Programs or Programs and Features menu, opening the site subfolder, and running BeyondTrust Jumpoint Configuration.


Clustered Jumpoint Setup: Adding Nodes

The steps for creating a clustered Jumpoint in /login are the same as for a standalone, except that once you have created the clustered Jumpoint, you can add nodes to it. At least one node needs to be installed for the Jumpoint to be online.

Click the Add Node link to download either the 32-bit or 64-bit installer file.

If you are at the system you want to use as the Jumpoint host, you can run the installation file immediately.

Otherwise, save the file and then email it to the remote user to deploy on the system that will serve as the Jumpoint host.

Jumpoint Cluster Add Node

Follow the prompts and install the node. Note that there are no configuration screens of any kind. Once installed, the clustered Jumpoint will show the new node(s) installed, associated information, such as the public and private IP addresses, whether a node is online or offline, as well as the number of nodes installed.

Nodes can be deleted but cannot be individually edited. In the access console, none of the nodes are visible, only the Jumpoint under which they are installed. Nodes function as redundant connection points. When a user needs to use the Jumpoint, one of the nodes will be selected randomly. At least one node must be online for the Jumpoint to work.