Skip to main content

Inspect and troubleshoot a system

You can check a system's state, installed apps, processes and logs from the Systems screen without connecting to it, and without using any session time.

You can check a system's state, installed apps, processes and logs from the Systems screen without connecting to it, and without using any session time.

Before you start

Make sure you have the following:

  • The system is online, with a green dot on the Systems screen.

  • Admin > Account Settings > Automation Enabled is on. Inspect runs as automation.

  • For Processes and Open windows, someone is signed in to the system.

Inspecting a system

⋮ > Inspect reads the state of a system without opening a session. It has four views: System info, Installed apps, Processes and Open windows, each in a dialog with a refresh button.

The System info dialog, showing hostname, OS, session state, uptime, locale and timezone, displays and available shells

System info shows Hostname, OS, Session state, Logged-in user, Uptime, Locale / timezone, Displays, Available shells and Script languages. Check Session state first: logged_out means nobody is signed in, and the actions that need a desktop session will not work.

Installed apps lists each application's Name, where it was found (Source: start-menu or app-paths), and the Program path.

The Processes dialog, listing PID, name, CPU, memory, user and state for each process

Processes lists PID, Name, CPU %, Mem (MB), User and State, busiest first. Open windows lists the windows on the signed-in desktop, or No open windows.

Reading the server log

⋮ > Get logs shows the HyperView Server log from the system. Choose the time range at the top right (Last 30 minutes by default), and use the refresh button to fetch newer lines.

⋮ > Set log level changes how much the server writes: TRACE, DEBUG, INFO, WARN, ERROR or FATAL. Raise it to reproduce an issue, then set it back.

Troubleshooting

  • This action is not permitted by the system's automation policy. Inspect and the other actions that reach into a system run as automation, and stop working when automation is switched off for the account. Turn on Admin > Account Settings > Automation Enabled and click Retry. If it is already on, check the capability policy that applies. See Create and use capability policies.

  • No interactive user is logged in on the system — this action requires a logged-in session. Processes, Open windows, Transfer files and Send command run inside a signed-in desktop session. Use Connect to sign in to the system, then click Retry. System info > Session state tells you in advance.

    Admin > Account Settings, with Automation Enabled switched on

Related articles

Did this answer your question?