After done the patching activity in TEM the server status are showing pending restart.
after done the several reboot still the server status are showing pending restart only for along time also the action was not expired, not stopped by anyone still the action is in open status.
Turns out the issue is with Hytrust, which has its own registry key related to Pending Restart. We’ve reached out to both HCL and Hytrust support. Hytrust states the registry key must remain. Anyone have experience with Hytrust.
Alan, if you don’t know what is causing the pending restart state and you just want BigFix to ignore this , is there a wild card setting? Would this cause issues of some sort?
With the setting _BESClient_ActionManager_PendingRestartExclusions=:; all entries in the Microsoft registry key HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations are ignored because every entry is a path containing a colon. Using this colon followed by semicolon value, this is a wildcard approach that some customers have used with this client setting.