If I start a policy based repair task for patching lets say at 10 PM and assume that policy sync interval is 30 minutes for all the devices I am targeting using this repair task.
At 10:40 PM I realized that I don't want to patch, so I right click the task and cancel it, when I canceled the task almost all or some devices started running vulscan, of course after vulscan is finished they are going to be patched (repaired).
So my questions is are they not going to patch, since I cancel the task? or they are going to be patched since by the time I canceled the task most of the devices already received the policy (sync the policy).
If they are going to patch then how can we stop them from doing so, do we need to manually login to all the devices those received the policy and kill the vulscan process on it? is it going to stop them, I am sure Yes.
Cannot we somehow remotely kill the vulscan process on those devices instantly without login to each of them, to be specific these devices are communicating with LANDesk Core server through CSA (management gateway).
Of course we can deliver the batch script using distribution to kill the vulscan process but that's going to take 30 minutes (my policy sync interval), by that time all will be partially or completely patched depending on the no. of patches they require.
Please let me know your ideas / insights / working knowledge on this.