Use a Jumpoint to Jump to a Remote System
Once a Jumpoint has been installed on a remote network, permitted representatives can use the Jumpoint to initiate sessions with Windows computers on that same network, even if those computers are unattended. Additionally, a permitted representative can Jump to computers on the same network segment as their local system, even without a Jumpoint.
A Jumpoint can be used to start a standard support session, to start a Remote Desktop Protocol session with a Windows system, to Shell Jump to a SSH-enabled or Telnet-enabled network device, or to start a session with an Intel® vPro Windows system.
To Jump through a Jumpoint, you must have access to a Jumpoint and must have the user account permission Allowed Jump Methods: Remote Jump via a Jumpoint. To Jump on your local network, you must have the user account permission Allowed Jump Methods: Local Jump on the local network.
To Jump without a pre-installed client, open the Jump to… dialog from:
- The Support menu of the representative console
- The Start button at the top of the representative console
- The Jump To button at the top of the representative console
From the Jumpoint dropdown, select the network that hosts the computer you wish to access. Depending on your account permissions, you can Jump to a system on your local network or a network on which a Jumpoint is installed.
Enter the hostname or IP address of the system you wish to access. Alternatively, if network browsing is enabled from the /login > Jump > Jumpoint page, you can click the [...] button to browse the directory tree.
Once you have located the computer you wish to access, click Jump.
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 will be pushed to the remote system, and a session will attempt to start.
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.