Users managing macOS devices within ControlUp reported an issue where script execution events only displayed “script started” and “script completed” messages without showing which script was run or its output. This behavior was a departure from prior functionality, where script details and outputs were visible. Windows devices did not exhibit this problem, and macOS scripts continued to generate output as expected. The concern arose when verifying the actual execution of scripts on macOS devices became necessary, but the ControlUp console failed to surface detailed script information.
Further investigation revealed that ControlUp versions 2.17 and 2.18 for macOS, as well as the Windows version, should include script details in raw event data accessible either through developer browser tools or the ControlUp API endpoint at https://api.controlup.io/reference/get-system-events. However, in the normal device view within ControlUp, the description field showing script details was missing or blank, even though the event index properly contained the script output information. This suggested a user interface issue rather than a complete loss of the event data.
The root cause appeared to be tied to the macOS 2.18 release state. The 2.18 build available was a special release candidate (RC) version, not yet generally available (GA), and it contained fixes targeting this exact problem. Users running this 2.18 RC version (including builds like 2.18.301.5B9E7EB35 and RC9) reported that the issue was resolved in those builds, with script details properly displayed alongside event logs. ControlUp staff offered to enable this release candidate on affected tenants to restore full visibility of macOS script execution events.
In summary, the lack of script detail visibility on macOS devices in ControlUp event views was a recognized bug in releases prior to 2.18. The problem was fixed in the 2.18 RC macOS agent builds, which restored proper logging and display of script names and outputs. Users encountering this should verify their macOS agent version and upgrade to the 2.18 RC or later when it becomes generally available. Meanwhile, script event data can still be queried directly via the ControlUp API or found in event indices, offering a workaround until the UI fully reflects the script details. For more information on monitoring system events and interacting with the ControlUp API, consult the official documentation at https://docs.controlup.com/ and https://api.controlup.io/reference/get-system-events.
Read the entire ‘Troubleshooting Missing macOS Script Details in ControlUp Event Logs and Resolution via 2.18 RC Agent’ thread below:
Is there anyone with macOS devices that can see if they are seeing the same
MacOS device events it just shows script started and script completed but it’s not showing what script run or the output of the script
Only notice it today as I was asked to check if the script run on a device
Windows is fine
The macOS scripts do have an output and it was working before I could see the output of the script
I have a few – looking to see if we have any scripts for them and will update you.
TY
I didn’t have any custom ones but I imported one from the script library that should return data (and did by uploading it to the index it was supposed to). No details under the description field in CU4D view.
2.18 appears to resolve that.
2.17 should show events though.
macOS 2.17, 2,18 and Windows should show the associated script in the raw event data though. Which you can see in the browser tools or via api.controlup.io/reference/get-system-events
2.18 is only a Special build for macOS is not GA yet
here is a macOS device that is on 2.18 and still no details what script started
I think this is fixed in latest Mac OS 2.18 RC build
Cc
is that 2.18.301.5B9E7EB35
same – on 2.18 – in the device view, description is missing. event index shows description properly
Hey guys! This exact problem is also fixed in the last version of RC9 of 2.18
I’ll ask support to enable this RC on your tenant as well
Awesome, Thanks
Continue reading and comment on the thread ‘Troubleshooting Missing macOS Script Details in ControlUp Event Logs and Resolution via 2.18 RC Agent’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp Scripts & Triggers
