/build/static/layout/Breadcrumb_cap_w.png
08/22/2018 627 views
With Windows 10 we are finding many instances where Microsoft is making our life difficult. One big area is with patches, once they are installed the systems want to reboot immediately which causes a bit of problem. How does Kace handle this part of patching? We have about 50 of our 650 systems that could be in use 24/7.... we really would like the option to prompt the users to reboot when convenient. what are our options and what is recommended?
0 Comments   [ + ] Show comments

Comments


All Answers

4
Patching has three job types:
Detect:  Looks for missing patches and reports them to the appliance.  
Deploy:  Installs as many known missing patches as possible before a reboot is required, then stops.  Has the option to reboot.
Detect and Deploy:  Detects, Deploys, and reboots in a cycle until all patches are installed.

In Deploy, and Detect and Deploy, the reboot options are No Reboot, Prompt User, and Force Reboot.  With No Reboot, the user will have to reboot on their own.  Prompting the user gives them the option to reboot now or delay it by a given number of minutes.  They can only delay it a given number of times before it forces the reboot, but you could set it to 99 to make this unlikely.

If you're really concerned about reboots, I would suggest separate jobs for detecting and deploying, with the Completion Message in the Deploy job telling them to reboot when possible, and no forced reboot.

You may just need to play with it on a test computer to see what works best for your environment.
Answered 08/22/2018 by: ondrar
Fourth Degree Brown Belt