Had this issue using webui patch policy which ended up not being a problem. But now I am curious if there is a simple way to stop a scheduled action after the client has already downloaded content and is just waiting to run.
If you stop the action itself before the client runs it AND the client gets the update that the action has been stopped, then the client should not end up running it.
The key is “the client gets the update that the action has been stopped” depends upon UDP notifications from the parent relay, or command polling, or gather interval, or persistent connections. If the client doesn’t get UDP notifications from it’s parent relay, then it could be 6 hours or more until it learns that the action has been stopped unless command polling is enabled.
Thank you, sir! I’ll have to check out command polling.
1 Like
See here:
- https://github.com/jgstew/bigfix-content/blob/master/fixlet/clientsettings/Set%20__BESClient_Comm_CommandPollEnable_%20to%20_1_%20-%20Universal.bes
- https://github.com/jgstew/bigfix-content/blob/master/fixlet/clientsettings/Set%20__BESClient_Comm_CommandPollIntervalSeconds_%20to%20_4000_%20-%20Universal.bes