Yes, beyond only using a reboot after deploying patches, Shavlik Protect does have Power Management features.
You can read more about how these work in the help document:
These are only in the advanced version of the product so if you don't have access currently but would like to use these features I'd suggest contacting our sales team to get it added in.
To answer your second question, you can use a bit of a workaround to get Protect to initiate a reboot on all the machines if you include the patch type filter 'custom actions' in your patch scanning template. The custom action patch is a dummy patch that will always show missing and cause a deployment to go out to all machines within the machine group that you scan, and if your deployment template is set to always reboot - then all machines will be deployed and get a reboot even if no real patches are missing.
I hope this helps. Let me know if you have any further questions.
Thank you. This seems to be what I need. Do I have to define what a custom action is? If so, where do I do that?
You can enable the 'custom action' item in your scans by checking the box for it when you edit/create a custom scan template. See this help document for more info:
Then just use that scan template when you intend to reboot all systems scanned.