Add a Jump Client to an endpoint
Overview
This workflow shows you how to install a Jump Client on a Windows or Linux endpoint so that
your team can connect to it remotely through Privileged Remote Access (PRA). After you
complete this workflow, the endpoint appears as a Jump Item in the PRA console and is
available for remote sessions.
Before you begin
- You have administrator access to the PRA administrative interface.
- The target endpoint has internet access or network access to the PRA appliance.
- You have local administrator rights on the target endpoint (or can deploy software to it).
- PRA is licensed and your Jump Group is configured. If you have not yet created a Jump
Group, set one up before continuing.
Why this is important
Without a Jump Client, your team cannot connect to an endpoint through PRA. Installing
one removes the need for a VPN or shared credentials. PRA records every session, so your
organization maintains a full audit trail of who accessed each system and what they did.
Steps summary
| Step | Action |
|---|---|
| 1 | Sign in to the PRA administrative interface |
| 2 | Open the Jump Clients installer page |
| 3 | Configure and download the Jump Client installer |
| 4 | Run the installer on the target endpoint |
| 5 | Confirm the Jump Client appears in the console |
| 6 | Assign the Jump Client to a Jump Group |
Steps
-
Open a browser and go to your PRA appliance URL. Sign in with your administrator
credentials. -
In the left navigation, select Jump > Jump Clients.
-
Select Create New Jump Client. The installer configuration form opens.
-
In the Jump Group field, select the Jump Group you want this endpoint to belong to.
-
In the Name field, enter a display name for the endpoint. Use a name that makes the
system easy to identify — for example,PROD-WEBSERVER-01. -
Set any additional options that apply to your environment:
- Connection type: Select Active to have the Jump Client maintain a persistent
connection to PRA. Select Passive if the endpoint is behind a firewall that blocks
outbound connections. - Tag: Enter a tag if you want to group this Jump Client with others for filtering.
- Comments: Add notes about the system for other administrators.
- Connection type: Select Active to have the Jump Client maintain a persistent
-
Select Download Installer. PRA generates a pre-configured installer file. Save it
to a location you can access from the target endpoint. -
On the target endpoint, run the installer file:
- Windows: Double-select the
.exeinstaller. If prompted by User Account Control,
select Yes to allow the installation. - Linux: Open a terminal and run the installer with elevated privileges:
sudo ./bomgar-scc-<version>.bin
- Windows: Double-select the
-
Wait for the installation to complete. The Jump Client service starts automatically.
-
Return to the PRA administrative interface. Select Jump > Jump Clients and confirm
that the new endpoint appears in the list with a status of Connected. -
If the Jump Client does not appear within two minutes, verify that the endpoint can
reach the PRA appliance on port 443. Check the endpoint's firewall and proxy settings.
Assign the Jump Client to a Jump Group
If you did not select a Jump Group during configuration, or if you need to move the Jump
Client after installation, you can assign it now.
- In Jump > Jump Clients, locate the Jump Client in the list.
- Select the Jump Client name to open its details.
- In the Jump Group field, select the correct Jump Group.
- Select Save.
Verify the results
Confirm that the Jump Client appears in Jump > Jump Clients with a status of
Connected. Verify that the Jump Client is listed under the correct Jump Group. To
confirm end-to-end access, open the Representative Console or Access Console, locate the
Jump Item, and start a test session.
Next steps
- Set up an access policy to control who can connect to this Jump Item:
Users & Security > Access Policies - Add vault credentials for this endpoint so PRA can inject them during sessions:
Vault > Accounts - Deploy Jump Clients to multiple endpoints at once using the silent installer. Contact
your PRA administrator or refer to the PRA documentation for silent install flags.
Updated about 2 hours ago