Use Jump Clients to Access Unattended Computers

To access an individual computer without end-user assistance, install a Jump Client on that system either from within a session or from the Jump Clients page of the administrative interface. Your account permissions may disallow you from using Jump Clients, or you may be allowed to Jump but not to deploy the clients yourself. You also may be allowed to pin clients to your personal queue or only to one of your team queues. You may be disallowed to set passwords, or you may be allowed to access all Jump Clients without needing a password.

The Jump Interface

Load Jump Client List

Jump Clients appear below the queues pane of the representative console. Click Refresh to see the Jump Clients available to you. The list may contain both active and passive Jump Clients. [See Active and Passive Jump Clients]

Jump Clients are grouped according to who can access them – only the representative who created them, a particular team, or all representatives. You may see Jump Clients pinned to your personal queue and to your team queues, as well as to other teams whose Jump Clients your team has been granted access to. Team Managers and Team Leads can also view Jump Clients that team members of a lower role have pinned to their personal queues.

Jump Clients Menu

Jump to a Jump Item

Browse through groups or dynamically search for computers. Once you have found the computer you wish to access, double-click the entry, or select the entry and click the Jump button. This will attempt to start a session with the remote computer.

Note: If you need to access Jump Clients when no user is available, make sure the session permissions are set either to disable prompting or to default to Allow for unattended sessions.

Attempt to Wake Up Jump Client

Depending on the permissions set by your administrator, you may also be able 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 representative will have an advanced option to provide a password for WOL environments that require a secure WOL password.

Jump Client Access from Script

You may programmatically connect to a Jump Client directly from your systems management or ticketing tool. If your search results in only one Jump Client, the session will start immediately. If multiple Jump Clients are returned, select one of the Jump Clients listed in the selection window and click OK.

Note: For details about scripting, see www.bomgar.com/docs/content/integrations/api/client-script.

 

Jump Client Properties

Jump Client Properties

Organize and manage Jump Clients by selecting one or more Jump Clients and clicking Properties.

To review properties of other types of Jump items, please see the appropriate section in this guide.

Jump Clients include a Comments field for a name or description, making sorting, searching, and identifying Jump Clients faster and easier.

Move Jump Clients from one queue to another by selecting a team or representative queue from the Location dropdown. The ability to move Jump Clients to or from different queues depends upon your account permissions. Note that multiple support teams and Embassies may be able to access Jump Clients pinned to one team queue, depending on rules set by your Bomgar software administrator.

Select the Public Portal through which this Jump Client should connect. If a session policy is assigned to this public portal, that policy may affect the permissions allowed in sessions started through this Jump Client. The ability to set the public portal depends on your account permissions.

Further organize Jump Clients by entering the name of a new or existing group. While the selected Jump Clients will be grouped together under the group name, they will still be listed under the queue in which each is pinned. To move a Jump Client back into its top-level group, leave this field blank.

Change a Jump Client's mode from the Connection dropdown. Active Jump Clients send statistics to the Bomgar Appliance on a defined interval. Passive Jump Clients send statistics to the Bomgar Appliance once a day or upon a manual check in. Based on the options your administrator sets, these statistics may include the remote computer’s logged-in console user, operating system, uptime, CPU, disk usage, and a screen shot from the last update.

Once a Jump Client has a password set, its icon will show that it is locked, and its screen shot will also be locked. In order to Jump to a locked Jump Client, you must provide its password. Also, you must provide the password to remove a locked Jump Client via the Jump Client interface; you do not need the password to unpin from within a session, as you would already have provided the password to Jump into the session.

If Start Quietly is checked, the customer client will not take focus and will remain minimized in the taskbar or dock when a session is started.

Choose session policies to assign to this Jump Client. Session policies assigned to this Jump Client have the highest priority when setting session permissions. The Customer Present Session Policy applies when the end user is determined to be present. Otherwise, the Customer Not Present Session Policy applies. Customer presence is detected when the Jump Client session starts. The session policy used for the session does not change throughout the session, regardless of any changes in the customer's presence while the session is in progress. The ability to set a session policy depends on your account permissions.

To set when representatives are allowed to access this Jump Client, choose a Jump Policy. These policies are configured by your administrator in the /login interface.

New Jump Client Properties

When pinning a Jump Client from within a session and customizing its properties beforehand, you also have the option to set when the Jump Client expires. This can be never, at a specific time and date, or after a certain length of time. An expired Jump Client automatically uninstalls from the remote system and is removed from the list in the Jump Client interface.

 

If you no longer need access to a remote desktop, select the Jump Client and click the Remove button, or right-click on the Jump Client and select Remove from the menu. If the remote user manually uninstalls the Jump Client, it will remain in your queue, along with the statistics from its last update, but you will not be able to access that computer. You may select multiple Jump Clients to remove them all at the same time.

Note: If a Jump Client goes offline and does not connect back to the Bomgar Appliance for 180 days, it will automatically be uninstalled from the target computer and will be removed from the representative console queue.

Active and Passive Jump Clients
Active Jump Client Passive Jump Client

Maintains a persistent connection to the Bomgar Appliance.

Listens for a remote access request from the Bomgar Appliance.

Note: Some firewall configuration may be required.

Sends statistics to the Bomgar Appliance at regular intervals.

Sends statistics to the Bomgar Appliance once a day or upon manual check-in.

Enables remote access to any desktop operating system supported by Bomgar.

Enables remote access to any desktop operating system supported by Bomgar.

Number of installable clients is limited by your Bomgar Appliance model.

B200 B300 B400
Up to 1,000 Active Jump Clients Up to 5,000 Active Jump Clients Up to 10,000 Active Jump Clients

 

Number of installable clients is limited by your Bomgar Appliance model.

B200 B300 B400
Up to 1,000 Passive Jump Clients Up to 5,000 Passive Jump Clients Up to 10,000 Passive Jump Clients

If you need more passive Jump Clients, visit www.bomgar.com/help.

Note: The maximum number of Jump Clients available to a Virtual Appliance is based on allocated resources. See the Virtual Appliance Sizing Guidelines at www.bomgar.com/docs.

Tip: Passive Jump Clients are designed to support a large number of Jump Clients within an internal network. Active Jump Clients are highly recommended if you do not control the remote network [e.g., customers' desktops] or if the remote network is unknown [e.g., laptops].