Troubleshooting VSA 10 Agent deployment issues

Agent deployment failure

If the VSA 10 Agent deployment fails, check the following:

  • Can you ping the remote device from the probe?
  • Is the device marked as Probe in the same subnet as the device on which you are planning to install the VSA 10 Agent (target device)?

    • NOTE  If the target device and the probe are on different subnets, then installation will fail. The probe and the target device should be in the same subnet.

  • Check if the admin share on the remote device is accessible. Run this command from the elevated Terminal window and enter the valid credentials: \\ip-address\admin$
  • Check whether the .NET Framework version 4.0 or higher is installed on the remote device.
  • Ensure you are using the correct Domain Administrator credentials (username and password).

If the issue persists, enable the diagnostic logging on the agent (probe) from Settings > Diagnostics in the VSA 10 Agent, then send the deploy command once again and check for errors in the trace.log file, which is located in the VSA 10 installation directory. If you can't resolve the issue, send the trace.log file to VSA 10 Support. Refer to Kaseya Helpdesk.

Unable to add probe

If you are unable to add a probe because all systems are marked as read-only, you may need to change the device access setting to Full Access. Refer to Managing user account device access.