Evaluating Stopped Action

Hello team,

An action that was ran as a policy last 10/22 was stopped last 11/02. However, one of the machines still received the action on the 17th and did a reboot on 11/22. Could the issue be here due to the client machine’s slow processing of the action? Could it be that although it did receive the action last 10/22, it was only by Nov17th that it was able to receive the action and have it executed?

Is there a way to find out which machines are still processing the action? Maybe by debug logging?

Debug logging will help but it is a large task to do that on all machines.
Better way is to look for the Action .fxf file on the machines (use an analysis to do that) and then you will know how many (if any) still thinks that action is valid.
If the processing of actions is so long then the customer needs to look at what they are doing and how as that should not be something that takes so long!
Run the client usage profiler and better still use this link to setup a review of all clients :

http://www-01.ibm.com/support/docview.wss?uid=swg21669200

Dave L.