Update download not proceeding to the Download phase on Monterey 12.3.1 when run from Jamf **intel mac** about super HOT 7 CLOSED

Very interesting.

First, by skipping the LaunchDaemon, you are going to cause problems for the Jamf agent. Specifically, if it takes a long time for the super workflow, during that time the Jamf agent will be hung waiting for super to complete. What if the download does take over an hour, or worse, what if the user doesn't make a dialog selection for many hours? In either case, super will wait indefinitely and thus also the Jamf agent will hang and not perform any other management.

Second, the LanchDaemon literally just restarts super via the super-starter script, so it is very strange that there is any difference at all between that restart run of super vs manually via Terminal. Are you sure it's not just that the first run of softwareupdate hung, but the second run on the same system worked?

In any case, I'll run some more tests to see if I can replicate the issue.

from super.

@Macjutsu Thank you for the quick reply. Trust me I went through your script and understand the reason for LaunchDaemon. I was skipping for testing point of view only to pin point the issue. We have this issue on few devices we are testing (a laptop ,VM) I am currently testing on VM, so for every test, I can revert back to the same state where I never triggered the Softwareupdate.

also to rule out when the script was ran from Jamf with out LaunchDaemon its working fine so the first run of softwareupdate is not causing that issue, its only causing the issue when run from the LaunchDaemon.

I will do some more testing on a clean VM with out Jamf and our customizations to rule out if anything that we added causing this issue.

Thank you so much again.

from super.

I also use VMs for testing, and I can confirm that for both Intel and Apple Silicon, softwareupdate --download --all on macOS 12 is hanging, but only when run via super and via the LaunchDaemon.

This is exceptionally weird because it works fine via MDM command, or on older OSes, or when running super directly from Terminal.

from super.

More evidence... https://developer.apple.com/forums/thread/701096

Looks like it's related to the download notifications, which I would prefer to hide anyhow as they would likely collide with IBM Notifier and jamfHelper.

from super.

Thank you for testing and confirming. Thinking and researching about other workarounds and what others are doing.

from super.

I'm testing one right now! I will share once the workaround is confirmed.

from super.

Confirmed workaround on both Intel and Apple silicon. Thanks for finding this one!
https://github.com/Macjutsu/super/blob/main/CHANGELOG.md#111

from super.