On some workstations, patches are staged and ready to deploy but the user does not deploy them and they do not deploy automatically after the timeout period? Is there a way to start the deployment from the workstation on these computers?
Our Windows patches are set to "detect, stage and on-demand deploy". I'm finding that some users are not deploying patches and the "Automatically deploy after x time" setting isn't triggering the deployment either.
Is there a way to trigger the deployment remotely via the KACE console, something similar to using the 'runkbot' command for inventory?
So you dont deploy? I would think you'd need to set up a deploy schedule to require your users to restart. Most users in my experience will not do a restart until forced.
We do a daily detect and then schedule the deployments. We give users the install notification as well as restart notification.
This is interesting, I never paid much attention to the stage option. Was just looking at the kace info on this and there is an interesting note
Detect and Stage: Scans for compatible patches, and downloads the applicable files to the agent device for later deployment.
Detect, Stage and On-demand Deploy: Scans for compatible patches, and downloads the applicable files to the agent device for later deployment pending user initiation.
It is important to note that whenever a Patch Action does both a Detect pass and something else (as is the case with Detect and Deploy and Detect and Rollback), the action is repeated cyclically until the Detection process finds no further patches to deploy or rollback. This may result in multiple Reboot Actions for a single scheduled run.
Ive had an issue with servers/workstations where if multiple patches are needed and one requires a restart first then I need to schedule another install. Wondering if I use a detect with deploy rather than just a detect if that means the devices will restart however many times is needed to complete.
Sorry to go off subject here but this is interesting.
open a SR with KACE support. I replicated it and were not able to replicate this. Probably there is something badly setup or you ran into a misled feature, I did not see.