How do you know if the "Pending Restart" status is triggered by a TEM action?
See the following description of troubleshooting steps to determine the cause of a Pending Restart status.
Resolving the problem
To determine whether a particular computer is in a "Pending Restart" state due to a TEM Action, take a look in the TEM Console to see which BES Support Fixlet message is reporting relevant for that machine:
- Fixlet ID 390: "Restart Needed - Triggered by a BES Action"
- Fixlet ID 391: "Restart Needed - Not Triggered by a BES Action"
The "BESPendingRestart" key is written if the action command "action requires restart" is run, or if the action command "action may require restart" is run and the "PendingFileRenameOperations" value is set when the command is run.
IBM authored content will include "action may require restart" if the action deploys any updates that may require the machine to be restarted. Thus the "BESPendingRestart" key will be set when an update is deployed through TEM, and the machine has "PendingFileRenameOperations" at the end of the action.
Fixlet ID 390 and 391 targets the "BESPendingRestart" key to determine whether or not the "Pending Restart" state was triggered by a TEM Action.
For more information about the "BESPendingRestart" and "PendingFileRenameOperations" registry values, see the following article here