This suggestion seems like a very easy change that would help us greatly. I doubt anybody would be unhappy about a change like this, but I would be curious to see if there is any argument against it.
Our policy is to give a group of our servers "sanity" reboots after our monthly patching, regardless of whether it is required by the patches.
In addition, I have seen more than a few patches that leave the machine wanting to reboot and Kaseya didn't seem to notice.
If the "reboot" button on the Patch Status screen was available at all times and add a column denoting whether a reboot is required at that time.
Some form validation would be required to ensure that you don't reboot a server that is still patching, but that should be minor.
In my feeble opinion, this would make Kaseya a more powerful tool, while giving the operator more control.
I'm sure I'm going to get flamed now, so have at me! heh
Copyright © 2012 Kaseya International Limited. All rights reserved. Kaseya and the Kaseya k-bug logo are among the trademarks or registered trademarks owned by or licensed to Kaseya International Limited. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners.