Remote commands
Run vetted presets or ad-hoc scripts inside a guest through the Verlocx agent, with full output in the audit log.
How it works
Remote commands run a script inside a guest without RDP, SSH keys or a network path into the VM. The command travels over the Verlocx agent's own connection, runs in the guest and the output comes back to the browser. Find it on the VM's Management tab.
Two permission tiers
| Tier | Permission | Use |
|---|---|---|
| Presets | vm.remote.exec | Allow-listed, vetted scripts such as flush DNS, restart a service or collect system info. Safe to hand to 1st-level support. |
| Ad-hoc scripts | vm.remote.exec.arbitrary | Any script, run as SYSTEM in the guest |
- PowerShell and cmd are supported, with a configurable timeout.
- Both tiers are also available through the REST API with the same permission checks.
Treat vm.remote.exec.arbitrary like local administrator rights on every VM the holder can reach. The preset tier exists so support staff don't need it.
Scheduled tasks
The Management tab also lists the guest's own scheduled tasks (Windows Task Scheduler or cron), read through the agent, with search, filter and sort.
Audit
- Every run records who ran what, on which VM, the exit code and the complete output in the VM's Activity tab.
- An offline agent (the command never ran) is reported differently from a script that ran and exited with an error.
Features on this page
- Remote command presets
- Ad-hoc scripts
- Guest scheduled tasks
- Remote commands over the API
More in Virtual machinesAll topics
Create a VMThe seven-step New VM wizard, how names map to VMIDs, placement, and what happens after Create.Power actionsStart, shutdown, reboot, hard stop, suspend and resume, each with its own permission, for one VM or many.The VM page and consoleThe Virtual Machines list, a VM's tabs, and the browser console (noVNC, SSH and RDP).