Regarding the Patching Schedule, Reboot Options
Regarding the Patching Schedule Reboot Options, I was hoping to see an option that is between “Force Reboot” and “Prompt User”. What I was looking for was “If there is a user logged on, then prompt user” and “If there is no one logged on Force Reboot”.
We have a few hundred machines (student and faculty/staff) that get patched every night. I want to make sure that the machines get patched (and may need a reboot) and not wait till someone uses the machine to reboot, so forced reboot is great. But, then again, I don’t want a student working on his thesis to lose his work as he stepped away from the computer.
Rob Seamon commented
If the "Automatically Reboot When no one is logged in" problem with the system account being counted as a logged in user has been fixed in newer versions can this be closed out now?
Otherwise the admin would have to set the timeouts and tries to small enough numbers so that if just a system user is logged in overnight that it will be rebooted by morning.
Jon DeMersseman commented
The feedback below and the votes should rightly be combined with the request entitled "Additional end-user options for patch installs." They both cover the same feature in different words. If they were combined, the combined entry would be the second most request feature with 638 votes.
Tom Napier commented
There should be a scheduling option to install patches on device shutdown. When the workstation is powered on again, the verify action would be performed.
Joseph Belanger commented
I see this is still under review with 109 votes, but not implemented. Why can't the Prompt user also have the option to keep prompting the user to reboot, but not actually reboot until the user is ready?
Pam Kelly commented
You can run a shutdown script and WOl Script on all computers to bypass the auto reboot when no one is logged in feature. And if you set up your replication share not to run during hours users are on the computer so it does automatically reboot when the user logs in.
Jim Veigl commented
Also add force log off, so if a user is logged in it will log them out. We have lots of users that just lock their machine then leave. When they come in the next morning, log in, they have to go through all the reboots.
Maybe this shouldn't be closed - have recently discovered that the "Automatically Reboot When no one is logged in" option that has been implemented doesn't actually work! When trying it on our machines it doesn't make any difference (it still waits in the background until the 30 minute timeout message that we have setup finishes, which is what happens if someone is logged on).
After querying this with Kace, they say that the reason the option doesn't work properly is because the System user is counted as a logged in user, hence there is always someone logged in.
Jon Hall commented
This has been implemented in v5.4.70402 and should probably be closed as such.
Also, even if a user clicks on update..there is no clear indication that the machine will restart when it finishes patching. Some users have been "surprised" after clicking the "ok" button since it allows users to continue working but then when Kace finishes it suddenly shuts everything down without any additional warning and restarts. It would be nice if it would prompt them again to save any open documents before the restart.
Yes, we have this issue with users working on documents and get distracted by something else (student comes into the office to see a professor...next thing you know the machine is rebooting without saving documents/webpages, etc.). This is not very good for employee morale.
Jeff Brown commented
I agree, this is an excellent idea that I would like to see implemented.
That's a great idea. This is also a big issue during our patch pushes.
matt vogt commented
Agreed. This is available in other management applications.
the easiest thing to do is just check for the existence of explorer.exe on windows machines. we've used this verification in other kbox scripts before we reboot the machine.
We really need this as well with our 600+ machines. This is especially true when users ignore the reboot message and no more patches will be applied until the computer eventually gets rebooted. This should be a very easy feature to implement but will be a very powerful tool once in use.