Remote Control

NAVIGATION   Modules > Devices > Device List > select a device > Manage > Remote Control

PERMISSIONS  Remote Control > Use IT Glue Passwords

PERMISSIONS  Remote Control > Allow 1-Click access

Remote Control enables you to connect to any monitored Windows device, and to any monitored macOS device without locally logged-in users. Remote Control allows you to control any console or remote session. This article describes the process.

BEFORE YOU BEGIN  For this feature to be available, the managed device must be powered on and checking in to your VSA 10 platform.

NOTE  Devices hosted on Azure Cloud may experience issues with the remote control tools; this is currently not a supported environment.

Overview

VSA 10 supports two different methods by which you can connect to a target device: 

  • Console sessions:  Take control of the computer as if you were sitting in front of it.
  • Remote Desktop:  Collaborate with users currently active on the machine. While connected, you can also transfer files to and from the device.

Remote Control on Demand

Remote Control on Demand (RCoD) enables VSA 10 technicians to gain temporary remote desktop access to a computer without an agent installed, even if the user does not have Administrator-level permissions.

For details, refer to Remote Control on Demand.

Prerequisites

Before you can remotely control an endpoint, both the managed device and the computer you'll be using to control it must meet the following requirements:

  • On your local computer: Download and install the Remote Desktop Client application from Onboarding > Downloads in VSA 10.
  • NOTE  The first time you use the Remote Control Client (whether RCoD or standard Remote Control), it will automatically detect and install updates. When this happens, a message will appear stating that a new update is available and the update process has begun; the session will continue without interruption.

  • On the managed device: The device must have remote control enabled. Refer to the Enable Remote Control on a managed device section of this article for further details
  • Windows systems: Must be able to reach CRL (Certificate Revocation Lists) and OCSP (Online Certificate Status Protocol) endpoints to validate SSL/TLS certificates. These checks are performed by Windows itself and not by Kaseya.
    • When VSA Remote Control establishes a TLS/SSL connection, Windows attempts to validate the certificate chain. As part of this validation process, Windows must contact the CRL/OCSP distribution points embedded in the certificate. These URLs are almost always HTTP endpoints published by the certificate authorities (CAs).
    • If the system cannot reach the following URLs, certificate validation will fail, and the connection will fail or time out.
      • http://crl.usertrust.com/TrustedSecureCertificateAuthorityDV.crl
      • http://crt.usertrust.com/TrustedSecureCertificateAuthorityDV.crt
      • http://ocsp.usertrust.com

NOTE  Remote Desktop does not support the remote takeover of headless devices (physical devices with no attached monitor) unless the device has an active virtual monitor. In these cases, third-party video adapters or other software typically can be used to generate a virtual display, however devices that are truly headless (no GPU, no display driver, no desktop context) will not be able to accept control via Remote Desktop.

How to...