Feature request: uber aggressive mode

[flammable]

(pun intended 😛)

Would it be possible to have Nudge be even more aggressive if we're past X number of days? In my org, the vast majority of users patch when nudged, but I've got a few holdouts. It's been just over two weeks since our last deadline passed, and I can see in MunkiReport's app usage module that Nudge has activated for some users many times (like, 400, 600, and even 1300). The average is not nearly that high.

I considered swapping out the LaunchAgent for those users - I'm using the default, which is 30 minutes. However, I don't want to do that for the entire fleet, since almost everyone else actually patches when nudged. I was hoping for a way to make Nudge harder to ignore, but only for the problematic users.

Maybe a second, more frequent, LaunchAgent that only has an effect when the deadline has passed a user configurable amount of days?

Thanks for considering this!

[erikng]

I don't think the launch agent approach is the right one as after the cutoff deadline, nudge should always be in memory as the close buttons go away. My initial thought would say to update the elapsedRefreshCycle to something very aggressive, like 61 seconds.

But perhaps there could be additional userExperience options here

• lock the nudge window to the forefront for x amount of time - Lock Screen for x seconds upon initial load/refresh #135
• lock the mouse and/or keyboard events for x amount of time (if there's even an API for this)
• ignore the acceptableApps key and just minimize everything
• attempt to safely close applications
• lock the screen and require them to re-authenticate

This is really all I can come up with and would need others to chime in.

[flammable]

Thanks! I really like the idea of changing elapsedRefreshCycle - having the UI refresh very frequently was where I was going with the LaunchAgent, but I see now how that wouldn't work. Ignoring acceptableApps is also a good one.

I love the idea of locking the screen and keyboard/mouse, but we might want to avoid anything that makes it harder for the user to actually update the machine. I don't think I can get away with quitting apps, even if users are unlikely to lose data. 😂

Let me think about this some more. I'll post to the Slack channel to see if anyone has more ideas!

[erikng]

@flammable do you think with the new full screen blur option that this can be closed? Or do you have any more ideas?

[stefaniccc]

^ +1

[flammable]

#316 and 3af0d7a will make a huge difference for us. If we wanted to go farther with this, I liked the ideas you mentioned earlier, but I think these two features are probably enough for my needs.

Thank you so much - both for Nudge, and for considering this!