Assets | RS for Desktop

Remote Jump enables a privileged user to connect to an unattended remote computer on a network outside of their own network. Remote Jump depends on a Gateway.

A Gateway acts as a conduit for access to computers on a known remote network. A single Gateway installed on a computer within a LAN is used to access multiple systems, eliminating the need to pre-install software on every computer you might need to access.

Local Jump enables a privileged user to connect to an unattended remote computer on their local network. Within the local area network, the BeyondTrust user's computer can initiate a session to a Windows or Linux system directly without using a Gateway.

ℹ️

• Remote Jump and Local Jump are available only for Windows systems. Jump Clients are needed for remote access to Mac computers. To connect to a Windows computer without a Jump Client, that computer must have Remote Registry Service enabled (disabled by default in Vista) and must be on a domain.
• To view the properties of multiple Assets, the items selected must be the same type (e.g., all Jump Clients, all Remote Jumps, etc.). To review properties of other types of Assets, see the appropriate section in this guide.

Enter a Name for the Asset. This name identifies the item in the session tabs. This string has a maximum of 128 characters.

From the Gateway dropdown, select the network that hosts the computer you wish to access. The representative console remembers your Gateway choice the next time you create this type of Asset. Enter the Hostname / IP of system you wish to access.

Move Assets from one Asset Group to another using the Asset Group dropdown. The ability to move Assets to or from different Asset Groups depends upon your account permissions.

Further organize Assets by entering the name of a new or existing Tag. Even though the selected Assets are grouped together under the tag, they are still listed under the Asset Group in which each is pinned. To move an Asset back into its top-level Asset Group, leave this field blank.

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

Assets include a Comments field for a name or description, which makes sorting, searching, and identifying Assets faster and easier.

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

Choose a Session Policy to assign to this Asset. The session policy assigned to this Asset has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Choose session policies to assign to this Asset. Session policies assigned to this Asset 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.

The way customer presence is determined is set by the Use screen state to detect Customer Presence Asset 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 Asset 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.

Create a Local Asset

To create a Local Asset, click the Create button in the Asset Management Interface. From the dropdown, select Local Jump. Local Assets appear in the Asset Management Interface with Jump Clients and other types of Asset shortcuts.

Organize and manage existing Assets by selecting one or more Assets and clicking Properties.

ℹ️

To view the properties of multiple Assets, the items selected must be the same type (e.g., all Jump Clients, all Remote Jumps, etc.). To review properties of other types of Assets, see the appropriate section in this guide.

Enter a Name for the Asset. This name identifies the item in the session tabs. This string has a maximum of 128 characters.

Enter the Hostname / IP of the system you wish to access.

Move Assets from one Asset Group to another using the Asset Group dropdown. The ability to move Assets to or from different Asset Groups depends upon your account permissions.

Further organize Assets by entering the name of a new or existing Tag. Even though the selected Assets are grouped together under the tag, they are still listed under the Asset Group in which each is pinned. To move an Asset back into its top-level Asset Group, leave this field blank.

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

Assets include a Comments field for a name or description, which makes sorting, searching, and identifying Assets faster and easier.

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

Choose a Session Policy to assign to this Asset. The session policy assigned to this Asset has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Choose session policies to assign to this Asset. Session policies assigned to this Asset 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.

The way customer presence is determined is set by the Use screen state to detect Customer Presence Asset 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 Asset 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.

Use an Asset

To use an Asset to start a session, select the shortcut from the Asset Management Interface and click the Jump button.

You must provide administrative credentials to the remote computer in order to complete the Jump. The administrative rights must be either a local administrator on the remote system or a domain administrator.

The client files are pushed to the remote system, and a session attempts to start. Depending on the session permissions, the end-user may be prompted to accept or deny the session. If no response is received within a defined interval of time, the session either starts or cancels, again depending on the session permissions.

ℹ️

If you need to access systems through a Gateway when no user is available, make sure the public portal permissions and your account permissions are set either to disable prompting or to default to Allow.