Every week I create an action for the ‘restart needed - triggered by a BES action’ fixlet. I start it Friday mornings at 8:00AM client local time with a 24 hour timer and automatic execution at the end of the timer. I have a few users that when they leave for the day they shut down their machine (leaving the restart action in a snooze state). When they bring it back up Monday morning, they work for a few hours and then get hit with the restart action that executes immediately. The underlying issue is that the restart required is not clearing after a shutdown, and the user gets hit anyway.
Is this a bug, or is there a setting I’m missing in the action setup?
I have seen a similar problem, I have installed a patch using TEM, and the action reported Pending Restart. I then rebooted the server manually and the action still stays as Pending Restart, and the Restart Needed triggered by a BES action fixlet is still relevant.
I schedule patching of 300 servers each weekend, and run a separate restart action within TEM at the end of our change window. I need to know whether any servers have failed to reboot so run a webreport against the group of servers that were patched, showing any server that has a restart needed fixlet relevant.
This works quite well, but there are often false positives for servers which have been manually rebooted outside of TEM, and the guys who get called out to investigate don’t like that.