Kevin M. White

Also looking back further in this thread... your original issue was related to the API call failing... which is not directly related to what `super` does if it's going to...

Please try the latest release of `super` as it may resolve this issue: https://github.com/Macjutsu/super/releases/tag/v4.1.0-beta1

Good ideas here. During the maintenance window would you want to force the update/restart if someone was logged into the system? I ask because if there was a habitually logged...

Thanks for this! I look forward to implementing this in v4.0.

This is partially implemented via the new scheduled installation options in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 It would be entirely too complicated to have multiple simultaneous workflows... instead you can override your default workflow...

Are your users required to change their local passwords on a regular basis? As for information... example super.logs showing password failures is where you should start.

According to that log, you are correct that `super` asked for auth and then four days later the computer was restarted. In between that time `super` didn't do anything with...

Thanks for your thorough investigation. So the goal is to download the update in the background without authentication before bothering the user to restart. To be clear, `softwareupdate` is designed...

Significant testing went into the design of `super`, and it was determined that the empty password method (for downloads) was the most reliable. This download process is reliable for thousands...

Though I have not had time to confirm this behavior... it would break many `super` workflows and require significant changes. Many `super` users leverage MDM authentication or no saved authentication...