Use Jump shortcuts

Create Jump Shortcuts to start standard support sessions, to start Remote Desktop Protocol sessions or VNC sessions, to Shell Jump to SSH-enabled or Telnet-enabled network devices, or to start Intel® vPro sessions.

When creating a large number of Jump shortcuts, it may be easier to import them via a spreadsheet than to add them one by one in the representative console. Go to /login > Jump > Jump Items. From the dropdown in the Jump Shortcuts Mass Import Wizard section, select the type of Jump Item you wish to add, and then click Download Template. Using the text in the CSV template as column headers, add the information for each Jump shortcut you wish to import. If any required fields are missing, import fails. Optional fields can be filled in or left blank.

Once you have completed filling out the template, use Import Jump Shortcuts to upload the CSV file containing the Jump Item information. The maximum file size allowed to be uploaded at one time is 5 MB. Only one type of Jump Item can be included in each CSV file. The CSV file should use the format described in the tables below.

Local Jump Shortcut help

Remote Jump Shortcut help

Local VNC Jump Shortcut help

Remote VNC Jump Shortcut help

Remote RDP Jump Shortcut help

Local RDP Jump Shortcut help

Shell Jump Shortcut help

Intel vPro Shortcut help

Remote or Local Jump shortcuts

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 Jumpoint.

A Jumpoint acts as a conduit for access to computers on a known remote network. A single Jumpoint 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 Jumpoint.

ℹ️

Note

Remote Jump and Local Jump are available only for Windows systems. Jump Clients are needed for remote access to Mac computers. To Jump 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.

Create a Remote Jump shortcut

To create a Remote Jump shortcut, click the Create button in the Jump interface. From the dropdown, select Remote Jump. Remote Jump shortcuts appear in the Jump interface with Jump Clients and other types of Jump Item shortcuts.

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

ℹ️

Note

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

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

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

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

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

Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.

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

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

Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item 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 Jump Item. Session policies assigned to this Jump Item 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 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.

Create a Local Jump shortcut

To create a Local Jump shortcut, click the Create button in the Jump interface. From the dropdown, select Local Jump. Local Jump shortcuts appear in the Jump interface with Jump Clients and other types of Jump Item shortcuts.

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

ℹ️

Note

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

Enter a Name for the Jump Item. 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 Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.

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

Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.

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

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

Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item 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 Jump Item. Session policies assigned to this Jump Item 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 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.

Use a Jump shortcut

To use a Jump shortcut to start a session, select the shortcut from the Jump 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.

ℹ️

Note

• If you need to access systems through a Jumpoint 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.
• Jump Items can be set to allow multiple users to simultaneously access the same Jump Item. If set to Join Existing Session, other users are able to join a session already underway. The original owner of the session receives a note indicating another user has joined the session, but is not allowed to deny them access.

Local or Remote RDP shortcuts

Use BeyondTrust to start a Remote Desktop Protocol (RDP) session with a remote Windows or Linux System. Because RDP sessions are converted to BeyondTrust sessions, users can share or transfer sessions, and sessions can be automatically audited and recorded as your administrator has defined for your site.

To use Local RDP through BeyondTrust, you must be on the same network segment as the target system and must have the user account permission Allowed Jump Methods: Local RDP.

To use Remote RDP through BeyondTrust, you must have access to a Jumpoint and must have the user account permissions Allowed Jump Methods: Remote RDP.

Create a Local RDP shortcut

1. To create a Local Microsoft RDP shortcut, click the Create button in the Jump interface. From the dropdown, select Local RDP. RDP shortcuts appear in the Jump interface with Jump Clients and other types of Jump Item shortcuts.
2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

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

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. Enter the Hostname / IP of the system you wish to access.

ℹ️

Note

By default, the RDP server listens on port 3389, which is therefore the default port BeyondTrust attempts. If the remote RDP server is configured to use a different port, add it after the hostname or IP address in the form of : or : (for example, 10.10.24.127:40000).

5. Provide the Username to sign in as, along with the Domain.
6. Select the Quality at which to view the remote screen. This cannot be changed during the RDP session. Select the color optimization mode to view the remote screen. If you are going to be primarily sharing video, select Video Optimized; otherwise, select between Black and White (uses less bandwidth), Few Colors, More Colors, or Full Color (uses more bandwidth). Both Video Optimized and Full Color modes allow you to view the actual desktop wallpaper.
7. To start a console session rather than a new session, check the Console Session box.
8. If the server's certificate cannot be verified, you receive a certificate warning. Checking Ignore Untrusted Certificate allows you to connect to the remote system without seeing this message.
9. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
10. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
11. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
    Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
12. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.
13. Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Create a Remote RDP shortcut

1. To create a Remote Microsoft RDP shortcut, click the Create button in the Jump interface. From the dropdown, select Remote RDP. RDP shortcuts appear in the Jump interface with Jump Clients and other types of Jump Item shortcuts.
2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

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

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. From the Jumpoint dropdown, select the network that hosts the computer you wish to access. The representative console remembers your Jumpoint choice the next time you create this type of Jump Item. Enter the Hostname / IP of system you wish to access.

ℹ️

Note

By default, the RDP server listens on port 3389, which is therefore the default port BeyondTrust attempts. If the remote RDP server is configured to use a different port, add it after the hostname or IP address in the form of : or : (for example, 10.10.24.127:40000).

5. Provide the Username to sign in as, along with the Domain.
6. Select the Quality at which to view the remote screen. This cannot be changed during the RDP session. Select the color optimization mode to view the remote screen. If you are going to be primarily sharing video, select Video Optimized; otherwise, select between Black and White (uses less bandwidth), Few Colors, More Colors, or Full Color (uses more bandwidth). Both Video Optimized and Full Color modes allow you to view the actual desktop wallpaper.
7. To start a console session rather than a new session, check the Console Session box.
8. If the server's certificate cannot be verified, you receive a certificate warning. Checking Ignore Untrusted Certificate allows you to connect to the remote system without seeing this message.
9. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
10. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
11. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
    Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
12. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.
13. Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Use an RDP shortcut

1. To use a Jump shortcut to start a session, select the shortcut from the Jump interface and click the Jump button.
2. You are prompted to enter the password for the username you specified earlier.
3. Your RDP session now begins. Begin screen sharing to view the remote desktop. You can send the Ctrl-Alt-Del command, capture a screenshot of the remote desktop, and share clipboard contents. You can also share or transfer the RDP session with other logged-in BeyondTrust users, following the normal rules of your user account settings.

Multi-monitor support

An option allows you to open a Remote Support connection expanded across all the monitors on the client computer regardless of the client monitor configuration. With this feature, you can fully utilize all the monitors connected to the client computer, therefore being able to adjust screen sizing and scaling during an RDP session across multiple monitors.

ℹ️

Note

• If you are using full screen view while using this feature, the remote system is displayed across all of your monitors.
• Jump Items can be set to allow multiple users to simultaneously access the same Jump Item. If set to Start New Session, then a new independent session starts for each user who Jumps to a specific RDP Jump Item. The RDP configuration on the endpoint controls any further behavior regarding simultaneous RDP connections.

Local or Remote VNC shortcuts

Use BeyondTrust to start a VNC session with a remote system. Because VNC sessions are converted to BeyondTrust sessions, users can share or transfer sessions, and sessions can be automatically audited and recorded as defined by your administrator for your site.

To use Local VNC through BeyondTrust, you must be on the same network segment as the target system and must have the user account permission Allowed Jump Methods: Local VNC.

To use Remote VNC through BeyondTrust, you must have access to a Jumpoint and must have the user account permission Allowed Jump Methods: Remote VNC.

Use BeyondTrust to start a VNC session with a remote system. Because VNC sessions are converted to BeyondTrust sessions, users can share or transfer sessions, and sessions can be automatically audited and recorded as defined by your administrator for your site.

To use Local VNC through BeyondTrust, you must be on the same network segment as the target system and must have the user account permission Allowed Jump Methods: Local VNC.

To use Remote VNC through BeyondTrust, you must have access to a Jumpoint and have the user account permission Allowed Jump Methods: Remote VNC.

Create a Local VNC shortcut

1. To create a Local VNC shortcut, click the Create button in the Jump interface. From the dropdown, select Local VNC. VNC shortcuts appear in the Jump interface along with Jump Clients and other types of Jump Item shortcuts.
2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

To view the properties of multiple Jump Items, the items selected must be the same type (e.g., all Jump Clients, all Remote Jumps, etc.).

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. Enter the Hostname / IP of the system you wish to access.
5. By default, the VNC server listens on port 5900, which is, therefore, the default port BeyondTrust attempts. If the remote VNC server is configured to use a different port, enter it in the Port field.
6. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
7. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
8. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
9. Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
10. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.
11. Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Create a Remote VNC shortcut

1. To create a Remote VNC shortcut, click the Create button in the Jump interface. From the dropdown, select Remote VNC. VNC shortcuts appear in the Jump interface along with Jump Clients and other types of Jump Item shortcuts.
2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

To view the properties of multiple Jump Items, the items selected must be the same type (e.g., all Jump Clients, all Remote Jumps, etc.).

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. From the Jumpoint dropdown, select the network that hosts the computer you wish to access. The representative console remembers your Jumpoint choice the next time you create this type of Jump Item. Enter the Hostname / IP of system you wish to access.
5. By default, the VNC server listens on port 5900, which is the default port BeyondTrust attempts. If the remote VNC server is configured to use a different port, enter it in the Port field.
6. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
7. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
8. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
9. Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
10. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.
11. Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Use a VNC shortcut

1. To use a Jump shortcut to start a session, select the shortcut from the Jump interface and click the Jump button.
2. When establishing the connection to the VNC server, the system prompts you to enter the user name and password.
3. Your VNC session now begins. Begin screen sharing to view the remote desktop.
   You can send the Ctrl-Alt-Del command, capture a screenshot of the remote desktop, and share clipboard text contents. You also can share, transfer, or record the VNC session, following the normal rules of your user account settings.

ℹ️

Note

Jump Items can be set to allow multiple users to simultaneously access the same Jump Item. If set to Join Existing Session, other users are able to join a session already underway. The original owner of the session receives a note indicating another user has joined the session, but is not allowed to deny them access.

Shell Jump shortcuts

With Shell Jump, quickly connect to an SSH-enabled or Telnet-enabled network device to use the command line feature on that remote system. For example, run a standardized script across multiple systems to install a needed patch, or troubleshoot a network issue.

Create a Shell Jump shortcut

1. To create a Shell Jump shortcut, click the Create button in the Jump interface. From the dropdown, select Shell Jump. Shell Jump shortcuts appear in the Jump interface along with Jump Clients and other types of Jump Item shortcuts.

ℹ️

Note

Shell Jump shortcuts are enabled only if their Jumpoint is configured for open or limited Shell Jump access.

2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

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

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. From the Jumpoint dropdown, select the network that hosts the computer you wish to access. The representative console remembers your Jumpoint choice the next time you create this type of Jump Item. Enter the Hostname / IP of system you wish to access.
5. Choose the Protocol to use, either SSH or Telnet.
6. Port automatically switches to the default port for the selected protocol but can be modified to fit your network settings.
7. Enter the Username.
8. Select the Terminal Type, either xterm or VT100.
9. You can also select to Send Keep-Alive Packets to keep idle sessions from ending. Enter the number of seconds to wait between each packet send.
10. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
11. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
12. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
13. Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
14. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.
15. Choose a Session Policy to assign to this Jump Item. The session policy assigned to this Jump Item has the highest priority when setting session permissions. The ability to set a session policy depends on your account permissions.

Use a Shell Jump shortcut

1. To use a Jump shortcut to start a session, select the shortcut from the Jump interface and click the Jump button.
   If attempting to Shell Jump to an SSH device without a cached host key, you receive an alert that the server's host key is not cached and that there is no guarantee that the server is the computer you think it is.
2. If you choose Save Key and Connect, then the key is cached on the Jumpoint's host system so that future attempts to Shell Jump to this system do not result in this prompt. Connect Only starts the session without caching the key, and Abort ends the Shell Jump session.
3. If you Shell Jump to an SSH device with keyboard interactive MFA enabled, there is a secondary prompt for input.
4. When you Shell Jump to a remote device, a command shell session immediately starts with that device. If you Shell Jump to a provisioned SSH device with an unencrypted key or with an encrypted key whose password has been cached, you are not prompted for a password. Otherwise, you are required to enter a password. You can then send commands to the remote system.

Intel vPro Jump shortcuts

Using Intel® Active Management Technology, privileged users can support fully provisioned Intel vPro Windows systems below the OS level, regardless of the status or power state of these remote systems.

Create an Intel® vPro shortcut

1. To create an Intel® vPro shortcut, click the Create button in the Jump interface. From the dropdown, select Intel® vPro. Intel® vPro shortcuts appear in the Jump interface along with Jump Clients and other types of Jump Item shortcuts.
2. Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

ℹ️

Note

To view the properties of multiple Jump Items, the items selected must be the same type (e.g., all Jump Clients, all Remote Jumps, etc.).

3. Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.
4. From the Jumpoint dropdown, select the network that hosts the computer you wish to access. The representative console remembers your Jumpoint choice the next time you create this type of Jump Item. Enter the Hostname / IP of system you wish to access.
5. Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.
6. Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.
7. Select the Public Portal through which this Jump Item 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 Item. The ability to set the public portal depends on your account permissions.
8. Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.
9. To set when users are allowed to access this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.

Use an Intel® vPro shortcut

Depending on your Jumpoint setup, you may be prompted to enter a username and password.

The Jumpoint detects the provisioned vPro hardware. If the credentials, provided during either the Jumpoint configuration or the Jump attempt, match the credentials of the vPro-provisioned system, the connection is initiated.

Depending on how the vPro computer is provisioned, you might be prompted to enter a user consent code before performing certain actions.

If a consent code is required, a pop-up appears on the remote screen. An end user must provide you with this code before you can gain hardware access.

Once the connection is made, you have control of the remote vPro hardware. You can then use the vPro session tools to work on the remote system.

ℹ️

Note

Jump Items can be set to allow multiple users to simultaneously access the same Jump Item. If set to Join Existing Session, other users are able to join a session already underway. The original owner of the session receives a note indicating another user has joined the session, but is not allowed to deny them access.