This was implemented only for windows updates.... Can we get it for Dell driver updates?

we'll need to be able to set limits on how long users can delay too

what version number and what is the ETA?

This is the most requested feature from our executives and employees. This would solve a lot of the issues of patching during sales meetings and board meetings, etc.

Yes please let's bump this again! We need this feature!

Well, let's bump it again here in 2020.

Here's one possible approach:
Add a couple of fields to the Patch Schedule: "Allow users to initiate?" and "Labels for Self Initiation"

Then expose the flagged patch schedules in the user UI. If the agent is online, they get an "Initiate" button for the patch schedule.

This would be a great feature. We'd like to set up a "self-service patching" option in our user UI so users can launch a scheduled patching session (detect & deploy against a certain set of patches marked with a Smart Label) whenever is most convenient for them.

Still reviewing in 2019? Numerous votes and comments from 2017. Where is the actual action?
Waist of time really

This will be very useful for our org too, we have only laptops.

This would be perfect for laptop users who aren't necessarily on the work network during patching hours. It would give them the chance to have their machines update over the VPN when they aren't using them instead of being interrupted during after-hours work or having to wait for the machine to update and reboot during work hours.

I would really like to see this added as well. +3 votes.

+3 for me! This would really help us

Allowing user to initiate the patch schedule or allowing us to initiate a path schedule OnDemand via a script would be very helpful. We are a global and mobile community that demands users have more control.

This would be a massive improvement for us, and greatly appreciated. Is there any update on the review, or an ETA?

Another one that if i had more votes, I would use all 10 of them.
On demand Patching is required for patching after an image. We should have the ability to kick off patching immediately after imaging has been completed via a script, similar to Runkbot.exe 4 0. Current work around is to have a patching schedule to run every 1-2hrs, which works ok but takes some time to complete and if alot of patches are missing, patching can restart detection and never truly complete in time.

Also, with the patch on demand, I would like it so that we don't need it to be in a schedule to initiate a patch on demand, or if a schedule is needed, then make it so that the alert window that usually came up would be just a notification icon such that they would be able to open the notification icon to initiate the install -- kind of like how SCCM has a notification icon that allows the user to open and then say they want to install the patch.

Really wish this would happen. I've had so many users hit snooze on the initial message then when they're finished with their task ask wonder how they can do the updates now before they leave for a meeting and we have to say there's nothing we can do besides wait for the install prompt to pop up again. We can either make the OK/Snooze time super annoying, or tell users we can't help them, and neither are good options.

Another vote for this. Combined with:

https://kace.uservoice.com/forums/82699-k1000/suggestions/2558401-additional-end-user-options-for-patch-installs

...it seems like there's decent demand for this.

It'd be great if the patch prompt, once snoozed, went to an icon in the system tray a user could go back to, click, and start the patch process.

Agree. Also would add the end user needs a way to start patching if snoozed. We have 90% laptop and they only are in during business hours. That means patching during the day... yay! They can snooze for a couple of hours at a time but they can never start when they actually have time so it passes into the next day or another snooze. Lots of complaints. So, my votes count as representative of 700+ users :)

Yes we have sysadmins that would rather install their own patches on servers from WSUS and reboot them then let KACE do it