macOS custom script policy shows no output in Action HistorySolved

Hello,

Thanks for reaching out to Hexnode Connect.

This behavior depends entirely on the method used to deploy the script to your macOS device.

When scripts are deployed through a Custom Policy, they are treated as background configuration items that run according to your configured execution intervals. While the Action History will confirm whether the policy itself was successfully associated with the device, the portal does not capture or display the stdout/shell output for these scheduled, policy-based script runs.

If you need to view the shell output for troubleshooting or validation, you must run the script using a direct remote action instead:

• Navigate to Manage > Devices.
• Select your macOS device.
• Click Actions > Deployment > Execute Custom Script.

When a script is executed via this direct remote action, a new entry will appear in the device’s Action History. Once the command completes, a Show Output button will become available, allowing you to view the script’s exact results.

Best Practice: Use policy-based scripts when you need silent, recurring executions, and use the “Execute Custom Script” remote action when you need immediate execution with visible output.

I hope this clarifies where to find your script logs! Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM