Jump Client Settings
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 operating system, uptime, console user, CPU, disk usage, and a thumbnail of the remote screen.
The Active Jump Client Statistics Update Interval determines how often these statistics are updated. Managing which statistics are viewed and how often can help to regulate the amount of bandwidth used. The more active Jump Clients you have deployed, the fewer the statistics and the longer the interval may need to be.
Also set the maximum number of Jump Clients to upgrade at the same time. Note that if you have a large number of Jump Clients deployed, you may need to limit this number to regulate the amount of bandwidth consumed. You may further regulate the bandwidth used during upgrades by setting Maximum bandwidth of concurrent Jump Client upgrades.
Note: Neither of these settings affects Console upgrades or Bomgar Button deployments.
Allow simultaneous representative access to a single Jump Client provides a way for multiple representatives to gain simultaneous access to the same Jump Client without having to be invited to join an active support session by another representative. The first representative to access the Jump Client maintains ownership of the session. Representatives in a shared Jump session will see each other and be able to chat.
Restrict Local Uninstall/Disable of Jump Clients limits the remote user’s ability to uninstall or disable Jump Clients from the right-click context menu, reducing the need to reinstall Jump Clients that should not have been uninstalled. If this option is enabled, only users with appropriate privileges on the target machine may uninstall the Jump Client via the host system's "uninstall programs" mechanism.
Set whether ad-hoc Jump Clients pinned during a session should by default be active or passive. The Passive Jump Client Port specifies which port a passive Jump Client will use to listen for a "wake up" command from the appliance. Ensure that firewall settings allow inbound traffic on this port for your hosts with passive Jump Clients. Once awake, Jump Clients always connect to the appliance on port 80 or 443 outbound.
Jump Clients allow for one of two modes of behavior, active or passive. The default mode can be set from the Configuration > Jump Clients page, and the mode can be switched from the Jump interface of the representative console.
A Jump Client in active mode maintains a persistent connection to the Bomgar Appliance, waiting for session requests. It sends statistics updates as frequently as once per minute, as defined in the Jump Client Settings on the Configuration > Jump Clients page.
A passive Jump Client does not maintain a connection to the appliance but rather listens for connection requests. It sends statistics updates only once per day or upon manual check-in. By setting Jump Clients to passive mode, you can have a larger number of deployed Jump Clients without markedly increasing the appliance load.
In order to use a passive Jump Client, the appliance must be able to initiate contact with the computer on which the passive Jump Client is installed. This requirement may necessitate that you modify firewall rules to allow incoming connections to the target computer through the configured listen port. By default, this port is 5832; this can be modified from the Configuration > Jump Clients page.
Passive mode may best be used on internal systems rather than external ones, although with correct firewall configurations, it may be used in either implementation. The following table presents key differences between the two modes.
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].