-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended way to implement patch days? #190
Comments
I'm considering a small redesign of how we use super. I think I will create a single policy with a trigger, then use policies to trigger super for different conditions, such as self service, once a week, etc. If you're using Jamf, I am using a 3 day deferral period and I only allow the policy to run on Tuesday, Wednesday, and Thursday. This way no one is triggered and discover they have to update when they boot up their machine on Monday. You can create a user-side policy limitation to only launch on the desired weekday (assuming it's always a Tuesday or similar). Set the policy frequency to once a week at check in. |
This is partially implemented via the new scheduled installation options in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 Stay tuned... |
Hi!
We are using SUPER in combination with an MDM system (not JAMF, but similar in function) and using configuration profiles.
A question regarding (recurring) patch days: We would like to have pending updates being announced on a certain weekday only. If there are any updates, users should get a four-days window to apply updates and restart (if necessary). After performing any updates, SUPER should again mute until the next patch day. Currently, I am doing this by manually adjusting the „WorkflowZeroDateManual“ parameter each week in the global config profile for all devices.
I am sure there is a better way doing this — and I am not sure if this parameter is even the best handle ...
I would be happy to get a few ideas how this could be implemented best.
Kind regards,
Ron.
The text was updated successfully, but these errors were encountered: