Appearance
Scripts and Agent Updates
WebWorkstationScripts and agent updates can change an endpoint. Use an approved script whenever possible, confirm the target organization and endpoints, and review the result before considering the task complete.
Run a script on an endpoint
- Open the endpoint and select Scripts.
- Choose an approved script or the authorized ad-hoc option available to your role.
- Review the target endpoint and any parameters before starting the script.
- Monitor the execution status and output in the endpoint detail view.
A live script is intended for an online endpoint. If the endpoint disconnects while a command is being sent, ZynoRMM may report a failure instead of resending it automatically; repeating an uncertain command could run it twice.
Manage the script library
RMM managers manage saved scripts from ZynoRMM > Settings > Scripts. Keep descriptions and categories meaningful, restrict access to scripts that can make broad changes, and retire scripts that are no longer approved.
Script output, paths, commands, and parameters can contain sensitive information. Follow your organization's audit and data-handling practices when reviewing or sharing execution details.
Queue an agent update
Managers use ZynoRMM > Settings > Upgrades to review and queue agent upgrades. The update workflow uses signed update packages and tracks each eligible endpoint separately.
A release does not become deployable to your organization's agents until an authorized technician has reviewed and approved it. The vendor cannot push an agent update to your endpoints directly.
When reviewing an upgrade, distinguish these outcomes:
| Status | Meaning |
|---|---|
| Pending | The endpoint has not received the queued update yet, often because it is offline. |
| In progress | The update was sent and the endpoint may restart while it applies it. |
| Successful | The endpoint reconnected with the expected version change. |
| Failed | The update or its confirmation did not complete; review the endpoint before retrying. |
| Cancelled | The endpoint should not receive that queued update. |
| Expired | ZynoRMM did not receive a version-changing reconnect within about ten minutes, or a newer queued update replaced the tracking entry. The older installer is not forcibly stopped. |
An update can be queued for compatible endpoint operating-system families and can also apply to a newly enrolled matching endpoint while it remains active. Cancelled pending updates do not run later. A replacement update can be queued after an earlier update expires, but an installer already running on the endpoint may still need endpoint-specific follow-up.
Common issues
| Problem | What to check |
|---|---|
| A script is unavailable | Confirm that the endpoint is online when needed and that your technician role is authorized for scripts. |
| Script output is missing | Refresh the endpoint detail view, then check whether the command was interrupted. Do not immediately run a mutating script again if its outcome is uncertain. |
| An update stays pending | The endpoint may be offline or not yet eligible for the queued package. Check Last Seen, operating system, and current version. |
| An update stays in progress | Allow time for the endpoint to restart and report its new version. If no changed version is reported after about ten minutes, ZynoRMM marks the update expired and allows a newer update to be queued. Check the endpoint's installed version before retrying. |
| A cancelled update still appears in history | History is retained for operational review; cancellation prevents future pending delivery. |