Jump | PRA Cloud

Install on Windows systems

Windows instructions

Mass deploy on Windows

Install on Linux

Linux instructions

Install on Mac systems

Mac instructions

Mass deploy on macOS

Deploy a Jump Client on a Raspberry Pi

Raspberry Pi instructions

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:

Select your desired platform and click Download.
Copy the provided command into your command line interface (CLI), or click Download to download the .msi installer file.
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 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.

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

Maintenance

Field Name	Description
Number of days before Jump Clients that have not connected are automatically deleted	This 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 lost	This 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 Behavior	If 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.

Field Name

Description

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

This 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 lost

This 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 Behavior

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

Updated 3 months ago