A browser console allows you to access a remote server through a web browser.
To add or launch a browser console, enable Browser Consoles for a client.
- A user with Consoles Manage permission can add, edit, or remove a console.
- A user with Consoles View permission can view consoles created by other users.
- A user can configure preference of browser console setting from the user preference setting option.
The following are prerequisites for launching browser consoles:
- An HTML-enabled browser is required to launch a browser console.
- Browser consoles (and its related features) should be activated for the client.
- Agent version 7.0.0 (or higher).
- Gateway version 5.5.0 (or higher).
- Verify that you have whitelisted specific IPs. If you have not whitelisted the IP addresses, see Public IP addresses for the list.
- Whitelisted IPs must have both inbound and outbound communication to access remote consoles.
Type of supported protocols
The types of supported protocols supported by the browser console are the following:
Browser consoles provide the following key features:
- Playback console recording
- Clipboard access
- Shared Drive
Adding browser consoles
Add the details of the remote device to launch a browser console. Remote device information must be provided to launch browser consoles.
A general recommendation is to select the Network Level Authentication (NLA) option on the remote Windows device for secure communication. RDP operates on NLA which is a secured channel of communication. Connecting users must be aware of NLA settings on the target device.
If NLA is enabled on the target device, connecting users can access the target device only with certain authentication. The following are the key considerations for adding consoles:
- With domain: (Mandatory) Provide username, password, and domain values for credential sets.
- Without domain: (Mandatory) Provide username and password for manual login.
If NLA is disabled on the target device, connecting users can access the target device without any authentication. Username and password fields can be left empty in manual login.
NoteNLA is mandatory for Windows 2016 and above versions.
Launching browser consoles
To launch a browser console:
- Go to Infrastructure and select the category associated to the target resource.
- Click the device name to launch a browser console.
- From the resource Overview page, click the Consoles button.
- From the console list, click the browser console icon associated with the console name.
- Provide Ticket ID/Alert ID to associate the console activity to a ticket.
- For Activity Log Note, provide comments (required) for browser console activity.
- Select one of the following:
- Use Credentials: If credentials are available in a credential set, select the set from the Credentials drop-down. When the console is launched, the device can be directly accessed.
- Manual Login: When the console is launched, manually log onto each device.
Note: Private keys are mandatory for SSH keypair-based authentication.
- Click Launch. The browser console appears in a new tab.
- Provide the credentials in the browser console.
The target remote device should now be connected enabling activities to be performed on the device.
Disconnecting browser consoles
After activities have been performed on the console, disconnect from the session.
To disconnect a browser console:
- Press the Ctrl+Alt+Shift keystroke combination to display the Clipboard window.
- From the username drop-down menu, click Disconnect.
The session is disconnected.