ayaRemote Documentation

Troubleshooting

Resolve installation, agent connectivity, and remote-access issues.

The device does not appear in the panel

  1. Verify that ayaServices is running in Windows Services.
  2. Confirm that the computer can reach the ayaRemote API address.
  3. Make sure the installer belongs to the correct organization.
  4. Restart the service and wait a few minutes.
  5. Clear panel filters and check whether deleted records are included.

The agent appears offline

  • Confirm that the computer is powered on and connected to the network.
  • Check the ayaServices service.
  • Ensure that a firewall or proxy is not blocking the API.
  • Verify that the system clock is correct.

Inventory is out of date

Full inventory refreshes at scheduled intervals. Restarting the agent can trigger its initial connection flow. Review service logs if the problem continues.

Remote connection does not open

  • Verify that the agent is online.
  • Confirm that ayaDesk is installed and running on the target.
  • Check that the organization has an active Pro license.
  • Verify the user's remote-access permission.
  • Allow the browser to open the ayaDesk link.

A remote command remains pending

Application removal, power actions, and package deployment commands are received while the agent is online. An offline device may leave the command pending until the agent reconnects.

Preparing a support request

Include the company name, computer name, time of the issue, and visible error message. Never send passwords, recovery keys, or API keys.

On this page