present. Otherwise, the Customer Not Present Session Policy applies.The way customer presence is determined is set
by the Use screen state to detect Customer Presence Jump Item setting in the /login interface. When enabled, a
customer is considered present only if a user is logged in, the system is not locked, and a screen saver is not running.
When disabled, a customer is considered present if a user is logged in, regardless of the screen state. Customer presence
is detected when the Jump Item 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.
3. Alternatively, you can select a Jump Group to which to pin the Jump Client, not setting any properties. From the Jump Group
dropdown, select whether to pin the Jump Client to your personal list of Jump Items or to a Jump Group shared by other users.
Pinning to your personal list of Jump Items means that only you (and higher ranking roles on your team, such as Team Lead and
Team Manager if you are a Team Member, and Team Manager if you are a Team Lead) can access this remote computer through
this Jump Client. Pinning to a shared Jump Group makes this Jump Client available to all members of that Jump Group.
4. Depending on the session permissions, the customer could receive a message that you are requesting to install a Jump Client.
The customer is asked to allow or refuse the request.
5. Once the Jump Client is installed, the remote computer appears in the Jump interface of the representative console. You might
have to refresh the interface to see the new Jump Client.
Support representatives can access unattended Android devices through session pinning. For more information, please see
Initiate an Android Support Session at www.beyondtrust.com/docs/remote-support/getting-started/customer-
client/android/android-support.htm.
Prior to Support
Jump Clients can be installed on remote computers in anticipation of the need for remote access. This method of installation can be
applied to one system or multiple systems simultaneously. You can easily automate the mass deployment of your Jump Client network by
allowing customization during installation. The Jump Client command line installer has switches that allow a script to modify a variety of
Jump Client parameters when executed. This enables you to create custom mass deployment scripts to pull in variables from other
sources and use the variables to modify the Jump Client parameters at install time.
You can easily manage active installers from the Jump Client Installer list. This list shows all previously installed active Jump Client
installers. Administrators and privileged users can view, download, delete, or extend Jump Client installers.A warning message appears at
the top of the list: Installing more than one Jump Client as the same user or more than one Jump Client as a service on the same system is
being phased out in a future release. In the Representative Console you may use the copy action on a Jump Client to apply different
policies to the same endpoint. Click Dismiss to remove the warning message.
1. From the /login administrative interface, go to Jump > Jump Clients.
2. At the top of the Jump Client Installer List, click Add.
3. From the Jump Group dropdown, select whether to pin the Jump
Client to your personal list of Jump Items or to a Jump Group shared
by other users. Pinning to your personal list of Jump Items means
that only you (and higher ranking roles on your team, such as Team
Lead and Team Manager if you are a Team Member, and Team
Manager if you are a Team Lead) can access this remote computer
through this Jump Client. Pinning to a shared Jump Group makes
this Jump Client available to all members of that Jump Group.
4. Select the Public Portal through which you want this Jump Client to
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.
SALES: www.beyondtrust.com/contact
SUPPORT: www.beyondtrust.com/support
DOCUMENTATION: www.beyondtrust.com/docs
16
©2003-2024 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or
depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.
TC: 7/9/2024
REMOTE SUPPORT
JUMP CLIENT GUIDE