Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
The Remote Session feature in LogicMonitor provides a secure way to remotely access and operate on devices from within your LogicMonitor portal. Remote sessions are enabled via the use of Apache Guacamole, a clientless remote desktop gateway that requires no plugins or client software.
The remote session protocols available for establishing a communication stream between your account and the Collector monitoring your device are RDP, SSH, VNC, Telnet, and HTTP/S. The protocol must be configured for the device endpoint in order to be able to establish a remote session connection. Remote sessions take place via a secure SSL connection where supported by the protocol (Telnet is not encrypted and for HTTP/S you have the option to use SSL/HTTPS or just HTTP).
Note: The maximum duration for a remote session is 60 minutes. After 60 minutes, whether you are currently interacting with the remote device or not, the session will time out.
To initiate a remote session:
Any protocol can be used if properly configured on the device, but typically RDP is used for Windows devices and SSH is for non-Windows/Linux devices.
Note: Collector version 28.600 or a higher numbered version is required to use VNC, Telnet, and HTTP/S. If a lower numbered Collector version is in use, these protocol selections will be disabled and a message to that effect will be displayed upon mouse-over.
Note: You must log into the device within three minutes of initiating the remote session or the session will time out.
Note: LogicMonitor does NOT currently support SSH key authentication or Network Level Authentication on Windows.
Note: Some platforms are not supported by the Apache Guacamole clipboard copy-and-paste feature, as discussed in the Apache Guacamole Frequently Asked Questions.
LogicMonitor supports several Remote Session protocol properties that you can use to override default connection behavior.
For more information on adding/updating properties for a resource, see Resource and Instance Properties.
Remote sessions do not change the underlying authentication and access control of the device operating system, but they do allow access to the device in situations where it may not otherwise be possible. For this reason, LogicMonitor has several controls in place that serve to limit access to the Remote Session feature on a global or more granular basis:
Please note the following requirements/limitations:
Note: While not possible with some redirects, if they are known the path can be added as the value for the remotesession.http.rootpath property to connect to the redirect page directly.
In This Article