Kevin M. White
Kevin M. White
As you are using Jamf Pro... have you consulted with the documentation? https://github.com/Macjutsu/super/wiki/Jamf-Pro-Deployment#jamf-pro-policy
Closing as this is not an issue with `super`.
Please try the latest release of `super` as it may resolve this issue: https://github.com/Macjutsu/super/releases/tag/v4.1.0-beta1
There are many updates in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 that may resolve this behavior. Please try it out.
Unless you can provide some evidence of failure... like log excerpts... there isn't anything I can do to help with this issue.
There are many updates in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 that may resolve this behavior. Please try it out.
This is partially implemented via the new scheduled installation options in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 Stay tuned...
So eventually in `super` there will be a concept of "scheduling", as opposed to just deferring until a deadline. I think this will provide a more logical framework for having...
This is "effectively" implemented via the new `--workflow-reset-super-after-completion` option 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 with...
As a reminder... `super` is asking the system `softwareupdate` service to download... if it can't download... the only thing `super` can do is try again later... you need to troubleshoot...