Opening a remote Console on an Agent
Use the Remote Console functionality to open a remote Console on an online Agent. This is useful, for example, if a user phones you about a problem and you want to start a remote session on the user's computer to find the cause of this problem.
- The Agent must be online.
- The Agent must be running Microsoft Windows 8.1, Windows 10, or Windows Server 2016 or later.
- Your administrative role must at least have Read permissions to the Agent.
- Microsoft Terminal Services Client must be installed on the computer that runs the Console.
- The Agent and the Console must be able to access the same Dispatcher.
To open a remote Console, right-click the relevant Agent and click Remote Console. This sets up a temporary tunnel between the Console and the Agent via a Dispatcher. Both the Agent and the Console will initiate an outgoing IP connection to the Dispatcher, after which Ivanti Automation will start an RDP-session to set up the remote Console.
- Consider adding additional firewall rules to disallow incoming RDP-traffic on the Agent. In this situation, only Ivanti Automation will be allowed to use Remote Consoles. This allows you to rely on the Audit Trail and to enforce compliancy.
- The Audit Trail reflects the duration of the Remote Console session.
- RDP takes care of encrypting the data that is sent.