Remote Control log files

Remote Control log files are often necessary when trying to troubleshoot any issues encountered when trying to connect to remote devices using VSA 10. Often, logs are needed from both the device being connected from (the source) and the device being connected to (the destination).

If you are having issues with Remote Control and need to engage support, it is recommended that you gather the below items: 

  1. A detailed description of the issue with screenshots of the behavior, and any related errors.
  2. Steps to reproduce the issue (along with a short screen recording, if possible).
  3. A screenshot of the Administration > Server Admin > Overview page.
  4. The number of managed endpoints that are affected.
  5. Operating system details of the affected devices (both the source and destination devices).
  6. The version of the Remote Control application on the source machine.
  7. Collect the Remote Control logs per the following scenarios(whichever is applicable) and store the logs in two separate folders, one for the source and one for the destination device.
  1. On the source Windows device, open the Start menu and type PowerShell.
  2. Right-click the PowerShell option and select Run as Administrator from the menu.
  3. Run this PowerShell command to enable the logging of the VSA X Remote Control desktop application:

    Set-ItemProperty -Path 'HKCU:\Software\Kaseya\VSA X\Remote Desktop' -Name LogLevel -Value "DEBUG" -Type String

    NOTE  Step 3 only needs to be performed on the source Windows device.

  4. In VSA 10, navigate to Configuration > Settings > General and make sure that Enable agent diagnostic logging on device card is checked.


  5. To enable diagnostic logging at the device level, in Devices > Device List, navigate to the source Windows device, and click Diagnostic Loggingunder Manage.

  6. Click Enable under Actions.

  7. In the popup that appears, set how long you want to turn on the logging for (up to 72 hours) and click Enable Diagnostic Logging.

    NOTE  Enabling logging for an extended period of time can cause performance issues on devices. Only enable it for as long as it is needed to reproduce the issue and gather logs.

  8. Repeat steps 5-7 to enable logging for the destination Windows machine.
  9. With diagnostic logging now enabled for both the source and destination machines, reproduce the issue. Take screenshots and/or screen recordings where able.
  10. Wait for 2-3 minutes to allow the error logs to append in the diagnostic files.
  11. Download the logs from the source and destination machines. To do this, for each device, click Diagnostic Logging, and then click Download Logs. Ensure that the logs are labeled to indicate which is from the source machine and which is from the destination machine.


  12. Copy the %appdata%\VSA X Remote Control\remotecontrolclient.log file from the source machine.


  1. On the source Windows device, open the Start menu and type PowerShell.
  2. Right-click the PowerShell option and select Run as Administrator from the menu.
  3. Run this PowerShell command to enable the logging of the VSA X Remote Control desktop application:

    Set-ItemProperty -Path 'HKCU:\Software\Kaseya\VSA X\Remote Desktop' -Name LogLevel -Value "DEBUG" -Type String

  4. In VSA 10, navigate to Configuration > Settings > General and make sure that Enable agent diagnostic logging on device card is checked.


  5. To enable diagnostic logging at the device level, in Devices > Device List, navigate to the source Windows device, and click Diagnostic Logging under Manage.

  6. Click Enable under Actions.

  7. In the popup that appears, set how long you want to turn on the logging for (up to 72 hours) and click Enable Diagnostic Logging.

    NOTE  Enabling logging for an extended period of time can cause performance issues on devices. Only enable it for as long as it is needed to reproduce the issue and gather logs.

  8. Reproduce the issue. Take screenshots and/or screen recordings where able.
  9. Wait for 2-3 minutes to allow the error logs to append in the diagnostic files.
  10. On the destination macOS machine, navigate to the Console application (Finder > Applications > Utilities > Console), and download the system.log and remotecontrolagent.log from Log Reports.
  11. Additionally, download the crash reports related to VSA if any. These can be found at Finder > Applications > Utilities > Console > Crash Reports.
  12. Download the logs from the source and destination machines. To do this, for each device, click Diagnostic Logging, and then click Download Logs. Ensure that the logs are labeled to indicate which is from the source machine and which is from the destination machine.


  13. Copy the %appdata%\VSA X Remote Control\remotecontrolclient.log file from the source Windows machine.
  1. On the source macOS machine, open the VSA X Remote Control app, and in the app menu, ensure Enable Debug Mode is checked.

  2. In VSA 10, navigate to Configuration > Settings > General and make sure that Enable agent diagnostic logging on device card is checked.



  3. To enable diagnostic logging, in Devices > Device List, navigate to the destination Windows OS device, and click Diagnostic Logging under Manage.

  4. Click Enable under Actions.

  5. In the popup that appears, set how long you want to turn on the logging for (up to 72 hours) and click Enable Diagnostic Logging.

    NOTE  Enabling logging for an extended period of time can cause performance issues on devices. Only enable it for as long as it is needed to reproduce the issue and gather logs.

  6. Reproduce the issue. Take screenshots and/or screen recordings where able.
  7. Wait for 2-3 minutes to allow the error logs to append in the diagnostic files.
  8. On the source macOS machine, open the VSA X Remote Control app, and in the app menu, click Diagnostic Report to create a log archive on the desktop.


  9. Download the logs from the source and destination machines. To do this, for each device, click Diagnostic Logging, and then click Download Logs. Ensure that the logs are labeled to indicate which is from the source machine and which is from the destination machine.

  1. On the source macOS machine, open the VSA X Remote Control app, and in the app menu, ensure Enable Debug Mode is checked.

  2. Reproduce the issue. Take screenshots and/or screen recordings where able.
  3. Wait for 2-3 minutes to allow the error logs to append in the diagnostic files.
  4. On the source macOS machine, open the VSA X Remote Control app, and in the app menu, click Diagnostic Report to create a log archive on the desktop.

  5. On the destination macOS machine, navigate to the Console application (Finder > Applications > Utilities > Console), and download the system.log and remotecontrolagent.log from Log Reports.
  6. Additionally, download the crash reports related to VSA, if present. These can be found at Finder > Applications > Utilities > Console > Crash Reports.